Turn off all Microsoft Lync Server 2010, Group Chat Channel Servers and Lookup Servers, but leave the Compliance Server running.

Manually verify that all compliance data has been processed by doing the following:

• Ensure that data processing and purging is complete. The Compliance Server processes data at a conversation interval that you configure during installation. Additionally, it purges data every 15 minutes. Give the Compliance Server sufficient time to perform both of these tasks, based on your installation options.
  
  
• On the Compliance Server, open the Message Queuing management console. Verify that the Queue Messages folder of Private Queues for ocs_groupchat is empty. The queue is empty when no more output is being created and all messages have been processed.
  
  
• On each Channel Server, open the Message Queuing management console. The Queue Messages folder of the remote Outgoing Queues for the currently active Compliance Server should be empty. These queues are identified with the label DIRECT=OS:compliance-server-fqdn\private$\ocs_groupchat.
  
  
• After the data is processed and purged, inspect the database. The table tblComplianceData should contain only data from the most recent conversation interval. All data from prior conversation intervals should have been purged.
  
  
• Verify that the data from the most recent conversation interval was successfully processed by inspecting the compliance XML output files. The output file that has the latest time stamp should correspond to the data from the most recent conversation interval in tblComplianceData.
  
  

Turn off the Compliance Server.

Clean up the compliance database by doing the following:

• Back up the compliance data tables in the database: tblComplianceData, tblComplianceParticipant, and tblLastComplianceID.
  
  
• Delete all rows from tblComplianceData, tblComplianceParticipant, and tblLastComplianceID.
  
  

Disable the active Compliance Server by masking its serverType value in the Microsoft Lync Server 2010, Group Chat database by doing the following:

• In the Microsoft Lync 2010 Group Chat database, find the row in tblServerIdentity that has a serverType value of 4 and a serverAddress value that corresponds to the fully qualified domain name (FQDN) of the server you want to disable. Because only one Compliance Server can be active in a pool, there must never be more than one row with a serverType value of 4.
  
  
• Update this row, giving it a new serverType value of 104. The specific value that is used here is not important, as long as it is easily recognizable. Choosing a number ending with a 4 will help identify the unused rows in the tblServerIdentity table.