Topic Last Modified: 2011-05-10
This topic summarizes all of the phases and steps for migrating from Microsoft Office Communicator 2007 R2 to Microsoft Lync Server 2010.
Phase 1: Plan Your Migration
from Office Communications Server 2007 R2
Before you begin the migration process, you need to be aware of and plan for special considerations involved with several aspects of migration.
Phase 1 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Prepare for user migration |
Consider identifying a few users to be test users and a group of users to be in the pilot pool. |
|
|
Plan for migrating Archiving and Monitoring Servers |
Lync Server 2010 Archiving and Monitoring Servers cannot collect data from the legacy deployment, and legacy Archiving and Monitoring Servers cannot collect data from the Lync Server 2010 deployment. If you want archiving and monitoring functionality during the coexistence phase of migration, you need to consider several issues. |
|
|
Plan for administering servers after migration |
During the coexistence phase of migration, you need to use the administrative tools that correspond to the server version you want to manage. |
|
|
Plan for migrating multiple pools and sites |
Lync Server 2010 supports multi-site and multi-pool deployments. Migrating multiple pools from the legacy deployment requires some special considerations. |
Phase 2: Prepare for
Migration
Before you begin migration, you must perform several preparatory tasks to ready your environment for migration.
Phase 2 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Apply Office Communicator 2007 R2 updates |
Apply the Office Communicator 2007 R2 updates that are required for migration to Lync Server 2010. |
|
|
Run Best Practices Analyzer |
Run the Best Practices Analyzer to determine whether your legacy deployment is configured according to Microsoft best practices. |
|
|
Back up systems and data |
Perform a full system backup and document your existing system, including an inventory of user accounts. |
|
|
Configure clients for migration |
Configure clients on the existing system in preparation for migration. |
Phase 3: Deploy Lync Server 2010
Pilot Pool
Deploy a pilot pool that reflects your Lync Server architecture plans. You will merge topology information and configuration settings from your existing deployment into this pilot pool.
Phase 3 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Determine the pilot pool architecture |
Review the reference topology that is used for this document. The steps described in this document are based on the reference topology. Your steps may vary depending on your Lync Server deployment. |
|
|
Deploy the pilot pool |
Deploy a pilot pool that includes the same features and workloads that are in your legacy deployment. If you want to continue archiving and monitoring throughout migration, include these features in the pilot deployment. |
|
|
Verify pool coexistence |
After you deploy the pilot pool and before you begin to migrate to Lync Server, view pool information to verify that the legacy pool and pilot pool coexist. |
Phase 4: Merge Topologies
You merge your legacy pool with your Lync Server 2010 pilot pool by first merging topology information and then importing legacy policies and configuration settings.
Phase 4 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Install Windows Management Instrumentation (WMI) Backward Compatibility Package |
Install the WMI Backward Compatibility Package as a prerequisite to running the Topology Builder Merge wizard. |
|
|
Merge topologies by using Topology Builder |
Run the Topology Builder Merge wizard to merge your legacy topology information with your Lync Server topology. |
|
|
Import policies and settings |
Run the Import-CsLegacyConfiguration cmdlet to import policies, voice routes, dial plans, Communicator Web Access URLs, and dial-in access numbers to Lync Server, and then verify that all the policies were imported. |
|
|
Verify topology information |
View the topology in Topology Builder to verify that the merge was successful. Run the Get-CsConferenceDirectory cmdlet to verify that conference directory information was imported. |
Phase 5: Configure the Pilot
Pool
Configure the pilot pool so that users can communicate between the legacy pool and pilot pool, and move some users to the pilot pool.
Phase 5 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Connect pilot pool to legacy Edge Server |
Configure Lync Server to use the federated route that is used by the legacy pool. |
|
|
Authorize connection to legacy Edge Server |
Add the Lync Server Front End Server or Standard Edition server and Director in your pilot pool to the list of servers that are authorized to connect to the legacy Edge Server. This step is required for audio/visual (A/V) conferencing to work for users who join by using the legacy Edge Server. |
Authorize Connection to Office Communications Server 2007 R2 Edge Server |
|
Connect pilot pool to legacy Mediation Server |
Configure Lync Server to use the Mediation Server that is used by the legacy pool. |
|
|
Move some users to pilot pool |
Use Lync Server 2010 Control Panel or Lync Server Management Shell to move a few users to the pilot pool as test users. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed. |
|
|
Move multiple users to pilot pool |
You can move groups of users to the Lync Server 2010 pilot pool. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed. |
Phase 6: Verify Your Pilot
Migration
After merging information and configuring the pilot pool, verify that configuration settings imported correctly and that the pilot pool functions as expected before continuing the migration process.
Phase 6 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Verify configuration settings |
Verify that the policies and settings in your legacy pool were imported to Lync Server. |
|
|
Test pilot pool functionality |
Run some functional tests with pilot users to ensure that the pilot pool functions as expected. |
Phase 7: Add Edge Server and
Director
Add an Edge Server and a Director to the pilot pool.
Phase 7 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Deploy pilot Director and Edge Servers |
Define a Director pool and an Edge pool. Install the files on the Director and Edge Servers, configure certificates, and start services, and then verify that the pilot pool and legacy pool are running correctly and that you can administer them. |
Phase 8: Move from Pilot
Deployment to Production
Finalize route configuration, move users, and migrate response groups and Exchange Unified Messaging (UM) contacts to the pilot pool.
Phase 8 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Configure federation routes and media traffic |
Transition the federation route and media traffic route from the legacy deployment to the Lync Server Edge Server and Director:
|
|
|
Verify federation and remote access for external users |
Run functional tests to verify that federation performs as expected, testing with each type of external user supported by your organization. |
|
|
Move remaining users |
Move the remaining users from the legacy pool to the pilot pool and verify their assigned conference policy. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed. |
Verify User Replication has Completed Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 R2 Migration) |
|
Migrate response groups |
Ensure that the Response Group application is installed in your pilot pool, and then move Response Group settings from the legacy pool to the Lync Server pool. Verify that all agent groups, queues, and workflows were imported to Lync Server. |
|
|
Test response groups |
Run some functional tests to verify that the imported response groups function as expected. |
|
|
Move Exchange Unified Messaging (UM) contact objects |
Migrate Auto Attendant and Subscriber Access contact objects to the Lync Server pool, and then run a script on the server running Microsoft Exchange to add them to the Exchange UM IP gateways and hunt groups. |
|
|
Verify that Exchange UM contact objects are removed from the legacy pool |
On the legacy pool, verify that no Exchange UM contact objects remain. |
Verify that all Exchange UM Contact Objects are Removed from the Legacy Pool |
Phase 9: Complete Post-Migration
Tasks
Migrate and configure additional features, remove legacy Archiving and Monitoring Servers, configure Mediation Server, and deploy Lync Server clients.
| Step | Description | Documentation |
|---|---|---|
|
Migrate dial-in access numbers |
Move the contact objects for dial-in access numbers to Lync Server. |
|
|
Enable Microsoft Exchange 2010 SP1 Outlook Web App and IM integration |
Create a trusted application pool, and add the Exchange 2010 SP1 Client Access Server (CAS) as a trusted application server. |
|
|
Migrate Address Book |
If you customized your legacy deployment for Address Book by grouping Address Book entries by organization unit (OU) or by customizing Address Book normalization rules, configure Lync Server for these customizations. If you did not customize Address Book, Address Book is migrated to Lync Server along with the rest of your topology and no other configuration is required. |
|
|
Enable remote call control |
Configure Lync Server for routing CSTA requests and configure Lync Server users for remote call control. (Installing a SIP/CSTA gateway for remote call control is a prerequisite to migration.) |
|
|
Remove legacy Archiving and Monitoring Servers |
After all users are removed from all legacy pools, Archiving and Monitoring Servers can be removed from the legacy deployment. |
|
|
Migrate Mediation Server |
After all users are moved to Lync Server, configure the Lync Server Mediation Server. You must upgrade or replace legacy gateways, configure the Lync Server Mediation Server, and change voice routes to use the new Mediation Server. |
|
|
Migrate Communicator Web Access |
Transition Communicator Web Access functionality to Microsoft Lync Web App. If you need instant messaging (IM) and presence for reach scenarios, maintain the previous version of Communicator Web Access and point it to Lync Server. If you do not need IM and presence for reach scenarios, no further configuration is required. |
|
|
Use applications built on Microsoft Unified Communications Managed API (UCMA) 2.0 Core SDK |
Lync Server 2010 works with Microsoft Unified Communications Managed API (UCMA) 3.0 Core SDK, but you can enable users homed on a Lync Server pool to use a UCMA 2.0 application homed on a legacy pool during the coexistence phase. |
Migrate Applications Built on Microsoft Unified Communications Managed API (UCMA) 2.0 Core SDK |
|
Configure trusted application servers |
If you create a new trusted application server after you merge the legacy topology with the Lync Server topology, set the next hop pool as a Lync Server pool. |
|
|
Configure the Meeting Join page |
Configure the Meeting Join page for the Lync Server clients that can be used to join a scheduled meeting. |
|
|
Deploy clients |
Configure policies for users and clients, and deploy Lync Server 2010 clients. |
Phase 10: Decommission the
Legacy Site
When everything is moved from the legacy pool, decommission the pool and servers.
Phase 10 Migration Steps
| Step | Description | Documentation |
|---|---|---|
|
Move conference directories |
Move conference directories to Lync Server. The Import-CsLegacyConferenceDirectory cmdlet run during the merge imports only information to support interoperability. Conference directories must be moved to the Lync Server pool before the legacy pool is decommissioned or dial-in conferences will no longer work. |
|
|
Decommission legacy servers and pools |
Decommission legacy pools and remove legacy servers and server roles. |
|
|
Remove BackCompat site in Topology Builder |
After all the pools are deactivated, remove the BackCompat site. |
|