Hi,

I know there are lots of posts out there explaining the various ways of upgrading the Lync 2010 client to Lync 2013 (In my case I want to include the updates for the Skype for Business Interface) but do not seem to be having any joy at all.

I would like to take advantage of the Supersedence feature however have a few queries;

-How would I add both of the clients to SCCM, as an MSI or script installer (.exe)?

-What are the recommended command line switches for whichever of the above is recommended?

I have also tried to achieve this by creating an MSP file with the OCT as I believe this is supposed to uninstall previous versions of Lync. With this I seem to be getting the below error in the AppEnforce.log;

Invalid data file "setup.exe /adminfile RemoveLync2010.msp" to execute using file association

Just wondering if anyone has any further recommendations or methods?

Regards

Leon

Hi,

I didn't think there was an MSI based version of Skype for business?

I thought it was click to run only? 

Another point is Microsoft don't support having an MSI based version of office installed along with the click to run version of skype for business.

https://support.microsoft.com/en-us/kb/2753630/en-us?wa=wsignin1.0

https://community.office365.com/en-us/f/156/t/358878?ss-src=related

I am just looking at office and skype for business for a site now but will be using click to run for each with the ODT

Regarding the MSP maybe try specifying the full path to the MSP

Try running your uninstall locally on the machine without configuration manager.

http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account

Once you get it working via a command line locally under the system account it will work fine in ConfigMgr.

• Edited by Richard.Knight 17 hours 5 minutes ago

Hi,

I didn't think there was an MSI based version of Skype for business?

I thought it was click to run only? 

Another point is Microsoft don't support having an MSI based version of office installed along with the click to run version of skype for business.

https://support.microsoft.com/en-us/kb/2753630/en-us?wa=wsignin1.0

https://community.office365.com/en-us/f/156/t/358878?ss-src=related

I am just looking at office and skype for business for a site now but will be using click to run for each with the ODT

Regarding the MSP maybe try specifying the full path to the MSP

Try running your uninstall locally on the machine without configuration manager.

http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account

Once you get it working via a command line locally under the system account it will work fine in ConfigMgr.

• Edited by Richard.Knight 17 hours 3 minutes ago

Richard,

My understanding was that the Lync 2013 client with the required update installed (at least KB2889923) provides the S4B interface. The only configuration that is not fully enabled until the servers are upgraded to Skype for Business 2015 is the full "Home user" Skype Directory Integration.

We are not using O365 within our environment for Office Installs.

Also FYI the .MSP file is located in the same folder as setup.exe I had tried it in the updates folder however this had previously failed

Regards

Leon

Richard,

Thanks for the edit, and the useful link I will give that a try.

I had been testing locally but obviously was not able to address the challenge of running under the system context.

I will also bookmark your blog - thank you!

Hi.

Thanks for the info on coming from an older version.

The blog isn't mine but no worry's. you could try referencing the MSP with %~dp0 to specify the full path.

I am not sure if this is the cause of the issue mind, just I have seen some installers wanting the full path to a file like an xml so maybe this is the same.

https://htipe.wordpress.com/2008/10/09/the-dp0-variable/

Like i said though once you have it working via command line it should work fine in ConfigMgr.

• Edited by Richard.Knight 16 hours 39 minutes ago

Hi.

Thanks for the info on coming from an older version.

The blog isn't mine but no worry's. you could try referencing the MSP with %~dp0 to specify the full path.

I am not sure if this is the cause of the issue mind, just I have seen some installers wanting the full path to a file like an xml so maybe this is the same.

https://htipe.wordpress.com/2008/10/09/the-dp0-variable/

Like i said though once you have it working via command line it should work fine in ConfigMgr.

• Edited by Richard.Knight 16 hours 36 minutes ago

Hi,

I didn't think there was an MSI based version of Skype for business?

I thought it was click to run only? 

Another point is Microsoft don't support having an MSI based version of office installed along with the click to run version of skype for business.

https://support.microsoft.com/en-us/kb/2753630/en-us?wa=wsignin1.0

https://community.office365.com/en-us/f/156/t/358878?ss-src=related

I am just looking at office and skype for business for a site now but will be using click to run for each with the ODT

Regarding the MSP maybe try specifying the full path to the MSP

Try running your uninstall locally on the machine without configuration manager.

http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account

Once you get it working via a command line locally under the system account it will work fine in ConfigMgr.

• Edited by Richard.Knight Thursday, August 20, 2015 2:45 PM

edit as what i put previously was incorrect

• Edited by Richard.Knight Saturday, August 22, 2015 2:10 PM

edit as what i put previously was incorrect

• Edited by Richard.Knight Saturday, August 22, 2015 2:10 PM

Hi.

Thanks for the info on coming from an older version.

The blog isn't mine but no worry's. you could try referencing the MSP with %~dp0 to specify the full path.

I am not sure if this is the cause of the issue mind, just I have seen some installers wanting the full path to a file like an xml so maybe this is the same.

https://htipe.wordpress.com/2008/10/09/the-dp0-variable/

Like i said though once you have it working via command line it should work fine in ConfigMgr.

• Edited by Richard.Knight Thursday, August 20, 2015 3:12 PM

Hi.

Thanks for the info on coming from an older version.

The blog isn't mine but no worry's. you could try referencing the MSP with %~dp0 to specify the full path.

I am not sure if this is the cause of the issue mind, just I have seen some installers wanting the full path to a file like an xml so maybe this is the same.

https://htipe.wordpress.com/2008/10/09/the-dp0-variable/

Like i said though once you have it working via command line it should work fine in ConfigMgr.

• Edited by Richard.Knight Thursday, August 20, 2015 3:12 PM

Richard

Have tried this morning and with the above command setup.exe /adminfile RemoveLync2010.msp I am presented with the Microsoft Lync 2013 installation window;

I have also added the full UNC path to the MSP file with the same result.

I presume this is indicating that something is incorrect with the MSP file?

• Edited by Leon1983 11 minutes ago

Richard

Have tried this morning and with the above command setup.exe /adminfile RemoveLync2010.msp I am presented with the Microsoft Lync 2013 installation window;

I have also added the full UNC path to the MSP file with the same result.

I presume this is indicating that something is incorrect with the MSP file?

• Edited by Leon1983 9 minutes ago

Richard

Have tried this morning and with the above command setup.exe /adminfile RemoveLync2010.msp I am presented with the Microsoft Lync 2013 installation window;

I have also added the full UNC path to the MSP file with the same result.

I presume this is indicating that something is incorrect with the MSP file?

• Edited by Leon1983 Friday, August 21, 2015 7:39 AM

Richard

Have tried this morning and with the above command setup.exe /adminfile RemoveLync2010.msp I am presented with the Microsoft Lync 2013 installation window;

I have also added the full UNC path to the MSP file with the same result.

I presume this is indicating that something is incorrect with the MSP file?

• Edited by Leon1983 Friday, August 21, 2015 7:39 AM

The upgrade from Lync to Skype is via a Windows Update.  No need for supersedence, https://support.microsoft.com/en-us/kb/3039779 here was the first force install of the upgrade from Lync to Skype because of a vulnerability.  I believe this has been superseded but you can follow the chain to the latest version of the Skype update.

Just to update whoever is following this thread. I am now trying another method in trying to roll out this upgrade. I have heard that there are sometimes issues trying to uninstall products using the OCT so now I will be doing this using an SCCM 2012 R2 Task sequence and will update this post accordingly

I ended up redoing mine, ditched the ODT method as it doesn't support KMS, found an issue in the OCT where it doesn't install lync and one drive. Patched the OCT recreated MSP to install office 2013 with lync and one drive. Included the 2 updates within the office installer to update lync to skype for business. Left office installation at default to remove previous versions.

It works fine, removes office 2010 and installs 2013 with skype for business perfectly. Thanks for the info you posted. Much appreciated

We use kb3054791 to convert our Lync 2013 clients to S4B.

They generally update with WSUS/ConfigMgr 2012 though.

I don't think this is exactly what your asking, but could be a different approach.

Mark

Hi, thanks for the post, but I am trying to update 2010 to S4B and not 2013...

Good to know the office 2010 - 2013 upgrade works well with the OCT, as stated I have not been able to get this to work with the Lync client only so I am going to try using a task sequence instead. The uninstall part has work already. Just need to add the Lync 2013 client with the update for install and then hopefully I should be good to go.

Would be interested as to why the OCT hasn't worked for me...

Ok so for those who are following this thread I have made further progress now. It would appear that I was receiving the above prompt when testing using the PSEXEC tool as suggested by Richard because I had the display level set to be "Full" and it should be "None" as per the below

The install is now timing out though when deploying it as a Task sequence at the S4B install stage and I will investigate now...

• Edited by Leon1983 22 hours 20 minutes ago
• Marked as answer by Leon1983 22 hours 15 minutes ago

I ended up redoing mine, ditched the ODT method as it doesn't support KMS, found an issue in the OCT where it doesn't install lync and one drive. Patched the OCT recreated MSP to install office 2013 with lync and one drive. Included the 2 updates within the office installer to update lync to skype for business. Left office installation at default to remove previous versions.

It works fine, removes office 2010 and installs 2013 with skype for business perfectly. Thanks for the info you posted. Much appreciated

I also had to upgrade the OCT due to the same issue as Richard suggested in this post as per the instructions at the top of this blog

http://blogs.technet.com/b/odsupport/archive/2014/03/11/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx

Turns out the install is now failing due to an office architecture issue;