Migrate from OCS 2007 R2 to Lync 2010 (Part I)

Required Updates for Office Communications Server 2007 R2

Before migrating to Microsoft Lync Server 2010, apply updates to your Microsoft Office Communications Server 2007 R2 environment. Updates required are listed in following table.

Check Programs and Features in Control Panel on the computer running Office Communications Server 2007 R2 to determine whether these updates have been applied.

Office Communications Server 2007 R2 Required Updates:

Application	Update
Microsoft Office Communicator 2007 R2	July 2010 Update package
Microsoft Office Live Meeting 2007	July 2010 Update package
Microsoft Office Live Meeting Conferencing Add-In	July 2010 Update package
Office Communications Server 2007 R2	September 2010 Update package
Microsoft Office Communicator 2007 R2 Phone Edition	July 2010 Update package

Download OCS 2007 R2 BPA

Microsoft Office Communications Server 2007 R2 Best Practices Analyzer tool gathers configuration information from an Office Communications Server 2007 R2 deployment and determines whether the configuration is set according to Microsoft best practices. You can install the tool on a client computer that runs Microsoft .NET Framework 2.0, or directly on the server that runs Office Communications Server.

It is recommended that you install and run this tool on a client computer. In order for the Best Practices Analyzer to collect a full set of data, Office Communications Server 2007 R2 Administrative Tools should also be installed locally on the client computer.

Prepare End Users for Migration

This topic contains recommended client deployment steps you should take before migrating to Microsoft Lync Server 2010. Configuration changes should be made on Office Communications Server 2007 R2. It is important that you perform these steps before migrating.

To Configure Clients Prior to Migration:

1. Deploy the most recent server, client, and device updates (hotfixes) for Microsoft Office Communications Server 2007 R2 as listed in Apply Office Communications Server 2007 R2 Updates.

2. On Office Communications Server 2007 R2, use Client Version Filtering to allow only clients with the most current updates installed, as listed in Apply Office Communications Server 2007 R2 Updates to sign in.

3. On Office Communications Server 2007 R2, use Client Version Filtering to block Lync Server 2010 clients from signing in. Follow the steps described in Configuring Client Version Filtering at http://go.microsoft.com/fwlink/?LinkId=202488 to add the version filters listed in the following table. For each version filter, assign the action Block.

Lync Client	Lync User agent header	Lync Version
Lync 2010	OC	4...*
Lync Web App	CWA	4...*
Lync 2010 Phone Edition	OCPhone	4...*
Lync 2010 Attendee

Lync Server 2010 Coexistence with OCS 2007 R2 (Office Communications Server 2007 R2)

The following figure shows pilot pool reference topology used in this document. Lync Server 2010 is installed alongside with an existing Office Communications Server 2007 R2 installation. After merging the topologies, a few test users will be homed on Lync Server 2010 and then communicate with users who are homed on Office Communications Server 2007 R2 servers, which will show interoperability between users who are homed in different pools can continue to communicate and use the existing workloads and perimeter network infrastructure.

Initially, a Lync Server 2010 pool is deployed in parallel with Office Communications Server 2007 R2. External traffic and federation is done through the legacy Edge Server environment. The following table lists fully qualified domain names (FQDNs) for various server roles used in this topology and is supplied solely for reference purposes.

Lync Server Role	Office Communications Server 2007 R2 FQDN	Lync Server 2010 FQDN
Standard Edition Server	SE-R2.DOMAIN.NET	LYNC-SE.DOMAIN.NET
Edge Server	EDGE-R2.DOMAIN.NET	LYNC-EDGE.DOMAIN.NET
Director	DIR-R2.DOMAIN.NET	LYNC-DIR.DOMAIN.NET
Mediation Server	MEDSVR01.DOMAIN.NET	Collocated on LYNC-SE.DOMAIN.NET