Uninstall of Lync 2010

We are in the middle of rolling out O365 Pro Plus on Win 7 and I was wondering if there was a script to
uninstall Lync 2010? I have the OffScrub10.vbs script that removes the Office 2010 suite, but Lync is not included in that suite, therefore is left on the PC once the script is complete. Is there an easy way to remove this application other than Programs and
Features?

Hi,
Here is a similar case may help you:
https://social.technet.microsoft.com/Forums/lync/en-US/69e32128-4581-4be5-9a44-b5d133e1f480/slient-unninstall-of-lync-2010-on-client-machines-script-required?forum=ocsclients
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Similar Messages

Uninstall Legacy Lync 2010 enterprise and install Lync 2013

I have a customer who has Lync 2010 enterprise and decided to install Lync 2013 but don't want migration and instead want to uninstall Lync 2010 . I would like to know in this case how to clean the active directory schema from Lync 2010 ?
and If there's anything else to consider before uninstalling Lync 2010 ? I will have to disable/remove all currently Lync enabled users but is there anything else?
I found this article, but would like to know what's the steps in sequence of removing Lync in this case?
https://social.technet.microsoft.com/wiki/contents/articles/9849.how-to-remove-lync-server-2010-from-active-directory.aspx
for example, do I have to first
1- Disable LYnc users.
2- Uninstall Lync server Application from Control panel
3- Remove Lync from Active Directory?
Would appreciate your help. thanks
thanks
Mohammed JH

Hi
Check this to Uninstall Lync 2010
http://terenceluk.blogspot.nl/2011/01/step-by-step-instructions-for.html
Check this to remove AD References
http://blog.ucmadeeasy.com/2010/11/09/lync-server-2010-active-directory-references-and-how-to-remove-them/
http://digitalbamboo.wordpress.com/2014/01/28/how-to-clean-your-server-of-old-active-directory-lync-ad-references-in-the-rtc-service-when-removing-the-last-2010-pool-fails-to-publish-in-the-lync/
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Uninstall Microsoft Lync By Using Applications in Configuration Manager

Dear,
I wants to remove Microsoft Lync 2010 by using create deployment application in SCCM 2012 and install Microsoft Lync 2013 at the same time, kindly I wants to know shall I create two packages for each one first I have to uninstall Microsoft Lync 2010 by create
new package and create another package for install Lync 2013? Kindly I need steps for doing this job.
Thanks..

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
Please refer http://social.technet.microsoft.com/Forums/en-US/configmanagerapps/thread/dc8c5dfa-eb1d-4ca6-8713-e37ba4175734
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

Uninstall Lync 2010 client, Install Lync 2013 using Group Policy/VB/MS Customisation Tool

Hi, I am using Group Policy/vb/Lync customization tools to deploy 2013 and remove 2010. The machines have Office 2010. The vb script is as below:
Dim objShell 'As Object
Dim objFSO 'As FileSystemObject
'-- SET OBJECTS
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objShell = CreateObject("WScript.Shell")
strComputerName = objShell.ExpandEnvironmentStrings("%COMPUTERNAME%")
Dim WshNetwork : Set WshNetwork = WScript.CreateObject("WScript.Network")
objShell.Run """\\xxxxxxxxx - Do not Remove\Lync Install 2013 2010\Lync 2013 Outlook 2010\setup.exe"""
I have amended the OCT with relevant settings, Lync 2013 installs but Lync 2010 does not uninstall. Here is how i have it set:
In the Office Customization Tool - Set-up - Add Installation and Run Programs,
In target - pointing to the Lync2010 exe file (on above share)
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!
Hope you can help.

Hi,
Based on your description, we can refer to the following threads for help.
Slient Unninstall of Lync 2010 on client machines script required
http://social.technet.microsoft.com/Forums/lync/en-US/69e32128-4581-4be5-9a44-b5d133e1f480/slient-unninstall-of-lync-2010-on-client-machines-script-required
Scripting a Lync 2010 client Uninstall
http://social.technet.microsoft.com/Forums/en-US/a65bd0d0-daa1-4616-8725-63f349fdde86/scripting-a-lync-2010-client-uninstall?forum=lyncconferencing
For this issue is more related to Lync, in order to get better help, we can ask the question in the following TechNet dedicated Lync forum.
Lync 2010 and OCS - Lync Clients and Devices
http://social.technet.microsoft.com/Forums/lync/en-US/home?forum=ocsclients&filter=alltypes&sort=lastpostdesc
In addition, for it also involves scripts, we can also ask for help in the following scripting forum.
The Official Scripting Guys Forum
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG&filter=alltypes&sort=lastpostdesc
Hope it helps.
Best regards,
Frank Shen

I uninstalled Lync 2010 and it still launches. How do I uninstall it?

This is a weird one I know but I need to uninstall Lync 2010 on several laptops.
My process has been to uninstall it from add/remove programs. It seems to uninstall properly. Note that I think it is a click to run version of Lync.
However, on a reboot the program is still there and will launch. It no longer has a reference in Add/remove programs.
How can I uninstall it properly?

Hi,
Please check if Lync 2010 folder is still exist, if exist please delete manually.
Please also delete information about Lync 2010 (Communicator) in Registry Editor HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE.
Please also check if Lync 2010 software set to Startup, if set please disable it.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Uninstalling CMS from Lync 2010

Now that the CMS has been migrated to our Lync 2013 FE servers, I need to remove the replica from our single Lync 2010 server using
Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn <FQDN of SQL Server> -SqlInstanceName <Name of source server>
We plan on keeping the Lync 2010 server around for a bit even though there are no users on it. I have a single Trusted App for webmail integration still attached to the Lync 2010 server which I plan to move to 2013 sometime in the future. Our
Edge is still 2010.
Question is by removing the CMS replica from the Lync 2010 server, will this interfere with operation of the Edge server? All I am doing is removing CMS replica which is something you are supposed to do after moving CMS to 2013 but I am not sure where the
Edge is currently pulling its replica data from. Since the Edge has access to all internal FE servers I assume that if its getting changes from the 2010 FE and I remove that replica, it will get changes going forward from the 2013 FE. Is there any way
to see the Lync FE replication partners so I can verify this?
Eventually, we will build out a 2013 Edge and at that time decommission the 2010 completely. Its a very simple environment. Just IM and presence. No telephony, monitoring or archiving.

You can establish a pool pairing that includes the pool hosting the Central Management store, a backup Central Management store database is set up in the backup pool,
and Central Management store services are installed in both pools. At any point in time, one of the two Central Management store databases is the active master, and the other is a standby. The content is replicated by the Backup Service from the active master
to the standby.
Lisa Zheng
TechNet Community Support

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Lync 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Lync Client 2013 not Signing in, But Lync 2010 Do Sign In

Dears,
I have a weird problem, I have installed Lync 2013 FE Server, after I finished installing it I tried to test the log in with the Lync 2013 client, it asked for authentication but everytime I enter the authentication it gives me an error of server is unavailable
now.
I've checked the DNS records, ports and certificate everything is fine, but it doesn't sign in. The weird issue here is that I tried to use a Lync 2010 client and it signed successfully with no error and within 2 seconds!!!
The only thing different in my deployment here is that I've updated the Lync to CU1 before I start the services for the first time and also before requesting and assigning the certificates.
Please do anyone has an idea of why this is happening? I will try tomorrow to uninstall Lync and its databases and start fresh without the CU1.

Hi,
Please check if the Lync 2013 uses the automatical configuration to sign in Lync seve.
Please check the Client version policy in the Lync server control panel. Maybe the client version policy block it with mistake configuration.
Have a test to install the Lync 2013 on other PC then check the issue again.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Sean Xiao
TechNet Community Support

Add Lync 2010 To Existing Office 2010 ProPlus Deployments?

Office 2010 ProPlus was deployed with Word, Excel PowerPoint and Outlook 2 years ago. We are now going to deploy Lync 2010 and need an easy way to add Lync to the existing Office installations. On new installations we will add Lync as part of
the build image.
We do not have SCCM. Is there a user-friendly way to deploy the msp update file to existing Office installations that lack Lync that does not require SCCM? I have thought of making some kind of startup script, but I don't think it will be a good
idea for that installation script to run at every reboot. We only want it to run until Lync is installed and not again.
Also, some users have already installed a stand alone version of Lync 2010 on their systems that is not part of the Office Suite. Will we need to remove that version before the version in the Office suite can be added or does the stand alone Lync installer
actually use and install the same files from the Office suite?

From memory, Lync2010, although it is an included benefit/entitlement within OFF2010ProPlus, doesn't install as part of the main suite setup.exe, there's a separate setup.exe/installer for Lync2010 ?
So, it shouldn't just be an MSPfile applied to modify ProPlus, you'll need to run the installer for Lync anyway?
You might want to create an MSPfile for the Lync installation, to get the desired installation experience+customisation.
Regardless, you should probably have a "wrapper" script, and in the script, do some kind of detection for Lync=present (maybe check the uninstall regkeys or check for presence of the exe under programfiles).
if found, then skip the installation step.
if absent, perform the installation step.
similar to this:
http://technet.microsoft.com/en-us/library/ff602181(v=office.14).aspx
There is also a separate Lync installer, for customers who don't have OfficeProPlus, and you may need to detect for that, and decide accordingly.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Finally about to decomission the Lync 2010 Edge. Small question

Getting ready to finally decommission our Lync 2010 Edge in favor of a 2013 Edge. The only reason I have kept the 2010 Edge around was because we still have a single 2010 FE server. All our users are on 2013 FE servers so the 2010 FE is just sitting there
do nothing. I thought it was best practice to remove the 2010 Edge first and then decommission the 2010 FE.
Does it really matter which server I decommission first? I can't see how but thought I would ask. I am sure there are companies that have 2013 Edge servers with a mix of 2010 and 2013 FE servers but it doesn't hurt to ask I guess.

Hi shadowtuck,
In general, you could decommission the Edge server first.
I don’t think this is a problem, all the Lync 2010 Servers are not working.
And there’s a document about
Uninstalling Microsoft Lync Server 2010 and Removing Server Roles
for your reference.
http://www.microsoft.com/en-us/download/details.aspx?id=18692
Best regards,
Eric

Decommission Lync 2010

Hi
I have just upgraded a Lync 2010 Standard system to 2013. The cms is moved to 2013 and I have uninstalled cms on the 2010 server. The users and conference data is moved to 2013. Therefore, my last step is to decommission the 2010. Before
I procedure with this in the Topology, I notice two things. 1. When I use the command Get-CsSite the old 2010 shows as register and so on. But if I use Get-CsService the new 2013 is primary and in Topology all points to new cms in site. Howe come Get-CsSite
point to 2010? The other thing is when I open up Control Panel the old and new URL is given. Does the URL disappear when 2010 removed in Topology?
Best Regard
Daniel

Hi,
The Lync Server Management Shell Get-CsSite retrieves information for all the Lync Server sites. It should show all the sites information and the pool, services. Make sure all Edge Sever and PSTN Gateway point to the new Lync Sever 2013 Pool.
During the co-existence environment, it will show both Lync Server 2010 and 2013 URL to access Lync Server Control Panel, after delete the Lync Server 2010 pool from topology, the Lync Server 2010 URL will disappear.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Lync 2010 Will Not Open Anymore

The problem is happening so far on three Windows 7 computers that used to be able to open Lync, but not anymore. Click the program icon to launch the program and the sign in box appears but Lync stalls at contacting server and signing in. A Lync message
appears, "Cannot sign in because the server is temporarily unavailable. If the problem continues, please contact your support team."
Steps taken to resolve
1) Verified the certificate hadn’t expired
2) Deleted communicator folders in both folder locations, c:\users\username\app data\local\microsoft and c:\users\username\app data\roaming\microsoft
3) Deleted the SSID folders
4) Tried the manual configuration to connect to Lync by entering the sip domain name for the internal and external server names
5) Restarted pc, and also shut down the pc.
6) Logged onto a different pc as myself and Lync 2010 opens for me. When another end-user log onto my pc, they duplicate the same issue with Lync stalling and not opening and receive the same error message.
7) Uninstalled and reinstalled Lync

Hi,
Please double check if the client trust the CA that issued the certificate on Lync server.
Please disable firewall on your issued local workstation to check if the issue caused by ports.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

CMS database move from Lync 2010 to 2013 went well but.....

Something odd when I was done. Everything went perfectly. No errors at all and went as expected. I noticed though after everything was done and I had not yet uninstalled the CMS from Lync 2010 that two services on the Lync 2010 were stopped but in an Automatic
startup state. They are the "Lync Server File Transfer Agent' and the "Lync Server Master Replicator Agent'. Thought it was odd they were both stopped. I am sure it had something to do with the CMS move and all the scripting that goes on. The rest
of the Lync services are running.
I am thinking though if they were supposed to be stopped, why not disable them. Why leave them at Automatic. I am not seeing any errors or warnings at all on the Lync 2010 or 2013 servers. Application, System and Lync Server logs are clean. Everything appears
to be OK.
Thing that concerns me though is when I run the Get-CsManagementStoreReplicationStatus on the 2013 FE, the databases all come back looking good with UpToDate = True but the last replication was last night (about 8-9 hours ago) shortly after I completed the
procedure.
I want to just uninstall the CMS on Lync 2010 which is the last step but I want to make sure everything is OK before I do. Not sure if I should start those services. I never rebooted the 2010 server after moving the CMS. Seems if I did, those services would
have tried to start. Very confused here.
Wanted to add also that I have both the above services on the 2013 FE server and they are both running. And, when I run Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus on my Lync 2013 FE, it says it is the active master and active file
transfer agent so maybe that is why the services are stopped? If so, what if I had rebooted the 2010 server. Those services would have tried to start because they are set to Automatic.
I guess the real question here is how often should the Lync servers being updating their replicas with each other. We have a very small environment right now with only a few hundred users.

This process of transferring information updates from master to replica is called replication. The replication process consists of copying information between directories from the master to the replicas, applying the changes received to the
replica and report status back to the master.
The MASTER generates the data package containing new changes to CMS and stores a copy in each to-replica directory for every replica.
The data package must be copied to all replicas. All Lync Server 2013 servers, except the Edge Server, uses the Windows file copy SMB protocol mechanism to push the data package from the CMS master to the replica.
For Edge servers, since Edge servers is not a member of domain, the file copy is performed over an HTTPS channel. The Edge Server runs a Web Service on the port specified for the ManagementServices in the topology document. The default port is 4443. Even
you Move CMS store and CMS Master service from 2010 to 2013, the replication is a logical concept so you can replicate CMS information with the help of Lync server 2013 CMS master service.
You can refer to the link below, it is for Lync server 2010 but similar for Lync server 2013:
https://blogs.technet.com/b/jenstr/archive/2010/10/13/what-is-central-management-store-cms.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Uninstall of Lync 2010

Similar Messages

Maybe you are looking for