Shut down all Group Chat Channel Servers and Lookup Servers, but leave the Compliance Server running.

Use the following steps to manually verify that all compliance data has been processed:

• Ensure that data processing and purging is complete. The Compliance Server processes data at a conversation interval that you configure during installation. In addition, it purges data every 15 minutes. Give the server adequate time to perform both of these tasks, based on your installation options.
  
  
• On the Compliance Server computer, open the Message Queuing management console. Verify that the Queue Messages folder of the Private Queue for ocs_groupchatis empty.
  
  
• On each of the Channel Server computers, 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 tblComplianceDatashould only contain 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 with the latest timestamp should correspond to the data from the most recent conversation interval in tblComplianceData.
  
  

Shut down the Compliance Server.

Use the following steps to clean up the compliance database:

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

Use the following steps to disable the active Compliance Server by masking its serverTypevalue in the Group Chat database:

• In the Group Chat database, find the row in tblServerIdentitythat has a serverTypevalue of 4 and a serverAddressvalue that corresponds to the 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 serverTypevalue of 4.
  
  
• Update this row, giving it a new serverTypevalue of 104. The specific value used here does not matter, as long as it is easily recognizable. Choosing a number ending with the digit ‘4’ will help document the purpose of the unused rows in the tblServerIdentitytable.