Migrating multiple sites and pools
Topic Last Modified: 2012-09-17
Lync Server 2013 supports multi-site and multi-pool deployments. The process of migrating multiple pools from Lync Server 2010 to Lync Server 2013 requires the following considerations:
After deploying a Lync Server 2013 pilot pool, you need to define a subset of pilot users that will be moved to the Lync Server 2013 pool, and a methodology for validating the functionality of the users. For example, after moving a user to the pilot pool, verify the user’s conference policy has moved to Lync Server 2013.
After deploying an Edge Server in the pilot pool, you need to validate that external users can communicate with the Lync Server 2013 pool.
After transitioning the federated routes from Lync Server 2010 Edge Servers to the pilot Lync Server 2013 Edge Servers, you need to validate that federated users can communicate with the Lync Server 2013 pool.
After moving all the users and non-user contact objects, you need to validate that the Lync Server 2010 pool is empty.
After verifying that the Lync Server 2010 pool is empty, you can then deactivate the pool.
For details about how to deactivate the legacy Lync Server 2010 pool and servers, see Phase 8: Decommission legacy pools.