Decommissioning Legacy Lync 2010 After Migration to Lync 2013 – Part 2


In part 1 I wrote about what can be considered a guide on a number of post-migration steps to be done before starting with decommissioning of the Legacy Lync 2010 infrastructure, in this article I will be writing on the steps of removing and uninstalling of the legacy Lync 2010 servers.

Moving Conference Directories

Before you remove the Lync 2010 frontend from the Topology you must move the conference directory to the new Lync 2013 pool, actually if you tried to remove the legacy frontend and to publish the topology you will get an error that the conference directory is not moved and still hosted on the legacy Lync pool you trying to delete.

Moving Conference directory is achieved using the Get-CsConferenceDirectory

  • · First list all the conference directories in your infrastructure that is hosted on the Legacy Lync

PS C:> Get-CsConferenceDirectory | Where-Object {$_.ServiceID -match “LY2010 pool FQDN”}

  • · Now take not of their Identity which should be a Numeric value
  • · Move them using the Move-CsConferenceDirectory

PS C:> Move-CsConferenceDirectory -Identity “Numeric Value” -TargetPool “LY2013 Pool FQDN”

Some cases you get error when trying to run this command, the workaround is to close the PowerShell session and start a new one and try again.

Remove Association to the Archive& Monitoring Server

We are getting close now to finish the uninstalling process, hang in there 🙂

NOTE: Archiving & Monitoring data are not moved to Lync 2013 infrastructure, make sure to back up the data before going ahead and decommission the roles

Without removing the association to the Archive or Monitoring server (If you have them deployed) you will not be able to remove the frontend servers / pool from the topology, also don’t forget about the SQL store

Here is how:

  • · Start Lync Topology Builder
  • · Download the topology (by now you should know what you doing here 🙂

  • · Expand Lync Server >> your site >> Lync server 2010
  • · Double click type of deployment you have (Standard or Enterprise)
  • · Right click the pool name >> Select Edit Properties
  • · Scroll down and clear the box in front of “Associate Archiving server”, “Associate Monitoring Server” and “Associate Edge Pool”

  • · Click Ok
  • · Expand “Archiving Servers” >> right click the Archiving server name and select “Delete”
  • · On the “Delete Dependent Stores” click Ok
  • · Publish the Topology

Now log into the Archiving & monitoring servers, run the Lync deployment wizard, click on “Install or update Lync server system” then click on step:2 Setup or Remove Lync Server Components and this will uninstall the Lync role running on the server.

Remove Association to the Trunks & Gateways

If you have Enterprise Voice deployed and associated Trunks to the Frontend server (in case Mediation server is collocated), or to a standalone Mediation server, you must remove the associated trunks to be able to remove the server, this is allowed only or done by removing the Gateway itself which automatically removes the trunk (Hope that you planned that ahead 🙂 )

  • · While still on the Topology Builder expand “shared Components”
  • · Expand PSTN Gateways

  • · Delete the gateways associated with your Lync 2010 Frontend servers/pool or mediation server
  • · Publish the topology

Removing Association to SQL Store, and deleting the Lync 2010 servers / Pool

Deleting the Lync 2010 Servers

This parts applies to most of Lync 2010 roles as in Frontends, Standalone Mediations, Directors, Edge, Archiving and Monitoring servers, once you removed the association to other components in the topology of those roles,

You can delete them from the topology, I’ll write about Frontend Standard edition, but this applies to most of them.

  • · Start the topology builder
  • · Expand the topology >> your site >> Lync 2010 Server >> standard edition
  • · Right click the frontend pool and select “Delete”

Don’t publish the topology yet 🙂 go to next part

Delete the associated SQL Store

  • · While still on the topology builder and after deleting the Standard edition Frontend server
  • · Go to Shared Components >> SQL Server Stores
  • · Right click the SQL Store associated with Lync 2010 Pool
  • · Select Delete
  • · Publish the Topology

Uninstalling the Lync 2010 Server role (Frontends, standalone mediation & Directors)

Wait a minute for the replication to take place, if you don’t want to wait from a PowerShell run the following cmdlet

Then check if all replication status reporting “up to date” using the following cmdlet

Now you can log into the Lync 2010 Frontend server and start the uninstallation process same way you did with Archiving & Monitoring stated above.

With Mediation Server, Director you do the same, remove them from the topology, publish the topology, wait for replication then login to the servers and start the installation wizard to remove the roles.

Uninstalling Edge 2010 Server

in case of Edge server, you need to remove it from the topology, publish it and make sure that the replication reached the Lync 2010 Edge server, if not then export the configuration as a zip file using following cmdlet

  • · Copy the file to the Lync 2010 Edge server
  • · Import it using the import-CsConfiguration cmdlet

  • · Start the Lync 2010 Deployment wizard on the machine, and do as before with Frontend and Archiving server to uninstall the roles.

Congratulation your infrastructure is now running on Lync 2013 server only, welcome to the club 🙂

Author: Lyncdude

A Senior Microsoft Unified Communications Consultant with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. Worked Closely with Microsoft Dubai for 3 years designing , building and supporting Exchange and Lync Infrastructures. A Microsoft Certified ITP in Lync, Exchange and also attended Microsoft Partner Primer Filed Support Engineer T1 Training for Microsoft Lync 2010.

4 thoughts on “Decommissioning Legacy Lync 2010 After Migration to Lync 2013 – Part 2”

  1. Fantastic walkthrough – appreciated it very much!

    I was left with Empty Lync2010 Folders beside my active Lync 2013 folder. is this normal?
    Anyway you know to clean that last little bit?

    1. Hi Dave, as long as you removed your Lync 2010 infrastructure and followed my steps and have no problems shown in the Lync 2013 infrastructure (Event viewer, user experiences ) i’ll say go ahead and copy the folder somewhere and delete the original, if any problems were reported move it back in 🙂

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s