Decommissioning a Deployment

 

Topic Last Modified: 2013-09-11

Some situations require that you remove all server roles, Standard Edition servers, and Front End pools at all sites, and that you roll back the environment. For example, in a disaster recovery scenario, a hardware failure scenario, an upgrade scenario, or other situation where you must completely remove the servers, pools, and settings.

Tip

Before you decommission a deployment, do the following:

• Provide users with sufficient notice to ensure that they can plan for the down time.

• Deactivate the server roles on the weekend or holiday, or during other off-peak hours.

• Disable monitoring in System Center Operations Manager or third-party monitoring system

Recommended Order of Operations

The following checklist defines the phases of the decommissioning process in the order in which we strongly recommend that you perform the tasks:

√	Phase	Documentation
	Phase 1: Disable all users that are enabled for Lync Server.	Search for Lync Server 2010 Users AND Enable or Disable Users for Lync Server 2010 OR Get-CsUser AND Disable-CsUser
	Phase 2: Delete all conference directories.	Move a Conference Directory and Dial-in Conferencing Contact Objects
	Phase 3: Remove Voice Components as needed: Delete all Contact objects enabled for Lync Server Enterprise Voice features by using Lync Server Management Shell. If the Lync Server 2010 response groups have been migrated to a Lync Server 2013 deployment, do not remove the contact objects of the migrated response groups. If response groups have been migrated, skip the document “Remove Response Group Service Workflow Contact Objects” that is listed in the “Documentation” column. For more information, see https://technet.microsoft.com/en-us/library/jj204854.aspx. Remove Enterprise Voice routes by using Lync Server Control Panel. Remove all Call Park orbits by using Lync Server Control Panel. Remove all tables for Enterprise Voice unassigned phone numbers. Back up the Location Information service database. Back up the custom music on hold file. Delete Enterprise Voice routes. Reassign the public switched telephone network (PSTN) gateway.	Remove Exchange Unified Messaging (UM) Contact Objects Remove Response Group Service Workflow Contact Objects Remove Dial-in Conferencing Access Number Contact Objects Remove Common Area Phone and Analog Device Contact Objects Remove Call Park Service Orbits Delete an Unassigned Number Range Back Up the Location Information Service Database Back Up the Custom Music On-Hold File Remove Enterprise Voice Routes Reassign the PSTN Gateway
	Phase 4: Confirm that the Front End Server or pool is empty.	Confirm that a Front End Pool or Front End Server is Vacant
	Phase 5: Run the Remove Deployment Wizard in Topology Builder.	Run the Remove Deployment Wizard
	Phase 6: Publish the finalized topology by using Lync Server Management Shell.	Publish the Topology from the Remove Deployment Wizard
	Phase 7: Verify that replication is complete by using Lync Server Management Shell.	Verify Replication of Changes to Central Management Store, Servers, and Services
	Phase 8: Remove local component files on each server by using the Deployment Wizard.	Remove Lync Server 2010 Files from Servers (Except Central Management Server)
	Phase 9: Publish a final, empty topology using the FinalizeUninstall parameter of Publish-CsTopology cmdlet.	Publish Final Topology and Remove Last Front End
	Phase 10: Remove all SQL Server databases, instances, and the Central Management store by using Lync Server Management Shell.	Remove all SQL Server Instances, Databases, and the Central Management Store
	Phase 11: (Optional) Remove any prerequisite software from the Front End Server.	Remove Prerequisite Software From Lync Server
	Phase 12: (Optional) Remove any local groups that remain on the Front End Server.	Remove Local Groups
	Phase 13: (Optional) Check for existence of the Active Directory Domain Services (AD DS) service control point (SCP) for the Central Management store, and if it is still defined, remove it by using Lync Server Management Shell. Note This is only necessary if you are decommissioning the deployment to install a new deployment in which the Central Management store is hosted by a different SQL Server-based Back End Server.	Remove the Central Management Store Service Control Point in Active Directory Domain Services (Optional) Remove-CsConfigurationStoreLocation
	Phase 14: (Optional) Unprep the domain.	Using Cmdlets to Reverse Domain Preparation
	Phase 15: (Optional) Unprep the forest.	Using Cmdlets to Reverse Forest Preparation