Topic Last Modified: 2011-05-10

This topic summarizes all of the phases and steps Front End Serverfor migrating from Microsoft Office Communicator 2007 to Microsoft Lync Server 2010.

Phase 1: Plan Your Migration from Office Communications Server 2007

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.	User Migration (Office Communications Server 2007 Migration)
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.	Migrating Archiving and Monitoring Servers (Office Communications Server 2007 Migration)
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.	Administering Servers after Migration (Office Communications Server 2007 Migration)
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.	Migrating Multiple Pools (Office Communications Server 2007 Migration)

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 updates	Apply the Office Communicator 2007 updates that are required for migration to Lync Server 2010.	Apply Office Communications Server 2007 Updates
Run Best Practices Analyzer	Run the Best Practices Analyzer to determine whether your legacy deployment is configured according to Microsoft best practices.	Run Best Practices Analyzer (Office Communications Server 2007 Migration)
Back up systems and data	Perform a full system backup and document your existing system, including an inventory of user accounts.	Back Up Systems and Data (Office Communications Server 2007 Migration)
Configure clients for migration	Configure clients on the existing system in preparation for migration.	Configure Clients for Migration (Office Communications Server 2007 Migration)

Phase 3: Deploy Lync Server 2010 Pilot Stack

Deploy a pilot stack that reflects your Lync Server architecture plans. You will merge topology information and configuration settings from your existing deployment into this pilot stack. The stack refers to deploying Lync Server 2010 Edge Server and Director concurrently with the Lync Server pool.

Phase 3 Migration Steps

Step	Description	Documentation
Determine the pilot stack 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.	Lync Server 2010 Pilot Stack Architecture
Deploy the pilot stack	Deploy a pilot stack 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.	Deploy Lync Server 2010 Pilot Stack
Verify stack coexistence	After you deploy the pilot stack and before you begin to migrate to Lync Server, view pool information to verify that the legacy pool and pilot pool coexist.	Verify Pilot Stack Coexistence with Legacy Pool (Office Communications Server 2007)

Phase 4: Merge Topologies

You merge your legacy deployment with your Lync Server 2010 pilot deployment 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.	Install WMI Backward Compatibility Package (Office Communications Server 2007 Migration)
Merge topologies by using Topology Builder	Run the Topology Builder Merge wizard to merge your legacy topology information with your Lync Server topology.	Merge Using Topology Builder Merge Wizard (Office Communications Server 2007 Migration)
Import policies and settings	Run the Import-CsLegacyConfiguration cmdlet to import policies, voice routes, dial plans, and Communicator Web Access URLs to Lync Server, and then verify that all the policies were imported.	Import Policies and Settings (Office Communications Server 2007)
Verify topology information	View the topology in Topology Builder to verify that the merge was successful.	Verify Topology Information (Office Communications Server 2007 Migration)
Verify configuration settings	Verify that the policies and settings in your legacy pool were imported to Lync Server.	Verify Configuration Settings (Office Communications Server 2007 Migration)

Phase 5: Configure the Pilot Stack

Configure the pilot stack 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.	Connect Pilot Stack to Legacy Edge Servers (Office Communications Server 2007)
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.	Authorize Connection to Office Communications Server 2007 Edge Server
Connect pilot pool to legacy Mediation Server	Configure Lync Server to use the Mediation Server that is used by the legacy pool.	Connect Pilot Stack to Legacy Mediation Server
Move some users to pilot deployment	Use Lync Server 2010 Control Panel or Lync Server Management Shell to move a few users to the pilot deployment as test users. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed.	Verify User Replication has Completed (Office Communications Server 2007 Migration) Move Legacy User to Pilot Stack (Office Communications Server 2007)
Move multiple users to pilot stack	You can move groups of users to the Lync Server 2010 pilot deployment. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed.	Verify User Replication has Completed (Office Communications Server 2007 Migration) Move Multiple Users (Communications Server 2007 Migration)

Phase 6: Verify Your Pilot Migration

After merging information and configuring the pilot pool, verify that configuration settings imported correctly and that the pilot deployment functions as expected before continuing the migration process.

Phase 6 Migration Steps

Step	Description	Documentation
Test pilot deployment functionality	Run some functional tests with pilot users to ensure that the pilot deployment functions as expected.	Run Functional Tests Against Workloads (Office Communications Server 2007)

Phase 7: Transition from Pilot to Production

Move remaining users, move Exchange Unified Messaging (UM) contacts, and then verify that all Exchange UM contact objects are removed from the legacy pool.

Phase 7 Migration Steps

Step	Description	Documentation
Move remaining users	Move the remaining users from the legacy pool to the pilot deployment and verify their assigned conference policy. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed.	Verify User Replication has Completed (Office Communications Server 2007 Migration) Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 Migration) Move Multiple Users (Communications Server 2007 Migration)
Move Exchange 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.	Move Exchange Unified Messaging Contact Objects (Office Communications Server 2007)
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 Office Communications Server 2007 Pool

Step

Description

Documentation

Move remaining users

Move the remaining users from the legacy pool to the pilot deployment and verify their assigned conference policy. Before using the Move-CsLegacyUser cmdlet, verify that user replication has successfully completed.

Verify User Replication has Completed (Office Communications Server 2007 Migration)

Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 Migration)

Move Multiple Users (Communications Server 2007 Migration)

Move Exchange 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.

Move Exchange Unified Messaging Contact Objects (Office Communications Server 2007)

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 Office Communications Server 2007 Pool

Phase 8: Complete Post-Migration Tasks

Migrate and configure additional features, remove legacy Archiving and Monitoring Servers, configure Mediation Server, and change federation routes and verify external user access, and deploy Lync Server clients.

Phase 8 Migration Steps

Step	Description	Documentation
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.	Enable Exchange 2010 SP1 Outlook Web App and IM Integration
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.	Migrate Address Book (Office Communications Server 2007)
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.)	Enable Remote Call Control (Office Communications Server 2007)
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.	Remove Legacy Archiving and Monitoring Servers (Office Communications Server 2007)
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 then change voice routes to use the new Mediation Server.	Migrate Mediation Server (Office Communications Server 2007 Migration)
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.	Migrate Communicator Web Access (Office Communications Server 2007)
Migrate from applications built on Microsoft Unified Communications Managed API (UCMA) 1.0 Core SDK	Lync Server 2010 works with Microsoft Unified Communications Managed API (UCMA) 3.0 Core SDK. If you use external applications built on UCMA 1.0, you can run them in an environment that includes Lync Server 2010. However, direct coexistence and migration of these applications is not supported.	Migrate Applications Built on Microsoft Unified Communications Managed API (UCMA) 2.0 Core SDK (Office Communications Server 2007)
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 Trusted application servers (Office Communications Server 2007 Migration)
Configure the Meeting Join page	Configure the Meeting Join page for the Lync Server clients that can be used to join a scheduled meeting.	Configure the Meeting Join Page (Office Communications Server 2007 Migration)
Change federation routes	Transition from the federation route of the legacy deployment to the federation route of the Lync Server Edge Server: Remove the legacy federation association from the Lync Server site. Configure the legacy Edge Server as a non-federating Edge Server. Configure certificates on the Lync Server Edge Server. Change the legacy federation route to use the Lync Server Edge Server. Update the Lync Server Edge Server federation next hop server. Enable Lync Server Edge Server federation, publish the configuration changes, and then configure the Lync Server Edge Server.	Change Federation Routes (Office Communications Server 2007 Migration)
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.	Verify Federation and Remote Access for External Users (Office Communications Server 2007 Migration)
Deploy clients	Configure policies for users and clients, and deploy Lync Server 2010 clients.	Deploy Lync Server 2010 Clients

Phase 9: Decommission the Legacy Site

When everything is moved from the legacy pool, decommission the pool and servers.

Phase 9 Migration Steps

Step	Description	Documentation
Decommission legacy servers and pools	Decommission legacy pools and remove legacy servers and server roles.	Decommissioning Servers and Pools (Office Communications Server 2007)
Remove BackCompat site in Topology Builder	After all the pools are deactivated, remove the BackCompat site.	Remove BackCompatSite (Office Communications Server 2007 Migration)