Answered by:
Uninstall Lync 2010 client and install Lync 2013

Question
-
I need to create an application to uninstall Lync 2010 and install Lync 2013 client. The Lync 2013 client by design does not uninstall the 2010 client. What is the best way to do this in SCCM 2012 SP1?Wednesday, February 6, 2013 4:51 PM
Answers
-
What about creating an application for Lync 2010 (incl install / uninstall command line) and use supersedence (so that Lync 2013 supersedes Lync 2010)?
Torsten Meringer | http://www.mssccmfaq.de
- Proposed as answer by Nicholas JonesMicrosoft employee Sunday, February 24, 2013 12:08 PM
- Marked as answer by Robert Marshall - MVPMVP Thursday, March 7, 2013 8:04 PM
Wednesday, February 6, 2013 4:56 PM
All replies
-
What about creating an application for Lync 2010 (incl install / uninstall command line) and use supersedence (so that Lync 2013 supersedes Lync 2010)?
Torsten Meringer | http://www.mssccmfaq.de
- Proposed as answer by Nicholas JonesMicrosoft employee Sunday, February 24, 2013 12:08 PM
- Marked as answer by Robert Marshall - MVPMVP Thursday, March 7, 2013 8:04 PM
Wednesday, February 6, 2013 4:56 PM -
That's a good idea. Never used that before. Question: Does it uninstall before installing the new software or vise versa?Wednesday, February 6, 2013 5:12 PM
-
That can be configured when creating the supersedence relationship.
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, February 6, 2013 5:32 PM -
So I gave it a try and the uninstall is not working.. The file is being copied to the client but give me this error message in the logs:
Prepared working directory: C:\Windows\ccmcache\d AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Prepared command line: "C:\Windows\ccmcache\d\LyncSetup.exe" /uninstall AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Executing Command line: "C:\Windows\ccmcache\d\LyncSetup.exe" /uninstall with user context AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Working directory C:\Windows\ccmcache\d AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Post install behavior is NoAction AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Waiting for process 3732 to finish. Timeout = 120 minutes. AppEnforce 2/6/2013 9:36:33 AM 4412 (0x113C)
Process 3732 terminated with exitcode: 1 AppEnforce 2/6/2013 9:36:34 AM 4412 (0x113C)
Looking for exit code 1 in exit codes table... AppEnforce 2/6/2013 9:36:34 AM 4412 (0x113C)
Unmatched exit code (1) is considered an execution failure. AppEnforce 2/6/2013 9:36:34 AM 4412 (0x113C)If I run the command manually from the cmd it works fine and uninstalls the software. Is there a piece I am missing?
Wednesday, February 6, 2013 5:41 PM -
Hi,
Have you configured the uninstall to run with administrative priviliges? It could the reason that it tries to uninstall in user context.
Regards,
Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Wednesday, February 6, 2013 6:41 PM -
I'm also interested in doing this as well. Did you find a solution for this? Thanks!Friday, February 22, 2013 3:22 PM
-
-
sounds good. was the supersedence set up easy once you have the 2013 package ready?Friday, February 22, 2013 7:04 PM
-
on a side note have you deployed Lync 2010 Mobility server?Friday, February 22, 2013 7:05 PM
-
That part is very easy. The pain was getting the Lync 2010 client to uninstall. :) Hard finding the correct command line that worked for me. I am not a package expert but I am getting there.Saturday, February 23, 2013 12:19 AM
-
We have had it for many months deployed on our edge server.Saturday, February 23, 2013 12:20 AM
-
that sounds great. any way I can contact you via email?Monday, February 25, 2013 9:30 PM
-
So what exactly was the final command line that worked for you?Monday, February 25, 2013 11:06 PM
-
Hi, you can create customize the Lync2013 Admin file (navigate to your Microsoft Office setup folder, etc //Lync2013/setup.exe /admin) and create an msp file. Create a package and deploy it.
There is a portion in the MSP file where you can set what Office does after installation and before installation. This will uninstall Lync 2010 during the Office 2013 installation
1. Copy the Lync 2010 setup file (LyncSetupVolume.exe) into the same folder as your Lync 2013, create a folder called Lync2010.
2. Run eg: //Lync2013/setup.exe /admin to create a new msp file (you can also use an existing msp file if available)
3. In the MSP file , go to Setup>Add installations and run programs> add a command line (after installation, do not choose before installation) , etc //Lync2013/Lync2010/LyncSetupVolume.exe /silent /uninstall
4. Save the file.
5. Create a package with Lync 2013 //Lync2013/setup.exe /adminfile automated.msp
6. Deploy it.
You can customize the Office2013 Admin file to your liking as well. To test it out, may I suggest to deploy it through SCCM to a test machine as Available first and see if it works before deploying it as Required.Tuesday, February 26, 2013 2:33 PM -
I'm struggling with a command line myself for a uninstall for Lync 2010. Can you tell me what worked for you?
This is painful!!! ThankS!!!
Thursday, August 1, 2013 7:20 PM -
I tried this and it didn't work for me.. I wonder why..Thursday, August 1, 2013 7:21 PM
-
I'm using SCCM 2007 tho. but, don't think it matters.Thursday, August 1, 2013 7:21 PM
-
Create a software task sequence in SCCM. Kill the Lync 2010 EXE, then uninstall Lync 2010 with the original Lync 2010 installer. Then install Lync 2013.
--Example Task Seq--
taskkill /f /im communicator.exe /t (command line)
taskkill /f /im ucmapi.exe /t (command line)
Uninstall Lync 2010 (Software Install)
Install Lync 2013 (Software Install)---End Task Seq----
Example of Lync 2010 uninstall command used with the Lync 2010 msi installer file.
msiexec.exe /uninstall Lync.msi /qn
Example of Lync 2013 install command used with the Lync 2013 installer you downloaded.
setup.exe /adminfile Lync32bit.MSP (Use MSP file you create by using the command setup.exe /admin)
Modify as needed. This is not meant to be exact file names for all situations. Your install may vary.
Thursday, August 8, 2013 7:20 PM -
Create SCCM package as a script
Batch file
-----------------------------------------------------
MsiExec.exe /QN /NORESTART /X{81BE0B17-563B-45D4-B198-5721E6C665CD}
setup.exe /adminfile Lync32bit.MSP
exit
Thursday, August 22, 2013 6:23 PM -
Hi, I am a bit stuck with this. I am planning on uninstalling Lync 2010 and installing 2013.(I am using a vb+GPO script on logon). Lync 2013 installs, but Lync 2010 does not.
In the Office Customization Tool - Set-up - Add Installation and Run Programs,
In target - pointing to the Lync2010 exe file
In Arguments - /silent /uninstall
Is this correct?
Also, i would have thought that, Remove Previous Installations, it would have an option to remove Lync2010?
Anyway..pulling my hair out here!
Thanks
Tuesday, February 4, 2014 1:08 PM -
For the ones who are using ConfigMgr 2012, use APPLICATIONS instead of packages.
- Configure application for Lync 2010
- Configure application for Lync 2013
- Configure Lync 2013 application to supersede the Lync 2010
- Deploy Lync 2013
More info on deploying Lync 2013:
http://blog.naevette.com.au/2013/10/15/packaging-lync-2013-for-enterprise-deployment/
http://phyllisinit.wordpress.com/2013/03/11/how-to-upgrade-lync-2010-to-lync-2013-using-sccm2012/
- Proposed as answer by Narcoticoo Tuesday, February 4, 2014 3:08 PM
Tuesday, February 4, 2014 3:07 PM -
- Proposed as answer by 74KMS Thursday, April 10, 2014 1:35 PM
Wednesday, April 9, 2014 7:16 AM -
Hi, you can create customize the Lync2013 Admin file (navigate to your Microsoft Office setup folder, etc //Lync2013/setup.exe /admin) and create an msp file. Create a package and deploy it.
There is a portion in the MSP file where you can set what Office does after installation and before installation. This will uninstall Lync 2010 during the Office 2013 installation
1. Copy the Lync 2010 setup file (LyncSetupVolume.exe) into the same folder as your Lync 2013, create a folder called Lync2010.
2. Run eg: //Lync2013/setup.exe /admin to create a new msp file (you can also use an existing msp file if available)
3. In the MSP file , go to Setup>Add installations and run programs> add a command line (after installation, do not choose before installation) , etc //Lync2013/Lync2010/LyncSetupVolume.exe /silent /uninstall
4. Save the file.
5. Create a package with Lync 2013 //Lync2013/setup.exe /adminfile automated.msp
6. Deploy it.
You can customize the Office2013 Admin file to your liking as well. To test it out, may I suggest to deploy it through SCCM to a test machine as Available first and see if it works before deploying it as Required.This looks like it could work, but I don't understand your pathing. Are you trying to say you used a UNC path? Because all of this is going to end up in the ccmcache folder. I don't understand how you path to that folder when the folder name is going to be random.
I can't believe that MS makes the most difficult software to deploy. Out of the dozens of applications I've built the office stuff is always the biggest pain.
- Proposed as answer by Tom Mellen Tuesday, October 6, 2015 2:37 PM
- Unproposed as answer by Tom Mellen Tuesday, October 6, 2015 2:37 PM
Wednesday, November 19, 2014 1:16 AM -
Old topic but unresolved simply. Just adding my two cents to try and help for all the googlers out there. For those times when your organization has already installed Lync, and you know not from where or how, the following line will remove it:
wmic product where "name like 'Microsoft Lync 2010%%'" call uninstall /nointeractive
This will call the uninstall method that the software told the OS it uses when installed. It will work on virtually all well coded software, whether it uses installshield, MSI, WYSE, etc. The %% is a wildcard that tells the line above to uninstall anything that starts with "Microsoft Lync 2010." This command WILL uninstall EVERYTHING that matches the string, so be careful. "Microsoft Lync%%" will remove the following:
Microsoft Lync 2010
Microsoft Lync 2010 SDK
Microsoft Lync 2013
This works on Adobe Flash, Acrobat, Weatherbug, IrFranView, and a ton of other software. Microsoft project, however, failed to uninstall this way. An XML Config has to be setup for that.
Unattended, I used the following script to remove Lync 2010 in preparation for a Lync 2013 install:
taskkill /F /IM communicator.exe
taskkill /F /IM lync.exe
wmic product where "name like 'Microsoft Lync%%%%'" call uninstall /nointeractive
REM The following command aborts a restart if one is required from the previous uninstall
c:\windows\system32\shutdown /a
Tuesday, October 6, 2015 2:53 PM -
Best way I've found to uninstall Lync 2010 client is using Windows Installer and corresponding GUID:
MsiExec.exe /X{7D9109C3-58A9-4AFD-A1D3-47E7D811726E} /quiet
And you are done =)
(Found App GUID in the Registy as usuall)
Hope it helps
Thursday, December 3, 2015 4:45 PM