Ls Migrate Ocs2007 r2

Migrating from Microsoft OfficeCommunications Server 2007 R2 to MicrosoftLync Server 2010

Microsoft Lync Server 2010Published: December 2010

NON-ACTIVATEDVERSIONwww.avs4you.com

This document is provided “as-is”. Information and views expressed in this document, includingURL and other Internet Web site references, may change without notice. You bear the risk ofusing it.

Some examples depicted herein are provided for illustration only and are fictitious. No realassociation or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in anyMicrosoft product. You may copy and use this document for your internal, reference purposes.This document is confidential and proprietary to Microsoft. It is disclosed and can be used onlypursuant to a non-disclosure agreement.

Copyright © 2010 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, ActiveSync, ActiveX, Excel, Forefront, Groove, Hyper-V, InternetExplorer, Lync, MSDN, MSN, OneNote, Outlook, PowerPoint, RoundTable, SharePoint,Silverlight, SQL Server, Visio, Visual C++, Windows, Windows Media, Windows PowerShell,Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. Allother trademarks are property of their respective owners.


ContentsMigration from Office Communications Server 2007 R2 to Lync Server 2010 1Before You Begin the Migration 2Migration Process 2Migration Phases 3Planning for Client Migration 4Client Planning Steps during Migration 4Migration Considerations for Meetings 6Client Version Check 10Migrating User Settings to Lync Server 2010 12Client Interoperability 25

Phase 1: Plan Your Migration from Office Communications Server 2007 R2 29User Migration 29Administering Servers after Migration 29Migrating Multiple Sites and Pools 30

Phase 2: Prepare for Migration 31Apply Office Communications Server 2007 R2 Updates 31Run Best Practices Analyzer 32Back Up Systems and Data 32Configure Clients for Migration 32

Phase 3: Deploy Lync Server 2010 Pilot Pool 33Lync Server 2010 Pilot Pool Architecture 33Deploy Lync Server 2010 Pilot Pool 35Verify Pilot Pool Coexistence with Legacy Pool 38

Phase 4: Merge Topologies 41Install WMI Backward Compatibility Package 41Merge Using Topology Builder Merge Wizard 42Import Policies and Settings 47Verify Topology Information 49

Phase 5: Configure the Pilot Pool 52Connect Pilot Pool to Legacy Edge Servers 52Authorize Connection to Office Communications Server 2007 R2 Edge Server 54Connect Pilot Pool to Legacy Mediation Server 55Move Legacy User to Pilot Pool 57Move Multiple Users 61Verify User Replication has Completed 64

Phase 6: Verify Your Pilot Migration 65Verify Configuration Settings 65Run Functional Tests Against Workloads (optional) 70

Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool 74Deploy Pilot Director and Edge Servers 74

Phase 8: Move from Pilot Deployment into Production 81Configure Federation Routes and Media Traffic 81Verify Federation and Remote Access for External Users 90Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 R2


Migration) 91Move Multiple Users 96Migrate Response Groups 99Run Functional Tests for Response Groups 101Move Exchange Unified Messaging Contact Objects 102Verify that all Exchange UM Contact Objects are removed from the Legacy Pool 103

Phase 9: Complete Post-Migration Tasks 104Migrate Dial-in Access Numbers 104Enable Exchange 2010 SP1 Outlook Web App and IM Integration 106Migrate Address Book 108Enable Remote Call Control 110Remove Legacy Archiving and Monitoring Servers 112Migrate Mediation Server 113Configure Mediation Server 113Change Voice Routes to use the new Lync Server 2010 Mediation Server 114Transition a collocated Mediation Server to a Stand-Alone Mediation Server (optional)115

Migrate Communicator Web Access 116Repoint Communicator Web Access to Lync Server 2010 119

Migrate Applications Built on Microsoft Unified Communications Managed API (UCMA) 2.0Core SDK 120

Configure Trusted application servers 120Configure the Meeting Join Page 121Deploy Lync Server 2010 Clients 123

Phase 10: Decommission Legacy Site 123Decommissioning Servers and Pools 124Remove BackCompatSite 124

Migrate Using Lync Server 2010 Management Shell (optional) 126Define Edge Server Input File 126Create a Custom Edge Server Input File 127Run Migration Cmdlets 132


5

Migration from Office Communications Server2007 R2 to Lync Server 2010The topics in this section guide you through the process of migrating from Microsoft OfficeCommunications Server 2007 R2 to Microsoft Lync Server 2010. If you intend for your OfficeCommunications Server 2007 R2 deployment to coexist with a Lync Server 2010 deployment,this guide also includes some essential information for operating in this mixed environment.

Tip:Before you begin, watch the short video at http://go.microsoft.com/fwlink/?LinkId=206444for an overview of the steps required to migrate from Microsoft Office Communicator2007 R2 to Microsoft Lync Server 2010.

This guide provides information specific to upgrading your existing deployment. It does notexplain how to change your existing topology. This guide does not cover the implementation ofnew features. When a detailed procedure is documented elsewhere, this guide directs you to theappropriate document or document section.

Note:This document does not address configuration specific to Enterprise Voice. The LyncServer Response Group service and Dial-in conferencing are covered.

This document defines terms as specified in the following list.

migrationMoving your production deployment from a previous version of Office CommunicationsServer to Lync Server 2010.

upgradeInstalling a newer version of software on a server or client computer.

coexistenceThe temporary environment that exists during migration when some functionality has been migrated to Lync Server 2010 and other functionality still remains on a prior versionof Office Communications Server.

interoperabilityThe ability of your deployment to operate successfully during the period of coexistence.

In This Section Before You Begin the Migration

Phase 1: Plan Your Migration from Office Communications Server 2007 R2

Phase 2: Prepare for Migration

Phase 3: Deploy Lync Server 2010 Pilot Pool

Phase 4: Merge Topologies


6

Phase 5: Configure the Pilot Pool

Phase 6: Verify Your Pilot Migration

Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool

Phase 8: Move from Pilot Deployment into Production

Phase 9: Complete Post-Migration Tasks

Phase 10: Decommission Legacy Site

Migrate Using Lync Server 2010 Management Shell (optional)

Before You Begin the MigrationBefore you begin, we recommend that you read this document and the following guides tofamiliarize yourself with deploying the corresponding Lync Server 2010 roles:

Deploying Lync Server 2010 Enterprise Edition

Deploying Lync Server 2010 Standard Edition

Deploying Edge Servers

Planning for Clients and Devices in Lync Server 2010

Tip:For a quick overview of the steps required to migrate from Microsoft Office Communicator2007 R2 to Microsoft Lync Server 2010, watch the short video athttp://go.microsoft.com/fwlink/?LinkId=206444.

In This Section Migration Process

Migration Phases

Planning for Client Migration

Migration ProcessThe recommended and supported migration procedure for Microsoft Lync Server 2010 is theside-by-side migration procedure. This topic describes why you should use side-by-side migrationand includes information about coexistence and an alternate migration method.

Side-By-Side MigrationIn nearly every migration, you should use the side-by-side migration path. In a side-by-sidemigration, you deploy a new server with Lync Server 2010 alongside a corresponding server thatis running Office Communications Server 2007 R2, and then you transfer operations to the newserver. If it becomes necessary to roll back to Office Communications Server 2007 R2, you haveonly to shift operations back to the original servers. Be aware that in this situation, any newmeetings scheduled with upgraded clients will not work, and the clients would also need to bedowngraded.


7

Coexistence TestingAfter you have deployed Lync Server 2010 in parallel with Office Communications Server 2007R2, the topology represents a coexistence testing state of the two deployments. Before migratingto Lync Server 2010, it is important to test both deployments and ensure services are started;each site can be administered, and clients can communicate with current and legacy users. Priorto migrating all users in Phase 8: Move from Pilot Deployment into Production, it is veryimportant that you understand the state of each deployment and ensure that each deployment isfunctional and working properly. Typically, this coexistence testing phase exists throughout thepilot testing of Lync Server 2010. Legacy users are moved to Lync Server 2010 for a period oftime to ensure that application compatibility and features and functions are working properly. Afterpilot testing, users and applications are moved to the production version of Lync Server 2010,and the legacy pools and applications of Office Communications Server 2007 R2 are retired.

Migrate using Lync Server Management ShellThe recommended method for migrating to Lync Server 2010 is described in Phase 4: MergeTopologies. This method uses the Topology Builder merge wizard feature. An alternate method,described in Migrate Using Lync Server 2010 Management Shell (optional), uses a command-lineapproach to migrating. This method requires creating an input file with Edge Server information,and running a series of Lync Server Management Shell commands. While this method replacesthe Topology Builder Merge wizard procedure described in Phase 4: Merge Topologies, therecommended process is to use Topology Builder and follow the guidelines in Phase 4. However,if you do plan to use this command-line based approach, read the topic thoroughly.

Migration PhasesIn Microsoft Lync Server 2010communications software, you define sites on your network thatcontain Lync Server 2010 components. A site is a set of computers that are well-connected by ahigh-speed, low-latency network, such as a single local area network (LAN) or two networksconnected by a high-speed fiber optic network.

A Front End pool is a set of Front End Servers configured identically, that work together toprovide services for a common group of users. A pool provides scalability and failover capabilityto your users. Each server in a pool must run an identical server role or roles. A Standard Editionserver, designed for small organizations, also defines a pool and runs on a single server. Thisenables you to have Lync Server functionality for a lesser cost, but does not provide a true high-availability solution.

The following phases describe the process of a pool migration from Office CommunicationsServer 2007 R2 to Lync Server 2010. For multiple sites containing multiple pools, each individualpool should follow this phased approach.

Phase 1: Plan Your Migration from Office Communications Server 2007 R2

Phase 2: Prepare for Migration

Phase 3: Deploy Lync Server 2010 Pilot Pool


8

Phase 4: Merge Topologies

Phase 5: Configure the Pilot Pool

Phase 6: Verify Your Pilot Migration

Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool

Phase 8: Move from Pilot Deployment into Production

Phase 9: Complete Post-Migration Tasks

Phase 10: Decommission Legacy Site

Important:This sequence is designed to minimize coexistence and interoperability issues duringmigration. Implementing Lync Server 2010 in a different sequence is not supported.

Planning for Client MigrationThis section outlines client-related considerations when planning a migration to Microsoft LyncServer 2010 communications software. It discusses the user impact of migrating meetings andthe type of information that is migrated. Because a migration process often requires a period oftime during which various client versions coexist, this section also provides information aboutplanning for client compatibility and interoperability.

In This Section Client Planning Steps during Migration

Migration Considerations for Meetings

Client Version Check

Migrating User Settings to Lync Server 2010

Client Interoperability

Client Planning Steps during MigrationThis topic discusses important planning considerations for migration and outlines therecommended client-related steps during the migration process. To facilitate a smooth migrationto Microsoft Lync Server 2010 communications software, you should consider how users will beaffected during the period of coexistence, deploy the appropriate clients to maximize productivity,and ensure that user settings are properly migrated or configured in the new environment.

Client Considerations for MigrationTo help minimize the impact of migration on user productivity, include the following client-relatedconsiderations during the migration planning phases.

In Lync Server 2010, most of the Group Policy settings used in previous OfficeCommunications Server releases are now controlled by in-band provisioning client policiesthat are server-based. You can manage these settings by using the Lync Server ControlPanel, the Windows PowerShell command-line interface, or both. To understand how GroupPolicy settings in your existing deployment map to Lync Server 2010 settings, see MigratingUser Settings to Lync Server 2010.


9

Office Communicator 2007 R2 client bootstrapping policies are also used by Lync Server2010. It is only necessary to configure these policies if you want to change existing policies orif you want to set new policies. If you do not plan to configure client bootstrapping policies, oryou want legacy client bootstrapping policies to remain in effect, no action is necessary. Fordetails, see Migrating User Settings to Lync Server 2010.

Determine how Lync Server 2010 clients will interact with previous client versions. Fordetails, see Client Interoperability.

For manager/delegate support, both managers and delegates must be migrated to Lync 2010at the same time.

If you are deploying conferencing, understand how meetings have changed in Lync Server2010 and determine how migration will affect new and existing meetings. For details, seeMigration Considerations for Meetings.

Decide how users who do not have Lync 2010 installed will participate in Lync Server 2010meetings and configure the meeting join page accordingly. For example, in addition to LyncWeb App, you can allow users to join meetings by using Microsoft Lync 2010 Attendee or aprevious version of Communicator. For details, see Configure the Meeting Join Page.

Overview of Client-Related Tasks during the Migration ProcessPhases 2 and 9 of the migration process include specific steps for migrating clients. These stepsare summarized below. For more information, see the detailed steps for these phases in themigration process.

In Phase 2: Prepare for Migration, use client version rules on your existing server to allow onlyclients with the most current updates to sign in, and to block Lync Server 2010 clients fromsigning in.

In Phase 9: Complete Post-Migration Tasks, after users have been migrated to Lync Server2010, do the following:

1. Use client version rules on your new Lync Server 2010 server to allow only clients with themost current updates installed to sign in.

2. If necessary, configure the Group Policy settings that are required for client bootstrapping.For details, see Key Client Policies and Settings. Configuration of these settings is onlynecessary if you want to change existing client bootstrapping policies or if you want to setnew client bootstrapping policies. If you do not plan to configure client bootstrapping policies,or you want legacy client bootstrapping policies to remain in effect, no action is necessary.

3. Configure other user and client policies for specific users or groups of users by usingMicrosoft Lync Server 2010 Control Panel, Windows PowerShell command-line interface, orboth.

4. Deploy the latest version of Lync Server 2010 along with the latest cumulative updates.

5. (Optional) If your organization requires Lync 2010 enhanced presence privacy mode, aftermigration is complete, define a Client Version Policy Rule to prevent earlier client versionsfrom signing in. Then, enable enhanced presence privacy mode. For details, see ConfiguringEnhanced Presence Privacy Mode in the Deployment documentation.


10

Important:Do not enable Lync 2010 enhanced presence privacy mode until every user on agiven server pool has the most current client versions installed. Lync 2010 privacysettings are not honored by earlier client versions. If earlier clients are allowed to signin, a Lync 2010 user’s availability, contact information, or photo could be viewed bysomeone who has not been authorized to do so. Additionally, a Lync 2010 user’sprivacy management options are reset if that user subsequently logs on with anearlier version of the client.

6. (Optional) If you use remote call control, create a group policy to set the Enable integrationwith your phone system option in the Phone integration section in Lync 2010.

Migration Considerations for MeetingsThe following topics are discussed in this section:

Changes to meetings in Microsoft Lync Server 2010

Migrating users based on their conferencing needs

Migrating existing meetings and meeting content

User experience during migration

Microsoft Lync 2010 communications software compatibility with meetings on earlier serverversions

Configuring the Meeting Join webpage

Changes to Meetings in Lync Server 2010In earlier versions of Office Communications Server, there are two types of meetings:

Conference calls (Lync 2010 client, conf:// URL prefix)

Web conferences (Live Meeting client, meet:// URL prefix)In Microsoft Lync Server 2010, all newly-scheduled meetings use Lync 2010 as the primary client,and have a URL prefix of https://.

During migration, Lync Server 2010 fully supports the earlier meeting types:

Previously scheduled conference calls and Live Meeting web conferences are moved to theLync Server 2010 server.

For users who have been migrated to the Lync Server 2010 server but do not have Lync2010 installed, previous meeting types can still be modified or created.

For details, see the “User Experience During Migration” section later in this topic.

Default Lync Server 2010 Meeting OptionsIn earlier versions of Office Communications Server, scheduled meetings allowed anonymoususers to attend meetings by default. In Lync Server 2010, meeting access for scheduled meetingsis set to “My company” by default. Anonymous users and participants who use dial-inconferencing but for whom authentication fails are transferred to the lobby. Presenters can admitthese users to the meeting.

However, for unscheduled Lync Server meetings, including Meet Now meetings, participant


11

access is set to Everyone, including people outside my company by default, so anonymoususers can join without waiting in the lobby.

Lync Server 2010 Meeting ClientsYou can use the following clients to join meetings scheduled through the Online Meeting Add-infor Microsoft Lync 2010:

Lync 2010

Microsoft Lync 2010 Attendant

Microsoft Lync Web App

Microsoft Lync 2010 Attendee

Microsoft Office Communicator 2007 and Microsoft Office Communicator 2007 R2 (that is,only if the administrator has enabled them. For details, see the “Configuring the Meeting JoinWebpage” section later in this topic.)

You cannot use the following clients to join meetings scheduled through the Online Meeting Add-in for Lync 2010:

Communicator Web Access

Microsoft Office Live Meeting 2007The Lync Web App or Lync 2010 Attendee are the recommended alternatives for users who donot have Lync 2010 or Lync 2010 Attendant installed.

Migrating Users Based on Their Conferencing NeedsConsider migrating frequent meeting organizers early in the process so that they can takeadvantage of the new sharing, collaboration, and lobby management features of Lync Server2010.

For users who need web conferencing features specific to Live Meeting—particularly support forlarge meetings and break-out rooms—you have the following options:

Advise organizers to use the Live Meeting service, if available in your organization.

Leave the organizers homed on the earlier version of Office Communications Server, so theycan continue to schedule server-based Live Meeting web conferences.

Migrating Existing Meetings and Meeting ContentWhen a user account is moved from Microsoft Office Communications Server 2007 R2 to a LyncServer 2010 server, the following information moves along with the user account:

Meetings already scheduled by the user. This includes Communicator conference calls(conf:// URL prefix) and Live Meeting conferences (meet:// URL prefix).

The user’s personal identification number (PIN). The user’s current PIN continues towork until it expires or the user requests a new PIN.

The following information does not move to the new server:

Meeting content. You should advise meeting organizers to reload content into theirscheduled meetings after migration.

Notes:When the Online Meeting Add-in for Lync 2010 is first used to schedule new meetings, a new


12

default conference identifier is created. The default conference identifier is the http address andconference ID that is ordinarily reused for all scheduled meetings.

This should only be an issue for organizers who memorize their conference identifier and give itout to others. Most meeting attendees will join by clicking the join link in the new meetinginvitation, and previously scheduled Office Communications Server 2007 R2 meetings willcontinue to work.

User Experience During MigrationThis section discusses the conferencing experience of users migrated to Lync Server 2010 bothbefore and after Lync 2010 is installed.

Before Lync 2010 Is InstalledAfter a user is migrated to the Lync Server 2010 server, but before new clients are installed, thefollowing Office Communications Server 2007 R2 client functionality continues to work on thenew server:

All scheduling functionality in the Conferencing Add-in for Microsoft Office Outlook

All meeting links in previously sent meeting invitations

Meet Now conferences in Office Communicator 2007 R2

Escalation to Live Meeting (Share Information Using Live Meeting) from Office Communicator2007 R2

Dial-in conferencing numbers

Note:Existing dial-in conferencing numbers work whether the meeting is hosted on OfficeCommunicator 2007 R2 server or a Lync Server 2010 server. However, the latestOffice Communicator 2007 R2 cumulative update is required on the OfficeCommunicator 2007 R2 server pools.

After Lync 2010 Is InstalledWhen a migrated user installs Lync 2010, the Online Meeting Add-in for Lync 2010 is installedtoo. This has the following effects:

All subsequently scheduled meetings use the new meeting format, which uses an https://address instead of the legacy meet:// Live Meeting address.

For an existing meeting that is migrated to Lync Server 2010, the organizer can modify mostmeeting details as usual. However, if the organizer wants to change the meeting end date,end time, participant list, or the meeting subject, the organizer must reschedule the meetingin the new Lync 2010 meeting format. When the organizer changes any of these details, theadd-in will prompt the organizer to manually reschedule the meeting and send an updatedmeeting invitation to all participants.

In an IT-managed deployment of Lync 2010, the administrator has the option of uninstallingthe Conferencing Add-in for Microsoft Office Outlook, which is used to schedule Live Meetingserver and service-based meetings. However, you may have users who need to continue toschedule Live Meeting service meetings. In this case, you can allow both add-ins to coexist.

The following meeting functionality continues to work for users who have installed Lync 2010:


13

All meeting links in previously sent meeting invitations, including Communicator conferencecalls (conf:// URL prefix) and Live Meeting conferences (meet:// URL prefix).

Audio conferencing information in previously sent meeting invitations, including meeting IDs.

Sharing functionality in Office Communicator 2007 R2 meetings.

Sharing functionality in peer-to-peer conversations or conferences that include OfficeCommunicator 2007 R2 users.

Note:In previous versions of Office Communications Server, all users could initiate desktopsharing in meetings. In Lync Server 2010 only meeting presenters can initiatedesktop sharing. In recurring meetings that are migrated to Lync Server 2010,attendees can no longer initiate desktop sharing. If they need to do so, they musthave a meeting presenter promote them to presenter so that they can initiate desktopsharing.

Meetings with Federated Organizations that Use Previous ClientsUsers in federated organizations who are using Microsoft Office Communicator 2007 or MicrosoftOffice Communicator 2005 clients cannot join Lync Server 2010 meetings in your organization ifthose meetings are locked by the organizer. You need to reschedule these meetings in LyncServer 2010 so that when federated participants join the meeting by using the new https://meeting URL, they have the option of using either Lync 2010 Attendee or Lync Web App.

Lync 2010 Compatibility with Meetings on Earlier Versions of Office CommunicationsServerUsers who have Lync 2010 installed can attend meetings hosted on earlier versions of OfficeCommunications Server, but the following considerations apply:

For Communicator meetings, new Lync 2010 features are not available

For Live Meeting web conferences, Lync 2010 users must also have the Live Meeting clientinstalled in order to attend. The email invitation contains instructions for installing the LiveMeeting client.

Configuring the Meeting Join WebpageYou can control the clients that are available for joining scheduled Lync Server 2010 meetings byconfiguring the meeting join page. When a user clicks a meeting link, the meeting join pagedetects whether a client is already installed on the user’s computer. If a client is already installed,the default client opens and joins the meeting. If a client is not installed, the meeting join pagedisplays options for joining the meeting with alternate clients.

The meeting join page always contains the option to use Microsoft Lync Web App. In addition tothis option, you can decide whether to show links for Microsoft Lync 2010 Attendee or a previousversion of Communicator. The scenarios are as follows:

If Lync 2010 or Microsoft Lync 2010 Attendant is installed, the client starts and joins themeeting..

If neither Lync 2010 nor Lync 2010 Attendant is installed and Lync 2010 Attendee is installed,Lync 2010 Attendee starts..


14

If no Lync Server 2010 client is installed, the meeting join webpage appears and gives theuser the following options:

Use Lync Web App

Download Lync 2010 Attendee (this link is hidden by default)

Use a previous version of Communicator (this link is hidden by default)For the scenario in which neither Lync 2010 nor Lync 2010 Attendee is installed, you canconfigure the meeting join page in Microsoft Lync Server 2010 Control Panel (that is, under theSecurity,Web Service settings). You can also configure these same settings by using the New-CsWebServiceConfiguration or Set-CsWebServiceConfiguration Windows PowerShellcmdlets with the ShowDownloadCommunicatorAttendeeLink andShowJoinUsingLegacyClientLink parameters.

Client Version CheckThe Client Version Check application provides you with a way to define a set of rules that specifythe version of clients that are supported in your Microsoft Lync Server 2010 environment. Whentwo clients of differing versions interact, the features that are available to either client can belimited by the capabilities of the other released client. To make the greatest use of featuresincluded in Microsoft Lync Server 2010 communications software and to improve the overall userexperience, you can use the Client Version Check to restrict the client versions that are used inyour Lync Server environment.

Using Client Version Policy to Specify Supported and Restricted VersionsYou can create client version policies to explicitly support or restrict client versions. When asupported client logs on or is invited to a session, the client version policy checks the SIP UserAgent header to determine the client version. Depending on the version of the client, and therules that you have configured, the client version policy does one of the following:

Allows the client to log on to the pool (that is, the Allow option).

Allows Lync 2010 clients to log on and receive updates from Windows Server UpdateService or Microsoft Update (that is, the Allow and Upgrade option). This action is availableonly for Microsoft Lync 2010 (where User Agent is OC).

Allows the client to log on and presents the user with a message that indicates the user canupgrade their client. The message comes with the URL that you specify, and the user canclickthat URL to go to the page represented (that is, the Allow with URL option) and upgradetheir client.

Prevents the client from logging on to the pool (that is, the Block option). Prevents Lync 2010 clients from logging on and allows the client to receive updates from

Windows Server Update Service or Microsoft Update (that is, the Block and Upgradeoption). This action is available only for Microsoft Lync 2010 (where User Agent is OC).

Prevents the client from logging on and presents the user with a message that indicates theuser is using a client that is not supported. The message comes with the URL that youspecify, and the user can click that URL to go to the page represented (that is, the Blockwith URL option).


15

Each pool maintains a client version control list that you configure. This list contains rules thatspecify the client versions you want to filter and the appropriate action for each client version. TheClient Version Check can act according to a specific client version number. It can also actaccording to a client version that is less than or equal to or greater than or equal to the versionnumber that you specify. The Client Version Check also includes a configuration option thatspecifies the default action for clients that are not included in the client version control list.

When you configure the Client Version Check, you specify the way in which clients are handledduring logon. The Client Version Check provides options for configuring the following:

User Agent header. This is the name of the agent for the client version.

Identity. This is the scope that the rule should be applied to. If multiple rules with differentlevels of scope are triggered, the scope with the lowest level of granularity is applied. Forexample, if a service level rules states that the client should be blocked, but a user level rulealso states that the client should be allowed, the client will be allowed as a user level rule isthe most granular.

Note:Because anonymous users are not associated with a user, site, or service,anonymous users are affected by global-level policies only.

Client version number. This includes the major version number, the minor version number,the build number, and the QFE number. The number is presented in the following format:<major version>.<minor version>.<build number>.<qfe number>.

Matching rules. These specify the comparison operations to perform to identify the specificversion or range of versions of the client to which the filtering action is to apply.

Action to take based on client version. Available values are Allow, Block, Allow withURL, Block with URL, Allow and Upgrade, and Block and Upgrade.

Client download URL. This is used only for the Block with URL and Allow with URLoptions.

A default list of rules is installed when you install Lync Server 2010. To customize the set up rulesfor your deployment, you can edit an existing rule, or you can create a new rule. If you do notwant to block earlier version of the client, you will need to modify this list.

Note:The default list of rules automatically blocks earlier versions of Microsoft Communicatorand Microsoft Communicator Phone Edition that try to connect to Lync Server 2010. Ifyou would like to change this behavior, you can create a new rule to allow earlier clientsto connect to the Lync Server 2010 server and then add this to the top of the list.Although you can also edit the default rules to allow earlier clients to connect, we do notrecommend this approach.

Important:The rules are listed in their order of precedence. For example, if you have a rule thatallows Communicator clients with a version 1.5 or later to connect, followed by a ruleblocking clients earlier than version 2.0, the first rule will match and thus takes


16

precedence. As a result, Communicator 1.5 clients can connect.

Client version checks in the version control list act on specific criteria. However, you also need toconfigure a default rule to apply to clients that do not match any other client version rule,specifying one of the following: Allow, Block, or Block with URL.

Migrating User Settings to Lync Server 2010This topic provides the information you need to successfully migrate user and client settings fromMicrosoft Office Communications Server 2007 R2 to Lync Server 2010.

In Microsoft Lync Server 2010 communications software, most of the group policy settings usedin previous versions of Office Communications Server are now controlled by server-based, or in-band provisioning, client policies. In addition, certain Group Policy settings are used for clientbootstrapping.

This topic contains information about the following settings:

Group Policy settings required for client bootstrapping

Obsolete or superseded Office Communicator 2007 R2 group policies

Lync Server 2010 in-band provisioning setting and Windows PowerShell command-lineinterface cmdlet equivalents for Office Communicator 2007 R2 Group Policy settings

Selected new Lync Server 2010 user and client settings

Group Policy Settings for Client BootstrappingBecause Office Communicator 2007 R2 client bootstrapping policies are also used by Lync 2010,it is only necessary to configure them if you want to change existing policies or if you want to setnew policies. If you do not plan to configure client bootstrapping policies, or you want legacyclient bootstrapping policies to remain in effect, no action is necessary.

Group Policies Needed for Client BootstrappingGroup Policy setting Description

ConfigurationMode Specify how Microsoft Lync 2010 identifies the transport and server to use during sign-in. If youenable this policy setting, you must specify ServerAddressInternal, ServerAddressExternal, and Transport.

ConfigurationMode\ServerAddressExternal If you enable ConfigurationMode, you must configure this setting, which specifies the server name used by clients and federated contacts when connecting from outside the external firewall.

ConfigurationMode\ServerAddressInternal If you enable ConfigurationMode, you must configure this setting, which specifies the server name used when clients connect from inside the organization’s firewall.

ConfigurationMode\Transport If you enable ConfigurationMode, you must spe


17

cify Transport Layer Security (TLS). onTransmissi Control Protocol (TCP) is no longersupported.

ConfiguredServerCheckValues Specifies a list of server version names separated by semi-colons that Microsoft Lync Server 2010 will log on to, in addition to the server versions that are supported by default.

DisableHttpConnect During sign-in, Lync Server 2010 attempts to connect to the server using TLS. If is the attemptis not successful, Lync tries to connect using HTTP. Use this policy to disable the fallback HTTP connection attempt.

DisableNTCredentials Requires the user to provide logon credentials for Lync rather than automatically using the Windows credentials during sign-in to a Session Initiation Protocol (SIP) server.

DisableServerCheck By default, Lync checks the server name and version before signing in. Set this policy to 1 in order to bypass the server version check.

EnableBitsForGalDownload This policy allows Lync 2010 to use Background Intelligent Transfer Service (BITS) to download the Address Book Services files.

EnableSIPHighSecurityMode Enables Lync to send and receive instant messages more securely. This policy has no effect on Windows .NET or Microsoft Exchange Serverservices.If you do not configure this policy setting, Lynccan use any transport. But if it does not use TLS and if the server authenticates users, Lync must use either NTLM or Kerberos authentication.

EnableStrictDNSNaming When set to False, allows Lync to automaticallydetect and more securely communicate with SIP servers that have non-standard fully qualifieddomain names (FQDNs).

EnableTracing Turn on tracing for Lync, primarily for use to assist customer problem solving.

FirstRunLaunchMode This policy defines the behavior of the Lync First Run user experience. This setting determines whether the First Run is enabled, and whethe


18

r it runs automatically.

HelpMenuText Specifies the text to display to the user in the Help menu for the Help website.

HelpMenuURL Specifies which website to open when the userselects the Help menu text item in the Help menu. Both HelpMenuText and HelpMenuURL need to be specified in order for the Help menu item to appear in Lync.

PreventRun Prevents users from running Lync. You can configure this policy setting under both ComputerConfiguration and User Configuration, but the policy setting under Computer Configuration takes precedence.

SavePassword Enables Lync to store passwords.

SipCompression Defines when to turn on SIP compression. By default, SIP compression is enabled based on adapter speed. Note that setting this policy mightcause an increase in sign-in time.

Obsolete Group PoliciesThe following table lists the Office Communicator 2007 R2 Group Policy settings that are eitherobsolete or superseded in Lync Server 2010.

Obsolete Group PoliciesObsolete Group Policy Lync Server 2010 in-band provisi

oning settingWindows PowerShell cmdlet

AbsUseFallback None

DisablePC2PCVideo EnableP2PVideo Set-CsConferencingPolicy

DisableRCCForwarding AllowCallForwarding Set-CsVoicePolicy

EnableUPNP ucEnableSipSecurityMode

MaxAudioVideoBitRate AudioBitRateVideoBitRate

ucMaxVideoRateAllowed

Set-CsConferencingPolicySet-CsMediaConfiguration

Configuring Clients by Using Windows PowerShellIn Lync Server 2010, client policies, except for those required for bootstrapping are configured byusing Windows PowerShell cmdlets or the Lync Server Control Panel. This section summarizesthe Windows PowerShell cmdlets and parameters which correspond to Office CommunicationsServer 2007 R2 Group Policy settings.


19

CsClientPolicyThe majority of Group Policy settings from previous versions of Office Communications Servercan be configured by using the Windows PowerShell cmdlets New-CsClientPolicy or Set-CsClientPolicy. For details, see the Lync Server Management Shell documentation.

Most CsClientPolicy parameters have the same name as the equivalent Office CommunicationsServer 2007 R2 Group Policy. This overview section summarizes the renamed, unchanged, andnew policies that can be set by using CsClientPolicy.

Policies Renamed in Lync Server 2010Office Communications Server 2007R2 Group Policy

Lync Server 2010 in-band provisioning setting / CsClientPolicy parameter

Description

AllowUnencryptedFileTransfer EnableUnencryptedFileTransfer When set to True, userswill be allowed to exchange files with external users whose instant messaging software does not support encrypted filetransfers. When set to False, users will only beable to exchange files with external users who have software that supports encrypted file transfers.

CallLogAutoArchivingPolicy EnableCallLogAutoArchiving Enables/disables automatic archiving of call logs to Microsoft Outlookmailbox.

DGRefreshPeriod DGRefreshInterval Indicates the amount oftime Lync 2010 waits before automatically refreshing the membership list of any distribution group that has been "expanded" in the Contacts list. (Expanding a distribution group means displaying all the members in that group.) DGRefreshInterval can be set to an


20

y integer value between30 seconds and 28,800seconds (8 hours), inclusive. The default value is 28,800 seconds.

EnableFullScreenVideoPreviewDisabled

EnableFullScreenVideo When set to True, this parameter does two things: 1) enables full screenvideo (with the correct aspect ratio) for Lync 2010 calls; and, 2) disablesvideo preview for Lync2010 calls. When set toFalse then full screen video is not available in Lync 2010, but video preview is available.

IMAutoArchivingPolicy EnableIMAutoArchiving Enables/disables automatic archiving of IM conversations to Outlook mailbox.

MusicOnHoldAudioFile MusicOnHoldAudioFile Enables/disables abilityfor the user to specify the Music On Hold file.

MusicOnHoldDisabled EnableClientMusicOnHold Enables/disables MusicOn Hold. Note that the corresponding Group Policy setting is DisableClientMusicOnHold. Thesesettings also apply to Microsoft Lync 2010 Attendant.

NotificationsForNewSubscribers EnableNotificationForNewSubscribers

When set to True, any time you are added to someone’s Contacts list you will receive notification that you have been added to the list. In addition, the notification dialog box will provide options for you to add this person to your Contacts list


21

, or to block them from ivewing your presence information. When set toFalse, you will not be notified if you are added tosomeone’s Contacts list.

PC2PCASEncryption P2PAppSharingEncryption Enables or disables application sharing encryption in peer-to-peer (twousers) conversations.

PlayAbbrDialTone PlayAbbreviatedDialTone When set to True, a 3-second dial tone will beplayed any time a Lync2010-compatible handset is taken off the hook.(A Lync 2010 handset looks like a standard telephone, but plugs into aUSB port on your computer and is used to make Lync 2010 calls ratherthan "regular" phone calls.) When set to True, a30-second dial tone is played any time a Lync 2010-compatible handsetis taken off the hook.

SafeTransfer AttendantSafeTransfer Attendant - Safe Transfer

The following table summarizes the unchanged policies that can be set by using CsClientPolicy.

Unchanged Client Policy NamesLync Server 2010 in-band provisioning setting / CsClientPolicy parameter

Description

AutoDiscoveryRetryInterval After a failed connection attempt, specifies theamount of time Lync 2010 waits before trying again to connect to Lync Server. The AutoDiscoveryRetryInterval can be set to any integer value between 15 and 480 minutes (8 hours), inclusive. The default value is 30 minutes.


22

BlockConversationFromFederatedContacts Blocks conversation from federated contacts.

CalendarStatePublicationInterval Sets time interval to publish calendar data to presence.

CustomStateURL Sets custom presence states URL.

DisableCalendarPresence Disables calendar presence.

DisableEmailComparisonCheck Disables email comparison check for Outlook public IM connectivity integration.

DisableEmoticons Disables emoticons in instant messages.

DisableFederatedPromptDisplayName Prevents showing the display name of federated contacts in the notification dialog (does not include contact who use public IM connectivity).

DisableFreeBusyInfo Disables publishing free/busy information.

DisableHandsetOnLockedMachine Configures handset use on locked computer.

DisableHTMLIM Prevents HTML text in instant messages.

DisableInkIM Prevents Ink in instant messages.

DisableMeetingSubjectAndLocation Disables publishing meeting subject and location information.

DisableOneNote12Integration Disables Microsoft OneNote integration.

DisableOnlineContextualSearch Disables online contextual search.

DisablePhonePresence Disables call presence.

DisablePICPromptDisplayName Prevents showing the display name of public IM connectivity contacts in the notification dialogbox.

DisablePresenceNote Disables presence note.

DisableRTFIM Prevents rich text in instant messages.

DisableSavingIM Prevents users from saving instant messages.

EnableAppearOffline Enables the state Appear Offline.

EnableEventLogging Turns on event logging for Lync 2010.

EnableSQMData Specifies instrumentation.

EnableTracing Turns on tracing for Lync 2010.

EnableURL Allows hyperlinks in instant messages.

MAPIPollInterval Specifies how often Lync 2010 retrieves MAPIdata from the Exchange public folders. MAPIPollInterval can be set to any integer value betwe


23

en 5 minutes and 480 minutes (8 hours); ve.inclusi The default value is 30 minutes.

MaximumNumberOfContacts Indicates the maximum number of contacts a user is allowed to have. The maximum contactscan be set to any integer value between 0 and1000, inclusive. When set to 0, that prevents the user from having any contacts.

WebServicePollInterval For users of Microsoft Exchange Server 2007 or later, WebServicePollInterval specifies how often Lync 2010 retrieves data from Exchange Web Services. WebServicePollInterval can be setto any integer value between 5 minutes and 480 minutes (8 hours); inclusive. The default value is 30 minutes.

The following table summarizes the new policies that can be set by using CsClientPolicy.

New Lync Server 2010 Client PoliciesLync Server 2010 in-band provisioning setting /CsClientPolicy parameter

Description

AbsUsage (in-band) / AddressBookAvailability (Windows PowerShell)

Can be set to download the Address Book only,use Address Book web search only, or use both.

ConferenceIMIdleTimeout Indicates the number of minutes that a user canremain in an instant messaging session withouteither sending or receiving an instant message.

CustomizedHelpURL Replaces the default Lync 2010 help link with the location of your organization-specific Help. Use in conjunction with EnableEnterpriseCustomizedHelp.

CustomLinkInErrorMessages URL for a web site that can be added to errormessages in Lync 2010.

DisableContactCardOrganizationTab Enables or disables the contact card organization tab.

DisableFeedsTab Enables or disables the activity feeds tab.

DisablePoorDeviceWarnings Disables device warnings that appear whenever a faulty or obsolete device is detected.

DisablePoorNetworkWarnings Disables network quality warnings that may appear during a conversation.


24

DisplayPhoto Determines whether or not photos (of both theuser and his or her contacts) are displayed.

DisplayPublishedPhotoDefault Sets the default for display of other contacts’ published photos. Can be overridden by users.

EnableDelegation Enables the call delegation. See also EnableExchangeDelegationSync in this table.

EnableDiagnosticsLogsCollection Enables or disables the Collect Logs button, which is used to collect logs for the investigationof audio, video, or connectivity issues. This feature allows the user to capture the necessary logs and metrics and compress them into a .cab file. The user then manually uploads logs per the administrator’s instructions, who sends the logs to Microsoft for troubleshooting purposes.

EnableEnterpriseCustomizedHelp Allows you to replace the default Lync 2010 help link with the location of your organization-specific online help. Use in conjunction with CustomizedHelpURL.

EnableExchangeContactSync When enabled, Lync 2010 creates a corresponding personal contact in Microsoft Outlook for each person on a user’s Contacts list.

EnableExchangeDelegateSync When enabled, the client retrieves the Exchange calendar delegates (users who have authoring and editing rights on the manager’s calendar)and uses these settings to update delegates inLync Server 2010. Use this setting in conjunction with the EnableDelegation setting, which is configurable in the CsVoicePolicy cmdlets or in Lync Server Control Panel.

EnableHotdesking When enabled, a user can log on to a Lync 2010 Phone Edition phone in a shared workspaceusing his or her Lync Server 2010 account.

EnableVOIPCallDefault When enabled, a Lync 2010 call is placed any time a user employs the click-to-call feature.

ExcludedContactFolders Indicates which Microsoft Outlook contact folders (if any) should not be searched any time Lync 2010 searches for new contacts.

HotdeskingTimeout Timeout interval for a user logged on to a "hot desk" phone.


25

MaximumDGsAllowedInContactList Indicates the maximum number of distribution rgoups that a user can configure as a contact.

MaxPhotoSizeKB Set this policy to 0 to remove photos from Lync2010 and disable the photo user interface. Default: 10.

PhotoUsage Enables or disables display of photos.

PolicyEntry Provides a way to add settings not covered by the default parameters.

SearchPrefixFlags Represents the Address Book attributes that should be searched any time a user searches fora new contact.

ShowManagePrivacyRelationships Enables or disables the Manage Privacy Relationships option in the View by menu.

ShowRecentContacts Shows or hides the Recent Contacts option inthe Display Options menu.

ShowSharepointPhotoEditLink Controls whether users see the Edit in Mysiteselection in their My Picture options. Edit in Mysite allows users to show a picture from Microsoft SharePoint MySite.

SPSearchCenterExternalURL External URL for the SharePoint site used for keyword searches (also known as expert searches). This URL will appear at the bottom any of keyword search results that appear in Lync 2010. If the user clicks this URL, his or her web browser will open up to the SharePoint site, giving the user the opportunity to conduct searches using SharePoint’s search capabilities.

SPSearchCenterInternalURL Internal URL for the SharePoint site used for keyword searches (also known as expert searches). This URL will appear at the bottom any of keyword search results that appear in Lync 2010.If the user clicks this URL, his or her web browser will open up to the SharePoint site, giving theuser the opportunity to conduct searches usingSharePoint’s search capabilities.

SPSearchExternalURL Internal URL for the SharePoint site used for keyword searches (also known as expert searches). Lync 2010 will use the SharePoint site located at this URL any time an external user (that is, a user who has access the system from outsid


26

e the organization’s firewall) conducts a dkeywor search.

SPSearchInternalURL Lync 2010 will use the SharePoint site locatedat this URL any time an internal user (that is, auser who has logged on from inside the organization’s firewall) conducts a keyword search.

For details, see the following topics:

Set-CsClientPolicy in the Lync Server Management Shell documentation

Overview of Client Policies and Settings

Lync 2010 New Features

Additional Client PoliciesThe following table lists the Lync Server 2010 in-band provisioning settings and WindowsPowerShell cmdlets that are either not configurable through Windows PowerShell or configuredby using a Windows PowerShell cmdlet other than New-CsClientPolicy or Set-CsClientPolicy.Many of these settings correspond to Communications Server 2007 R2 Group Policy settings andhave been renamed in Lync Server 2010.

Communications Server 2007 R2 Group Policy EquivalentsOffice CommunicationsServer 2007 R2 GroupPolicy setting

Lync Server 2010 in-band provisioning setting

Windows PowerShell cmdlet

Cmdlet parameters

AbsInsideURL AbsInternalServerUrl

None None

AbsOutsideURL AbsExternalServerUrl

None None

Portrange\MaxMediaPort

ucMaxMediaPort None None

Portrange\MinMediaPort

ucMinMediaPort None None

Portrange\Enabled ucPortRangeEnabled

None None

DisableApplicationSharingControl

AllowParticipantControl

CsConferencingPolicy AllowExternalUserControl

DisableDataConferencing

EnableDataCollaboration

CsConferencingPolicy EnableDataCollaboration

DisableAVConferencing

AllowIPAudio, AllowIPVideo

CsConferencingPolicy;CsUser

AllowIPAudio, AllowIPVideo; AudioVideoDisabled


27

DisableFileTransfer AllowFileTransfer CsFileTransferFilterConfiguration(Lync 2010)CsConferencingPolicy (Web conferencing)

--

IMWarning IMWarning CsIMFilterConfiguration

WarnMessage

MRASServerURI mrasURI None None

PC2PCAVEncryption ucPC2PCAVEncryption

CsMediaConfiguration EncryptionLevel

msRTCLine line CsUser LineURI

TelephonyMode TelephonyMode CsUser UCEnabled, RemoteCallControlTelephonyEnabled

ExUMEnabled ExUMEnabled CsUser MCSVoiceMail

DisableSimultaneousRinging

AllowSimultaneousRinging

CsVoicePolicy AllowSimulRing

VoicemailURI VoicemailURI None None

Client InteroperabilityThis topic discusses the ability of Microsoft Lync Server 2010 communications software clients tocoexist and interact with clients from earlier versions of Office Communications Server.

There are two types of client compatibility:

Multiple points of presence (MPOP) The ability of a single user to sign in to a server withmultiple clients and multiple client versions.

Interoperability The ability to interact with another user who is signed in using a differentclient type, or an earlier version of the same client.

Planning for Compatibility

Important:In order to fully test the new Lync Server 2010 features during migration, you mustensure that previous client versions have the most recent updates, or hotfixes, installed.For details, see Planning for Client Migration.

Lync Server 2010 fully supports interoperability among Lync Server 2010 clients.

Most instant messaging (IM), presence, and voice features are also supported when interactingwith Microsoft Office Communications Server 2007 R2 and Microsoft Office CommunicationsServer 2007 clients. For details, see the "Lync Server 2010 Interoperability with Previous ClientVersions" section later in this topic.

For best results with meetings, see Migration Considerations for Meetings.


28

Compatibility among Lync Server 2010 ClientsAll Lync Server 2010 clients can interoperate with other Lync Server 2010 clients.

Most Lync Server 2010 clients also support the multiple points of presence scenario—that is, asingle user can be signed in at multiple locations—with the following exception:

Microsoft Lync 2010 Attendant users can only be signed in simultaneously with phonesrunning Microsoft Lync 2010 Phone Edition. Simultaneous sign-in with other Lync Server2010 clients is not supported.

Multiple Points of Presence (MPOP) with Previous Client VersionsThe following table describes the client versions that are supported when a single user is signedin to Lync Server 2010 at multiple locations.

Note:Lync Server 2010 clients cannot sign in to previous server versions.

Client Versions Supported for Sign-in from Multiple LocationsCurrent client version Client version MPOP support (with required upd

ates)

Lync 2010

Microsoft Lync 2010 Attendee

Microsoft Office Communications Server 2007R2

Microsoft Office Communications Server 2007

2007 R2 release of Microsoft Office Communicator Web Access

Microsoft Office Communicator Web Access (2007 release)

Phones running Microsoft Office Communicator2007 R2 Phone Edition

Phones running Microsoft Office Communicator2007 Phone Edition

Microsoft Communicator for Mac 2011

Microsoft Lync 2010 Attendant Phones running Microsoft Lync 2010 Phone Edition

Phones running Lync 2010 Phone Edition Microsoft Office Communicator 2007 R2

Microsoft Office Communicator 2007


2007 R2 release of Microsoft Office Communicator Mobile

Microsoft Office Communicator 2007 R2

Microsoft Office Communicator 2007

Microsoft Office Communicator 2007 R2 PhoneEdition

Microsoft Office Communicator 2007 Phone Edi


29

tion


Lync Server 2010 Interoperability with Previous Client VersionsThis section discusses Lync Server 2010 interoperability support for clients that shipped withOffice Communications Server 2007 R2 and Office Communications Server 2007.

Note:Communicator Web Access and Microsoft Office Live Meeting 2007 cannot be used tojoin new meetings scheduled on Lync Server 2010. Lync 2010, Microsoft Lync 2010Attendee, and Microsoft Lync Web App are the recommended alternatives. For details,see Migration Considerations for Meetings.

IM, Presence, Voice, and Video InteroperabilityThe following table describes the availability of these features during migration.

IM, Presence, and Voice Interoperability with Previous Client VersionsLync Server 2010 clients

Office Communications Server 2007 R2 clients

Office Communications Server 2007 clients

Lync Server 2010Clients

IM, presence, voice,and video supported

IM, presence, voice, andvideo supported

IM, presence, and videosupported; some voice feature limitations (see thefollowing section in this topic)

Interaction with Microsoft Office Communicator 2005 clients (basic presence and IM) issupported only if the Office Communicator 2005 user is on a federated network.

Voice Interoperability ConsiderationsVoice interoperability issues to be aware of are as follows:

Office Communicator 2007 does not support voice features added in Communicator 2007 R2and Lync 2010, such as call park, team call, and response group service.

Call park issues you should be aware of during migration are as follows:

A call parked by a Lync 2010 user cannot be unparked by clients or devices signed in toan earlier version of Office Communications Server.

You cannot park a call to a Office Communications Server 2007 client or device.Conferencing Interoperability ConsiderationsWhen a user account is moved from Communications Server 2007 R2 to a Lync Server 2010server, the following information moves along with the user account:

Meetings already scheduled by the user.

The user’s PIN (there is no need for new PIN assignment).The following information does not move to the new server:


30

Meeting content. You should advise meeting organizers to reload content into their scheduledmeetings after migration.

The following tables describe two conferencing interoperability scenarios:

Previous client version interoperability with Lync Server 2010 meetings

Lync 2010 interoperability with meetings hosted or scheduled on previous server versions

Previous Client Versions and Lync Server 2010 MeetingsCommunicator 2007 R2and Communicator 2007 interoperability

Schedule Lync Server2010 Meetings

Join Lync Server 2010Meetings

Behavior in Lync Server 2010 Meetings

Before user is moved to Lync Server 2010

Not supported. Supported if enabled. For details, see Migration Considerations for Meetings.

No access to new collaboration features unless meeting is escalated to use Lync WebApp.

No access to new lobby management features.

After user is moved toLync Server 2010, butbefore new clients are installed

Continue using the Conferencing Add-in forMicrosoft Office Outlook to schedule conference calls and Live Meeting web conferences.

Supported if enabled. For details, see Migration Considerations for Meetings.

No access to new collaboration features unless meeting is escalated to use Lync Server 2010.

No access to new lobby management features.

For details, see Migration Considerations for Meetings.

Lync 2010 Interoperability With Meetings Hosted or Scheduled on Previous Versions ofOffice Communications ServerLync 2010 interoperability with meetings on previous versions of Office Communications Server

Lync 2010 user experience

Scheduling Lync 2010 users cannot schedule meetings onearlier server versions.

When modifying the end date, subject, or attendee list of meetings migrated from previous server versions to Lync Server 2010, users are prompted to convert the meeting to Lync Server 2010.

Joining No issues.


31

In meeting New Lync 2010 features are unavailable.

Manager/Delegate InteroperabilityFor the manager/delegate scenario, both manager and delegate must be using Lync 2010.

Interoperability with Existing Custom ApplicationsFor the purposes of this discussion an existing custom application is defined as follows:

The application uses the Microsoft Office Communicator Automation API or the MicrosoftUnified Communications Client API.

The application runs in a migration environment, on a machine where either Communicator2007 R2 or Communicator 2007 is connected to a server running Lync Server 2010.

Existing custom applications can sign in to a Lync Server 2010 server and interact with LyncServer 2010 clients. However, the following limitations apply:

Existing custom applications do not have access to Lync 2010 features.

Running a Unified Communications Client API custom application on the same computer asLync 2010 is not recommended.

If your organization plans to enable enhanced presence privacy mode, UnifiedCommunications Client API custom applications may need to be rewritten. For details, seePlanning for Clients, Lync 2010 New Features in the Getting Started documentation, and theMicrosoft Lync 2010 SDK.

See AlsoPlanning for Clients

New Client Features

Phase 1: Plan Your Migration from Office CommunicationsServer 2007 R2This section covers planning topics for migrating from Microsoft Office Communications Server2007 R2 to Microsoft Lync Server 2010.

In This Section User Migration

Administering Servers after Migration

Migrating Multiple Sites and Pools

User MigrationA generally accepted best practice for migrations is to create several test users and use them toconduct systems tests. After you have successfully moved and tested those accounts, you shouldidentify a group of pilot production users and move their accounts and conduct validation tests onthem. When you get satisfactory results, you can move the rest of your users to the newdeployment.


32

Administering Servers after MigrationIn general, you must use the administrative tools that corresponds to the server version that youwant to manage.

Use the Office Communications Server 2007 R2 snap-in as follows:

To manage Office Communications Server 2007 R2 users and servers.

To access the Active Directory Users and Computers snap-in on Office CommunicationsServer 2007 R2 or on a computer with the Office Communications Server 2007 R2administrative tools installed.

Use the Lync Server 2010 Control Panel as follows:

To move legacy Office Communications Server 2007 R2 users to Lync Server 2010.

To manage users on Lync Server 2010 after moving them from Office CommunicationsServer 2007 R2.

Important:Only the Lync Server 2010 Control Panel should be used to move users to and fromLync Server 2010.

To manage Lync Server 2010 servers and services.You cannot install the Office Communications Server 2007 R2 administrative tools and the LyncServer 2010 Control Panel on the same computer. Also, the Lync Server 2010 Control Panel isnot installed automatically on each server. You must manually choose on which workstation orserver you want to install the tools. To install the Lync Server 2010 Control Panel, follow theprocedure inside the topic Install Topology Builder with the Administrative Tools in theDeployment documentation.

Migrating Multiple Sites and PoolsMicrosoft Lync Server 2010 supports multi-site and multi-pool deployments. The process ofmigrating multiple pools from Microsoft Office Communications Server 2007 R2 to Lync Server2010 requires the following considerations:

1. After deploying a Lync Server pilot pool and importing the Office Communications Server2007 R2 pool configuration to the Lync Server pool, you need to define a subset of pilot usersthat will be moved to the Lync Server pool, and a methodology for validating the functionalityof the users.

2. After deploying an Edge Server in the pilot pool, you need to validate that external users cancommunicate with the Lync Server pool.

3. After transitioning the federated routes from Communications Server 2007 R2 Edge Serversto the pilot Lync Server Edge Servers, you need to validate that federated users cancommunicate with the Lync Server pool.

4. After moving all the users and non-user contact objects, you need to validate that theCommunications Server 2007 R2 pool is empty.

5. After verifying that the Communications Server 2007 R2 pool is empty, you can then


33

deactivate the pool.

6. After verifying that all pools are deactivated, and all Communications Server 2007 R2 EdgeServers have been uninstalled, use the Topology Builder Merge wizard to remove the legacytopology from the site. Finally, use Topology Builder to delete the BackCompatSite.

For details about how to deactivate the legacy Office Communications Server 2007 R2 pooland servers, see Phase 10: Decommission Legacy Site.

Phase 2: Prepare for MigrationBefore you begin to migrate to Microsoft Lync Server 2010 from Microsoft Office CommunicationsServer 2007 R2, follow the steps described in this section.

In This Section Apply Office Communications Server 2007 R2 Updates

Run Best Practices Analyzer

Back Up Systems and Data

Configure Clients for Migration

Apply Office Communications Server 2007 R2 UpdatesBefore you migrate to Microsoft Lync Server 2010, updates must be applied to your MicrosoftOffice Communications Server 2007 R2 environment. The updates required are listed in thefollowing table.

For the most up-to-date information about Office Communications Server 2007 R2 updates, seeUpdates Resource Center for Office Communications Server 2007 R2 and Clients athttp://go.microsoft.com/fwlink/?LinkId=199488.

Check the Programs and Features application in the Control Panel on your OfficeCommunications Server 2007 R2 deployment to determine if any of these updates have beenapplied.

Office Communications Server 2007 R2 Required UpdatesApplication Update URL

Microsoft Office Communicator 2007 R2

July 2010 Update package

http://go.microsoft.com/fwlink/?LinkId=204763

Microsoft Office Live Meeting 2007



Microsoft Office Live Meeting Conferencing Add-In



Office Communications Server 2007 R2

September 2010 Update package


Microsoft Office Commun July 2010 Update pa http://go.microsoft.com/fwlink/?LinkId=204767


34

icator 2007 R2 Phone itioEdn

ckage

Run Best Practices AnalyzerThe Microsoft Office Communications Server 2007 R2 Best Practices Analyzer tool gathersconfiguration information from an Office Communications Server 2007 R2 deployment anddetermines whether the configuration is set according to Microsoft best practices. You can installthe tool on a client computer that runs Microsoft .NET Framework 2.0, or directly on the serverthat runs Office Communications Server. We recommend that you install and run this tool on aclient computer. The Office Communications Server 2007 R2 Administrative Tools should also beinstalled locally on the client computer so that the Best Practices Analyzer can collect a full set ofdata.

For details about installing the Office Communications Server 2007 R2 Administrative Tools on a32-bit client computer, see "32-Bit Tools: Office Communications Server 2007 R2 Deploymentand Management" at http://go.microsoft.com/fwlink/?LinkId=199486.

You can download the Office Communications Server 2007 R2 Best Practices Analyzer from theMicrosoft Download Center at http://go.microsoft.com/fwlink/?linkid=144315.

Back Up Systems and DataBefore you begin the migration to Microsoft Lync Server 2010, we strongly recommend that youperform a full system backup and document your existing system, including an inventory of useraccounts that are homed on each pool, so that you can roll back to Microsoft OfficeCommunications Server 2007 R2 if it becomes necessary.

Multiple tools and programs are available for backing up and restoring data, settings, andsystems. For details and procedures, see the Office Communications Server 2007 R2 Backupand Restoration Guide at http://go.microsoft.com/fwlink/?LinkId=168162. The Backup andRestoration Guide focuses on the use of tools and programs that are provided with OfficeCommunications Server 2007 R2 and on components that are available in Microsoft SQL Server2008 and Microsoft SQL Server 2005.

Configure Clients for MigrationThis topic contains the recommended client deployment steps you should take prior to migratingto Microsoft Lync Server 2010. These configuration changes should be made on OfficeCommunications Server 2007 R2. It is very important that you perform these steps prior tomigrating. For details, see Planning for Client Migration.

To configure clients prior to migration

1. Deploy the most recent server, client, and device updates (hotfixes) for Microsoft OfficeCommunications 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 cl


35

ients with the most current updates installed, as listed in Apply Office CommunicationsServer 2007 R2 Updates to sign in.

3. On Office Communications Server 2007 R2, use Client Version Filtering to block LyncServer 2010 clients from signing in. Follow the steps described in Configuring ClientVersion 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.

Client User agent header Version

Lync 2010 OC 4.*.*.*

Lync Web App CWA 4.*.*.*

Lync 2010 Phone Edition OCPhone 4.*.*.*

Lync 2010 Attendee AOC 4.*.*.*

Phase 3: Deploy Lync Server 2010 Pilot PoolThis section describes the reference topology covered in this document. It also covers the stepsrequired to deploy a pilot deployment of Lync Server 2010, and a few key validation steps toensure the two pools are coexisting.

In This Section Lync Server 2010 Pilot Pool Architecture

Deploy Lync Server 2010 Pilot Pool

Verify Pilot Pool Coexistence with Legacy Pool

Lync Server 2010 Pilot Pool ArchitectureThe following figure shows the pilot pool reference topology used in this document. Lync Server2010 is installed side by side 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 thencommunicate with users who are homed on Office Communications Server 2007 R2 servers. Thiswill show interoperability between users who are homed in different pools can continue tocommunicate and use the existing workloads and perimeter network infrastructure.


36

Initially a Lync Server 2010 pool is deployed in parallel with Office Communications Server 2007R2. External traffic and federation is done through the legacy Edge Server environment. In Phase7: Add Lync Server 2010 Edge Server and Director to Pilot Pool, the Director and Edge Serverare added to the deployment.

The following table lists the fully qualified domain names (FQDNs) for the various server rolesused in this topology. It is supplied solely for reference purposes.

Server Role Office Communications Server 2007R2 FQDN

Lync Server 2010 FQDN

Standard Edition Server SE-R2.CONTOSO.NET LYNC-SE.CONTOSO.NET

Edge Server EDGE-R2.CONTOSO.NET LYNC-EDGE.CONTOSO.NET

Director DIR-R2.CONTOSO.NET LYNC-DIR.CONTOSO.NET

Mediation Server MEDSVR01.CONTOSO.NET Collocated on LYNC-SE.CONTOSO.NET

ImportantWe recommend deploying Lync Server 2010 Enterprise Edition for deployments that require atrue high-availability solution.

Important:We recommend collocating the Lync Server Mediation Server with a Lync Server FrontEnd pool or Standard Edition server when merging an Office Communications Server2007 R2 stand-alone Mediation Server.


37

Deploy Lync Server 2010 Pilot PoolOne of the first steps in a phased rollout is to deploy a Lync Server 2010 pilot pool. You willmerge topology information and configuration settings from an existing Office CommunicationsServer 2007 R2 pool to this pilot pool. The pilot pool is where you test coexistence of Lync Server2010 with your Office Communications Server 2007 R2 deployment. Coexistence is a temporarystate that lasts until you have moved all users and pools to Lync Server 2010.

You should deploy the same features and workloads in your pilot pool that you have in yourOffice Communications Server 2007 R2 pool. For detailed steps about deploying StandardEdition in your pilot environment, see Deploying Lync Server 2010 Standard Edition in theDeployment documentation. For detailed steps about deploying Enterprise Edition in your pilotenvironment, see Deploying Lync Server 2010 Enterprise Edition in the Deploymentdocumentation.

Important:Before you deploy your pilot pool, you need to decide whether you will deploy one LyncServer 2010 pool for each existing Office Communications Server 2007 R2 pool. Someconfiguration settings, such as Response Group, migrate for an entire pool with a singlecmdlet. Therefore, if you plan to consolidate pools or split pools into smaller pools duringyour migration and deployment, you need to plan which Office Communications Server2007 R2 pools map to which Lync Server 2010 pools and adjust your migrationaccordingly.

Note:When creating a new topology using Topology Builder, ensure that the primary SIPdomain (and any additional SIP domains) are named exactly as the legacy OfficeCommunications Server 2007 R2 SIP domains. If not, the Topology Builder Merge wizardprocedure in Phase 4: Merge Topologies will fail to create a topology. To find your legacyOffice Communications Server 2007 R2 SIP domains, open the Office CommunicationsServer 2007 R2 Administrative Tools snap-in. Right click the forest node, select GlobalProperties, and then under the General node note the list of SIP domains in theDomains list box. The checked domain is the primary or default domain.

When you deploy a pilot pool, you use the Define New Front End Pool wizard. The procedurethat follows discusses features and settings you should consider as part of your overall pilot pooldeployment process. This section only highlights key points you should consider as part of yourpilot pool deployment. For detailed steps, refer to the Deployment guides mentioned earlier. Thefollowing procedures match the pilot pool reference architecture listed in Lync Server 2010 PilotPool Architecture. Adapt these settings to match your deployment.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding serverroles. For details, see Delegate Setup Permissions in the Deployment documentation. For otherconfiguration changes, only membership in the RTCUniversalServerAdmins group is required.


38

Pilot Pool Deployment Considerations

1. When you define your pilot pool, you can choose to deploy an Enterprise Edition Front End Pool or a Standard Edition Server. Lync Server 2010 does not require that your pilot pool match what was deployed in your legacy pool.

2. On the Select collocated server roles page, we recommend you collocate the Mediation Server in Lync Server 2010. When merging a legacy topology with Lync Server 2010, we require that you first collocate the Lync Server 2010 Mediation Server. After merging the topologies and configuring the Lync Server 2010 Mediation Server, you can decide to keep the collocated Mediation Server or change it to a stand-alone server in your Lync Server 2010 deployment.

Important:Note that Lync Server 2010 Standard Edition server pools can only be servedby the collocated A/V Conferencing service installed. Thus, the check box is unavailable on this page but would be available on Lync Server 2010 EnterpriseEdition server.

Note:We highly recommend that you collocate the Mediation Server on a Front EndServer or Standard Edition server. However, if you do decide to move a colloc


39

ated Lync Server 2010 Mediation Server to a stand-alone Mediation Server, ese Transition a collocated Mediation Server to a Stand-Alone Mediation Server(optional).

3. On the Associate server roles with this Front End pool page, you can choose to enable archiving and monitoring if you want those server roles deployed as part of your pilot pool.

Important:During pilot pool deployment, do not choose the Enable an Edge pool to be used by the media component of this Front End pool option. This is a feature you will enable and bring online in a later phase of migration. Keep this setting cleared for now.


40

4. Continue completing the Define New Front End Pool wizard and click Finish when completed.

5. To publish your topology, right-click the Lync Server 2010 node and then click Publish Topology.

6. When the publish process has completed, click Finish.

7. To install a local copy of the configuration database and start the required services, see Setting Up Front End Servers and Front End Pools or Setting Up Standard Edition Server in the Deployment documentation.

Verify Pilot Pool Coexistence with Legacy PoolAfter you deploy the pilot pool and before you begin to migrate from Microsoft OfficeCommunications Server 2007 R2, verify the coexistence of the two pools by using theadministrative tools to view the pool information. For the Office Communications Server 2007 R2pool, use the Office Communications Server 2007 R2 administrative tool. For the Microsoft LyncServer 2010 pool, use Lync Server 2010 Control Panel.


41

Verify the Pool in Office Communications Server 2007 R2 Administrative Tool

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group.

2. Open the Office Communications Server 2007 R2 administrative tool.

3. Expand the Forest node, expand the Standard Edition Servers or Enterprise poolsnode, and then expand the pool or server name.

4. Ensure that the services are running on the Standard Edition server or Enterprise pool.

Verify the Pilot Pool in Lync Server Control Panel

1. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Installing and Using Administrative Tools.

2. Click Topology.3. Verify that the servers you deployed are present in your pilot pool.


42

Verify Lync Server services have started

1. From the Standard Edition server or Front End Server, open the Services applet from the Administrative Tools group.

2. Verify that the services listed match the list in the following figure.


43

Phase 4: Merge TopologiesThe following topics outline the steps needed to merge your Microsoft Office CommunicationsServer 2007 R2 pools to Microsoft Lync Server 2010 pools. First, you use the Topology BuilderMerge wizard to merge topology information. This tool collects information about your OfficeCommunications Server 2007 R2 environment, including Edge Server information, and publishesthat information to a database shared with Lync Server 2010. After you publish the mergedtopology, Topology Builder is used to view the Office Communications Server 2007 R2 topologyinformation and information about the newly deployed Lync Server 2010 topology. Finally, youuse Lync Server Management Shell cmdlets to import policies and configuration settings.

In This Section Install WMI Backward Compatibility Package

Merge Using Topology Builder Merge Wizard

Import Policies and Settings

Verify Topology Information

Install WMI Backward Compatibility PackageYou must install the Windows Management Instrumentation (WMI) Backward CompatibilityPackage as a prerequisite before running the Topology Builder Merge wizard. Lync Server 2010stores its configuration information in a Central Management store hosted on SQL Server 2008SP1 or SQL Server 2005 Service Pack 3. Microsoft Office Communications Server 2007 R2used the Windows Management Instrumentation (WMI) framework. The WMI BackwardCompatibility Package provides Lync Server 2010 the ability to merge WMI information fromOffice Communications Server 2007 R2 into the new format in Lync Server 2010.

If you attempt to run the Topology Builder Merge wizard without installing the WMI BackwardCompatibility package, you will see the following error:

If you attempt to run the Merge-CsLegacytopology cmdlet without installing the WMI BackwardCompatibility package, you will see the following error:


44

To install the WMI Backward Compatibility Package

1. On the Standard Edition Server or Front End server, log on to the computer with anaccount that is a member of the Administrators group.

2. From your installation media, navigate to \SETUP\AMD64\SETUP\OCSWMIBC.MSI.

3. Install OCSWMIBC.MSI.

Important:OCSWMIBC.msi must be installed on the machine where the Topology Builder Merge wizard is run.

Important:OCSWMIBC.msi can be installed on any machine in the domain that has the Lync Server 2010 Core Components and Lync Server Management Shell installed, and has access to the Office Communications Server 2007 R2 topology (WMI provider to Active Directory and SQL Server).

Merge Using Topology Builder Merge WizardTopology Builder is a new tool introduced in Microsoft Lync Server 2010. With Topology Builderyou can create, edit, and publish a Lync Server 2010 deployment topology. Additionally, theMerge feature allows you to import information from your previous Office Communications Serverenvironments, and integrate it into a consolidated view alongside your Lync Server 2010deployment.

Note:The Topology Builder Merge wizard also imports directories used for conferencing.

Note:See the topic Migrate Using Lync Server 2010 Management Shell (optional) as analternative method to using Topology Builder.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding server


45

roles. For details, see Delegate Setup Permissions in the Lync Server 2010 Standard Edition orEnterprise Edition deployment documentation. For other configuration changes, only membershipin the RTCUniversalServerAdmins group is required.

To merge topology information

1. From the Standard Edition Server or Front-End Server, click Start, then All Programs,then Microsoft Lync Server 2010, then Lync Server Topology Builder.

2. Select the option to Download topology from existing deployment and then click OK.

3. In the Save Topology As dialog box, select the Topology Builder file you want to useand click Save.

4. In the Actions pane, click Merge 2007 or 2007 R2 Topology.5. Click Next to continue.

6. In Specify Edge Setup, click Add.

7. In Specify Edge Version, select Office Communications Server 2007 R2 Edge Server and then click Next.

8. In Specify Edge Type, specify the type of Edge Server configuration and then click Next. This example uses the Single Edge Server option.


46

Important:Expanded Edge is not a supported configuration. An Expanded Edge must stfir be converted to a Single Edge Server or a Load-balanced consolidatedEdge server.

ImportantIf you use a Load-balanced consolidated Edge configuration, and you want to change the membership of that configuration by creating a new Edge pool using one of the legacy Communications Server 2007 R2 Edge servers, you must first remove the legacy Edge server from the existing Communications Server 2007 R2 Edge array and then publish the topology. Using the Topology Builder merge wizard, you then create a new Edge pool, add the legacy Edge server to this pool, and once again publish the topology. In this last step, you also have the option of adding another Edge server to the legacy Edge pool if required. After any additions or deletions to Edge Server pools, you must publish the topology.

9. In Specify Internal Edge Settings Information, enter the relevant information for yourEdge pool’s internal FQDN and ports as needed, and then click Next.

10. In Specify External Edge, enter the Web Conferencing FQDN information for your Edge Server.

Important:Before you click Next, do the next step in this procedure. It’s very important th


47

at you don’t miss step 11.

11. Check the This Edge pool is used for federation and public IM connectivity checkbox if you plan to use this Edge Server for federation. If you have multiple Edge Servers deployed, only one of them will be enabled for federation. If you do not check this box and you decide later that you want to enable federation, you must run the Topology Builder Merge wizard again, as well as publish your topology.

12. In Specify Next Hop, enter the FQDN of the next hop location in your environment. Inthe figure below, the legacy Director from the Office Communications Server 2007 R2deployment is shown. Click Finish.


48

13. In Specify Edge Setup, if all your Communications Server 2007 R2 Edge Servers have been added, click Next. If you have more Communications Server 2007 R2 Edge Servers to add, repeat steps 6 through 12.

14. In Specify Internal SIP port setting, select the default setting (that is, if you did not modify the default SIP port). Change as appropriate if you are not using a default port of5061. Click Next.

15. In Summary, click Next to begin merging the topologies.

16. The wizard page verifies that the merging of the topologies was successful.

17. In the Status column, verify that the value is Success and then click Finish to close the wizard.

18. In the left pane of Topology Builder, you should now see the BackCompatSite, which indicates that your Office Communications Server 2007 R2 environment has been merged with Lync Server 2010.


49

19. From the Actions pane, select Publish Topology, and then click Next.20. When the Publishing wizard completes, click Finish to close the wizard.

Note:It’s important that you complete the next topic, Import Policies and Settings toensure that the legacy policy settings are imported into Lync Server 2010.

Import Policies and Settings

After you merge your Microsoft Office Communications Server 2007 R2 topology information withyour Microsoft Lync Server 2010 pilot pool, you need to run a Lync Server Management Shellcmdlet to migrate your Office Communications Server 2007 R2 policies and configuration settingsto your Lync Server 2010 pilot pool.

The Import-CsLegacyConfiguration cmdlet imports policies, voice routes, dial plans,Communicator Web Access URLs, and dial-in access numbers to Lync Server 2010.


50

Note:Dial-in access numbers require an additional step to complete the migration to LyncServer 2010. During this period of coexistence, the dial-in access numbers that youimported exist both in your Office Communications Server 2007 R2 pool and in your LyncServer 2010 pool, but they cannot be modified in Lync Server 2010. They can bemodified in Office Communications Server 2007 R2, and then imported into Lync Server2010 by running Import-CsLegacyConfiguration. In addition, you cannot view OfficeCommunications Server 2007 R2 dial-in conferencing access numbers by using the Get-CsDialInConferencingAccessNumber cmdlet. You can view only Lync Server 2010dial-in access numbers by using this cmdlet. For details about how dial-in accessnumbers behave during coexistence, see Migrate Dial-in Access Numbers.

Note:

To migrate policies and settings

1. Log on to the Standard Edition server or Front End Server with an account that is a member of the RTCUniversalServerAdmins group.

2. From the Standard Edition server or Front End Server, click Start, then All Programs,then Microsoft Lync Server 2010, then Lync Server Management Shell.

3. Run:Import-CsLegacyConfiguration

Important:It’s a good practice to run this cmdlet whenever the Topology Builder Merge wizard, covered in the topic Merge Using Topology Builder Merge Wizard, is run.

Note:The Import-CsLegacyConfiguration cmdlet does not migrate PIN policy for dial-in conferencing. If you do not want to use the default PIN policy on Lync Server 2010, you need to modify the policy manually in your Lync Server 2010 pool. For details on how to modify PIN policy, see Modify the Default Dial-in Conferencing PIN Settings in the Deployment documentation.

Note:If the Anonymous Participants setting for Meetings is set to Enforce per user in your Office Communications Server 2007 R2 conferencing policy, two conferencing policies are created during migration: one with AllowAnonymousParticipantsInMeetings set to True and one with AllowAnonymousParticipantsInMeetings set to False.

Now that the policies have been imported, use the procedure that follows to see the imported policies in the Lync Server 2010 Control Panel.


51

To view imported policies

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or an account that is a member of the CsViewOnlyAdministrator role.


3. Click Voice Routing and view the imported policies.

4. Click Conferencing and view the imported policies.

5. Click External User Access and view the imported policies.

6. And finally, click Monitoring and Archiving and view the imported policies.

See Also(Optional) Verify PIN Policy Settings

Verify Topology InformationThe first step in verifying the merge completed successfully is to view the Microsoft OfficeCommunications Server 2007 R2 topology information that you merged with Microsoft LyncServer 2010. In Topology Builder, the BackCompatSite node displays the fully qualified domainname (FQDN) of each Office Communications Server 2007 R2 pool and server that you merged.

Note:If you have scaled Edge Servers, only the pool-level FQDN is displayed, not the FQDN ofeach server within the pool.

The following illustration is an example of a BackCompatSite node after merging an OfficeCommunications Server 2007 R2 Standard Edition server, a Director, an Edge Server, and astand-alone Mediation Server. You cannot edit any properties for these components. Use theBackCompatSite node to verify that all the Office Communications Server 2007 R2 pools andservers merged successfully.

To view BackCompatSite in Topology Builder

1. In your Office Communications Server 2007 R2 environment, open the Office Communications Server 2007 R2 administrative tool and note the FQDNs for the pools and servers that you want to merge.

2. In your Lync Server 2010 environment, open Topology Builder, and then expand the BackCompatSite node.

3. Verify that the FQDNs for the pools and servers that you merge are displayed.

Note:You do not see any information in BackCompatSite for server roles that are collocated on a Front End Server or Standard Edition server. Only server roles that are required for interoperability between Office Communications Server 20


52

07 R2 and Lync Server 2010 are merged.

You can also use Microsoft Lync Server 2010 Control Panel to view your merged topology. InLync Server Control Panel, you can see each server FQDN, pool FQDN, and site name for yourmerged topology. Merged servers have a Site name of BackCompatSite.

To view the merged topology in Lync Server Control Panel


2. On the Select URL page, select the Standard Edition server or Front End pool that corresponds to your pilot stack deployment.

3. Click Topology.4. On the Status tab, verify that servers and pools you merged appear by looking for Bac

kCompatSite in the Site column.


53

To see more detail about a merged pool, use the Get-CsPool cmdlet. In addition to theinformation that is available in Topology Builder and Lync Server Control Panel, this cmdletdisplays the services that run on the pool.

Note:When you publish the topology after running the Merge wizard in Topology Builder,conference directories are merged to Lync Server 2010. Conference Directories can beverified by running the Get-CsConferenceDirectory cmdlet.

To view services on a merged pool

1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

2. Run:Get-CsPool [-Identity <FQDN of the pool>]For example:Get-CsPool –Identity lync-se.contoso.net

To verify conference directories merged

1. In your Lync Server 2010 environment, open Lync Server Management Shell.

2. Run:


54

Get-CsConferenceDirectory3. Verify that all the conference directories for the pool or server you are merging are now

in Lync Server 2010.

Note:Each conference directory hosted on a pool is listed in the output of the Get-CsConferenceDirectory cmdlet. The FQDN of the pool that hosts the Conference Directory is displayed in ServiceId. ServiceId contains the type of serviceand FQDN of the pool. For example, UserServer:OCS2007R2.contoso.com

Phase 5: Configure the Pilot PoolNow that the pilot pool has been created and legacy deployment information has been mergedwith Lync Server 2010, this section identifies a few configurations that must be made to the pilotpool.

In This Section Connect Pilot Pool to Legacy Edge Servers

Authorize Connection to Office Communications Server 2007 R2 Edge Server

Connect Pilot Pool to Legacy Mediation Server

Move Legacy User to Pilot Pool

Move Multiple Users

Verify User Replication has Completed

Connect Pilot Pool to Legacy Edge ServersAfter deploying Lync Server 2010, a federation route for this site is not configured. In order to usethe federated route being used by Office Communications Server 2007 R2, Lync Server 2010must be configured to use this route.

To enable the Lync Server 2010 site to use the Director and Edge Server of the BackCompatSite,you must associate the legacy Edge pool by using Topology Builder.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper rights and permissions. Fordetails, see Delegate Setup Permissions in the Deployment documentation. For otherconfiguration changes, only membership in the RTCUniversalServerAdmins group is required.

Associate the legacy Edge pool using Topology Builder

1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.

2. Select your Lync Server 2010 site.


55

3. On the Actions menu, click Edit Properties.4. Under Site federation route assignment select Enable and choose the Office Comm

unications Server 2007 R2 Director listed.

Note:If you are not able to edit the Site federation route assignment setting that means an Edge Server was not selected when the Topology Builder Merge wizard was run. To enable this setting, see step 11 of the topic Merge Using Topology Builder Merge Wizard.

5. Click OK to close the Edit Properties page.6. In Topology Builder, navigate to the Standard Edition server or Front End pool, right

click the pool and select Edit Properties.7. Under Associations check the box next to Associate Edge pool (for media compon

ents).8. From the drop down list, select the Edge Server for the BackCompatSite.


56

9. Click OK to close the Edit Properties page.10. In Topology Builder, select the top-most node Lync Server 2010.11. From the Actions pane, select Publish Topology and then click Next.12. When the Publishing wizard completes, click Finish to close the wizard.

Authorize Connection to Office Communications Server 2007 R2 EdgeServerFor each Lync Server 2010 Front End Server or Standard Edition server and each Director inyour pilot pool, you must update the list of internal servers that are authorized to connect to theOffice Communications Server 2007 R2 Edge Server. Without these updates, external A/Vconferencing for users joining by using the legacy Edge Server will not work. This topic explainshow to add the Lync Server 2010 Front End Server or Standard Edition server and Director inyour pilot pool to the list of servers that are authorized to connect to the Office CommunicationsServer 2007 R2 Edge Server.


57

Authorize Connection to Office Communications Server 2007 R2 Edge Server

1. Log on to the Office Communications Server 2007 R2 Edge Server with an account that is a member of the RTCLocalServerAdmins group.

2. From the Office Communications Server 2007 R2 Edge Server, from the Administrative Tools group, open the Computer Management snap-in.

3. In the console tree, expand Services and Applications.4. Right-click Office Communications Server 2007 R2 and select Properties.5. Click the Internal tab.6. Under Add Server click Add.7. In the Add Office Communications Server dialog box, specify the appropriate inform

ation:

Specify the FQDN of each Lync Server 2010 Front End Server or Standard Editionserver.

Specify the FQDN of the Lync Server 2010 Director if you configured a static routeon the pool that specifies the next hop computer by its FQDN.

8. After you have added an entry for each Lync Server 2010 Front End Server or Standard Edition server and Director, click OK to close the Properties page.

Connect Pilot Pool to Legacy Mediation ServerAfter deploying Microsoft Lync Server 2010, a Mediation Server for this site is not configured. Inorder to use the Mediation Server being used by Microsoft Office Communications Server 2007,Lync Server 2010 must be configured to use this server.

Providing a Voice Route and Voice Policy existed in the legacy pool, after merging OfficeCommunications Server 2007 R2 with Lync Server 2010, and running the Import-CsLegacyConfiguration cmdlet, the Lync Server 2010 pilot pool now has all the necessaryconfiguration information to

route outbound calls through the legacy Office Communications Server 2007 R2 MediationServer

route inbound calls from the legacy pool to the Lync Server 2010 pool

Note:Lync Server 2010 Mediation Server features will not be functional until all MediationServer components are configured, which occurs later in this document. For details aboutconfiguring Lync Server 2010 Mediation Server, see Migrate Mediation Server.


58

Note:For details about finding qualified PSTN gateways, IP-PBXs and SIP Trunking servicesthat work with Lync Server 2010, see "Microsoft Unified Communications OpenInteroperability Program" at http://go.microsoft.com/fwlink/?LinkId=206015.

To enable the Lync Server 2010 pilot pool to use the legacy Mediation Server, you must have aVoice Route and Voice policy configured that point to the legacy Mediation Server. If you do nothave a legacy Voice Route or Voice Policy, use the following the procedure to configure thesesettings using Lync Server 2010 Control Panel or by using the Lync Server Management Shell.

To create a Voice Route to the legacy Mediation Server using Lync Server ControlPanel

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or minimally a member of the CsVoiceAdministrator administrative role.


3. Click Voice Routing, and then select the Route tab.4. Click New to create a New Voice Route.

5. Fill in the following fields:

Name: enter a descriptive name of the voice route. For this document we will useW13PSTNRoute.

Description: enter a short description of the voice route.6. Skip all remaining sections until you reach Associated gateways. Click Add. Select th

e default gateway listed and click OK.7. Under Associated PSTN Usages, click Select.8. From the Select PSTN Usage Record page, select the legacy Mediation Server FQD

N and then click OK.9. From the New Voice Route page, click OK to create the Voice Route.10. From the Voice Routing page, select Route.11. Move the newly created route to the top of the list and then select Commit.

To create a Voice Route to the legacy Mediation Server using Lync ServerManagement Shell

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or minimally a member of the CsVoiceAdministrator administrative role.



59

3. Get the FQDN of the legacy Mediation Server by running the following command:Get-CsService –MediationServerThe Identity parameter will contain the name of the legacy Mediation Server. In this example, the value is MediationServer:medsvr01.contoso.net

4. Next, verify that a voice policy exists for the legacy Mediation Server by running the following command:Get-CsVoicePolicyThe PSTNUsages parameter should not be empty, but return a value of {Local} or thename of any customer PSTNUsage created on the legacy Mediation Server.

5. Now that we have verified that a legacy Mediation Server exists and it has a voice policy, we create a route in the Lync Server 2010 pool that points to this legacy Mediation Server.

The following code defines a generic voice route that routes any outbound calls from the Lync Server 2010 pool to the legacy Mediation Server.New-CsVoiceRoute -Name W13PSTNRoute -NumberPattern ".*" -PstnUsages Local -PstnGatewayList @{Add="MediationServer:medsvr01.contoso.net "}

6. Finally, run the following command to set the default voice route for this pool.Set-CsVoiceRoute -Identity W13PSTNRoute -Priority 0

7. Run the Get-CsVoiceRoute to verify the voice route settings.

For our example, the Identity parameter should be set toW13PSTNRoute. The PSTNUsages should be set to {Local} and the PSTNGatewayList should point to the FQDN of the legacy Mediation Server, Mediation:medsvr01.contoso.net.

Move Legacy User to Pilot PoolYou can move a pilot user to the new Microsoft Lync Server 2010 deployment using the followingtwo methods: Microsoft Lync Server 2010 Control Panel and Lync Server Management Shell.There are requirements that must be met to ensure a smooth transition to Lync Server 2010. Fordetails before completing the procedures in this topic, see Configure Clients for Migration.

Important:You cannot use the Active Directory Users and Computers snap-in or the Microsoft OfficeCommunications Server 2007 R2 administrative tools to move users from your legacyenvironment to Lync Server 2010.

Important:The Move-CsLegacyUser cmdlet requires that user names are properly formed and donot have leading or trailing spaces. You cannot move a user account using the Move-


60

CsLegacyUser cmdlet if it contains leading or trailing spaces.

When you move a user to a Lync Server 2010 pool, the data for the user is moved to the back-end database that is associated with the new pool.

Important:Please note that this data includes the active meetings created by the legacy user. Forexample, if a legacy user has configured a my meeting conference, that conference willstill be available in the new Lync Server 2010 pool after the user has been moved. Thedetails to access that meeting will still be the same conference URL and conference ID.The only difference is that the conference is now hosted in the Lync Server 2010 pool,and not in the Office Communications Server 2007 R2 pool.

Note:Homing users on Lync Server 2010 does not require that you deploy upgraded clients atthe same time. New functionality will be available to users only when they have upgradedto the new client software.

The following figure shows users enabled for Office Communications Server 2007 R2 in theOffice Communications Server 2007 R2 administrative tool. These users will be moved to LyncServer 2010 using the Lync Server 2010 Control Panel or the Lync Server Management Shell.

The following figure provides a view of these same users in Lync Server 2010 Control Panel. TheRegistrar pool column entry for each user is set to Legacy, which indicates that these users arestill homed on Office Communications Server 2007 R2 and have not been moved to Lync Server2010.


61

To move a user by using the Lync Server 2010 Control Panel

1. Log onto a Standard Edition server or Front End Server with an account that is a member of the RTCUniversalServerAdmins group or a member of the CSAdministrator or CsUserAdministrator administrative role.

2. Click Start, then All Programs, then Microsoft Lync Server 2010, then Lync ServerControl Panel.

3. Click Users, click Add Filter, build the following query Legacy user Equal to True, and then click Find.

4. In the search results, select a user.

Note:Notice that the Registrar Pool column shows <Legacy>. This means that theuser you have selected is homed on Office Communications Server 2007 R2.

5. Click Action and then click Move selected users to pool.


62

Important:If Move selected users to pool is not available, ensure the account is a member of the CSAdministrator or CSUserAdministrator group.

6. In Move Users, select the Destination registrar pool, which is your Lync Server 2010pool, and then click OK.

7. Verify that the Registrar pool column for the user now contains the Lync Server 2010pool, which indicates that the user has been successfully moved.

To move a user by using the Lync Server 2010 Management Shell


2. Ensure the user account you are using is a member of the RTCUniversalServerAdmins group or a member of the CSAdministrator or CSUserAdministrator administrative role.

3. At the command line, type the following:

Get-CsUser –OnOfficeCommunicationServerUsing a legacy user’s sip address as a parameter, run the Move-CsLegacyUser cmdlet.


63

Move-CsLegacyUser –Identity "sip address" –Target "pool_FQDN"

As an example, to move one of the legacy users to the Lync Server 2010 pilot pool, wewould run:Move-CsLegacyUser –Identity "sip:[email protected]" –Target "lync-se.contoso.net"


Get-CsUser "sip address"The RegistrarPool identity now points to the pool you specified as “pool_name” in theprevious step. The presence of this identity confirms that the user has been successfully moved.

For more details about the Get-CsUser cmdlet described in this section, run: Get-Help Get-CsUser -Detailed

5. By using the Lync Server Control Panel, you can also verify that these users have been moved by viewing the Registrar pool column.

ImportantTo return a user to a legacy Office Communications Server 2007 R2 pool, or to move a user between Lync Server 2010 pools, see Move-CsUser in the Lync Server Management Shell documentation. For more details about the Move-CsUser cmdlet, run:Get-Help Move-CsUser

ImportantThe Move-CsLegacyUser cmdlet may fail with the following error:Move-CsLegacyUser : SetMoveResourceData failed because the user isnot provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< -Identity "[email protected]" -Target "lync-se.contoso.net" + CategoryInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId :MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLegacyUserCmdletIf you experience this error, see Verify User Replication has Completed for resolution.

Move Multiple UsersYou can move groups of users to the new Microsoft Lync Server 2010 deployment using thefollowing two methods: Lync Server Control Panel and Lync Server Management Shell. There arerequirements that must be met to ensure a smooth transition to Lync Server 2010. For detailsbefore completing the procedures in this topic, see Configure Clients for Migration.


64


Important:The Move-CsLegacyUser cmdlet requires that user names are properly formed and donot have leading or trailing spaces. You cannot move a user account using the Move-CsLegacyUser cmdlet if it contains leading or trailing spaces.


Important:This data includes the active meetings created by the legacy user. For example, if alegacy user has configured a my meeting conference, that conference will still beavailable in the new Lync Server 2010 pool, after the user has been moved. The detailsto access that meeting will still be the same conference URL and conference ID. Theonly difference is that the conference is now hosted in the Lync Server 2010 pool, andnot in Office Communications Server 2007 R2 pool.


To move multiple users by using the Lync Server Control Panel

1. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins group or minimally a member of the CsUserAdministrator administrative role.


3. Click Users, click Add Filter, build the query Legacy user Equal to True, and then click Find.

4. In the search results, select at least two users.


Important:If Move selected users to pool is not available, ensure the account is a member of the RTCUniversalUserAdmins group or a member of the CSAdministrator or CSUserAdministrator administrative role.

6. In Move Users, select the Destination Registrar pool, which is your Lync Server 201


65

0 pool, and then click OK.7. Verify that the Registrar pool column for the user now contains the Lync Server 2010

pool, which indicates that the user has been successfully moved.

For more details about the cmdlets described in this section, run:Get-Help <cmdlet name> -Detailed

To move multiple users by using the Lync Server Management Shell



3. At the command line, type the following and replace User1 and User2 with specific user names you want to move and replace pool_FQDN with the name of the destinationpool:

Get-CsUser –Filter {DisplayName –eq “User1” –or DisplayName – eq“User2”} | Move-CsLegacyUser –Target “pool_FQDN”

4. At the command line, type the following

Get-CsUser “User1”

The Registrar Pool identity should now point to the pool you specified as “pool_FQDN” in the previous step. The presence of this identity confirms that the user has been successfully moved.


66

To move all users at once by using the Lync Server Management Shell



Get-CsUser –OnOfficeCommunicationServer | Move-CsLegacyUser –Target “pool_FQDN”


Get-CsUser “user name”where user name is the name of a legacy user.

The Registrar Pool identity now points to the pool you specified as “pool_FQDN” in the previous step. The presence of this identity confirms that the user has been successfully moved.

ImportantThe Move-CsLegacyUser cmdlet may fail with the following error:Move-CsLegacyUser : SetMoveResourceData failed because the user isnot provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< -Identity "[email protected]” -Target "lync-se.contoso.net" + CategoryInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId :MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLegacyUserCmdletIf you experience this error, see the topic Verify User Replication has Completed for resolution.

Verify User Replication has CompletedWhen running the Move-CsUser and Move-CsLegacyUser cmdlets, you may experience afailure due to the initial replication of user information between Active Directory Domain Services(AD DS) and the Lync Server 2010 databases being out of sync. The time it takes for thesuccessful completion of the Lync Server 2010 User Replicator service's initial synchronizationdepends on the number of domain controllers that are hosted in the Active Directory forest thathosts the Lync Server 2010 pool. The Lync Server 2010 User Replicator service initialsynchronization process occurs when the Lync Server 2010 Front End Server is started for thefirst time. After that, the synchronization is then based on the User Replicator interval. Completethe following steps to verify user replication has completed before running the Move-CsUser and


67

Move-CsLegacyUser cmdlets.

Verify User Replication has completed

1. From a Lync Server 2010 Standard Edition server, from the Start menu, click Run.2. Enter eventvwr.exe and click OK.3. When Event Viewer opens, expand Applications and Services logs.4. Select Lync Server.

5. In the Actions pane click Filter Current Log.6. From the Event sources drop down list select LS User Replicator.7. In <All Event IDs> enter the event ID 30024 and then click OK.8. In the filtered events list, on the General tab, look for an entry that states user replicati

on has completed successfully.

Phase 6: Verify Your Pilot MigrationVerify that the migration completed successfully by following the steps described in this section.Verifying your migration encompasses two general areas:

Verifying the policies and configuration settings that you imported from an earlier version ofOffice Communications Server by using the Import-CsLegacyConfiguration cmdlet.

Running functional tests against each Microsoft Lync Server 2010 workload. This step isoptional.

In This Section Verify Configuration Settings

Run Functional Tests Against Workloads (optional)

Verify Configuration SettingsAfter you merge the topology and run the Import-CsLegacyConfiguration cmdlet, verify thatyour Microsoft Office Communications Server 2007 R2 policies and settings were imported toMicrosoft Lync Server 2010. The following table lists the policies and settings that you shouldverify.

Policies and Settings to Verify after MigrationIf you use this workload: Verify these policies and settings:

Instant messaging (IM) and conferencing Presence policy

Conferencing policy

Dial-in conferencing Dial-in access numbers

Dial plans


68

Enterprise Voice Voice policy

Voice routes

Dial plans

PSTN usage settings

Communicator Web Access Simple URLs

External users External access policies

Archiving Archiving policy

For most of these policies and settings you can use either Microsoft Lync Server 2010 ControlPanel or Lync Server Management Shell cmdlets. For the presence policy, however, you mustuse a cmdlet.

Note:To verify policies, you can compare the policy names that you have in your OfficeCommunications Server 2007 R2 deployment to the names that are now in Lync Server2010 to ensure that all the policies were imported. It is not necessary to compare all thesettings within a policy.

Note:For Mediation Server, legacy configuration settings like server ports and protocols are notmerged to Lync Server 2010. The administrator can configure these settings using theTopology Builder. Additionally, the default encryption level for Lync Server 2010Mediation Server is RequireEncryption. Ensure that your legacy Office CommunicationsServer 2007 R2 pool matches this default encryption level setting.

To verify policies and settings

1. In your Office Communicator 2007 R2 environment, make note of the names of dial plans (formerly known as location profiles), dial-in access numbers (Conferencing Attendant access phone numbers and regions), voice routes, and the policies listed in the preceding table, as well as the URLs used for Communicator Web Access.

2. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins or RTCUniversalServerAdmins group or minimally is a member of the CsViewOnlyAdministrator administrative role.


4. To verify imported conferencing policies, click Conferencing, click Conferencing Policy, and then verify that all the conferencing policies in your Office Communicator 2007R2 environment are included in the list.


69

Note:The Meeting policy from previous versions of Office Communications Server isnow known as the conferencing policy in Lync Server. Additionally, the Anonymous Particpants setting from previous versions of Office Communications Server is now a setting in the Lync Server conferencing policy.

Note:In Office Communications Server 2007 R2, if the conferencing policy is not setto use per user, only global policy settings are imported. No other conferencepolicies are imported in this situation.

Note:If Anonymous Participants is set to Enforce per user in your Office Communications Server 2007 R2 conferencing policy, two conferencing policies are created during migration: one with AllowAnonymousParticipantsInMeetings set to True and one with AllowAnonymousParticipantsInMeetings set to False.

5. To verify imported dial plans, click Voice Routing, click Dial Plan, and then verify thatall the dial plans in your Office Communicator 2007 R2 environment are included in thelist.

Note:In Lync Server 2010, location profiles are now referred to as dial-plans.

6. To verify imported voice policies, click Voice Routing, click Voice Policy, and then verify that all the voice policies in your Office Communicator 2007 R2 environment are included in the list.

Note:If voice policy is not set to use per user in your Office Communications Server2007 R2 environment, only global policy settings are imported. No other voicepolicies are imported in this situation.

7. To verify imported voice routes, click Voice Routing, click Route, and then verify thatall the voice routes in your Office Communicator 2007 R2 environment are included in the list.

8. To verify imported PSTN usage settings, click Voice Routing, click PSTN Usage, andthen verify that the PSTN Usage settings from your Office Communicator 2007 R2 environment are included in the list.

9. To verify imported external access policies, click External User Access, click External Access Policy, and then verify that all the external access policies in your Office Communicator 2007 R2 environment are included in the list.

10. To verify archiving policies, click Monitoring and Archiving, click Archiving Policy, and then verify that all the archiving policies in your Office Communications Server 2007R2 environment are included in the list.


70

11. Start the Lync Server Management Shell: Click Start, click All Programs, click oftMicros Lync Server 2010, and then click Lync Server Management Shell.

12. To verify presence policies, run:Get-CsPresencePolicyBy looking at the name in the Identity parameter, verify that all the presence policies inyour Office Communications Server 2007 R2 environment were imported.

To verify policies and settings by using cmdlets

1. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins or RTCUniversalServerAdmins group or minimally is a member of the CsViewOnlyAdministrator administrative role.


3. Run the cmdlets in the following table to verify policies and settings.

The syntax of these cmdlets is like the following example:Get-CsConferencingPolicyFor details about these cmdlets, run:Get-Help <cmdlet name> -Detailed

Cmdlets to Verify Configuration Settings

For this policy or setting: Use this cmdlet:

Presence policy Get-CsPresencePolicy

Conferencing policy Get-CsConferencingPolicy

Note:If conferencing policy is not set to use per user inyour Office Communications Server 2007 R2 environment, only global policy settings are imported.No other conferencing policies are imported in this situation.

Note:


71

If AnonymousParticipants is set to Enforce peruser in your Office Communications Server 2007R2 conferencing policy, two conferencing policiesare created during migration: one with nymousPAllowAnoarticipantsInMeetings set to True andone with ngsAllowAnonymousParticipantsInMeeti set to False.

Note:To enable federated users from your legacy Office Communications Server 2007 R2 deployment to join meetings scheduled by Lync Server 2010 users, the meeting policy assigned to the Lync Server 2010 user must allow anonymous scheduling.To configure anonymous scheduling, from the Lync Server Management Shell run Get-CsConferencingpolicy , then run Set-CsConferencingPolicy –Identity <ConferencingPolicyName> -AllowAnonymousParticipantsInMeetings$True

Dial-in access numbers Get-CsDialInConferencingAccessNumber

Note:This cmdlet returns only Lync Server 2010 dial-inaccess numbers. It does not return any Office Communications Server 2007 R2 dial-in access numbers.

Dial plans Get-CsDialPlan

Voice policy Get-CsVoicePolicy

Note:If voice policy is not set to use per user in your Office Communications Server 2007 R2 environment, only global policy settings are imported. No other voice policies are imported in this situation.

Voice routes Get-CsVoiceRoute

PSTN Usage Get-CsPstnUsage

URLs Get-CsSimpleUrlConfiguration


72

External access policies Get-CsExternalAccessPolicy

Archiving policy Get-CsArchivingPolicy

Run Functional Tests Against Workloads (optional)After verifying that topology information and configuration settings were merged correctly, youshould perform some functional tests to verify that the various workloads perform as expected.Run tests for each workload that you are deploying, starting with peer-to-peer sessions and thenexpanding to meetings of three or more participants. Include remote users and federated users toverify that external access works as expected.

Note:Although you perform these functional tests before the client rollout, you should deployMicrosoft Lync 2010 to a couple trial users homed on Microsoft Lync Server 2010 to usein these tests.

This section describes some example scenarios:

Functional Test Scenarios

Remote Office Communications Server 2007 R2 User and Internal Lync Server 2010 UserUsers

Remote user who is homed on Office Communications Server 2007 R2

Internal user who is homed on Lync Server 2010Scenarios1. The remote user calls the internal user and uses instant messaging (IM), desktop sharing,

and audio/video.

2. The internal user calls the remote user and uses IM, desktop sharing, and audio/video.

3. The remote user adds a third user, who is homed on Lync Server 2010, to a current IMsession. They use desktop sharing, and audio/video.

4. The internal user adds a third user, who is homed on Office Communications Server 2007R2, to a current IM session. They use desktop sharing, and audio/video.

Remote Office Communications Server 2007 R2 User and Remote Lync Server 2010 UserUsers


Remote user who is homed on Lync Server 2010Scenarios1. The remote Office Communications Server 2007 R2 user calls the remote Lync Server 2010

user and uses instant messaging (IM), desktop sharing and audio/video.


73

2. The remote Lync Server 2010 user calls the remote Office Communications Server 2007 R2user and uses IM, desktop sharing and audio/video.

3. The remote Lync Server 2010 user adds a third user, who is homed on Lync Server 2010 to acurrent IM session. They use desktop sharing and audio/video.

4. The remote Lync Server 2010 user adds a third user, who is homed on OfficeCommunications Server 2007 R2 to a current IM session. They use desktop sharing andaudio/video.

5. The remote Office Communications Server 2007 R2 user adds a third user, who is homed onLync Server 2010 to a current IM session. They use desktop sharing and audio/video.

6. The remote Office Communications Server 2007 R2 user adds a third user, who is homed onOffice Communications Server 2007 R2 to a current IM session. They use desktop sharingand audio/video.

Remote Lync Server 2010 User and Internal Office Communications Server 2007 R2 UserUsers

Remote user who is homed on Lync Server 2010

Internal user who is homed on Office Communications Server 2007 R2Scenarios1. The remote user calls the internal user and uses IM, desktop sharing, and audio/video.

2. The internal user calls the remote user and uses IM, desktop sharing, and audio/video.

3. The remote user adds a third user, who is homed on Office Communications Server 2007 R2,to a current IM session. They use desktop sharing, and audio/video.

4. The internal user adds a third user, who is homed on Lync Server 2010, to a current IMsession. They use desktop sharing, and audio/video.

Unscheduled ConferencingUsers

Internal user who is homed on Office Communications Server 2007 R2

Internal user who is homed on Lync Server 2010Scenarios1. A user homed on Office Communications Server 2007 R2 sets up an unscheduled (Meet

Now) A/V conference and invites a user homed on Lync Server 2010 and a user homed onOffice Communications Server 2007 R2.

2. A user homed on Lync Server 2010 sets up an unscheduled (Meet Now) A/V conference andinvites a user homed on Lync Server 2010 and a user homed on Office CommunicationsServer 2007 R2.

3. A user homed on Office Communications Server 2007 R2 shares the desktop during aconference.

4. A user homed on Lync Server 2010 shares the desktop during a conference.

5. A user homed on Lync Server 2010 shares a PowerPoint presentation during a conference.

Dial-in Conference Hosted on Office Communications Server 2007 R2


74

Users




Internal user who is homed on Lync Server 2010Scenarios

An internal Office Communications Server 2007 R2 user organizes a dial-in meeting(scheduled or unscheduled) that is hosted on Office Communications Server 2007 R2. Aremote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, andan internal Lync Server 2010 user join the meeting.

A remote Office Communications Server 2007 R2 user and a remote Lync Server 2010 userdial in to the conference.

Dial-in Conference Hosted on Lync Server 2010Users

Internal user who is homed on Lync Server 2010



Internal user who is homed on Office Communications Server 2007 R2Scenarios

An internal Lync Server 2010 user organizes a dial-in meeting (scheduled or unscheduled)that is hosted on Lync Server 2010. A remote Office Communications Server 2007 R2 user, aremote Lync Server 2010 user, and an internal Office Communications Server 2007 R2 userjoin the meeting.

A remote Office Communications Server 2007 R2 user and a remote Lync Server 2010 userdial in to the conference.

Conference Hosted on Office Communications Server 2007 R2 with Application SharingModalityUsers





Federated userScenarios

An Office Communications Server 2007 R2 internal user organizes a conference withapplication sharing modality. The conference is hosted on Office Communications Server2007 R2.

A remote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, aninternal Lync Server 2010 user, and a federated user join the meeting.


75

All users can view the shared desktop or application of the Office Communications Server2007 R2 internal user.

All other users in the meeting can start sharing in the same conference.

Conference Hosted on Lync Server 2010 with Application Sharing ModalityUsers





Federated userScenarios

A Lync Server 2010 internal user organizes a conference that is hosted on Lync Server 2010and adds the application sharing modality to the conference.

A remote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, aninternal Office Communications Server 2007 R2 user, and a federated user join the meeting.

All users can view the shared desktop or application of the Lync Server 2010 internal user.

All other users in the meeting can start sharing in the same conference.

Person-to-Person FederationUsers

A user who is homed on Lync Server 2010

A federated userScenarios

A Lync Server 2010 user calls a federated user. They use IM, audio/video, and desktopsharing.

A federated user calls a Lync Server 2010 user. They use IM, audio/video, and desktopsharing.

VoiceUsers




Remote user who is homed on Office Communications Server 2007 R2Scenarios:

A Lync Server 2010 user (internal or remote) calls a Office Communications Server 2007 R2user (internal or remote), puts the call on hold, and then resumes the call. One of the callingparties transfers the call to another user (Lync Server 2010 or Office Communications Server2007 R2 (internal or remote).

An Office Communications Server 2007 R2 user (internal or remote) calls a Lync Server 2010


76

user (internal or remote). One of the parties transfers the call to a public switched telephonenumber (PSTN).

A PSTN caller calls a Lync Server 2010 user. The Lync Server 2010 user transfers the call toa Office Communications Server 2007 R2 user.

A Lync Server 2010 user calls a PSTN and then transfers the call to an OfficeCommunications Server 2007 R2 user.

A Lync Server 2010 user sets a call forwarding rule with the call forwarding destination as aOffice Communications Server 2007 R2 user. The number is forwarded to the correctdestination.

A PSTN caller calls a Lync Server 2010 user. The Lync Server 2010 user parks the call, andanother Lync Server 2010 user retrieves the call.

Phase 7: Add Lync Server 2010 Edge Server and Director to PilotPoolThe topics in this section explain how to add a Lync Server 2010 Director and an Edge Server tothe pilot pool deployment. The topics provide configuration and verification guidance whenrunning the Deploy Director pool and the Deploy New Edge pool wizards.

In This Section Deploy Pilot Director and Edge Servers

Deploy Pilot Director and Edge ServersThis topic highlights configuration settings you should be aware of prior to deploying your LyncServer 2010 Edge Server and Director. The deployment and configuration processes for LyncServer 2010 are much different than in previous releases because Lync Server 2010 providesnew tools for installation and administration that change the way that you work with Lync Servercomponents. This section only highlights key points you should consider as part of your pilot pooldeployment. For detailed steps, see Deploying Edge Servers in the Deployment documentation,which describes the deployment process and also gives configuration information for externaluser access.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding serverroles. For details, see Delegate Setup Permissions in the Standard Edition server or EnterpriseEdition server deployment documentation. For other configuration changes, only membership inthe RTCUniversalServerAdmins group is required.

Define a Director Pool


77


2. On the welcome page, click Download Topology from Existing Deployment, and then save a local copy to a file.

3. In the left pane, expand the tree view, right click Director pools, and select New Director Pool.

4. On the Define the Director pool FQDN page, specify the computer fully qualified domain name (FQDN) (lync-dir.contoso.net for our example), select the Single computer pool option, and then click Next.

5. On the Define the file share page, select Use a previously defined file share or Define a new file share, and then click Next.

Note:The file share assigned to a Director is not actually used, so you can assign the file share of any pool in the organization.

6. On the Specify the Web Services URL page, specify the FQDN for the Director’s External Base URL, and then click Finish. The name must be resolvable from Internet DNS servers and point to the public IP address of the Reverse Proxy, which listens for HTTP/HTTPS requests to that URL and proxies it to the External Web Services virtual directory on that Director.

As you navigate through the Define New Edge Pool wizard, review the key configuration settingsshown in the following steps. Note that only a few pages of the Define New Edge Pool wizardare shown.

Define an Edge Pool

1. From Topology Builder, right-click Edge pools and then select New Edge pool.


78

2. An Edge pool can be a Multiple computer pool or Single computer pool.


79

3. On the Select features page, do not enable federation. Federation is currently routed through the legacy Office Communications Server 2007 R2 Edge Server. See the topicConfigure Federation Routes and Media Traffic for information on changing the federation route to Lync Server 2010 Edge Servers. This setting will be configured in a later phase of migration.


80

4. Next, continue completing the following wizard pages: External FQDNs, Define the intenral IP address, and Define the external IP address.

5. On the Define the next hop page, select the Director for the next hop of the Lync Server 2010 Edge pool.


81

6. On the Associate Front End pools page, do not associate a pool with this Edge poolat this time. External media traffic is currently routed through the legacy Office Communications Server 2007 R2 Edge Server. This setting will be configured in a later phaseof migration.


82

7. Click Finish and then Publish the topology.

8. Follow the steps in Setting Up the Director in the Deployment documentation to install the files on the new Director, configure certificates, and start the services.

9. Follow the steps in Install Edge Servers in the Deployment documentation to install thefiles on the new Edge Server, configure certificates, and start the services.

It’s very important that you follow the guidelines in the topics Deploying Edge Servers andSetting Up the Director in the Deployment documentation. This section merely provided someguidance on configuration settings when installing these server roles.

You should now have a legacy Office Communications Server 2007 R2 deployed in parallel witha Lync Server 2010 deployment. Each deployment includes an Edge Server, a Director, aMediation Server, and a Standard Edition server. The Mediation Server is collocated on theStandard Edition server in Lync Server 2010. It is configured as stand-alone server in OfficeCommunications Server 2007 R2. Federation for each deployment is through the legacy OfficeCommunications Server 2007 R2 Edge Server.

Verify that both deployments are running properly, services are started, and you can administereach deployment prior to moving to the next phase.


83

Phase 8: Move from Pilot Deployment into ProductionThe topics in this section describe tasks you must complete prior to moving your deployment ofLync 2010 from a pilot deployment to a production-level deployment.

In This Section Configure Federation Routes and Media Traffic

Verify Federation and Remote Access for External Users

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

Move Multiple Users

Migrate Response Groups

Run Functional Tests for Response Groups

Move Exchange Unified Messaging Contact Objects

Verify that all Exchange UM Contact Objects are removed from the Legacy Pool

Configure Federation Routes and Media TrafficFederation is a trust relationship between two or more SIP domains that permits users inseparate organizations to communicate across network boundaries. After you migrate to yourLync Server 2010 pilot pool, you need to transition from the federation route of your MicrosoftOffice Communications Server 2007 R2 Edge Servers to the federation route of your MicrosoftLync Server 2010 Edge Servers.

Use the procedures that follow to transition the federation route and the media traffic route fromyour Office Communications Server 2007 R2 Edge Server and Director to your Lync Server 2010Edge Server and Director, for a single-site deployment.

Important:Changing the federation route and media traffic route requires that you schedulemaintenance downtime for the Lync Server 2010 and Office Communications Server2007 R2 Edge Servers. This entire transition process also means that federated accesswill be unavailable for the duration of the outage. You should schedule the downtime for atime when you expect minimal user activity. You should also provide sufficient notificationto your end users. Plan accordingly for this outage and set appropriate expectationswithin your organization.

ImportantIf your legacy Office Communications Server 2007 R2 Edge Server is configured to use the sameFQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service,the procedures in this section to transition the federation setting to a Lync Server 2010 EdgeServer are not supported. If the legacy Edge services are configured to use the same FQDN, youmust first migrate all your users from Office Communications Server 2007 R2 to Lync Server


84

2010, then decommission the Office Communications Server 2007 R2 Edge Server beforeenabling federation on the Lync Server 2010 Edge Server. For details, see the following topics:

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

"Remove Servers and Server Roles" at http://go.microsoft.com/fwlink/?LinkId=205887

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper user rights for adding serverroles. For details, see Delegate Setup Permissions in the Standard Edition server or EnterpriseEdition server Deployment documentation. For other configuration changes, only membership inthe RTCUniversalServerAdmins group is required.

Remove the Legacy Federation Association from Lync Server 2010 Sites



3. In the Save Topology As dialog box, select the Topology Builder file you want to use,and click Save.

4. In the left pane, navigate to the site node.

5. Right-click the site and select Edit Properties.6. Select Federation route in the left pane.

7. Under Site federation route assignment, select Disable to disable the federation route through the BackCompatSite.


85

8. Click OK to close the Edit Properties page.

9. From Topology Builder, select the top node Lync Server 2010.10. From the Actions pane, select Publish Topology and complete the wizard.

Configure the Legacy Edge Server as a non-Federating Edge Server

1. From Topology Builder, in the Actions pane click Merge 2007 or 2007 R2 .Topology

2. Click Next to continue.

3. On the Specify Edge Setup, select the Edge Server Internal FQDN that is currently configured for federation and then click Change.


86

4. Click Next and accept the default settings until you get to the Specify External Edgepage:


87

5. In Specify External Edge, be sure to clear the This Edge pool is used for federation and public IM connectivity check box. This will remove the federation associationwith the BackCompatSite.

Important:This step is very important. You must clear this option to remove the legacy federation association.

6. Click Next and accept the default settings of the remaining pages of the wizard.

7. In Summary, click Next to begin merging the topologies.

Note:You may see the following message:WARNING : No Office Communications Server 2007 / Office Communications Server 2007 R2 Edge has been enabled for federation. This warning is expected and can be ignored.

8. In the Status column, verify that the value is Success and then click Finish to close the wizard.

9. From the Actions pane, select Publish Topology, and then click Next.10. When the Publishing wizard completes, click Finish to close the wizard.


88

As shown in the previous figure, the Site federation route assignment is set to Disabled.

Configure Certificates on the Lync Server 2010 Edge Server

1. Export the external Access Proxy certificate, with the private key, from the legacy Office Communications Server 2007 R2 Edge Server.

2. On the Lync Server 2010 Edge Server, import the Access Proxy external certificate from the previous step.

3. Assign the Access Proxy external certificate to the Lync Server 2010 external interfaceof the Edge Server.

4. The internal interface certificate of the Lync Server 2010 Edge Server should not be changed.

Change Office Communications Server 2007 R2 Federation Route to use Lync Server2010 Edge Server

1. On the Office Communications Server 2007 R2 Standard Edition server or Front End Server, log on with an account that is a member of the RTCUniversalServerAdmins group.

2. On the Office Communications Server 2007 R2 Standard Edition server or Front End Server, click Start, then Administrative Tools, then Office Communications Server 2


89

007 R2.3. In the left pane, expand the top node and then right click the Forest node. Select Prop

erties, then Global Properties.4. Click the Federation tab

5. Select the check box to enable federation and Public IM connectivity.

6. Enter the FQDN of the Lync Server 2010 Edge Server and then click OK.

Update Lync Server 2010 Edge Server Federation Next Hop

1. Returning to your Lync Server 2010 Standard Edition server or Front End Server, log on to the computer with an account that is a member of the RTCUniversalServerAdmins group.



4. In the left pane, navigate to the Edge pools node.5. Expand the node and right click the Edge Server listed. Select Edit Properties.6. On the General page, under Next hop selection, select from the drop-down list the Ly

nc Server 2010 Edge Server or Director, if a Lync Server 2010 Director was configured


90

.



Configure Lync Server 2010 Edge Server Outbound Media Path

1. From Topology Builder, navigate to the pool below Standard Edition Front End Servers or Enterprise Edition Front End pools.

2. Right click the pool and select Edit Properties.3. In the Associations section, check the box for Associate Edge pool (for media com

ponents).4. From the drop down box, select the Lync Server 2010 Edge Server.


Turn on Lync Server 2010 Edge Server Federation


91

1. From Topology Builder, in the left pane, navigate to the Edge pools node.2. Expand the node and right click the Edge Server listed. Select Edit Properties.

Note:Federation can only be enabled for a single Edge pool. If you have multiple Edge pools, select one to use as the federating Edge pool.

3. On the General page, select the Enable federation for this Edge pool (Port 5061) check box.


5. Next, navigate to the site node.

6. Right click the site and select Edit Properties.7. In the left pane, click Federation route.8. Under Site federation route assignment, select Enable and then from the list select t

he Lync Server 2010 Edge Server or Director Server listed.

9. Click OK to close the Edit Properties page.For multi-site deployments, complete this procedure at each site.


92

Publish Edge Server Configuration Changes


3. Wait for Active Directory replication to occur to all pools in the deployment.

Notes:You may see the following message:

Warning: The topology contains more than one Federated Edge Server. This can occur during migration to a higher version of the product. In that case, only one Edge Server would be actively used for federation. Verify that the external DNS SRV recordpoints to the correct Edge Server. If you want to deploy multiple federation Edge Server to be active concurrently (that is, not a migration scenario), verify that all federated partners are using Office Communications Server 2007 R2 or later. Verify that theexternal DNS SRV record lists all federation enabled Edge Servers.This warning is expected and can be safely ignored.

Configure Lync Server 2010 Edge Server

1. Bring all of the Lync Server 2010 Edge Servers online.

2. Update the external firewall routing rules or the hardware load balancer settings to send SIP traffic for external access (usually port 443) and federation (usually port 5061) tothe Lync Server 2010 Edge Server, instead of the legacy Edge Server.

3. Next, stop the Office Communications Server Access Edge from each Edge Servermachine.

4. From each legacy Edge Server machine, open the Services applet from the Administrative Tools.

5. In the services list, find Office Communications Server Access Edge.6. Right click the services name and select Stop to stop the service.

7. Lastly, set the Startup type to Disabled.8. In the services list, find Office Communications Server Access Edge.9. Right click the services name and select Properties.10. From the drop down list, select Disabled.11. Click OK to close the Properties window.

Verify Federation and Remote Access for External UsersAfter transitioning the federation route to the Lync Server 2010 Edge Server and Director, youshould perform some functional tests to verify that federation performs as expected. Tests for


93

external user access should include each type of external user that your organization supports,including any or all of the following.

Test Connectivity of External Users and External access

1. Users from at least one federated domain, an internal user on Lync Server 2010, and auser on Office Communications Server 2007 R2. Test instant messaging (IM), presence, audio/video (A/V), and desktop sharing.

2. Users of each public IM service provider that your organization supports (and for whichprovisioning has been completed) communicating with a user on Lync Server 2010 and a user on Office Communications Server 2007 R2.

3. Verify anonymous users are able to join conferences.

4. A user hosted on Office Communications Server 2007 R2 using remote user access (logging into Office Communications Server 2007 R2 from outside the intranet but withoutVPN) with a user on Lync Server 2010, and a user on Office Communications Server 2007 R2. Test IM, presence, A/V and desktop sharing.

5. A user hosted on Lync Server 2010 using remote user access (logging into Lync Server 2010 from outside the intranet but without VPN) with a user on Lync Server 2010, and a user on Office Communications Server 2007 R2. Test IM, presence, A/V and desktop sharing.

Move Remaining Users to Lync Server 2010 (Office Communications Server2007 R2 Migration)You can move users to the new Microsoft Lync Server 2010 deployment by using either LyncServer Control Panel or Lync Server Management Shell. You must meet some requirements toensure a smooth transition to Lync Server 2010. For details about prerequisites to completing theprocedures in this topic, see Configure Clients for Migration.





94

Important:Please note that this includes the active meetings created by the legacy user. Forexample, if a legacy user has configured a my meeting conference, that conference willstill be available in the new Lync Server 2010 pool, after the user has been moved. Thedetails to access that meeting will still be the same conference URL and conference ID.The only difference is that the conference is now hosted in the Lync Server 2010 pool,and not in Office Communications Server 2007 R2 pool.


Post Migration TaskAfter you move users, verify the conferencing policy that is assigned to them. To ensure thatmeetings organized by users homed on Lync Server 2010 work seamlessly with federated userswho are homed on Office Communications Server 2007 R2, the conferencing policy assigned tothe migrated users should allow anonymous participants. Conferencing policies that allowanonymous participants have Allow participants to invite anonymous users selected in LyncServer 2010 Control Panel and have AllowAnonymousParticipantsInMeetings set to True inthe output from the Get-CsConferencingPolicy cmdlet in the Lync Server Management Shell.For details about configuring conferencing policy by using Lync Server Management Shell, seeSet-CsConferencingPolicy in the Lync Server Management Shell documentation.

Example of Users Before MigrationThe following figure shows users enabled for Office Communications Server 2007 R2 in theOffice Communications Server 2007 R2 administrative tools. These users will be moved to LyncServer 2010 using the Lync Server Control Panel or Lync Server Management Shell.

The following figure provides a view of these same users in Lync Server Control Panel. The


95

Registrar pool column entry for each user is set to Legacy, which indicates that these users arestill homed on Office Communications Server 2007 R2 and have not been moved to Lync Server2010.

To move users by using the Lync Server 2010 Control Panel

1. Log onto the computer with an account that is a member of the RTCUniversalUserAdmins group or a member of the CsUserAdministrators administrative role.


3. Click Users, click Add Filter, build the following query Legacy user Equal to True, and then click Find.

4. In the search results, select a user. Here, we’ve selected Chen Yang.


96

Note:Notice that the Registrar pool column shows <Legacy>. This means that theuser you have selected is homed on Office Communications Server 2007 R2.


Important:If Move selected users to pool is not available, ensure the account is a member of the CSAdministrator or CSUserAdministrator group.

6. In Move Users, select the Destination registrar pool, which is your Lync Server 2010pool, and then click OK.


To move users by using the Lync Server Management Shell

1. Log onto the computer with an account that is a member of the RTCUniversalUserAdmins group or a member of the CsUserAdministrators administrative role.



97

3. At the command line, type the following:Move-CsLegacyUser –Identity “user name” –Target “pool_name”For example:Move-CsLegacyUser –Identity “Kate Jordan” –Target “lync-se.contoso.net”

4. At the command line, type the following:Get-CsUser “user name”The RegistrarPool identity in the following figure now points to the pool you specifiedas “pool_name” in the previous step. The presence of this identity confirms that the user has been successfully moved.

ImportantThe Move-CsLegacyUser cmdlet may fail with the following error:Move-CsLegacyUser : SetMoveResourceData failed because the user isnot provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< -Identity "[email protected]” -Target "lync-se.contoso.net" + CategoryInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser


98

) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId :MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLegacyUserCmdletIf you experience this error, see the topic Verify User Replication has Completed for resolution.

Move Multiple UsersYou can move groups of users to the new Microsoft Lync Server 2010 deployment using thefollowing two methods: Lync Server Control Panel and Lync Server Management Shell. There arerequirements that must be met to ensure a smooth transition to Lync Server 2010. For detailsbefore completing the procedures in this topic, see Configure Clients for Migration.




Important:This data includes the active meetings created by the legacy user. For example, if alegacy user has configured a my meeting conference, that conference will still beavailable in the new Lync Server 2010 pool, after the user has been moved. The detailsto access that meeting will still be the same conference URL and conference ID. Theonly difference is that the conference is now hosted in the Lync Server 2010 pool, andnot in Office Communications Server 2007 R2 pool.


To move multiple users by using the Lync Server Control Panel


2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr


99

ol Panel. For details about the different methods you can use to start Lync Server rolCont Panel, see Installing and Using Administrative Tools.

3. Click Users, click Add Filter, build the query Legacy user Equal to True, and then click Find.

4. In the search results, select at least two users.


Important:If Move selected users to pool is not available, ensure the account is a member of the RTCUniversalUserAdmins group or a member of the CSAdministrator or CSUserAdministrator administrative role.

6. In Move Users, select the Destination Registrar pool, which is your Lync Server 2010 pool, and then click OK.


For more details about the cmdlets described in this section, run:Get-Help <cmdlet name> -Detailed

To move multiple users by using the Lync Server Management Shell



3. At the command line, type the following and replace User1 and User2 with specific user names you want to move and replace pool_FQDN with the name of the destinationpool:


100

Get-CsUser –Filter {DisplayName –eq “User1” –or DisplayName – eq“User2”} | Move-CsLegacyUser –Target “pool_FQDN”

4. At the command line, type the following

Get-CsUser “User1”

The Registrar Pool identity should now point to the pool you specified as “pool_FQDN” in the previous step. The presence of this identity confirms that the user has been successfully moved.

To move all users at once by using the Lync Server Management Shell



Get-CsUser –OnOfficeCommunicationServer | Move-CsLegacyUser –Target “pool_FQDN”


Get-CsUser “user name”where user name is the name of a legacy user.

The Registrar Pool identity now points to the pool you specified as “pool_FQDN” in the previous step. The presence of this identity confirms that the user has been successfully moved.

ImportantThe Move-CsLegacyUser cmdlet may fail with the following error:Move-CsLegacyUser : SetMoveResourceData failed because the user isnot provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< -Identity "[email protected]” -Target "lync-se.contoso.net" + CategoryInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId :MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLegacyUserCmdletIf you experience this error, see the topic Verify User Replication has Completed for resolution.


101

Migrate Response GroupsYou can migrate response group settings (agent groups, queues, and workflows) that you createdon Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. When youmigrate Response Group settings, all the configuration settings, audio files, and contact objectsare moved from the Office Communications Server 2007 R2 pool to the Lync Server 2010 pool,and all calls to migrated response group phone numbers are handled by Lync Server 2010. Callsto migrated response groups will no longer be handled by Communications Server 2007 R2.

To migrate Response Group settings from Office Communications Server 2007 R2 to LyncServer 2010, you need to run a migration cmdlet and then update the URL that users need tosign into and out of their response groups. If the Back End server in your Microsoft OfficeCommunications Server 2007 R2 environment runs on SQL Server 2005, you first need to installthe SQL Server 2005 Native Client on the Lync Server 2010 computer where you plan to run theResponse Group migration cmdlet.

Note:The Response Group migration cmdlet requires that the Response Group application isinstalled in your Lync Server 2010 pilot pool. You can ensure that Response Group isinstalled by running the Get-CsService –ApplicationServer command.

Important:The Response Group migration cmdlet moves settings for the entire pool. You cannotselect specific groups, queues, or workflows to migrate.

Note:The following procedure for migrating Response Group settings assumes that you have aone-to-one relationship between Office Communications Server 2007 R2 and LyncServer 2010 pools. If you plan to consolidate or split up pools during your migration anddeployment, you need to plan which Office Communications Server 2007 R2 pool mapsto which Lync Server 2010 pool.

Note:After you run the Response Group migration cmdlet, the settings are still present, butunused, in your Office Communications Server 2007 R2 pool to allow for a potentialrollback.

After you migrate Response Group, use Lync Server Control Panel or Lync Server ManagementShell cmdlets to verify that all agent groups, queues, and workflows moved successfully.

To migrate Response Group settings

1. If the Back End Server in your Office Communications Server 2007 R2 pool runs on SQL Server 2005, download the Feature Pack for Microsoft SQL Server 2005 - December 2008 (SQLNCLI.MSI package) from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=204105, and then install it on the computer where you plan torun the Response Group migration cmdlet.


102

2. Log on to the computer with an account that is a member of the AdminsRTCUniversalServer group or has equivalent rights.


4. Run:Move-CsRgsConfiguration –Source <source pool FQDN> -Destination<destination pool FQDN>For example:Move-CsRgsConfiguration –Source se-r2.contoso.net –Destination lync-se.contoso.net

5. If you deployed the Response Group tab for Microsoft Office Communicator 2007 R2 inyour Office Communications Server 2007 R2 environment, remove the tab from the Office Communicator 2007 R2 tabs.xml file.

Note:Formal agents used the Response Group tab to sign in to their response groups before they could receive calls. If you deployed the Response Group tab, youchose the location for the Office Communicator 2007 R2 tabs.xml file when you deployed it.

6. Provide users with the updated URL that agents need to sign into and out of their response groups.

Note:The URL is typically https://webpoolFQDN/RgsClients/Tab.aspx, where webpoolFQDN is the fully qualified domain name (FQDN) of the web pool that is associated with the pool that you just migrated to Lync Server 2010.

Note:This step is not required after users upgrade to Microsoft Lync 2010 because the URL is available from the Tools menu in Lync 2010.

To verify Response Group migration by using Lync Server Control Panel

1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.


3. In the left navigation pane, click Response Groups.4. On theWorkflow tab, verify that all the workflows in your Office Communications Serv

er 2007 R2 environment are included in the list.

5. Click the Queue tab, and verify that all the queues in your Office Communications Server 2007 R2 environment are included in the list.


103

6. Click the Group tab, and verify that all the agent groups in your Office sCommunication Server 2007 R2 environment are included in the list.

To verify Response Group migration by using cmdlets

1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.

2. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.For details about the following cmdlets, run:Get-Help <cmdlet name> -Detailed

3. Run:Get-CsRgsAgentGroup

4. Verify that all the agent groups in your Office Communications Server 2007 R2 environment are included in the list.

5. Run:Get-CsRgsQueue

6. Verify that all the queues in your Office Communications Server 2007 R2 environmentare included in the list.

7. Run:Get-CsRgsWorkflow

8. Verify that all the workflows in your Office Communications Server 2007 R2 environment are included in the list.

Run Functional Tests for Response GroupsAfter you migrate your agent groups, queues, and workflows, run some functional tests to verifythat your response groups function as expected. This section describes some example scenarios.

Users:

User who is homed on Office Communications Server 2007 R2

User who is homed on Lync Server 2010

External user

An agent who is homed on Office Communications Server 2007 R2

An agent who is homed on Lync Server 2010Scenarios:

A Office Communications Server 2007 R2 user calls the response group on Lync Server2010.

A Lync Server 2010 user calls the response group.

An external user calls the response group.


104

A user calls the response group while the agent is on another call and goes to the queue.

Move Exchange Unified Messaging Contact ObjectsTo migrate Auto Attendant (AA) and Subscriber Access (SA) contact objects to the new MicrosoftLync Server 2010 deployment, you first move the objects from the legacy Office CommunicationsServer 2007 R2 deployment to the new the Lync Server deployment using the Get-CsExUmContact and Move-CsExUmContact cmdlets. On the Exchange Server, you then runthe ExchUCUtilWindows PowerShell script. This script will target the newly deployed Lync pool,and will:

Add it to the Unified Messaging IP gateways

Add it to the Unified Messaging hunt groups.

Note:In order to use the Get-CsExUmContact and Move-CsExUmContact cmdlets, you mustbe a member of the RTCUniversalUserAdmins group and have OU permission to theOU where the contacts objects are stored. OU permission can be granted using theGrant-OUPermission cmdlet.

To move contact objects by using the Lync Server Management Shell


2. For each pool registered with Exchange UM (where pool1.contoso.net is a pool from the Office Communications Server 2007 R2 deployment and pool2.contoso.net is the pool from the Lync Server deployment) at the command line, type the following:

Get-CsExUmContact -Filter {RegistrarPool –eq "pool1.contoso.net"} | Move-CsExUmContact -Target pool2.contoso.netTo verify that the contact objects are moved, run the Get-CsExumContact cmdlet andconfirm that RegisrtarPool is now pointing to the new target pool.

To run the ExchUCUtil Windows PowerShell script

1. Log on to the Exchange UM Server as a user with Exchange Organization Administrator privileges.

2. Navigate to the ExchUCUtil Windows PowerShell script.

In Exchange 2007, ExchUCUtil.ps1 is located at: %Program Files%\Microsoft\Exchange Server\Scripts\ExchUCUtil.ps1In Exchange 2010, ExchUCUtil.ps1 is located at: %Program Files%\Microsoft\Exchange Server\V14\Scripts\ExchUCUtil.ps1

3. If Exchange is deployed in a single forest, type:exchucutil.ps1Or, if Exchange is deployed in multiple forests, type:


105

exchucutil.ps1 -Forest:" <forest FQDN>" for multiple forest oymedeplntswhere forest FQDN specifies the forest in which Lync Server is deployed.

Important:Be sure to restart the Lync Server Front-End service (rtcsrv.exe) after you run exchucutil.ps1. Otherwise, Lync Server will not detect Unified Messaging in the topology.

Verify that all Exchange UM Contact Objects are removed from the LegacyPoolUse either the OCSUmUtil tool or the Get-CsExumContact cmdlet to verify that Exchange UMcontact objects have been removed from the legacy Office Communications Server 2007 R2pool. OCSUmUtil Is located in the following folder:

%Program Files%\Common Files\Lync Server 2010\Support\OcsUMUtil.exe

OCSUmUtil must be run from a user account that has:

Membership in the be RTCUniversalServerAdmins and RTCUniversalUserAdmins group(which includes rights to read Exchange Server Unified Messaging settings)

Domain rights to create contact objects in the specified organizational unit (OU) containerFor details about using the Get-CsExumContact cmdlet, see Get-CsExUmContact in the LyncServer Management Shell documentation.


106

Phase 9: Complete Post-Migration TasksThe topics in this section describe tasks that you will need to perform after you have completedyour migration to Microsoft Lync Server 2010.

In This Section Migrate Dial-in Access Numbers

Enable Exchange 2010 SP1 Outlook Web App and IM Integration

Migrate Address Book

Enable Remote Call Control

Remove Legacy Archiving and Monitoring Servers

Migrate Mediation Server

Migrate Communicator Web Access

Migrate Applications Built on Microsoft Unified Communications Managed API (UCMA) 2.0Core SDK

Configure Trusted application servers

Configure the Meeting Join Page

Deploy Lync Server 2010 Clients

Migrate Dial-in Access NumbersMigrating dial-in access numbers requires two steps: running the Import-CsLegacyConfiguration cmdlet (completed earlier in Import Policies and Settings) to migratedial plans and other dial-in access number settings, and running the Move-CsApplicationEndpoint cmdlet to migrate the contact objects. After you run the Import-CsLegacyConfiguration cmdlet, the migrated dial-in access numbers exist both in yourMicrosoft Office Communications Server 2007 R2 pool and in your Microsoft Lync Server 2010pool. During this coexistence period, dial-in access numbers that you created in OfficeCommunications Server 2007 R2 behave differently from dial-in access numbers that you createin Lync Server 2010, as described in this section.

After you run Import-CsLegacyConfiguration but before you run Move-CsApplicationEndpointDial-in access numbers that you created in Office Communications Server 2007 R2 have thefollowing characteristics:

Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in accessnumber page.

Appear on Lync Server 2010 meeting invitations and the dial-in access number page.

Can be viewed and modified in the Office Communications Server 2007 R2 administrativetool.


107

Important:If you make changes to dial-in access numbers in your Office CommunicationsServer 2007 R2 pool, you will need to rerun the Import-CsLegacyConfigurationcmdlet with the ReplaceExisting parameter to apply the same changes to your LyncServer 2010 pool. Re-importing with the ReplaceExisting parameter can overlayother changes you made in your Lync Server 2010 pool.

Cannot be viewed in Lync Server Control Panel, but can be viewed in Lync ServerManagement Shell (if you use the Get-CsDialinConferencingAccessNumber cmdlet withthe Region parameter).

Cannot be modified in Lync Server Control Panel or in Lync Server Management Shell.

Cannot be re-sequenced within the region by using the Set-CsDialInConferencingAccessNumber cmdlet with the –Priority parameter.

After you run Move-CsApplicationEndpointDial-in access numbers that you created in Office Communications Server 2007 R2, but havebeen moved to Lync Server 2010 have the following characteristics:

Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in accessnumber page.


Can be viewed in the Office Communications Server 2007 R2 administrative tool.

Cannot be modified in the Office Communications Server 2007 R2 administrative tool.

Can be viewed and modified in Lync Server Control Panel and in Lync Server ManagementShell.

Can be re-sequenced within the region by using the Set-CsDialinConferencingAccessNumber cmdlet with the Priority parameter.

Dial-in access numbers that you create in Lync Server 2010Dial-in access numbers that you create in Lync Server 2010 before, during, or after migrationhave the following characteristics:

Do not appear on Office Communications Server 2007 R2 meeting invitations and the dial-inaccess number page.


Cannot be viewed or modified in the Office Communications Server 2007 R2 administrativetool.

Can be viewed and modified in Lync Server Control Panel and in Lync Server ManagementShell.

Can be re-sequenced within the region by using the Set-CsDialinConferencingAccessNumber cmdlet with the Priority parameter.

You must finish migrating dial-in access numbers that point to an Office Communications Server2007 R2 pool before you decommission the Office Communications Server 2007 R2 pool. If youdo not complete dial-in access number migration as described in the following procedure,


108

incoming calls to the access numbers will fail.

Important:You must perform this procedure prior to decommissioning the Office CommunicationsServer 2007 R2 pool.

Note:We recommend that you move dial-in access numbers when network usage is low, incase there is a short period of service outage.

To identify and move dial-in access numbers

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group and open the Office Communications Server 2007 R2 administrative tool.

2. In the console tree, right-click the forest node, click Properties, and then click Conferencing Attendant Properties.

3. On the Access Phone Numbers tab, click Serviced by Pool to sort the access phonenumbers by their associated pool, and identify all the access numbers for the pool fromwhich you are migrating.

4. To identify the SIP URI for each access number, double-click the access number to open the Edit Conferencing Attendant Number dialog box, and look under SIP URI.


6. To move each dial-in access number to a pool hosted on Lync Server 2010, run:Move-CsApplicationEndpoint -Identity <SIP URI of the access number to be moved> -Target <FQDN of the pool to which the access number is moving>

7. In the Office Communications Server 2007 R2 Administrative tool, on the Access Phone Numbers tab, verify that no dial-in access numbers remain for the CommunicationsServer 2007 R2 pool from which you are migrating.

Note:When no more dial-in access numbers point to the Office Communications Server 2007 R2 pool, you can decommission the Office Communications Server 2007 R2 pool.

Enable Exchange 2010 SP1 Outlook Web App and IM IntegrationTo enable Exchange 2010 SP1 Outlook Web Access (OWA) and instant messaging (IM)integration with Microsoft Lync Server 2010, you must add the Exchange 2010 SP1 Client AccessServer (CAS) server to the Lync Server 2010 topology as a trusted application server.


109

ImportantThere are additional configuration requirements that depend on how your Exchange 2010 SP1server roles are configured:

If your CAS server is not collocated on the same server that is running Exchange 2010 SP1Unified Messaging (UM), in addition to creating a trusted application pool you must create atrusted application, which can only be done by using Lync Server Management Shell. The trustedapplication must be assigned a port number on which the application will run. The port must beunique within the trusted application pool. In other words, no other applications that use this portcan be defined in the specified pool. This port will not be used, but it must be assigned asdescribed in the “Create a trusted application for the Exchange 2010 SP1 CAS server” procedurelater in this topic.

If your CAS server is collocated on the same server that is running Exchange 2010 SP1 UM, andthe UM server is servicing a SIP dial plan that is integrated with Lync Server 2010, you only needto create a trusted application pool. It is not necessary to create a trusted application.

Create a trusted application pool

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or has the equivalent rights.


3. Run the following cmdlet:Get-CsSiteThis returns the siteID for the siteName in which you are creating the pool. For details,see Get-CsSite in the Lync Server Management Shell documentation.

4. Run the following cmdlet:New-CsTrustedApplicationPool -Identity <E14 CAS FQDN> –ThrottleAsServer $true –TreatAsAuthenticated $true –ComputerFQDN <E14 CASFQDN> -Site <Site> -Registrar <Pool FQDN in the site> -RequiresReplication $falseFor details, see New-CsTrustedApplicationPool in the Lync Server Management Shelldocumentation.

Important:If your CAS server is not collocated on the same server that is running Exchange 2010 SP1 Unified Messaging (UM), skip the remaining steps in this procedure and perform the “Create a trusted application for the Exchange 2010 SP1 CAS server” procedure later in this topic. If your CAS server is collocated on thesame server that is running Exchange 2010 SP1 Unified Messaging (UM), complete the steps in this procedure and do not perform the “Create a trusted application for the Exchange 2010 SP1 CAS server” procedure later in this topic.

5. Run Enable-CsTopology.


110


7. Select the option to Download Topology from existing deployment.8. In the Save Topology As dialog box, select the Topology Builder file you want to use,

and click Save.9. In the left pane, expand the tree until you reach Trusted application servers.10. Expand the Trusted application servers node.11. You should now see the Exchange 2010 SP1 CAS server listed as a trusted applicatio

n server.

Create a trusted application for the Exchange 2010 SP1 CAS server

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or has the equivalent rights.


3. If your CAS server is not collocated on the same server that is running Exchange 2010SP1 Unified Messaging (UM), run the following cmdlet:New-CsTrustedApplication -ApplicationId <AppID String> -TrustedApplicationPoolFqdn <E14 CAS FQDN> -Port <available portnumber>For details, see the topic New-CsTrustedApplication in the Lync Server Management Shell documentation.

4. Run Enable-CsTopology.5. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2

010, and then click Lync Server Topology Builder.6. Select the option to Download Topology from existing deployment.7. In the Save Topology As dialog box, select the Topology Builder file you want to use,

and click Save.8. In the left pane, expand the tree until you reach Trusted application servers.9. Expand the Trusted application servers node.10. You should now see the Exchange 2010 SP1 CAS server listed as a trusted applicatio

n server.

Migrate Address Book

In general, Address Book is migrated along with the rest of your topology. However, you mightneed to perform the following post-migration steps if you customized the following in yourMicrosoft Office Communications Server 2007 R2 environment:


111

Set the PartitionbyOU WMI property to group Address Book entries by organizational unit(OU).

Customize the Address Book normalization rules.Grouped Address Book EntriesIf you set the PartitionbyOU WMI property to True to create address books for each OU, youneed to set the msRTCSIP-GroupingId Active Directory attribute on users and contacts if youwant to continue grouping address book entries. You might want to group address book entries tolimit the scope of Address Book searches. To use the msRTCSIP-GroupingId attribute, write ascript to populate the attribute, assigning the same value for all of the users that you want togroup together. For example, assign a single value for all the users in an OU.

Address Book Normalization RulesIf you customized Address Book normalization rules in your Office Communications Server 2007R2 environment, you must migrate the customized rules to your pilot pool. If you did notcustomize Address Book normalization rules, you have nothing to migrate for Address Bookservice. The default normalization rules for Lync Server 2010 are the same as the default rulesfor Office Communications Server 2007 R2.

Note:If your organization uses remote call control and you customized Address Booknormalization rules, you must perform the procedure in this topic before you can useremote call control. The procedures require membership in theRTCUniversalServerAdmins group or equivalent rights.

To migrate Address Book customized normalization rules

1. Find the Company_Phone_Number_Normalization_Rules.txt file in the root of the Address Book shared folder, and copy it to the root of the Address Book shared folder in your Lync Server 2010 pilot pool.

2. Use a text editor, such as Notepad, to open the Company_Phone_Number_Normalization_Rules.txt file.

3. Certain types of entries will not work correctly in Lync Server 2010. Look through the file for the types of entries described in this step, edit them as necessary, and save the changes to the Address Book shared folder in your pilot pool.

Strings that include required whitespace or punctuation cause normalization rules to fail because these characters are stripped out of the string that is input to the normalization rules. If you have strings that include required whitespace or punctuation, you needto modify the strings. For example, the following string would cause the normalization rule to fail:\s*$\s*\d\d\d\s*$\s*\-\s*\d\d\d\s*\-\s*\d\d\d\dThe following string would not cause the normalization rule to fail:\s*$?\s*\d\d\d\s*$?\s*\-?\s*\d\d\d\s*\-?\s*\d\d\d\d


112

Enable Remote Call ControlRemote call control enables users to control their desktop private branch exchange (PBX) phonesby using Microsoft Lync 2010. Enabling remote call control requires five steps. The following tabledescribes where and when these steps occur when you are migrating to Microsoft Lync Server2010 from a previous version of Office Communications Server.

Step When occurs

Remove legacy trusted server entries Use the Office Communications Server 2007 R2 administrative tools to remove legacy trustedapplication server entries prior to moving them to Lync Server 2010.

Configure the remote call control gateway to communicate with the PBX.

When you deploy and configure your Lync Server 2010 pilot pool. If you plan to migrate remotecall control, this step is a prerequisite to migration.

Create trusted server and static route entries for routing requests to the remote call control gateway.

After the topology is merged and policies and settings are migrated. This is a manual step afterthe automated migration is complete. The procedures in this section describe how to perform these tasks.

Configure users for remote call control. When you migrate users. The remote call control setting is migrated along with all the other user settings. For details about migrating users, see Move Remaining Users to Lync Server 2010(Office Communications Server 2007 R2 Migration).

Configure Lync 2010. When you deploy Microsoft Lync 2010. Administrators can use group policy to apply this settingwhen they deploy clients. For details, see Deploy Lync Server 2010 Clients.

Verify Address Book phone number normalization rules, if you customized normalization rules.

After the topology is merged and policies and settings are migrated. This is a manual step afterthe automated migration is complete, and applies only if you customized the normalization rules. For details about migrating Address Book normalization rules, see Migrate Address Book.

To remove a legacy trusted server entry

1. Log on to the computer with an account that is a member of the RTCUniversalServer


113

Admins group.2. Open the Office Communications Server 2007 R2 administrative console.

3. Expand the tree and right-click the pool where the trusted server entry was created.

4. Click Properties, then Front End Properties.5. Select the Host Authorization tab.

6. Select a server and then click Remove.7. Click OK to close the Properties window.

To create a trusted server entry



3. Run:New-CsTrustedApplicationPool -Identity <FQDN of the new pool> `[-ComputerFqdn <FQDN of computer if more than one computer in pool or FQDN is different from pool FQDN>] `[-Registrar <Service ID or FQDN of Registrar service>] [-Site <Site ID where pool is homed>] `[-ThrottleAsServer <$true | $false>] [-TreatAsAuthenticated <$true | $false>]For example:New-CsTrustedApplicationPool –Identity lync-pool1.contoso.net `–ComputerFqdn computer1.contoso.net –Registrar co1-Registrar-1 –Site co1 `-TreatAsAuthenticated $true –ThrottleAsServer $true

4. Run:New-CsTrustedApplicationComputer –Identity <FQDN of computer> -Pool <FQDN of pool hosting the computer>

Note:This step is not required for Standard Edition server.

For example:New-CsTrustedApplicationComputer –Identity computer2.contoso.net–Pool lync-pool1.contoso.net

5. Run:New-CsTrustedApplication –ApplicationID <application name> –TrustedApplicationPoolFqdn <FQDN of pool where application resides>–Port <port number where application runs> -EnableTcp


114

For example:New-CsTrustedApplication –ApplicationID co1-ExternalServer-1 –TrustedApplicationPoolFqdn lync-pool1.contoso.net –Port 5060 -EnableTcp

To create a static route



3. Run:$tcpRoute = NewCsStaticRoute –TCPRoute –Destination <IP addressof the next hop router> `–Port <port for SIP routing> –MatchUri <FQDN of domain suffix that determines if message is handled by this router>or$tlsRoute = NewCsStaticRoute –TLSRoute –Destination <FQDN of thenext hop server> –Port <port for SIP routing> –MatchUri <FQDN ofdomain suffix that determines if message is handled by this router> -UseDefaultCertificate $trueFor example:$tcpRoute = NewCsStaticRoute –TCPRoute –Destination 192.168.0.240 –Port 7742 –MatchUri *.contoso.net

4. Run:Set-CsStaticRoutingConfiguration –Route @{Add=$tcpRoute, $tlsRoute}

Remove Legacy Archiving and Monitoring ServersIf your Office Communications Server 2007 R2 deployment contained an Archiving Server or aMonitoring Server, after migrating to Lync Server 2010, those servers can be removed from thelegacy environment provided all users have been removed from any remaining OfficeCommunications Server 2007 R2 pools. You can remove the Archiving Server or MonitoringServer in any sequence. The key requirement is that all users have been removed from anyremaining Office Communications Server 2007 R2 pools.

You can move users from Office Communications Server 2007 R2 to Lync Server 2010 byfollowing the procedures outlined in the following topics:

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


115

Move Multiple UsersAfter you have confirmed that all users have been removed from any remaining pools, follow theprocedure in "Removing Servers and Server Roles" athttp://go.microsoft.com/fwlink/?LinkId=205887.

Migrate Mediation ServerThe topics in this section describe configuration tasks that you will need to perform after you havecompleted your migration of Lync Server 2010 Mediation Server. Transitioning the collocatedMediation Server to a stand-alone Mediation Server is an optional task.

Configure Mediation Server

Change Voice Routes to use the new Lync Server 2010 Mediation Server

Transition a collocated Mediation Server to a Stand-Alone Mediation Server (optional)

Configure Mediation ServerThis procedure details the steps to configure the Lync Server 2010 pool to use the Lync Server2010 Mediation Server, instead of the legacy Office Communications Server 2007 R2 MediationServer.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding serverroles. For details, see Delegate Setup Permissions in the Standard Edition server or EnterpriseEdition server Deployment documentation. For other configuration changes, only membership inthe RTCUniversalServerAdmins group is required.

Note:For the latest information on finding qualified PSTN gateways, IP-PBXs and SIP Trunkingservices that work with Lync Server 2010, see "Microsoft Unified Communications OpenInteroperability Program" at http://go.microsoft.com/fwlink/?LinkId=206015.

Configure Mediation Server Using Topology Builder




4. In the left pane, navigate to PSTN gateways.5. Right-click PSTN gateways and select New IP/PSTN Gateway.6. Complete the Define New IP/PSTN Gateway page with the following information:

Enter the gateway FQDN or IP address. The FQDN of the gateway is required if the gateway uses the TLS protocol.


116

Accept the default value of the Listening port for IP/PSTN gateway or enter the enw listening port if it was modified.

Set the Sip Transport Protocol.7. In the left pane, navigate to the Enterprise Edition Front End pool or the Standard E

dition Server.8. Right-click the pool, and then click Edit Properties.9. Under Mediation Server, set the Listening ports.10. Next, associate the newly created PSTN gateway by selecting it and clicking Add.11. Associate the PSTN gateway to the Lync Server 2010 Mediation Server by selecting it

and clicking Make Default.12. In Topology Builder, select the top-most node Lync Server 2010.13. From the Actions pane, select Publish Topology and then click Next.14. When the Publishing wizard completes, click Finish to close the wizard.

Note:It is important that you complete the next topic, Change Voice Routes to use the newLync Server 2010 Mediation Server to ensure that the voice routes are pointing to thecorrect Mediation Server.

Change Voice Routes to use the new Lync Server 2010 Mediation ServerThis procedure changes the voice routes to use the Lync Server 2010 Mediation Server, insteadof the legacy Office Communications Server 2007 R2 Mediation Server.


Change the voice routes to use the new Mediation Server

1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or a minimally member of the CsVoiceAdministrator administrative role.


3. In the left pane, select Voice Routing and then Route.4. Click New to create a New Voice Route.

5. Fill in the following fields:

Name: Type a descriptive name of the voice route. For this document we will useW14PSTNRoute.


117

Description: Type a short description of the voice route.6. Skip all remaining sections until you reach Associated gateways. Click Add. Select th

e new default gateway and click OK.7. Under Associated PSTN Usages, click Select.8. From the Select PSTN Usage Record page, select a record name and then click OK.9. From the New Voice Route page, click OK to create the Voice Route.10. From the Voice Routing page, select Route.11. Move the newly created route to the top of the list and then select Commit.12. In Topology Builder, select the top-most node Lync Server 2010.13. From the Actions pane, select Publish Topology and then click Next.14. When the Publishing wizard completes, click Finish to close the wizard.

Transition a collocated Mediation Server to a Stand-Alone Mediation Server (optional)Use the procedure that follows to transition your Mediation Server, collocated on your StandardEdition server or Front End pool, to a stand-alone Mediation Server for a single-site deployment.


To transition a collocated Mediation Server to a stand-alone Mediation Server




4. In the left pane, navigate to Mediation pools.5. Right-click Mediation pools and select New Mediation Server.6. On the Define New Mediation Pool page, provide the FQDN of the new Mediation Ser

ver pool. Also, select whether this pool will be a single-server or multiple-server pool, and then click Next.

7. Select the next hop pool to which the new Mediation Server will route inbound calls, and then click Next.

8. Select the Edge pool to be used by the Mediation Server and then click Next.9. On the Specify PSTN gateways page, associate the previous PSTN gateway with the

Mediation Server. Select the gateway and then click Add.


118

10. Click Finish to close the Define New Mediation Pool wizard.11. From Topology Builder, select the top node Lync Server 2010.12. From the Actions pane, select Publish Topology and complete the wizard.

13. Follow the steps in Install the Files for Mediation Server in the Deployment documentation to install the files on the new Mediation Server.

14. After the files are installed on the Mediation Server, return to Topology Builder, and in the left pane navigate to the pool.

15. Right-click the pool and select Edit Properties.16. Under Mediation Server, clear the check box Collocated Mediation Server enabled

and then click OK.17. From Topology Builder, select the top node Lync Server 2010.18. From the Actions pane, select Publish Topology and complete the wizard.

Migrate Communicator Web AccessMicrosoft Lync Server 2010 has replaced Communicator Web Access with a new MicrosoftSilverlight based client called Microsoft Lync Web App. Depending on the requirements of yourorganization, you have several options available for migrating Communicator Web Accessfunctionality to Lync Server 2010.

Note:All procedures and guidance in this section apply to both Office Communications Server2007 and Office Communications Server 2007 R2 versions of Communicator WebAccess.

Lync Server 2010 only deployment, IM and presence are not required for reachscenariosYou do not need to perform any additional migration steps.

IM and presence are required for reach scenariosLync Web App does not support IM and presence. If this is a requirement of your organization, you must also maintain a deployed instance of the previous version of Communicator Web Access in your environment. Because Communicator Web Access can pointto a Lync Server pool as a next hop, there is no need to maintain a separate Office Communications Server pool.

Side-by-side deploymentIf you maintain an Office Communications Server pool deployed alongside a Lync Server pool, the user experience will vary depending on which server the user is homed to and which pool Communicator Web Access is pointing to. For details, see “Side-By-Side Deployment” later in this topic.

If you are going to maintain an instance of the previous version of Communicator Web Access,you need to point Communicator Web Access to the Lync Server pool. For details, Repoint


119

Communicator Web Access to Lync Server 2010.

Note:When Communicator Web Access is deployed, all users who sign in throughCommunicator Web Access have support for instant messaging (IM) and presence. Itdoes not matter if they are homed in the Office Communications Server pool or the LyncServer pool.

Deployment ScenariosIf a deployment contains Communicator Web Access server, then all users can access IM andpresence functionality irrespective of the following conditions:

Whether users are homed in an Office Communications Server pool or Lync Server pool

Whether the Communicator Web Access server is pointed to Office Communications Serveror Lync Server

The following table describes the behavior for the various deployment scenarios and end userexperience.

Scenario Behavior

All users are homed in the Lync Server pool

Communicator Web Access is pointed to the Lync Server pool

All users will have support for IM and presencethrough Communicator Web Access and meetings though Lync Web App.

All users are homed in the Lync Server pool

Communicator Web Access is pointed to the Office Communications Server pool

All users will have support for IM and presencethrough Communicator Web Access and meetings through Lync Web App.

Users are split between the Lync Server and the Office Communications Server pools

Communicator Web Access is pointed to the Office Communications Server 2007 R2 pool.

Lync Server homed users will have Reach for IM and presence through Communicator Web Access. These users will use the Lync Web Appfor meeting access.

Office Communications Server homed users will have Reach IM and presence using Communicator Web Access as long as Office Communications Server pool is running. These users willuse Communicator Web Access for meeting access.

If the user has migrated and joins or creates anew conference using Meet Now (JOIN Launcher link), the user will join the meeting using Lync reach. If the conference has yet to migrate, but the user has, the user will join the meeting using Communicator Web Access.


120

If the user has not been migrated, the new erenconfce will be created on the Office Communications Server 2007 R2 pool, and the user will use Communicator Web Access to join the conference. The user should also be able to join a conference created on Lync Server 2010 using the reach join Launcher link.

If using Communicator Web Access to join a conference, the user will have the IM and Presence features available. If joining the conference using the Reach client, the IM and Presence feature is not available.

Users are split between the Lync Server and the Office Communications Server pools

Communicator Web Access is pointed to the Lync Server pool.

Lync Server homed users will have Reach IM and presence support using Communicator WebAccess as long as the Lync Server pool is running and will have meeting through Lync Web App.

Office Communications Server homed used willhave both IM and presence and meeting support using Communicator Web Access.

If the user has migrated and joins or creates anew conference using Meet Now (JOIN Launcher link), the user will join the meeting using Lync reach. If the conference has yet to migrate, but the user has, the user will join the meeting using Communicator Web Access.

If the user has not been migrated, the new conference will be created on the Office Communications Server 2007 R2 pool, and the user will use Communicator Web Access to join the conference. The user should also be able to join a conference created on Lync Server 2010 using the reach join Launcher link.

If using Communicator Web Access to join a conference, the user will have the IM and Presence features available. If joining the conference using the Reach client, the IM and Presence feature is not available.

Repoint Communicator Web Access to Lync Server 2010The following procedure describes how to point Communicator Web Access to the Microsoft LyncServer 2010 pool.


121

Note:The procedure in this section applies to both Office Communications Server 2007 andOffice Communications Server 2007 R2 versions of Communicator Web Access.

Note:You must perform this procedure before you completely remove Office CommunicationsServer pools.

To Repoint Communicator Web Access server to Lync Server 2010

1. On a computer that is running the Communicator Web Access snap-in, log on as a member of the local Administrators group and the RTCUniversalServerAdmins group.

2. Click Start, point to Administrative Tools, and then click Communicator Web Access.

3. In the console pane, expand the name of the computer that hosts the virtual server forwhich you want to specify a next hop server, right-click the name of the virtual server, and then click Properties.

4. In the Properties dialog box, on the Next Hop tab, select a server or server pool from the Next hop pool dropdown.

5. Type the listening port of the server or server pool in the Port box and then click OK.

Note:Typically, Lync Server 2010 uses port 5061 as the listening port.

Migrate Applications Built on Microsoft Unified Communications ManagedAPI (UCMA) 2.0 Core SDKMicrosoft Lync Server 2010 communications software works with Microsoft UnifiedCommunications Managed API (UCMA) 3.0 Core SDK. If you have external applications built onUCMA 2.0 (which shipped with Office Communications Server), you can run these applications inan environment that includes servers running Lync Server 2010.

If you run a UCMA 2.0 application, homed on an Office Communications Server pool, you canenable users homed on a Lync Server 2010 pool to call into the application.

The trusted server entries are merged from the legacy Office Communications Server deploymentto Lync Server 2010 when the Topology Builder Merge wizard is run. After the merge, the trustedservice entries exist on both the Office Communications Server pool and the Lync Server 2010pool, and no further steps are needed for coexistence. Be sure to note that this copies only thetrusted service entries and route-related settings.

Configure Trusted application serversIn a mixed environment, if you create a new trusted application server after merging the legacyOffice Communications Server topology with Lync Server 2010, and you define a new trusted


122

application server using Topology Builder, you must set the next hop pool to be a Lync Server2010 pool. In a merged environment, both the legacy Office Communications Server pool and theLync Server 2010 pool appear in the drop down list. Selecting the legacy pool is not supported.

To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding serverroles. For details, see Delegate Setup Permissions in the Lync Server 2010 Standard Editionserver or Enterprise Edition server Deployment documentation. For other configuration changes,only membership in the RTCUniversalServerAdmins group is required.

Select Lync Server 2010 as next hop when creating a Trusted application server




4. In the right pane, right click Trusted application servers and click New Trusted Application Pool.

5. Enter the Pool FQDN of the trusted application pool and select whether it will be a single-server or multiple-server.

6. Click Next.7. On the Select the next hop page, from the dropdown list, select the Lync Server 2010

Front End pool. lync-se.contoso.net in our example.


123

8. Click Finish.9. Select the top node Lync Server 2010 and from the Actions pane, select Publish.

The Trusted Application Pool should have been created successfully and is associated with the correct Front End pool.

Configure the Meeting Join PageYou can control the Microsoft Lync Server 2010 clients that are available for joining scheduledLync Server 2010 meetings by configuring the meeting join page. When a user clicks a meetinglink in a meeting request, the meeting join page detects whether a Lync Server client is alreadyinstalled on the user’s computer. If a client is already installed, the default client opens and joinsthe meeting. If a client is not installed, the meeting join page displays options for joining themeeting with alternate clients.

The meeting join page always contains the option to use Microsoft Lync WebApp communications software. In addition to this option, you can decide whether to show links fordownloading Microsoft Lync 2010 Attendee or using a previous version of Microsoft OfficeCommunicator (Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007).

The meeting join scenarios are as follows:


124

If Microsoft Lync 2010 or Microsoft Lync 2010 Attendant is installed, the client starts and joinsthe meeting.

If neither Lync 2010 nor Lync 2010 Attendant is installed and Lync 2010 Attendee is installed,Lync 2010 Attendee starts and joins the meeting.

If no Lync Server client is installed, the meeting join page opens and gives the user thefollowing options:

Use Lync Web App.

Download Lync 2010 Attendee. (This link is hidden by default.)

Use a previous version of Office Communicator. (This link is hidden by default.)For the scenario in which no client is installed, you can configure the meeting join page by usingthe Microsoft Lync Server 2010 Control Panel (the Web Service page in the Security group). Youcan also configure the same settings by using the New-CsWebServiceConfiguration or Set-CsWebServiceConfiguration Lync Server Management Shell cmdlets with theShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters.

To configure the meeting join page by using the Lync Server 2010 Control Panel


2. In the left navigation bar, click Security.3. ClickWeb Service.4. Select or clear the Show Lync Attendee download link check box, depending on wh

ether you want to give users the option to download and join meetings by using Lync 2010 Attendee.

5. Select or clear the Show the link for user to join meeting using legacy client checkbox, depending on whether you want users to be able to join meetings by using a previous version of Communicator.

To configure the meeting join page by using Lync Server 2010 Management Shell


2. Run the following cmdlet:Get-CsWebServiceConfigurationThis cmdlet returns the web service configuration settings.

3. Run the following command, with the ShowDownloadCommunicatorAttendeeLink andShowJoinUsingLegacyClientLink parameters set to True or False, depending on your preference (for details about the parameters for this cmdlet, see the Lync Server Management Shell documentation):Set-CsWebServiceConfiguration -Identity global -ShowDownloadCommunicatorAttendeeLink $True -


125

ShowJoinUsingLegacyClientLink $True

Deploy Lync Server 2010 ClientsAfter you migrate users to Microsoft Lync Server 2010, do the following:

1. Use the Client Version Filter on the new Lync Server 2010 server to allow only clients withthe most current updates installed to sign in.

2. If necessary, configure the Group Policy settings that are required for client bootstrapping.For details, see Key Client Policies and Settings in the Planning documentation.Configuration of these settings is only necessary if you want to change existing clientbootstrapping policies or if you want to set new client bootstrapping policies. If you do notplan to configure client bootstrapping policies, or you want legacy client bootstrappingpolicies to remain in effect, no action is necessary.

3. Configure other user and client policies for specific users or groups of users by using LyncServer Control Panel, Lync Server Management Shell, or both. For details, see Key ClientPolicies and Settings and Migrating User Settings to Lync Server 2010 in the Planningdocumentation.

4. Deploy the latest version of Lync Server 2010 clients along with the latest cumulativeupdates. For details, see Deploying Clients and Devices in the Deployment documentation.

5. (Optional) If your organization requires Microsoft Lync 2010 enhanced presence privacymode, after migration is complete, define a Client Version Policy Rule to prevent earlier clientversions from signing in. Then, enable enhanced presence privacy mode.

Important:Do not enable Lync 2010 enhanced presence privacy mode until every user on agiven server pool has the most current client versions installed.

6. (Optional) If you use remote call control, create a group policy to set the Enable integrationwith your phone system option in the Phone integration section in Microsoft Lync 2010.

Phase 10: Decommission Legacy SiteThe following topics provide guidance in decommissioning pools, deactivating and removingservers and pools from a legacy deployment of Office Communications Server 2007 R2. Not allof the procedures listed in this section are required. Read the information in each of these topicsto determine which decommissioning procedure to use.

In This Section Decommissioning Servers and Pools

Remove BackCompatSite


126

Decommissioning Servers and PoolsThe following webpages contain details about decommissioning procedures for CommunicationsServer 2007 R2 Standard Edition or Enterprise Edition servers and pools:

Decommissioning Standard Edition at http://go.microsoft.com/fwlink/?LinkId=205889

Removing Servers and Server Roles at http://go.microsoft.com/fwlink/?LinkId=205887

Removing an Enterprise Pool at http://go.microsoft.com/fwlink/?LinkId=205888

Remove BackCompatSiteAfter all pools are deactivated and all Edge Servers have been uninstalled, run the TopologyBuilder Merge wizard to remove the BackCompatSite.To successfully publish, enable, or disable a topology when adding or removing a server role, youshould be logged in as a user who is a member of the RTCUniversalServerAdmins andDomain Admins groups. It is also possible to delegate the proper permissions for adding serverroles. For details, see Delegate Setup Permissions in the Standard Edition server or EnterpriseEdition server Deployment documentation. For other configuration changes, only membership inthe RTCUniversalServerAdmins group is required.

To remove BackCompat site from Topology Builder




4. In the Actions pane, click Merge 2007 or 2007 R2 Topology.5. Click Next to continue.

6. On the Specify Legacy Edge page, ensure that list of Edge Servers is empty. If the list is not empty, use the Remove button to remove all the legacy Edge Servers, and then click Next.


127

7. On the Specify Internal SIP port setting page, click Next.8. On the Summary page, click Next to begin merging the topologies to remove the lega

cy site.

Notes:On the Invoke Merge page you may see the following warning:

Total number of warnings is 1

Check for errors, warnings, and details in the log file at the following location: “%temp%\TopologyBuilder\[DATE-TIME]\MergeTopologyInvoke.log”

No Office Communications Server 2007 / Office Communications Server 2007 R2 Edge has been enabled for federation

Succeeded

Finished

9. Ignore the warning above and then click Finish.10. In the Status column, verify that the value is Success and then click Finish to close t

he wizard.

11. In the left pane of Topology Builder, expand the BackCompatSite and ensure no servers are listed.

12. Right-click the BackCompatSite, and then click Delete.


128

13. In Topology Builder, select the top-most node Lync Server 2010.14. From the Actions pane, select Publish Topology and then click Next.15. When the Publishing wizard completes, click Finish to close the wizard.

Migrate Using Lync Server 2010 Management Shell (optional)The following topics outline the steps needed to merge your Office Communications Server 2007R2 pools to Lync Server 2010 pools using the Lync Server Management Shell, and theassociated migration cmdlets. The topic Create a Custom Edge Server Input File defines anexample Edge Server input file, and then describes in detail the various parameters of that fileand also the necessary cmdlets that must be run to complete the migration. This section isoptional and replaces running the Topology Builder Merge wizard procedure, described in Phase4: Merge Topologies.

In This Section Define Edge Server Input File

Create a Custom Edge Server Input File

Run Migration Cmdlets

Define Edge Server Input FileIn Microsoft Office Communications Server 2007 R2, Edge Server information is not stored inWMI. As a result, the Merge-CsLegacyTopology cmdlet cannot retrieve information about yourEdge Servers. If you have Office Communications Server 2007 R2 Edge Servers that need to bemigrated, then you must create a custom XML file that contains your legacy Edge Serverinformation. To do so, it is recommended that you copy the code in the attached sample andmodify the relevant parameters to match your deployment. A copy of this code (input.xml) isincluded in the Migration folder. For a detailed explanation of the parameters and details aboutauthoring an Edge Server Input File, see Create a Custom Edge Server Input File.<?xml version="1.0" encoding="utf-8"?><TopologyInput xmlns ="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><EdgeClusters>

<EdgeCluster AP="true" MR="true" DP="true" Version="OCS2007R2"FederationEnabled=”true”>

<LoadBalancer InternalFqdn="edgeint.fqdn"ExternalDPFqdn="externalDP.fqdn" />

<Machines><Machine InternalFqdn = "node1.fqdn"/>


129

<Machine InternalFqdn = "anothernode1.fqdn"/></Machines><Ports InternalAPPort="5061" InternalDPPort="8057"

ExternalDPPort="443" /><DirectorOrEdgeNextHop Fqdn="director.fqdn.com" IsDirector="true" /></EdgeCluster>

</EdgeClusters><RegistrarClusterPort EnableAutoDiscoveryOfPorts = "false"

Port="5061" /></TopologyInput>

For a Consolidated Edge ServerEdit the input.xml file mentioned in the previous section and make the following changes listedbelow:

Replace edgeint.fqdn with the Office Communications Server 2007 R2 Edge Serverinternal FQDN.

Replace externalDP.fqdn with the Office Communications Server 2007 R2 Edge Serverexternal Data Proxy FQDN.

Replace node1.fqdn with the Office Communications Server 2007 R2 Edge Server internalFQDN.

Replace anothernode1.fqdn with the additional Office Communications Server 2007 R2Edge Server internal FQDN.

Replace director.fqdn.com with the Director or pool that is the next hop from the OfficeCommunications Server 2007 R2 Edge Server.

Set AP="true", MR="true", DP="true". Set FederationEnabled=”false” if you do not plan to use the legacy Edge Server for

federation.

Create a Custom Edge Server Input FileThe previous topic, Define Edge Server Input File, defined the building blocks for the input filerequired to merge the legacy topology using the Lync Server Management Shell. This topic divesdeeper into the layout and purpose of the input.xml file. This topic explains the variousparameters you need to set when authoring the Edge Server input.xml file.

The input.xml file, which can be created using any text editor, should look something like this:

<?xml version="1.0" encoding="utf-8"?>


130

<TopologyInputxmlns="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><EdgeClusters>

<EdgeCluster AP="true" MR="true" DP="true" Version="OCS2007R2"><LoadBalancer InternalFqdn="edgeint.fqdn”

ExternalDPFqdn="ExternalDP.Fqdn " /><Machines><Machine InternalFqdn = "node1.fqdn"/><Machine InternalFqdn = "anothernode1.fqdn"/>

</Machines><Ports InternalAPPort="5061" InternalDPPort="8057"

ExternalDPPort="443"/><DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /></EdgeCluster>

</EdgeClusters><RegistrarClusterPort EnableAutoDiscoveryOfPorts = "false" Port =

"5065" /></TopologyInput>

So what does all that mean? Well, to begin with, your XML file should start with the following XMLdeclaration: <?xml version="1.0" encoding="utf-8"?>

Note:Although it is optional, the XML declaration helps avoid any confusion regarding theversion or encoding type used in the file.

After the XML declaration you should then insert the <TopologyInput> element, like so:<TopologyInputxmlns="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">This element is very important: if <TopologyInput> is not present then schema validation will nottake place. In turn, that could cause Merge-CsLegacyTopology to try and merge a poorly-formed XML file. Because this is an XML file, it is important that this be a well-formed XML file. Asa result, you also need to add a closing tag for the <TopologyInput> element:</TopologyInput>That means that your XML file should now look like this:<?xml version="1.0" encoding="utf-8"?><TopologyInput


131

xmlns="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"></TopologyInput>

With the basic file structure in place, you are now ready to identify the Edge Server componentsdeployed in Office Communications Server. That is something you do inside the <EdgeClusters>element. With that in mind, your next step is to add opening and closing tags for the<EdgeClusters> element to the XML file:<?xml version="1.0" encoding="utf-8"?><TopologyInputxmlns="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<EdgeClusters>

</EdgeClusters>

</TopologyInput>

Inside the <EdgeClusters> element you then add as many as five child elements:

<EdgeCluster> The <EdgeCluster> element is where you define the different Edge Serverroles in your existing Office Communications Server topology. There are three roles you needto concern yourself with:

Lync Access Edge Server Previously known as the Access Proxy server, the AccessEdge Server is responsible for handling all SIP traffic that crosses your organization’sfirewall. If your topology includes an Access Edge Server, you need to add this attributeto the <EdgeCluster> element: AP="true"

Web Conferencing Edge Server The web Conferencing Edge Server (also known asthe Data Proxy server) relays traffic between the A/V Conferencing Server and externalclients. If your topology includes a web Conferencing Edge Server, you need to add thisattribute to the <EdgeCluster> element: DP="true"

A/V Edge Server The A/V Edge Server (also known as the Media Relay server)provides a single connection point that enables incoming and outgoing media traffic tohelp firewalls and Network Address Translation devices. If your topology includes an A/VEdge Server then you need to add this attribute to the <EdgeCluster> element:MR="true"Next, specify the version of Office Communications Server running in your legacydomain. For Office Communications Server 2007 R2, use this attribute and attributevalue: Version="OCS2007R2"


132

Finally, if you have enabled federation in Office Communications Server you should addFederationEnabled attribute to the <EdgeCluster> element:FederationEnabled="true"A completed <EdgeCluster> element will look something like this:<EdgeCluster AP="true" MR="true" DP="true" Version="OCS2007R2">

<LoadBalancer> The <LoadBalancer> element contains the fully qualified domain namesfor both your internal Edge Server load balancer and your external Edge Server loadbalancers. Note that for external load balancers, you must specify all your load balancers,including the Access Edge (AP), web Conferencing (DP), and A/V Edge (MR) load balancers.A complete <LoadBalancer> tag should look something like this:<LoadBalancer InternalFqdn="edgeint.fqdn "ExternalDPFqdn="ExternalDP.Fqdn” />If you do not use Edge Server load balancers then this element can be omitted.

<Machine> The <Machine> element contains the fully qualified domain name of your EdgeServer (note that this should be the server’s internal name). For example: <MachineInternalFqdn="node1.fqdn " />

<Ports> Use the <Ports> element to indicate the ports used by your Edge Servers. AnAPPort indicates an Access Edge Server, a DPPort indicates a web Conferencing EdgeServer, and an MRPort indicates a Media Relay Server. Be sure and distinguish betweeninternal ports and external ports. The following example defines the ports InternalAPPort,InternalDPPort, and ExternalDPPort:<Ports InternalAPPort="5061" InternalDPPort="8057"ExternalDPPort="443"/>

<DirectorOrEdgeNextHop> The <DirectorOrEdgeNextHop> element contains the fullyqualified domain name of your Edge Server’s next hop server: <DirectorOrEdgeNextHopFqdn="director.fqdn.com " /> If the next hop server is a Director, you must add theattribute IsDirector="true":<DirectorOrEdgeNextHop Fqdn=" director.fqdn.com " IsDirector="true"/>If the IsDirector attribute is not set to "True," Lync Server 2010 will not be able to use theOffice Communications Server 2007 R2 Director for federation.

Upon completion, the element should look similar to the following:<EdgeClusters><EdgeCluster AP="true" MR="true" DP="true"Version="OCS2007R2"><LoadBalancer InternalFqdn="edgeint.fqdn”ExternalDPFqdn="ExternalDP.Fqdn /><Machines><Machine InternalFqdn = "node1.fqdn"/><Machine InternalFqdn = "anothernode1.fqdn"/>


133

</Machines><Ports InternalAPPort="5061" InternalDPPort="8057"ExternalDPPort="443"/><DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /></EdgeCluster></EdgeClusters>

All that’s left now is to add the <RegistrarClusterPort> element; this is the section of the XML filewhere you define the port and the transport type for your Registrar cluster. A completed<RegistrarClusterPort> element, one that defines port 5065 and transport type MTLS, will looklike the following:<RegistrarClusterPort EnableAutoDiscoveryOfPorts = "false" Port ="5065" />The following conditions apply to the EnableAutoDiscoveryOfPorts parameter:

EnableAutoDiscoveryOfPorts is a required parameter but Port is an optional parameter.

If EnableAutoDiscoveryOfPorts is true and Port is provided, then the value of Port is ignored.

If EnableAutoDiscoveryOfPorts is false and Port is provided, then value of Port is used.

If EnableAutoDiscoveryOfPorts is false and Port is not provided, an error is logged as this isan unsupported configuration.

So finally, that gives us an XML file that can be used with the Merge-CsLegacyTopology cmdlet:<?xml version="1.0" encoding="utf-8"?><TopologyInputxmlns="urn:schema:Microsoft.Rtc.Management.Deploy.LegacyUserInput.2008"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><EdgeClusters>

<EdgeCluster AP="true" MR="true" DP="true" Version="OCS2007R2"FederationEnabled="true">

<LoadBalancer InternalFqdn="edgeint.fqdn”ExternalDPFqdn="ExternalDP.Fqdn " />

<Machines><Machine InternalFqdn = "node1.fqdn"/><Machine InternalFqdn = "anothernode1.fqdn"/>

</Machines><Ports InternalAPPort="5061" InternalDPPort="8057"

ExternalDPPort="443"/><DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /></EdgeCluster>

</EdgeClusters>


134

<RegistrarClusterPort EnableAutoDiscoveryOfPorts = "false" Port ="5065" /></TopologyInput>

Run Migration CmdletsThe migration process is carried out by a series of Lync Server Management Shell cmdlets.

The Merge-CsLegacyTopology cmdlet is used to migrate trusted service entries andconfiguration settings from Microsoft Office Communications Server 2007 R2 to Microsoft LyncServer 2010. This cmdlet creates an output file that contains the merged information from OfficeCommunications Server 2007 R2. This file is then used to publish information to the Lync Server2010Central Management store. Additionally, the Merge-CsLegacyTopology cmdlet allows youto input an XML file that contains Edge Server information. If you do not plan to import EdgeServer information, remove the -UserInputFileName D:\input.xml parameter from Step 2 in thefollowing procedure.

Important:Before running any of the migration cmdlets, be sure the account used is a member ofthe RTCUniversalServerAdmins group.

The steps to migrate are:

1. Start the Lync Server Management Shell: Click Start, click All Programs, click MicrosoftLync Server 2010, and then click Lync Server Management Shell.

2. Run:Merge-CsLegacyTopology -TopologyXmlFileName D:\output.xml -UserInputFileName D:\input.xmlWhere D:\output.xml is the path where Merge-CsLegacyTopology will write its output file.D:\input.xml is the path where Merge-CsLegacytopology expects to find the Edge Serverinput.xml file, defined earlier. Change the paths to match your environment accordingly.

3. Run:Publish-CsTopology -FileName D:\output.xml

4. Run:Enable-CsTopology

Note:To verify that this step completed successfully, see Verify Topology Information.

5. Run:Import-CsLegacyConfiguration

Note:You might see a warning, similar to the following, indicating a legacy policy settingname includes characters that are being replaced with an underscore. You can safely


135

ignore this warning. This policy setting name is a default policy that was included withOffice Communications Server 2007 R2. Lync Server 2010 will import this policy butreplace the offending characters with an underscore.

6. Run:Import-CsLegacyConferenceDirectory

7. Connect the pilot pool to the legacy Edge Servers by following the procedure in Connect PilotPool to Legacy Edge Servers.

Now that the merge has completed you can use Topology Builder and Lync Server Control Panelto administer the pool and view the overall side-by-side topology. For additional steps that youshould run after migration has completed, see Phase 6: Verify Your Pilot Migration.

See AlsoDefine Edge Server Input File

Create a Custom Edge Server Input File


Ls Migrate Ocs2007 r2

Documents

microsoft lync server

windows server

pilot pool lync server

sql server

new lync server

r2 edge server

legacy mediation server

collocated mediation