Topic Last Modified: 2011-04-04

If you deployed Archiving Server and Monitoring Server in your Microsoft Office Communications Server 2007 R2 environment, you can deploy these servers in your Microsoft Lync Server 2010 environment after you migrate your Front End pools. If archiving and monitoring functionality are critical to your organization, however, you should add Archiving Server and Monitoring Server to your pilot pool before you migrate so that the functionality is available during the migration process.

If you want archiving and monitoring functionality during the migration and coexistence phase, keep the following considerations in mind:

• Archiving data and monitoring data are not moved to the Lync Server 2010 deployment. The data you back up prior to decommissioning the legacy environment will be your history of activity in the Office Communications Server 2007 R2 environment.
  
  
• The Office Communications Server 2007 R2 version of Archiving Server and Monitoring Server can be associated only with a Communications Server 2007 R2 Front End pool. The Lync Server 2010 version of Archiving Server and Monitoring Server can be associated only with a Lync Server Front End pool.
  
  
• If you use Microsoft System Center Operations Manager (formerly Microsoft Operations Manager) to monitor call reliability and media quality, you must use the System Center Operations Manager 2007 R2 management pack to monitor Communications Server 2007 and the Lync Server 2010 Monitoring Management Pack for System Center Operations Manager 2007 R2 to monitor Lync Server.
  
  

  Note:
  For details about the Lync Server 2010 Monitoring Management Pack for System Center Operations Manager 2007 R2, see http://go.microsoft.com/fwlink/?LinkId=214711.

• During the time that your legacy and Lync Server 2010 deployments coexist, the Office Communications Server 2007 R2 version of Archiving Server and Monitoring Server gather data for users homed on Communications Server 2007 R2 pools. The Lync Server 2010 version of Archiving Server and Monitoring Server gather data for users homed on Lync Server pools.
  
  

  Note:
  During the phase of migration when you are still using your legacy edge with the new Lync Server pilot pool, the Office Communications Server 2007 R2 version of Archiving Server continues to gather data for users homed on Communications Server 2007 R2 pools and the Lync Server 2010 version of Archiving Server gathers data for users homed on Lync Server pools.

• When you run the Import-CsLegacyConfiguration cmdlet during the migration process, the legacy archiving and monitoring policies are imported to the Lync Server Central Management store.
  
  
• When you use the Move-CsLegacyUser cmdlet to move a Communications Server 2007 R2 user to a Lync Server pool, the cmdlet assigns the Lync Server policy that is equivalent to the legacy policy.
  
  
• If you use a third-party archiving and monitoring solution in conjunction with Archiving Server and Monitoring Server, talk to your vendor about when and how you need to integrate the third-party solution with Lync Server 2010.