Ls Migrate Ocs2007 r2

Migrating from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010
Microsoft Lync Server 2010

Published: December 2010
NON-ACTIVATED VERSION www.avs4you.com
This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft 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 only pursuant to a non-disclosure agreement. Copyright 2010 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveSync, ActiveX, Excel, Forefront, Groove, Hyper-V, Internet Explorer, 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. All other trademarks are property of their respective owners.
Contents
Migration from Office Communications Server 2007 R2 to Lync Server 2010 Before You Begin the Migration Migration Process Migration Phases Planning for Client Migration Client Planning Steps during Migration Migration Considerations for Meetings Client Version Check Migrating User Settings to Lync Server 2010 Client Interoperability Phase 1: Plan Your Migration from Office Communications Server 2007 R2 User Migration Administering Servers after Migration Migrating Multiple Sites and Pools Phase 2: Prepare for Migration Apply Office Communications Server 2007 R2 Updates Run Best Practices Analyzer Back Up Systems and Data Configure Clients for Migration Phase 3: Deploy Lync Server 2010 Pilot Pool Lync Server 2010 Pilot Pool Architecture Deploy Lync Server 2010 Pilot Pool Verify Pilot Pool Coexistence with Legacy Pool Phase 4: Merge Topologies Install WMI Backward Compatibility Package Merge Using Topology Builder Merge Wizard Import Policies and Settings Verify Topology Information Phase 5: Configure the Pilot Pool 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 Phase 6: Verify Your Pilot Migration Verify Configuration Settings Run Functional Tests Against Workloads (optional) Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool Deploy Pilot Director and Edge Servers Phase 8: Move from Pilot Deployment into Production 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 R2 1 2 2 3 4 4 6 10 12 25 29 29 29 30 31 31 32 32 32 33 33 35 38 41 41 42 47 49 52 52 54 55 57 61 64 65 65 70 74 74 81 81 90
Migration) 91 Move Multiple Users 96 Migrate Response Groups 99 Run Functional Tests for Response Groups 101 Move Exchange Unified Messaging Contact Objects 102 Verify that all Exchange UM Contact Objects are removed from the Legacy Pool 103 Phase 9: Complete Post-Migration Tasks 104 Migrate Dial-in Access Numbers 104 Enable Exchange 2010 SP1 Outlook Web App and IM Integration 106 Migrate Address Book 108 Enable Remote Call Control 110 Remove Legacy Archiving and Monitoring Servers 112 Migrate Mediation Server 113 Configure Mediation Server 113 Change Voice Routes to use the new Lync Server 2010 Mediation Server 114 Transition a collocated Mediation Server to a Stand-Alone Mediation Server (optional) 115 Migrate Communicator Web Access 116 Repoint Communicator Web Access to Lync Server 2010 119 Migrate Applications Built on Microsoft Unified Communications Managed API (UCMA) 2.0 Core SDK 120 Configure Trusted application servers 120 Configure the Meeting Join Page 121 Deploy Lync Server 2010 Clients 123 Phase 10: Decommission Legacy Site 123 Decommissioning Servers and Pools 124 Remove BackCompatSite 124 Migrate Using Lync Server 2010 Management Shell (optional) 126 Define Edge Server Input File 126 Create a Custom Edge Server Input File 127 Run Migration Cmdlets 132
Migration from Office Communications Server 2007 R2 to Lync Server 2010

The topics in this section guide you through the process of migrating from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. If you intend for your Office Communications 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=206444 for an overview of the steps required to migrate from Microsoft Office Communicator 2007 R2 to Microsoft Lync Server 2010. This guide provides information specific to upgrading your existing deployment. It does not explain how to change your existing topology. This guide does not cover the implementation of new features. When a detailed procedure is documented elsewhere, this guide directs you to the appropriate document or document section. Note: This document does not address configuration specific to Enterprise Voice. The Lync Server Response Group service and Dial-in conferencing are covered. This document defines terms as specified in the following list.
migration
Moving your production deployment from a previous version of Office Communications Server to Lync Server 2010. upgrade Installing a newer version of software on a server or client computer. coexistence
The temporary environment that exists during migration when some functionality has be en migrated to Lync Server 2010 and other functionality still remains on a prior version of Office Communications Server. interoperability The 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
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 Migration

Before you begin, we recommend that you read this document and the following guides to familiarize 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 Communicator 2007 R2 to Microsoft Lync Server 2010, watch the short video at http://go.microsoft.com/fwlink/?LinkId=206444.
In This Section

Migration Process Migration Phases Planning for Client Migration
Migration Process
The recommended and supported migration procedure for Microsoft Lync Server 2010 is the side-by-side migration procedure. This topic describes why you should use side-by-side migration and includes information about coexistence and an alternate migration method. Side-By-Side Migration In nearly every migration, you should use the side-by-side migration path. In a side-by-side migration, you deploy a new server with Lync Server 2010 alongside a corresponding server that is running Office Communications Server 2007 R2, and then you transfer operations to the new server. If it becomes necessary to roll back to Office Communications Server 2007 R2, you have only to shift operations back to the original servers. Be aware that in this situation, any new meetings scheduled with upgraded clients will not work, and the clients would also need to be downgraded.
Coexistence Testing After you have deployed Lync Server 2010 in parallel with Office Communications Server 2007 R2, the topology represents a coexistence testing state of the two deployments. Before migrating to 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. Prior to migrating all users in Phase 8: Move from Pilot Deployment into Production, it is very important that you understand the state of each deployment and ensure that each deployment is functional and working properly. Typically, this coexistence testing phase exists throughout the pilot testing of Lync Server 2010. Legacy users are moved to Lync Server 2010 for a period of time to ensure that application compatibility and features and functions are working properly. After pilot 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 Shell The recommended method for migrating to Lync Server 2010 is described in Phase 4: Merge Topologies. 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-line approach 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 replaces the Topology Builder Merge wizard procedure described in Phase 4: Merge Topologies, the recommended 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 Phases
In Microsoft Lync Server 2010communications software, you define sites on your network that contain Lync Server 2010 components. A site is a set of computers that are well-connected by a high-speed, low-latency network, such as a single local area network (LAN) or two networks connected by a high-speed fiber optic network. A Front End pool is a set of Front End Servers configured identically, that work together to provide services for a common group of users. A pool provides scalability and failover capability to your users. Each server in a pool must run an identical server role or roles. A Standard Edition server, designed for small organizations, also defines a pool and runs on a single server. This enables you to have Lync Server functionality for a lesser cost, but does not provide a true highavailability solution.
The following phases describe the process of a pool migration from Office Communications Server 2007 R2 to Lync Server 2010. For multiple sites containing multiple pools, each individual pool 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
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 during migration. Implementing Lync Server 2010 in a different sequence is not supported.
Planning for Client Migration

This section outlines client-related considerations when planning a migration to Microsoft Lync Server 2010communications software. It discusses the user impact of migrating meetings and the type of information that is migrated. Because a migration process often requires a period of time during which various client versions coexist, this section also provides information about planning 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 Migration This topic discusses important planning considerations for migration and outlines the recommended client-related steps during the migration process. To facilitate a smooth migration to Microsoft Lync Server 2010communications software, you should consider how users will be affected 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 Migration To help minimize the impact of migration on user productivity, include the following client-related considerations during the migration planning phases. In Lync Server 2010, most of the Group Policy settings used in previous Office Communications Server releases are now controlled by in-band provisioning client policies that are server-based. You can manage these settings by using the Lync Server Control Panel, the Windows PowerShell command-line interface, or both. To understand how Group Policy settings in your existing deployment map to Lync Server 2010 settings, see Migrating User Settings to Lync Server 2010.
Office Communicator 2007 R2 client bootstrapping policies are also used by Lync Server 2010. It is only necessary to configure these policies if you want to change existing policies or if you want to set new 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. For details, see Migrating User Settings to Lync Server 2010. Determine how Lync Server 2010 clients will interact with previous client versions. For details, see Client Interoperability. For manager/delegate support, both managers and delegates must be migrated to Lync 2010 at the same time. If you are deploying conferencing, understand how meetings have changed in Lync Server 2010 and determine how migration will affect new and existing meetings. For details, see Migration Considerations for Meetings. Decide how users who do not have Lync 2010 installed will participate in Lync Server 2010 meetings and configure the meeting join page accordingly. For example, in addition to Lync Web App, you can allow users to join meetings by using Microsoft Lync 2010 Attendee or a previous version of Communicator. For details, see Configure the Meeting Join Page.
Overview of Client-Related Tasks during the Migration Process Phases 2 and 9 of the migration process include specific steps for migrating clients. These steps are summarized below. For more information, see the detailed steps for these phases in the migration process. In Phase 2: Prepare for Migration, use client version rules on your existing server to allow only clients with the most current updates to sign in, and to block Lync Server 2010 clients from signing in. In Phase 9: Complete Post-Migration Tasks, after users have been migrated to Lync Server 2010, do the following: 1. Use client version rules on your new Lync Server 2010 server to allow only clients with the 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. Configuration of these settings is only necessary if you want to change existing client bootstrapping policies or if you want to set new 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 using Microsoft Lync Server 2010 Control Panel, Windows PowerShell command-line interface, or both. 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, after migration is complete, define a Client Version Policy Rule to prevent earlier client versions from signing in. Then, enable enhanced presence privacy mode. For details, see Configuring Enhanced Presence Privacy Mode in the Deployment documentation.
Important: Do not enable Lync 2010 enhanced presence privacy mode until every user on a given server pool has the most current client versions installed. Lync 2010 privacy settings are not honored by earlier client versions. If earlier clients are allowed to sign in, a Lync 2010 users availability, contact information, or photo could be viewed by someone who has not been authorized to do so. Additionally, a Lync 2010 users privacy management options are reset if that user subsequently logs on with an earlier version of the client. 6. (Optional) If you use remote call control, create a group policy to set the Enable integration with your phone system option in the Phone integration section in Lync 2010. Migration Considerations for Meetings The 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 2010communications software compatibility with meetings on earlier server versions Configuring the Meeting Join webpage
Changes to Meetings in Lync Server 2010 In 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 the Lync Server 2010 server. For users who have been migrated to the Lync Server 2010 server but do not have Lync 2010 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 Options In earlier versions of Office Communications Server, scheduled meetings allowed anonymous users to attend meetings by default. In Lync Server 2010, meeting access for scheduled meetings is set to My company by default. Anonymous users and participants who use dial-in conferencing but for whom authentication fails are transferred to the lobby. Presenters can admit these users to the meeting. However, for unscheduled Lync Server meetings, including Meet Now meetings, participant
10
access is set to Everyone, including people outside my company by default, so anonymous users can join without waiting in the lobby. Lync Server 2010 Meeting Clients You can use the following clients to join meetings scheduled through the Online Meeting Add-in for 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 Join Webpage section later in this topic.)
You cannot use the following clients to join meetings scheduled through the Online Meeting Addin for Lync 2010: Communicator Web Access Microsoft Office Live Meeting 2007
The Lync Web App or Lync 2010 Attendee are the recommended alternatives for users who do not have Lync 2010 or Lync 2010 Attendant installed. Migrating Users Based on Their Conferencing Needs Consider migrating frequent meeting organizers early in the process so that they can take advantage of the new sharing, collaboration, and lobby management features of Lync Server 2010. For users who need web conferencing features specific to Live Meetingparticularly support for large meetings and break-out roomsyou 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 they can continue to schedule server-based Live Meeting web conferences.
Migrating Existing Meetings and Meeting Content When a user account is moved from Microsoft Office Communications Server 2007 R2 to a Lync Server 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 users personal identification number (PIN).The users current PIN continues to work until it expires or the user requests a new PIN. Meeting content.You should advise meeting organizers to reload content into their scheduled meetings after migration.
The following information does not move to the new server:
Notes: When the Online Meeting Add-in for Lync 2010 is first used to schedule new meetings, a new
11
default conference identifier is created. The default conference identifier is the http address and conference ID that is ordinarily reused for all scheduled meetings. This should only be an issue for organizers who memorize their conference identifier and give it out to others. Most meeting attendees will join by clicking the join link in the new meeting invitation, and previously scheduled Office Communications Server 2007 R2 meetings will continue to work. User Experience During Migration This section discusses the conferencing experience of users migrated to Lync Server 2010 both before and after Lync 2010 is installed. Before Lync 2010 Is Installed After a user is migrated to the Lync Server 2010 server, but before new clients are installed, the following Office Communications Server 2007 R2 client functionality continues to work on the new 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 Communicator 2007 R2 Dial-in conferencing numbers

Note: Existing dial-in conferencing numbers work whether the meeting is hosted on Office Communicator 2007 R2 server or a Lync Server 2010 server. However, the latest Office Communicator 2007 R2 cumulative update is required on the Office Communicator 2007 R2 server pools.
After Lync 2010 Is Installed When a migrated user installs Lync 2010, the Online Meeting Add-in for Lync 2010 is installed too. 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 most meeting 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 meeting in the new Lync 2010 meeting format. When the organizer changes any of these details, the add-in will prompt the organizer to manually reschedule the meeting and send an updated meeting invitation to all participants. In an IT-managed deployment of Lync 2010, the administrator has the option of uninstalling the Conferencing Add-in for Microsoft Office Outlook, which is used to schedule Live Meeting server and service-based meetings. However, you may have users who need to continue to schedule 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:
12
All meeting links in previously sent meeting invitations, including Communicator conference calls (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 Office Communicator 2007 R2 users. Note: In previous versions of Office Communications Server, all users could initiate desktop sharing in meetings. In Lync Server 2010 only meeting presenters can initiate desktop 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 must have a meeting presenter promote them to presenter so that they can initiate desktop sharing.
Meetings with Federated Organizations that Use Previous Clients Users in federated organizations who are using Microsoft Office Communicator 2007 or Microsoft Office Communicator 2005 clients cannot join Lync Server 2010 meetings in your organization if those meetings are locked by the organizer. You need to reschedule these meetings in Lync Server 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 Communications Server Users who have Lync 2010 installed can attend meetings hosted on earlier versions of Office Communications 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 client installed in order to attend. The email invitation contains instructions for installing the Live Meeting client.
Configuring the Meeting Join Webpage You can control the clients that are available for joining scheduled Lync Server 2010 meetings by configuring the meeting join page. When a user clicks a meeting link, the meeting join page detects whether a client is already installed on the users computer. If a client is already installed, the default client opens and joins the meeting. If a client is not installed, the meeting join page displays options for joining the meeting with alternate clients. The meeting join page always contains the option to use Microsoft Lync Web App. In addition to this option, you can decide whether to show links for Microsoft Lync 2010 Attendee or a previous version of Communicator. The scenarios are as follows: If Lync 2010 or Microsoft Lync 2010 Attendant is installed, the client starts and joins the meeting.. If neither Lync 2010 nor Lync 2010 Attendant is installed and Lync 2010 Attendee is installed, Lync 2010 Attendee starts..
13
If no Lync Server 2010 client is installed, the meeting join webpage appears and gives the user 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 can configure the meeting join page in Microsoft Lync Server 2010 Control Panel (that is, under the Security, Web Service settings). You can also configure these same settings by using the NewCsWebServiceConfiguration or Set-CsWebServiceConfigurationWindows PowerShell cmdlets with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters. Client Version Check The Client Version Check application provides you with a way to define a set of rules that specify the version of clients that are supported in your Microsoft Lync Server 2010 environment. When two clients of differing versions interact, the features that are available to either client can be limited by the capabilities of the other released client. To make the greatest use of features included in Microsoft Lync Server 2010communications software and to improve the overall user experience, you can use the Client Version Check to restrict the client versions that are used in your Lync Server environment. Using Client Version Policy to Specify Supported and Restricted Versions You can create client version policies to explicitly support or restrict client versions. When a supported client logs on or is invited to a session, the client version policy checks the SIP User Agent header to determine the client version. Depending on the version of the client, and the rules 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 Update Service or Microsoft Update (that is, the Allow and Upgrade option). This action is available only 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 can upgrade their client. The message comes with the URL that you specify, and the user can clickthat URL to go to the page represented (that is, the Allow with URL option) and upgrade their 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 Upgrade option). 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 the user is using a client that is not supported. The message comes with the URL that you specify, and the user can click that URL to go to the page represented (that is, the Block with URL option).
14
Each pool maintains a client version control list that you configure. This list contains rules that specify the client versions you want to filter and the appropriate action for each client version. The Client Version Check can act according to a specific client version number. It can also act according to a client version that is less than or equal to or greater than or equal to the version number that you specify. The Client Version Check also includes a configuration option that specifies 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 handled during 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 different levels of scope are triggered, the scope with the lowest level of granularity is applied. For example, if a service level rules states that the client should be blocked, but a user level rule also states that the client should be allowed, the client will be allowed as a user level rule is the 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 specific version 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 with URL, 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 URL options.
A default list of rules is installed when you install Lync Server 2010. To customize the set up rules for your deployment, you can edit an existing rule, or you can create a new rule. If you do not want 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 Communicator and Microsoft Communicator Phone Edition that try to connect to Lync Server 2010. If you would like to change this behavior, you can create a new rule to allow earlier clients to 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 not recommend this approach. Important: The rules are listed in their order of precedence. For example, if you have a rule that allows Communicator clients with a version 1.5 or later to connect, followed by a rule blocking clients earlier than version 2.0, the first rule will match and thus takes
15
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 to configure 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 2010 This topic provides the information you need to successfully migrate user and client settings from Microsoft Office Communications Server 2007 R2 to Lync Server 2010. In Microsoft Lync Server 2010communications software, most of the group policy settings used in previous versions of Office Communications Server are now controlled by server-based, or inband provisioning, client policies. In addition, certain Group Policy settings are used for client bootstrapping. 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-line interface cmdlet equivalents for Office Communicator 2007 R2 Group Policy settings Selected new Lync Server 2010 user and client settings
Group Policy Settings for Client Bootstrapping Because 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 set new 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. Group Policies Needed for Client Bootstrapping
Group Policy setting Description
ConfigurationMode
Specify how Microsoft Lync 2010 identifies the t ransport and server to use during sign-in. If you enable this policy setting, you must specify Ser verAddressInternal, ServerAddressExternal, an d Transport. If you enable ConfigurationMode, you must con figure this setting, which specifies the server na me used by clients and federated contacts whe n connecting from outside the external firewall. If you enable ConfigurationMode, you must con figure this setting, which specifies the server na me used when clients connect from inside the o rganizations firewall. If you enable ConfigurationMode, you must spe
ConfigurationMode\ServerAddressExternal
ConfigurationMode\ServerAddressInternal
ConfigurationMode\Transport
16
cify Transport Layer Security (TLS). on Transmissi Control Protocol (TCP) is no longer supported. ConfiguredServerCheckValues Specifies a list of server version names separat ed by semi-colons that Microsoft Lync Server 2 010 will log on to, in addition to the server versi ons that are supported by default. During sign-in, Lync Server 2010 attempts to c onnect to the server using TLS. If is the attempt is not successful, Lync tries to connect using H TTP. Use this policy to disable the fallback HTT P connection attempt. Requires the user to provide logon credentials f or Lync rather than automatically using the Win dows credentials during sign-in to a Session Ini tiation Protocol (SIP) server. By default, Lync checks the server name and v ersion before signing in. Set this policy to 1 in o rder to bypass the server version check. This policy allows Lync 2010 to use Backgroun d Intelligent Transfer Service (BITS) to downloa d the Address Book Services files. Enables Lync to send and receive instant mess ages more securely. This policy has no effect o n Windows .NET or Microsoft Exchange Server services. If you do not configure this policy setting, Lync can use any transport. But if it does not use TL S and if the server authenticates users, Lync m ust use either NTLM or Kerberos authentication . When set to False, allows Lync to automatically detect and more securely communicate with SI P servers that have non-standard fully qualified domain names (FQDNs). Turn on tracing for Lync, primarily for use to as sist customer problem solving. This policy defines the behavior of the Lync Fir st Run user experience. This setting determine s whether the First Run is enabled, and whethe
DisableHttpConnect
DisableNTCredentials
DisableServerCheck
EnableBitsForGalDownload
EnableSIPHighSecurityMode
EnableStrictDNSNaming
EnableTracing FirstRunLaunchMode
17
r it runs automatically. HelpMenuText HelpMenuURL Specifies the text to display to the user in the H elp menu for the Help website. Specifies which website to open when the user selects the Help menu text item in the Help me nu. Both HelpMenuText and HelpMenuURL ne ed to be specified in order for the Help menu ite m to appear in Lync. Prevents users from running Lync. You can con figure this policy setting under both Computer Configuration and User Configuration, but the p olicy setting under Computer Configuration tak es precedence. Enables Lync to store passwords. Defines when to turn on SIP compression. By d efault, SIP compression is enabled based on a dapter speed. Note that setting this policy might cause an increase in sign-in time.
PreventRun
SavePassword SipCompression
Obsolete Group Policies The following table lists the Office Communicator 2007 R2 Group Policy settings that are either obsolete or superseded in Lync Server 2010. Obsolete Group Policies
Obsolete Group Policy Lync Server 2010 in-band provisi oning setting Windows PowerShell cmdlet

None EnableP2PVideo AllowCallForwarding ucEnableSipSecurityMode AudioBitRate VideoBitRate ucMaxVideoRateAllowed
AbsUseFallback DisablePC2PCVideo DisableRCCForwarding EnableUPNP MaxAudioVideoBitRate
Set-CsConferencingPolicy Set-CsVoicePolicy
Set-CsConferencingPolicy Set-CsMediaConfiguration
Configuring Clients by Using Windows PowerShell In Lync Server 2010, client policies, except for those required for bootstrapping are configured by using Windows PowerShell cmdlets or the Lync Server Control Panel. This section summarizes the Windows PowerShell cmdlets and parameters which correspond to Office Communications Server 2007 R2 Group Policy settings.
18
CsClientPolicy The majority of Group Policy settings from previous versions of Office Communications Server can be configured by using the Windows PowerShell cmdlets New-CsClientPolicy or SetCsClientPolicy. For details, see the Lync Server Management Shell documentation. Most CsClientPolicy parameters have the same name as the equivalent Office Communications Server 2007 R2 Group Policy. This overview section summarizes the renamed, unchanged, and new policies that can be set by using CsClientPolicy. Policies Renamed in Lync Server 2010
Office Communications Server 2007 R2 Group Policy Lync Server 2010 in-band provisio ning setting / CsClientPolicy para meter Description
AllowUnencryptedFileTransfer
EnableUnencryptedFileTransfer

CallLogAutoArchivingPolicy EnableCallLogAutoArchiving
When set to True, users will be allowed to excha nge files with external u sers whose instant mes saging software does n ot support encrypted file transfers. When set to F alse, users will only be able to exchange files w ith external users who h ave software that suppo rts encrypted file transfe rs. Enables/disables autom atic archiving of call log s to Microsoft Outlook mailbox. Indicates the amount of time Lync 2010 waits be fore automatically refres hing the membership lis t of any distribution grou p that has been "expan ded" in the Contacts list . (Expanding a distributi on group means display ing all the members in t hat group.) DGRefreshI nterval can be set to an
DGRefreshPeriod
DGRefreshInterval
19
y integer value between 30 seconds and 28,800 seconds (8 hours), inclu sive. The default value i s 28,800 seconds. EnableFullScreenVideoPreviewDis abled EnableFullScreenVideo When set to True, this p arameter does two thing s: 1) enables full screen video (with the correct a spect ratio) for Lync 201 0 calls; and, 2) disables video preview for Lync 2010 calls. When set to False then full screen vi deo is not available in L ync 2010, but video pre view is available. Enables/disables autom atic archiving of IM conv ersations to Outlook ma ilbox. Enables/disables ability for the user to specify th e Music On Hold file. Enables/disables Music On Hold. Note that the c orresponding Group Pol icy setting is DisableCli entMusicOnHold. These settings also apply to Mi crosoft Lync 2010 Atten dant. When set to True, any ti me you are added to so meones Contacts list y ou will receive notificati on that you have been a dded to the list. In additi on, the notification dialo g box will provide option s for you to add this per son to your Contacts list
IMAutoArchivingPolicy
EnableIMAutoArchiving
MusicOnHoldAudioFile

MusicOnHoldAudioFile EnableClientMusicOnHold
MusicOnHoldDisabled
NotificationsForNewSubscribers
EnableNotificationForNewSubscr ibers
20
, or to block them from i vewing your presence i nformation. When set to False, you will not be no tified if you are added to someones Contacts list . PC2PCASEncryption P2PAppSharingEncryption Enables or disables app lication sharing encrypti on in peer-to-peer (two users) conversations. When set to True, a 3second dial tone will be played any time a Lync 2010-compatible hands et is taken off the hook. (A Lync 2010 handset l ooks like a standard tel ephone, but plugs into a USB port on your comp uter and is used to mak e Lync 2010 calls rather than "regular" phone cal ls.) When set to True, a 30-second dial tone is p layed any time a Lync 2 010-compatible handset is taken off the hook. Attendant - Safe Transf er
PlayAbbrDialTone
PlayAbbreviatedDialTone
SafeTransfer
AttendantSafeTransfer
The following table summarizes the unchanged policies that can be set by using CsClientPolicy. Unchanged Client Policy Names
Lync Server 2010 in-band provisioning setting / C sClientPolicy parameter Description
AutoDiscoveryRetryInterval
After a failed connection attempt, specifies the amount of time Lync 2010 waits before trying a gain to connect to Lync Server. The AutoDisco veryRetryInterval can be set to any integer valu e between 15 and 480 minutes (8 hours), inclus ive. The default value is 30 minutes.
21
BlockConversationFromFederatedContacts CalendarStatePublicationInterval CustomStateURL DisableCalendarPresence DisableEmailComparisonCheck DisableEmoticons DisableFederatedPromptDisplayName
Blocks conversation from federated contacts. Sets time interval to publish calendar data to pr esence. Sets custom presence states URL. Disables calendar presence. Disables email comparison check for Outlook p ublic IM connectivity integration. Disables emoticons in instant messages. Prevents showing the display name of federate d contacts in the notification dialog (does not in clude contact who use public IM connectivity). Disables publishing free/busy information. Configures handset use on locked computer. Prevents HTML text in instant messages. Prevents Ink in instant messages.
DisableFreeBusyInfo DisableHandsetOnLockedMachine DisableHTMLIM DisableInkIM
DisableMeetingSubjectAndLocation DisableOneNote12Integration
DisableOnlineContextualSearch DisablePhonePresence DisablePICPromptDisplayName

Disables Microsoft OneNote integration. Disables online contextual search. Disables call presence.
Disables publishing meeting subject and locatio n information.
Prevents showing the display name of public I M connectivity contacts in the notification dialog box. Disables presence note. Prevents rich text in instant messages. Prevents users from saving instant messages. Enables the state Appear Offline. Turns on event logging for Lync 2010. Specifies instrumentation. Turns on tracing for Lync 2010. Allows hyperlinks in instant messages. Specifies how often Lync 2010 retrieves MAPI data from the Exchange public folders. MAPIPo llInterval can be set to any integer value betwe
DisablePresenceNote DisableRTFIM DisableSavingIM EnableAppearOffline EnableEventLogging EnableSQMData EnableTracing EnableURL MAPIPollInterval
22
en 5 minutes and 480 minutes (8 hours); ve. inclusi The default value is 30 minutes. MaximumNumberOfContacts Indicates the maximum number of contacts a u ser is allowed to have. The maximum contacts can be set to any integer value between 0 and 1000, inclusive. When set to 0, that prevents th e user from having any contacts. For users of Microsoft Exchange Server 2007 o r later, WebServicePollInterval specifies how of ten Lync 2010 retrieves data from Exchange W eb Services. WebServicePollInterval can be set to any integer value between 5 minutes and 48 0 minutes (8 hours); inclusive. The default valu e is 30 minutes.
WebServicePollInterval
The following table summarizes the new policies that can be set by using CsClientPolicy. New Lync Server 2010 Client Policies
Lync Server 2010 in-band provisioning setting / CsClientPolicy parameter
AbsUsage (in-band) / AddressBookAvailability ( Windows PowerShell) ConferenceIMIdleTimeout

Description
Can be set to download the Address Book only, use Address Book web search only, or use bot h. Indicates the number of minutes that a user can remain in an instant messaging session without either sending or receiving an instant message. Replaces the default Lync 2010 help link with th e location of your organization-specific Help. Us e in conjunction with EnableEnterpriseCustomiz edHelp. URL for a web site that can be added to error messages in Lync 2010. Enables or disables the contact card organizati on tab. Enables or disables the activity feeds tab. Disables device warnings that appear wheneve r a faulty or obsolete device is detected. Disables network quality warnings that may app ear during a conversation.
CustomizedHelpURL
CustomLinkInErrorMessages DisableContactCardOrganizationTab DisableFeedsTab DisablePoorDeviceWarnings DisablePoorNetworkWarnings
23
DisplayPhoto DisplayPublishedPhotoDefault EnableDelegation EnableDiagnosticsLogsCollection
Determines whether or not photos (of both the user and his or her contacts) are displayed. Sets the default for display of other contacts pu blished photos. Can be overridden by users. Enables the call delegation. See also EnableEx changeDelegationSync in this table. Enables or disables the Collect Logs button, w hich is used to collect logs for the investigation of audio, video, or connectivity issues. This feat ure allows the user to capture the necessary lo gs and metrics and compress them into a .cab f ile. The user then manually uploads logs per th e administrators instructions, who sends the lo gs to Microsoft for troubleshooting purposes. Allows you to replace the default Lync 2010 hel p link with the location of your organizationspecific online help. Use in conjunction with Cu stomizedHelpURL. When enabled, Lync 2010 creates a correspon ding personal contact in Microsoft Outlook for e ach person on a users Contacts list. When enabled, the client retrieves the Exchang e calendar delegates (users who have authorin g and editing rights on the managers calendar) and uses these settings to update delegates in Lync Server 2010. Use this setting in conjunctio n with the EnableDelegation setting, which is co nfigurable in the CsVoicePolicy cmdlets or in L ync Server Control Panel. When enabled, a user can log on to a Lync 201 0 Phone Edition phone in a shared workspace using his or her Lync Server 2010 account. When enabled, a Lync 2010 call is placed any ti me a user employs the click-to-call feature. Indicates which Microsoft Outlook contact folde rs (if any) should not be searched any time Lyn c 2010 searches for new contacts. Timeout interval for a user logged on to a "hot d esk" phone.
EnableEnterpriseCustomizedHelp
EnableExchangeContactSync
EnableExchangeDelegateSync
EnableHotdesking
EnableVOIPCallDefault ExcludedContactFolders
HotdeskingTimeout
24
MaximumDGsAllowedInContactList MaxPhotoSizeKB
Indicates the maximum number of distribution r goups that a user can configure as a contact. Set this policy to 0 to remove photos from Lync 2010 and disable the photo user interface. Defa ult: 10. Enables or disables display of photos. Provides a way to add settings not covered by t he default parameters. Represents the Address Book attributes that sh ould be searched any time a user searches for a new contact. Enables or disables the Manage Privacy Relat ionships option in the View by menu. Shows or hides the Recent Contacts option in the Display Options menu. Controls whether users see the Edit in Mysite selection in their My Picture options. Edit in M ysite allows users to show a picture from Micro soft SharePoint MySite. External URL for the SharePoint site used for k eyword searches (also known as expert search es). This URL will appear at the bottom any of k eyword search results that appear in Lync 2010 . If the user clicks this URL, his or her web brow ser will open up to the SharePoint site, giving th e user the opportunity to conduct searches usin g SharePoints search capabilities. Internal URL for the SharePoint site used for ke yword searches (also known as expert searche s). This URL will appear at the bottom any of ke yword search results that appear in Lync 2010. If the user clicks this URL, his or her web brows er will open up to the SharePoint site, giving the user the opportunity to conduct searches using SharePoints search capabilities. Internal URL for the SharePoint site used for ke yword searches (also known as expert searche s). Lync 2010 will use the SharePoint site locat ed at this URL any time an external user (that is , a user who has access the system from outsid
PhotoUsage PolicyEntry SearchPrefixFlags
ShowManagePrivacyRelationships ShowRecentContacts ShowSharepointPhotoEditLink
SPSearchCenterExternalURL
SPSearchCenterInternalURL
SPSearchExternalURL
25
e the organizations firewall) conducts a d keywor search. SPSearchInternalURL Lync 2010 will use the SharePoint site located at this URL any time an internal user (that is, a user who has logged on from inside the organiz ations 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 Policies The following table lists the Lync Server 2010 in-band provisioning settings and Windows PowerShell cmdlets that are either not configurable through Windows PowerShell or configured by 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 and have been renamed in Lync Server 2010. Communications Server 2007 R2 Group Policy Equivalents
Office Communications Server 2007 R2 Group Policy setting Lync Server 2010 i n-band provisioni ng setting dlet

Windows PowerShell cm Cmdlet parameters
AbsInsideURL AbsOutsideURL Portrange\MaxMediaP ort Portrange\MinMediaP ort Portrange\Enabled
AbsInternalServer None Url AbsExternalServe None rUrl ucMaxMediaPort ucMinMediaPort ucPortRangeEna bled None None None CsConferencingPolicy CsConferencingPolicy
None None None None None AllowExternalUserControl EnableDataCollaboration
DisableApplicationSha AllowParticipantC ringControl ontrol DisableDataConferenc EnableDataColla ing boration DisableAVConferencin AllowIPAudio, All g owIPVideo
CsConferencingPolicy; AllowIPAudio, AllowIPVid CsUser eo; AudioVideoDisabled
26
DisableFileTransfer
AllowFileTransfer
CsFileTransferFilterConfiguration -(Lync 2010)CsConfere ncingPolicy (Web conf erencing) CsIMFilterConfiguratio n None CsMediaConfiguration CsUser CsUser WarnMessage None EncryptionLevel LineURI UCEnabled, RemoteCall ControlTelephonyEnable d MCSVoiceMail AllowSimulRing None
IMWarning MRASServerURI PC2PCAVEncryption msRTCLine TelephonyMode
IMWarning mrasURI ucPC2PCAVEncr yption line TelephonyMode
ExUMEnabled DisableSimultaneous Ringing VoicemailURI
ExUMEnabled
CsUser
AllowSimultaneou CsVoicePolicy sRinging VoicemailURI None
Client Interoperability This topic discusses the ability of Microsoft Lync Server 2010communications software clients to coexist 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 with multiple clients and multiple client versions. InteroperabilityThe ability to interact with another user who is signed in using a different client 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 must ensure 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 interacting with Microsoft Office Communications Server 2007 R2 and Microsoft Office Communications Server 2007 clients. For details, see the "Lync Server 2010 Interoperability with Previous Client Versions" section later in this topic. For best results with meetings, see Migration Considerations for Meetings.
27
Compatibility among Lync Server 2010 Clients All Lync Server 2010 clients can interoperate with other Lync Server 2010 clients. Most Lync Server 2010 clients also support the multiple points of presence scenariothat is, a single user can be signed in at multiple locationswith the following exception: Microsoft Lync 2010 Attendant users can only be signed in simultaneously with phones running Microsoft Lync 2010 Phone Edition. Simultaneous sign-in with other Lync Server 2010 clients is not supported.
Multiple Points of Presence (MPOP) with Previous Client Versions The following table describes the client versions that are supported when a single user is signed in 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 Locations
Current client version Client version MPOP support (with required upd ates)
Lync 2010
Microsoft Lync 2010 Attendee
Microsoft Office Communications Server 2007 R2 Microsoft Office Communications Server 2007 2007 R2 release of Microsoft Office Communic ator Web Access Microsoft Office Communicator Web Access (2 007 release) Phones running Microsoft Office Communicator 2007 R2 Phone Edition Phones running Microsoft Office Communicator 2007 Phone Edition Microsoft Communicator for Mac 2011
Microsoft Lync 2010 Attendant Phones running Lync 2010 Phone Edition
Phones running Microsoft Lync 2010 Phone Edi tion Microsoft Office Communicator 2007 R2 Microsoft Office Communicator 2007 Microsoft Communicator for Mac 2011
2007 R2 release of Microsoft Office Communic ator Mobile
Microsoft Office Communicator 2007 R2 Microsoft Office Communicator 2007 Microsoft Office Communicator 2007 R2 Phone Edition Microsoft Office Communicator 2007 Phone Edi
28
tion Microsoft Communicator for Mac 2011 Lync Server 2010 Interoperability with Previous Client Versions This section discusses Lync Server 2010 interoperability support for clients that shipped with Office Communications Server 2007 R2 and Office Communications Server 2007. Note: Communicator Web Access and Microsoft Office Live Meeting 2007 cannot be used to join new meetings scheduled on Lync Server 2010. Lync 2010, Microsoft Lync 2010 Attendee, and Microsoft Lync Web App are the recommended alternatives. For details, see Migration Considerations for Meetings. IM, Presence, Voice, and Video Interoperability The following table describes the availability of these features during migration. IM, Presence, and Voice Interoperability with Previous Client Versions
Lync Server 2010 clie nts Office Communications S erver 2007 R2 clients Office Communications S erver 2007 clients
Lync Server 2010 Clients

IM, presence, voice, and video supported IM, presence, voice, and video supported
IM, presence, and video supported; some voice fe ature limitations (see the following section in this to pic)
Interaction with Microsoft Office Communicator 2005 clients (basic presence and IM) is supported only if the Office Communicator 2005 user is on a federated network. Voice Interoperability Considerations Voice interoperability issues to be aware of are as follows: Office Communicator 2007 does not support voice features added in Communicator 2007 R2 and 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 to an earlier version of Office Communications Server. You cannot park a call to a Office Communications Server 2007 client or device.
Conferencing Interoperability Considerations When a user account is moved from Communications Server 2007 R2 to a Lync Server 2010 server, the following information moves along with the user account: Meetings already scheduled by the user. The users PIN (there is no need for new PIN assignment).
The following information does not move to the new server:
29
Meeting content. You should advise meeting organizers to reload content into their scheduled meetings after migration. Previous client version interoperability with Lync Server 2010 meetings Lync 2010 interoperability with meetings hosted or scheduled on previous server versions
The following tables describe two conferencing interoperability scenarios:
Previous Client Versions and Lync Server 2010 Meetings

Communicator 2007 R2 and Communicator 200 7 interoperability Schedule Lync Server 2010 Meetings Join Lync Server 2010 Meetings Behavior in Lync Serv er 2010 Meetings
Before user is moved t o Lync Server 2010
Not supported.
Supported if enabled. F or details, see Migratio n Considerations for M eetings.
No access to new coll aboration features unl ess meeting is escala ted to use Lync Web App. No access to new lob by management featu res. No access to new coll aboration features unl ess meeting is escala ted to use Lync Serve r 2010. No access to new lob by management featu res.
After user is moved to Lync Server 2010, but before new clients are i nstalled

Continue using the Co nferencing Add-in for Microsoft Office Outlo ok to schedule confer ence calls and Live M eeting web conferenc es. Supported if enabled. F or details, see Migratio n Considerations for M eetings.
For details, see Migration Considerations for Meetings. Lync 2010 Interoperability With Meetings Hosted or Scheduled on Previous Versions of Office Communications Server
Lync 2010 interoperability with meetings on previ ous versions of Office Communications Server Lync 2010 user experience
Scheduling
Lync 2010 users cannot schedule meetings on earlier server versions. When modifying the end date, subject, or atten dee list of meetings migrated from previous ser ver versions to Lync Server 2010, users are pro mpted to convert the meeting to Lync Server 20 10.
Joining
No issues.
30
In meeting Manager/Delegate Interoperability
New Lync 2010 features are unavailable.
For the manager/delegate scenario, both manager and delegate must be using Lync 2010. Interoperability with Existing Custom Applications For the purposes of this discussion an existing custom application is defined as follows: The application uses the Microsoft Office Communicator Automation API or the Microsoft Unified Communications Client API. The application runs in a migration environment, on a machine where either Communicator 2007 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 Lync Server 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 as Lync 2010 is not recommended. If your organization plans to enable enhanced presence privacy mode, Unified Communications Client API custom applications may need to be rewritten. For details, see Planning for Clients, Lync 2010 New Features in the Getting Started documentation, and the Microsoft Lync 2010 SDK.
See Also
Planning for Clients
New Client Features
Phase 1: Plan Your Migration from Office Communications Server 2007 R2

This section covers planning topics for migrating from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010.
In This Section
User Migration Administering Servers after Migration Migrating Multiple Sites and Pools
User Migration
A generally accepted best practice for migrations is to create several test users and use them to conduct systems tests. After you have successfully moved and tested those accounts, you should identify a group of pilot production users and move their accounts and conduct validation tests on them. When you get satisfactory results, you can move the rest of your users to the new deployment.
31
Administering Servers after Migration

In general, you must use the administrative tools that corresponds to the server version that you want 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 Communications Server 2007 R2 or on a computer with the Office Communications Server 2007 R2 administrative tools installed. 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 Communications Server 2007 R2. Important: Only the Lync Server 2010 Control Panel should be used to move users to and from Lync Server 2010. To manage Lync Server 2010 servers and services. You cannot install the Office Communications Server 2007 R2 administrative tools and the Lync Server 2010 Control Panel on the same computer. Also, the Lync Server 2010 Control Panel is not installed automatically on each server. You must manually choose on which workstation or server you want to install the tools. To install the Lync Server 2010 Control Panel, follow the procedure inside the topic Install Topology Builder with the Administrative Tools in the Deployment documentation.
Use the Lync Server 2010 Control Panel as follows:
Migrating Multiple Sites and Pools

Microsoft Lync Server 2010 supports multi-site and multi-pool deployments. The process of migrating multiple pools from Microsoft Office Communications Server 2007 R2 to Lync Server 2010 requires the following considerations: 1. After deploying a Lync Server pilot pool and importing the Office Communications Server 2007 R2 pool configuration to the Lync Server pool, you need to define a subset of pilot users that will be moved to the Lync Server pool, and a methodology for validating the functionality of the users. 2. After deploying an Edge Server in the pilot pool, you need to validate that external users can communicate with the Lync Server pool. 3. After transitioning the federated routes from Communications Server 2007 R2 Edge Servers to the pilot Lync Server Edge Servers, you need to validate that federated users can communicate with the Lync Server pool. 4. After moving all the users and non-user contact objects, you need to validate that the Communications Server 2007 R2 pool is empty. 5. After verifying that the Communications Server 2007 R2 pool is empty, you can then
32
deactivate the pool. 6. After verifying that all pools are deactivated, and all Communications Server 2007 R2 Edge Servers have been uninstalled, use the Topology Builder Merge wizard to remove the legacy topology from the site. Finally, use Topology Builder to delete the BackCompatSite. For details about how to deactivate the legacy Office Communications Server 2007 R2 pool and servers, see Phase 10: Decommission Legacy Site.
Phase 2: Prepare for Migration

Before you begin to migrate to Microsoft Lync Server 2010 from Microsoft Office Communications Server 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 Updates
Before you migrate to Microsoft Lync Server 2010, updates must be applied to your Microsoft Office Communications Server 2007 R2 environment. The updates required are listed in the following table. For the most up-to-date information about Office Communications Server 2007 R2 updates, see Updates Resource Center for Office Communications Server 2007 R2 and Clients at http://go.microsoft.com/fwlink/?LinkId=199488. Check the Programs and Features application in the Control Panel on your Office Communications Server 2007 R2 deployment to determine if any of these updates have been applied. Office Communications Server 2007 R2 Required Updates
Application Update URL
Microsoft Office Commun July 2010 Update pa icator 2007 R2 ckage Microsoft Office Live Mee July 2010 Update pa ting 2007 ckage Microsoft Office Live Mee July 2010 Update pa ting Conferencing Add-In ckage Office Communications S September 2010 Up erver 2007 R2 date package Microsoft Office Commun July 2010 Update pa
http://go.microsoft.com/fwlink/?LinkId=204763 http://go.microsoft.com/fwlink/?LinkId=204764 http://go.microsoft.com/fwlink/?LinkId=204765 http://go.microsoft.com/fwlink/?LinkId=204766 http://go.microsoft.com/fwlink/?LinkId=204767
33
icator 2007 R2 Phone itio ckage Edn
Run Best Practices Analyzer

The Microsoft Office Communications Server 2007 R2 Best Practices Analyzer tool gathers configuration information from an Office Communications Server 2007 R2 deployment and determines whether the configuration is set according to Microsoft best practices. You can install the tool on a client computer that runs Microsoft .NET Framework 2.0, or directly on the server that runs Office Communications Server. We recommend that you install and run this tool on a client computer. The Office Communications Server 2007 R2 Administrative Tools should also be installed locally on the client computer so that the Best Practices Analyzer can collect a full set of data. For details about installing the Office Communications Server 2007 R2 Administrative Tools on a 32-bit client computer, see "32-Bit Tools: Office Communications Server 2007 R2 Deployment and Management" at http://go.microsoft.com/fwlink/?LinkId=199486. You can download the Office Communications Server 2007 R2 Best Practices Analyzer from the Microsoft Download Center at http://go.microsoft.com/fwlink/?linkid=144315.
Back Up Systems and Data
Before you begin the migration to Microsoft Lync Server 2010, we strongly recommend that you perform a full system backup and document your existing system, including an inventory of user accounts that are homed on each pool, so that you can roll back to Microsoft Office Communications Server 2007 R2 if it becomes necessary. Multiple tools and programs are available for backing up and restoring data, settings, and systems. For details and procedures, see the Office Communications Server 2007 R2 Backup and Restoration Guide at http://go.microsoft.com/fwlink/?LinkId=168162. The Backup and Restoration Guide focuses on the use of tools and programs that are provided with Office Communications Server 2007 R2 and on components that are available in Microsoft SQL Server 2008 and Microsoft SQL Server 2005.
Configure Clients for Migration

This topic contains the recommended client deployment steps you should take prior to migrating to Microsoft Lync Server 2010. These configuration changes should be made on Office Communications Server 2007 R2. It is very important that you perform these steps prior to migrating. 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 Office Communications Server 2007 R2 as listed in Apply Office Communications Server 200 7 R2 Updates. 2. On Office Communications Server 2007 R2, use Client Version Filtering to allow only cl
34
ients with the most current updates installed, as listed in Apply Office Communications Server 2007 R2 Updates to sign in. 3. On Office Communications Server 2007 R2, use Client Version Filtering to block Lync Server 2010 clients from signing in. Follow the steps described in Configuring Client Version Filtering at http://go.microsoft.com/fwlink/?LinkId=202488 to add the version f ilters listed in the following table. For each version filter, assign the action Block.
Client User agent header Version
Lync 2010 Lync Web App Lync 2010 Phone Edition Lync 2010 Attendee
OC CWA OCPhone AOC
4.*.*.* 4.*.*.* 4.*.*.* 4.*.*.*
Phase 3: Deploy Lync Server 2010 Pilot Pool
This section describes the reference topology covered in this document. It also covers the steps required to deploy a pilot deployment of Lync Server 2010, and a few key validation steps to ensure 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 Architecture

The following figure shows the pilot pool reference topology used in this document. Lync Server 2010 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 then communicate with users who are homed on Office Communications Server 2007 R2 servers. This will show interoperability between users who are homed in different pools can continue to communicate and use the existing workloads and perimeter network infrastructure.
35
Initially a Lync Server 2010 pool is deployed in parallel with Office Communications Server 2007 R2. External traffic and federation is done through the legacy Edge Server environment. In Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool, the Director and Edge Server are added to the deployment. The following table lists the fully qualified domain names (FQDNs) for the various server roles used in this topology. It is supplied solely for reference purposes.
Server Role Office Communications Server 2007 R2 FQDN Lync Server 2010 FQDN

EDGE-R2.CONTOSO.NET DIR-R2.CONTOSO.NET MEDSVR01.CONTOSO.NET
Standard Edition Server SE-R2.CONTOSO.NET Edge Server Director Mediation Server
LYNC-SE.CONTOSO.NET LYNC-EDGE.CONTOSO.NET LYNC-DIR.CONTOSO.NET Collocated on LYNCSE.CONTOSO.NET
Important We recommend deploying Lync Server 2010 Enterprise Edition for deployments that require a true high-availability solution. Important: We recommend collocating the Lync Server Mediation Server with a Lync Server Front End pool or Standard Edition server when merging an Office Communications Server 2007 R2 stand-alone Mediation Server.
36
Deploy Lync Server 2010 Pilot Pool

One of the first steps in a phased rollout is to deploy a Lync Server 2010 pilot pool. You will merge topology information and configuration settings from an existing Office Communications Server 2007 R2 pool to this pilot pool. The pilot pool is where you test coexistence of Lync Server 2010 with your Office Communications Server 2007 R2 deployment. Coexistence is a temporary state 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 your Office Communications Server 2007 R2 pool. For detailed steps about deploying Standard Edition in your pilot environment, see Deploying Lync Server 2010 Standard Edition in the Deployment documentation. For detailed steps about deploying Enterprise Edition in your pilot environment, see Deploying Lync Server 2010 Enterprise Edition in the Deployment documentation. Important: Before you deploy your pilot pool, you need to decide whether you will deploy one Lync Server 2010 pool for each existing Office Communications Server 2007 R2 pool. Some configuration settings, such as Response Group, migrate for an entire pool with a single cmdlet. Therefore, if you plan to consolidate pools or split pools into smaller pools during your migration and deployment, you need to plan which Office Communications Server 2007 R2 pools map to which Lync Server 2010 pools and adjust your migration accordingly.
Note: When creating a new topology using Topology Builder, ensure that the primary SIP domain (and any additional SIP domains) are named exactly as the legacy Office Communications Server 2007 R2 SIP domains. If not, the Topology Builder Merge wizard procedure in Phase 4: Merge Topologies will fail to create a topology. To find your legacy Office Communications Server 2007 R2 SIP domains, open the Office Communications Server 2007 R2 Administrative Tools snap-in. Right click the forest node, select Global Properties, and then under the General node note the list of SIP domains in the Domains 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 procedure that follows discusses features and settings you should consider as part of your overall pilot pool deployment process. This section only highlights key points you should consider as part of your pilot pool deployment. For detailed steps, refer to the Deployment guides mentioned earlier. The following procedures match the pilot pool reference architecture listed in Lync Server 2010 Pilot Pool Architecture. Adapt these settings to match your deployment. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required.
37
Pilot Pool Deployment Considerations 1. When you define your pilot pool, you can choose to deploy an Enterprise Edition Fro nt End Pool or a Standard Edition Server. Lync Server 2010 does not require that yo ur pilot pool match what was deployed in your legacy pool.

2. On the Select collocated server roles page, we recommend you collocate the Media tion Server in Lync Server 2010. When merging a legacy topology with Lync Server 20 10, we require that you first collocate the Lync Server 2010 Mediation Server. After me rging the topologies and configuring the Lync Server 2010 Mediation Server, you can d ecide to keep the collocated Mediation Server or change it to a stand-alone server in y our Lync Server 2010 deployment. Important: Note that Lync Server 2010 Standard Edition server pools can only be served by the collocated A/V Conferencing service installed. Thus, the check box is un available on this page but would be available on Lync Server 2010 Enterprise Edition server. Note: We highly recommend that you collocate the Mediation Server on a Front End Server or Standard Edition server. However, if you do decide to move a colloc
38
ated Lync Server 2010 Mediation Server to a stand-alone Mediation Server, e se 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 en able archiving and monitoring if you want those server roles deployed as part of your pi lot pool. Important: During pilot pool deployment, do not choose the Enable an Edge pool to be u sed by the media component of this Front End pool option. This is a featur e you will enable and bring online in a later phase of migration. Keep this settin g cleared for now.
39

6. When the publish process has completed, click Finish.
4. Continue completing the Define New Front End Pool wizard and click Finish when co mpleted. 5. To publish your topology, right-click the Lync Server 2010 node and then click Publis h Topology.
7. To install a local copy of the configuration database and start the required services, se e Setting Up Front End Servers and Front End Pools or Setting Up Standard Edition S erver in the Deployment documentation.
Verify Pilot Pool Coexistence with Legacy Pool

After you deploy the pilot pool and before you begin to migrate from Microsoft Office Communications Server 2007 R2, verify the coexistence of the two pools by using the administrative tools to view the pool information. For the Office Communications Server 2007 R2 pool, use the Office Communications Server 2007 R2 administrative tool. For the Microsoft Lync Server 2010 pool, use Lync Server 2010 Control Panel.
40
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 RTCUniversalServer Admins group. 2. Open the Office Communications Server 2007 R2 administrative tool. 3. Expand the Forest node, expand the Standard Edition Servers or Enterprise pools node, 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 Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 2. Click Topology. 3. Verify that the servers you deployed are present in your pilot pool.
41
Verify Lync Server services have started 1. From the Standard Edition server or Front End Server, open the Services applet from t he Administrative Tools group. 2. Verify that the services listed match the list in the following figure.
42
Phase 4: Merge Topologies

The following topics outline the steps needed to merge your Microsoft Office Communications Server 2007 R2 pools to Microsoft Lync Server 2010 pools. First, you use the Topology Builder Merge wizard to merge topology information. This tool collects information about your Office Communications Server 2007 R2 environment, including Edge Server information, and publishes that information to a database shared with Lync Server 2010. After you publish the merged topology, Topology Builder is used to view the Office Communications Server 2007 R2 topology information and information about the newly deployed Lync Server 2010 topology. Finally, you use 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 Package
You must install the Windows Management Instrumentation (WMI) Backward Compatibility Package as a prerequisite before running the Topology Builder Merge wizard. Lync Server 2010 stores its configuration information in a Central Management store hosted on SQL Server 2008 SP1 or SQL Server 2005 Service Pack 3. Microsoft Office Communications Server 2007 R2 used the Windows Management Instrumentation (WMI) framework. The WMI Backward Compatibility Package provides Lync Server 2010 the ability to merge WMI information from Office 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 Backward Compatibility package, you will see the following error:
If you attempt to run the Merge-CsLegacytopology cmdlet without installing the WMI Backward Compatibility package, you will see the following error:
43
To install the WMI Backward Compatibility Package 1. On the Standard Edition Server or Front End server, log on to the computer with an account 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 Build er Merge wizard is run.

Important: OCSWMIBC.msi can be installed on any machine in the domain that has the L ync Server 2010 Core Components and Lync Server Management Shell install ed, and has access to the Office Communications Server 2007 R2 topology (W MI provider to Active Directory and SQL Server).
Merge Using Topology Builder Merge Wizard

Topology Builder is a new tool introduced in Microsoft Lync Server 2010. With Topology Builder you can create, edit, and publish a Lync Server 2010 deployment topology. Additionally, the Merge feature allows you to import information from your previous Office Communications Server environments, and integrate it into a consolidated view alongside your Lync Server 2010 deployment. 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 an alternative method to using Topology Builder. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server
44
roles. For details, see Delegate Setup Permissions in the Lync Server 2010 Standard Edition or Enterprise Edition deployment documentation. For other configuration changes, only membership in 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 O K. 3. In the Save Topology As dialog box, select the Topology Builder file you want to use and 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 Ser ver and then click Next. 8. In Specify Edge Type, specify the type of Edge Server configuration and then click Ne xt. This example uses the Single Edge Server option.
45
Important: Expanded Edge is not a supported configuration. An Expanded Edge must st fir be converted to a Single Edge Server or a Load-balanced consolidated Edge server. Important If you use a Load-balanced consolidated Edge configuration, and you want to change th e membership of that configuration by creating a new Edge pool using one of the legacy C ommunications Server 2007 R2 Edge servers, you must first remove the legacy Edge serv er from the existing Communications Server 2007 R2 Edge array and then publish the topo logy. Using the Topology Builder merge wizard, you then create a new Edge pool, add th e legacy Edge server to this pool, and once again publish the topology. In this last step, yo u also have the option of adding another Edge server to the legacy Edge pool if required. A fter 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 your Edge pools internal FQDN and ports as needed, and then click Next.
10. In Specify External Edge, enter the Web Conferencing FQDN information for your Ed ge Server. Important: Before you click Next, do the next step in this procedure. Its very important th
46
at you dont miss step 11. 11. Check the This Edge pool is used for federation and public IM connectivity check box if you plan to use this Edge Server for federation. If you have multiple Edge Server s deployed, only one of them will be enabled for federation. If you do not check this bo x and you decide later that you want to enable federation, you must run the Topology B uilder 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. In the figure below, the legacy Director from the Office Communications Server 2007 R2 deployment is shown. Click Finish.
47

15. In Summary, click Next to begin merging the topologies. 16. The wizard page verifies that the merging of the topologies was successful.
13. In Specify Edge Setup, if all your Communications Server 2007 R2 Edge Servers hav e been added, click Next. If you have more Communications Server 2007 R2 Edge Se rvers to add, repeat steps 6 through 12. 14. In Specify Internal SIP port setting, select the default setting (that is, if you did not m odify the default SIP port). Change as appropriate if you are not using a default port of 5061. Click Next.
17. In the Status column, verify that the value is Success and then click Finish to close t he wizard. 18. In the left pane of Topology Builder, you should now see the BackCompatSite, which i ndicates that your Office Communications Server 2007 R2 environment has been merg ed with Lync Server 2010.
48

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: Its important that you complete the next topic, Import Policies and Settings to ensure 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 with your Microsoft Lync Server 2010 pilot pool, you need to run a Lync Server Management Shell cmdlet to migrate your Office Communications Server 2007 R2 policies and configuration settings to 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.
49
Note: Dial-in access numbers require an additional step to complete the migration to Lync Server 2010. During this period of coexistence, the dial-in access numbers that you imported exist both in your Office Communications Server 2007 R2 pool and in your Lync Server 2010 pool, but they cannot be modified in Lync Server 2010. They can be modified in Office Communications Server 2007 R2, and then imported into Lync Server 2010 by running Import-CsLegacyConfiguration. In addition, you cannot view Office Communications Server 2007 R2 dial-in conferencing access numbers by using the GetCsDialInConferencingAccessNumber cmdlet. You can view only Lync Server 2010 dial-in access numbers by using this cmdlet. For details about how dial-in access numbers 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 me mber of the RTCUniversalServerAdmins group.

3. Run: Import-CsLegacyConfiguration Important: Its a good practice to run this cmdlet whenever the Topology Builder Merge wi zard, covered in the topic Merge Using Topology Builder Merge Wizard, is run. Note: The Import-CsLegacyConfiguration cmdlet does not migrate PIN policy for d ial-in conferencing. If you do not want to use the default PIN policy on Lync Ser ver 2010, you need to modify the policy manually in your Lync Server 2010 po ol. For details on how to modify PIN policy, see Modify the Default Dial-in Conf erencing PIN Settings in the Deployment documentation. Note: If the Anonymous Participants setting for Meetings is set to Enforce per use r in your Office Communications Server 2007 R2 conferencing policy, two conf erencing policies are created during migration: one with AllowAnonymousPar ticipantsInMeetings set to True and one with AllowAnonymousParticipants InMeetings set to False.
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.
Now that the policies have been imported, use the procedure that follows to see the im ported policies in the Lync Server 2010 Control Panel.
50
To view imported policies 1. Log on to the computer with an account that is a member of the RTCUniversalServer Admins group or an account that is a member of the CsViewOnlyAdministrator role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 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 Information

The first step in verifying the merge completed successfully is to view the Microsoft Office Communications Server 2007 R2 topology information that you merged with Microsoft Lync Server 2010. In Topology Builder, the BackCompatSite node displays the fully qualified domain name (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 of each server within the pool. The following illustration is an example of a BackCompatSite node after merging an Office Communications Server 2007 R2 Standard Edition server, a Director, an Edge Server, and a stand-alone Mediation Server. You cannot edit any properties for these components. Use the BackCompatSite node to verify that all the Office Communications Server 2007 R2 pools and servers merged successfully. To view BackCompatSite in Topology Builder 1. In your Office Communications Server 2007 R2 environment, open the Office Commun ications Server 2007 R2 administrative tool and note the FQDNs for the pools and serv ers that you want to merge. 2. In your Lync Server 2010 environment, open Topology Builder, and then expand the B ackCompatSite 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 c ollocated on a Front End Server or Standard Edition server. Only server roles t hat are required for interoperability between Office Communications Server 20
51
07 R2 and Lync Server 2010 are merged.

You can also use Microsoft Lync Server 2010 Control Panel to view your merged topology. In Lync Server Control Panel, you can see each server FQDN, pool FQDN, and site name for your merged topology. Merged servers have a Site name of BackCompatSite.
To view the merged topology in Lync Server Control Panel 1. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 2. On the Select URL page, select the Standard Edition server or Front End pool that cor responds 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.
52
To see more detail about a merged pool, use the Get-CsPool cmdlet. In addition to the information that is available in Topology Builder and Lync Server Control Panel, this cmdlet displays 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 be verified 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 Micros oft 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:
53
Get-CsConferenceDirectory 3. 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 GetCsConferenceDirectory cmdlet. The FQDN of the pool that hosts the Confere nce Directory is displayed in ServiceId. ServiceId contains the type of service and FQDN of the pool. For example, UserServer:OCS2007R2.contoso.com
Phase 5: Configure the Pilot Pool

Now that the pilot pool has been created and legacy deployment information has been merged with Lync Server 2010, this section identifies a few configurations that must be made to the pilot pool.
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 Servers

After deploying Lync Server 2010, a federation route for this site is not configured. In order to use the federated route being used by Office Communications Server 2007 R2, Lync Server 2010 must 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, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper rights and permissions. For details, see Delegate Setup Permissions in the Deployment documentation. For other configuration 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 2 010, and then click Lync Server Topology Builder. 2. Select your Lync Server 2010 site.
54
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 m eans an Edge Server was not selected when the Topology Builder Merge wi zard was run. To enable this setting, see step 11 of the topic Merge Using Top ology 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.
55

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 Edge Server

For each Lync Server 2010 Front End Server or Standard Edition server and each Director in your pilot pool, you must update the list of internal servers that are authorized to connect to the Office Communications Server 2007 R2 Edge Server. Without these updates, external A/V conferencing for users joining by using the legacy Edge Server will not work. This topic explains how to add the Lync Server 2010 Front End Server or Standard Edition server and Director in your pilot pool to the list of servers that are authorized to connect to the Office Communications Server 2007 R2 Edge Server.
56
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 tha t is a member of the RTCLocalServerAdmins group. 2. From the Office Communications Server 2007 R2 Edge Server, from the Administrati ve 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 Edition server. Specify the FQDN of the Lync Server 2010 Director if you configured a static route on the pool that specifies the next hop computer by its FQDN.

Connect Pilot Pool to Legacy Mediation Server
Providing a Voice Route and Voice Policy existed in the legacy pool, after merging Office Communications Server 2007 R2 with Lync Server 2010, and running the ImportCsLegacyConfiguration cmdlet, the Lync Server 2010 pilot pool now has all the necessary configuration information to
8. After you have added an entry for each Lync Server 2010 Front End Server or Standar d Edition server and Director, click OK to close the Properties page.
After deploying Microsoft Lync Server 2010, a Mediation Server for this site is not configured. In order to use the Mediation Server being used by Microsoft Office Communications Server 2007, Lync Server 2010 must be configured to use this server.
route outbound calls through the legacy Office Communications Server 2007 R2 Mediation Server 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 Mediation Server components are configured, which occurs later in this document. For details about configuring Lync Server 2010 Mediation Server, see Migrate Mediation Server.
57
Note: For details about finding qualified PSTN gateways, IP-PBXs and SIP Trunking services that work with Lync Server 2010, see "Microsoft Unified Communications Open Interoperability 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 a Voice Route and Voice policy configured that point to the legacy Mediation Server. If you do not have a legacy Voice Route or Voice Policy, use the following the procedure to configure these settings 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 Control Panel 1. Log on to the computer with an account that is a member of the RTCUniversalServer Admins group or minimally a member of the CsVoiceAdministrator administrative rol e. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools.

4. Click New to create a New Voice Route. 5. Fill in the following fields: Description: enter a short description of the voice route. 7. Under Associated PSTN Usages, click Select.
3. Click Voice Routing, and then select the Route tab.
Name: enter a descriptive name of the voice route. For this document we will use W13PSTNRoute.
6. Skip all remaining sections until you reach Associated gateways. Click Add. Select th e default gateway listed and click OK. 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 Server Management Shell 1. Log on to the computer with an account that is a member of the RTCUniversalServer Admins group or minimally a member of the CsVoiceAdministrator administrative rol e. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell.
58
3. Get the FQDN of the legacy Mediation Server by running the following command: Get-CsService MediationServer The Identity parameter will contain the name of the legacy Mediation Server. In this ex ample, the value is MediationServer:medsvr01.contoso.net 4. Next, verify that a voice policy exists for the legacy Mediation Server by running the foll owing command: Get-CsVoicePolicy The PSTNUsages parameter should not be empty, but return a value of {Local} or the name 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 polic y, we create a route in the Lync Server 2010 pool that points to this legacy Mediation S erver. The following code defines a generic voice route that routes any outbound calls from th e Lync Server 2010 pool to the legacy Mediation Server. New-CsVoiceRoute -Name W13PSTNRoute -NumberPattern ".*" PstnUsages Local -PstnGatewayList @{Add="MediationServer:medsvr0 1.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 to W13PSTNRoute. The PSTN Usages should be set to {Local} and the PSTNGatewayList should point to the FQD N of the legacy Mediation Server, Mediation:medsvr01.contoso.net.
Move Legacy User to Pilot Pool

You can move a pilot user to the new Microsoft Lync Server 2010 deployment using the following two 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. For details 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 Office Communications Server 2007 R2 administrative tools to move users from your legacy environment to Lync Server 2010.
Important: The Move-CsLegacyUser cmdlet requires that user names are properly formed and do not have leading or trailing spaces. You cannot move a user account using the Move-
59
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 backend database that is associated with the new pool. Important: Please note that this data includes the active meetings created by the legacy user. For example, if a legacy user has configured a my meeting conference, that conference will still be available in the new Lync Server 2010 pool after the user has been moved. The details 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 at the same time. New functionality will be available to users only when they have upgraded to the new client software. The following figure shows users enabled for Office Communications Server 2007 R2 in the Office Communications Server 2007 R2 administrative tool. These users will be moved to Lync Server 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. The Registrar pool column entry for each user is set to Legacy, which indicates that these users are still homed on Office Communications Server 2007 R2 and have not been moved to Lync Server 2010.
60

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 mem ber of the RTCUniversalServerAdmins group or a member of the CSAdministrator o r CsUserAdministrator administrative role. 2. Click Start, then All Programs, then Microsoft Lync Server 2010, then Lync Server Control Panel. 3. Click Users, click Add Filter, build the following query Legacy user Equal to True, an d then click Find. 4. In the search results, select a user. Note: Notice that the Registrar Pool column shows <Legacy>. This means that the user you have selected is homed on Office Communications Server 2007 R2. 5. Click Action and then click Move selected users to pool.
61

Important: If Move selected users to pool is not available, ensure the account is a mem ber of the CSAdministrator or CSUserAdministrator group. 6. In Move Users, select the Destination registrar pool, which is your Lync Server 2010 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. To move a user by using the Lync Server 2010 Management Shell 1. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 2. Ensure the user account you are using is a member of the RTCUniversalServerAdmi ns group or a member of the CSAdministrator or CSUserAdministrator administrativ e role. 3. At the command line, type the following: Get-CsUser OnOfficeCommunicationServer Using a legacy users sip address as a parameter, run the Move-CsLegacyUser cmdl et.
62
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, we would run: Move-CsLegacyUser Identity "sip:kate@contoso.net" Target "lync -se.contoso.net" 4. At the command line, type the following: Get-CsUser "sip address" The RegistrarPool identity now points to the pool you specified as pool_name in the previous step. The presence of this identity confirms that the user has been successfull y moved. For more details about the Get-CsUser cmdlet described in this section, run: GetHelp Get-CsUser -Detailed 5. By using the Lync Server Control Panel, you can also verify that these users have bee n moved by viewing the Registrar pool column.

Get-Help Move-CsUser Important The Move-CsLegacyUser cmdlet may fail with the following error:
Important To return a user to a legacy Office Communications Server 2007 R2 pool, or to move a use r between Lync Server 2010 pools, see Move-CsUser in the Lync Server Management Sh ell documentation. For more details about the Move-CsUser cmdlet, run:
Move-CsLegacyUser : SetMoveResourceData failed because the user is not provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< Identity "jeff@contoso.net" -Target "lync-se.contoso.net" + Categor yInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser ) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId : MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLega cyUserCmdlet If you experience this error, see Verify User Replication has Completed for resolution.
Move Multiple Users

You can move groups of users to the new Microsoft Lync Server 2010 deployment using the following two methods: Lync Server Control Panel and Lync Server Management Shell. There are requirements that must be met to ensure a smooth transition to Lync Server 2010. For details before completing the procedures in this topic, see Configure Clients for Migration.
63
Important: You cannot use the Active Directory Users and Computers snap-in or the Microsoft Office Communications Server 2007 R2 administrative tools to move users from your legacy environment to Lync Server 2010.
Important: The Move-CsLegacyUser cmdlet requires that user names are properly formed and do not have leading or trailing spaces. You cannot move a user account using the MoveCsLegacyUser 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 backend database that is associated with the new pool. Important: This data includes the active meetings created by the legacy user. For example, if a legacy user has configured a my meeting conference, that conference will still be available in the new Lync Server 2010 pool, after the user has been moved. The details 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.
Note: Homing users on Lync Server 2010 does not require that you deploy upgraded clients at the same time. New functionality will be available to users only when they have upgraded to the new client software. 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 RTCUniversalUserAd mins group or minimally a member of the CsUserAdministrator administrative role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 3. Click Users, click Add Filter, build the query Legacy user Equal to True, and then cli ck Find. 4. In the search results, select at least two users. 5. Click Action and then click Move selected users to pool. Important: If Move selected users to pool is not available, ensure the account is a mem ber of the RTCUniversalUserAdmins group or a member of the CSAdministr ator or CSUserAdministrator administrative role. 6. In Move Users, select the Destination Registrar pool, which is your Lync Server 201
64
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.
To move multiple users by using the Lync Server Management Shell

Get-Help <cmdlet name> -Detailed
For more details about the cmdlets described in this section, run:
1. Log on to the computer with an account that is a member of the RTCUniversalUserAd mins group or minimally a member of the CsUserAdministrator administrative role. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. At the command line, type the following and replace User1 and User2 with specific us er names you want to move and replace pool_FQDN with the name of the destination pool: 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 suc cessfully moved.
65
To move all users at once by using the Lync Server Management Shell 1. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 2. At the command line, type the following: Get-CsUser OnOfficeCommunicationServer | Move-CsLegacyUser Tar get pool_FQDN 3. At the command line, type the following: 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 th e previous step. The presence of this identity confirms that the user has been successf ully moved.

Important The Move-CsLegacyUser cmdlet may fail with the following error: cyUserCmdlet
Move-CsLegacyUser : SetMoveResourceData failed because the user is not provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< Identity "jeff@contoso.net -Target "lync-se.contoso.net" + Categor yInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser ) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId : MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLega If you experience this error, see the topic Verify User Replication has Completed for resolut ion.
Verify User Replication has Completed

When running the Move-CsUser and Move-CsLegacyUser cmdlets, you may experience a failure 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 the successful completion of the Lync Server 2010 User Replicator service's initial synchronization depends on the number of domain controllers that are hosted in the Active Directory forest that hosts the Lync Server 2010 pool. The Lync Server 2010 User Replicator service initial synchronization process occurs when the Lync Server 2010 Front End Server is started for the first time. After that, the synchronization is then based on the User Replicator interval. Complete the following steps to verify user replication has completed before running the Move-CsUser and
66
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 Migration

Verify 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 of Office Communications Server by using the Import-CsLegacyConfiguration cmdlet. Running functional tests against each Microsoft Lync Server 2010 workload. This step is optional.
In This Section
Verify Configuration Settings Run Functional Tests Against Workloads (optional)
Verify Configuration Settings

After you merge the topology and run the Import-CsLegacyConfiguration cmdlet, verify that your Microsoft Office Communications Server 2007 R2 policies and settings were imported to Microsoft Lync Server 2010. The following table lists the policies and settings that you should verify. Policies and Settings to Verify after Migration
If 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
67
Enterprise Voice
Voice policy Voice routes Dial plans PSTN usage settings
Communicator Web Access External users Archiving
Simple URLs External access policies Archiving policy
For most of these policies and settings you can use either Microsoft Lync Server 2010 Control Panel or Lync Server Management Shell cmdlets. For the presence policy, however, you must use a cmdlet. Note: To verify policies, you can compare the policy names that you have in your Office Communications Server 2007 R2 deployment to the names that are now in Lync Server 2010 to ensure that all the policies were imported. It is not necessary to compare all the settings within a policy. Note: For Mediation Server, legacy configuration settings like server ports and protocols are not merged to Lync Server 2010. The administrator can configure these settings using the Topology Builder. Additionally, the default encryption level for Lync Server 2010 Mediation Server is RequireEncryption. Ensure that your legacy Office Communications Server 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 pla ns (formerly known as location profiles), dial-in access numbers (Conferencing Attenda nt access phone numbers and regions), voice routes, and the policies listed in the prec eding 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 RTCUniversalUserAd mins or RTCUniversalServerAdmins group or minimally is a member of the CsView OnlyAdministrator administrative role. 3. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 4. To verify imported conferencing policies, click Conferencing, click Conferencing Poli cy, and then verify that all the conferencing policies in your Office Communicator 2007 R2 environment are included in the list.
68
Note: The Meeting policy from previous versions of Office Communications Server is now known as the conferencing policy in Lync Server. Additionally, the Anony mous Particpants setting from previous versions of Office Communications S erver is now a setting in the Lync Server conferencing policy. Note: In Office Communications Server 2007 R2, if the conferencing policy is not set to use per user, only global policy settings are imported. No other conference policies are imported in this situation. Note: If Anonymous Participants is set to Enforce per user in your Office Commu nications Server 2007 R2 conferencing policy, two conferencing policies are cr eated during migration: one with AllowAnonymousParticipantsInMeetings s et to True and one with AllowAnonymousParticipantsInMeetings set to Fal se. 5. To verify imported dial plans, click Voice Routing, click Dial Plan, and then verify that all the dial plans in your Office Communicator 2007 R2 environment are included in the list. Note: In Lync Server 2010, location profiles are now referred to as dial-plans.

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.
6. To verify imported voice policies, click Voice Routing, click Voice Policy, and then ver ify that all the voice policies in your Office Communicator 2007 R2 environment are incl uded in the list.
7. To verify imported voice routes, click Voice Routing, click Route, and then verify that all the voice routes in your Office Communicator 2007 R2 environment are included in t he list. 8. To verify imported PSTN usage settings, click Voice Routing, click PSTN Usage, and then verify that the PSTN Usage settings from your Office Communicator 2007 R2 envi ronment are included in the list. 9. To verify imported external access policies, click External User Access, click Externa l Access Policy, and then verify that all the external access policies in your Office Co mmunicator 2007 R2 environment are included in the list. 10. To verify archiving policies, click Monitoring and Archiving, click Archiving Policy, a nd then verify that all the archiving policies in your Office Communications Server 2007 R2 environment are included in the list.
69
11. Start the Lync Server Management Shell: Click Start, click All Programs, click oft Micros Lync Server 2010, and then click Lync Server Management Shell. 12. To verify presence policies, run: Get-CsPresencePolicy By looking at the name in the Identity parameter, verify that all the presence policies in your 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 RTCUniversalUserAd mins or RTCUniversalServerAdmins group or minimally is a member of the CsView OnlyAdministrator administrative role. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. Run the cmdlets in the following table to verify policies and settings. The syntax of these cmdlets is like the following example: Get-CsConferencingPolicy For 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 Conferencing policy
Get-CsPresencePolicy Get-CsConferencingPolicy Note: If conferencing policy is not set to use per user in your Office Communications Server 2007 R2 envi ronment, only global policy settings are imported. No other conferencing policies are imported in thi s situation. Note:
70
If AnonymousParticipants is set to Enforce per user in your Office Communications Server 2007 R2 conferencing policy, two conferencing policies are created during migration: one with nymousP AllowAnoarticipantsInMeetings set to True and one with ngs AllowAnonymousParticipantsInMeeti set to Fal se. Note: To enable federated users from your legacy Offic e Communications Server 2007 R2 deployment t o join meetings scheduled by Lync Server 2010 u sers, the meeting policy assigned to the Lync Ser ver 2010 user must allow anonymous scheduling. To configure anonymous scheduling, from the Ly nc Server Management Shell run GetCsConferencingpolicy , then run SetCsConferencingPolicy Identity <Conf erencingPolicyName> AllowAnonymousParticipantsInMeetings $True

Dial-in access numbers Get-CsDialInConferencingAccessNumber
Note: This cmdlet returns only Lync Server 2010 dial-in access numbers. It does not return any Office Co mmunications Server 2007 R2 dial-in access num bers. Dial plans Voice policy Get-CsDialPlan Get-CsVoicePolicy Note: If voice policy is not set to use per user in your O ffice Communications Server 2007 R2 environme nt, only global policy settings are imported. No ot her voice policies are imported in this situation. Voice routes PSTN Usage URLs Get-CsVoiceRoute Get-CsPstnUsage Get-CsSimpleUrlConfiguration
71
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, you should 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 then expanding to meetings of three or more participants. Include remote users and federated users to verify that external access works as expected. Note: Although you perform these functional tests before the client rollout, you should deploy Microsoft Lync 2010 to a couple trial users homed on Microsoft Lync Server 2010 to use in these tests. This section describes some example scenarios: Functional Test Scenarios
Remote Office Communications Server 2007 R2 User and Internal Lync Server 2010 User Users Remote user who is homed on Office Communications Server 2007 R2 Internal user who is homed on Lync Server 2010
Scenarios 1. 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 IM session. They use desktop sharing, and audio/video. 4. The internal 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. Remote Office Communications Server 2007 R2 User and Remote Lync Server 2010 User Users Remote user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Lync Server 2010
Scenarios 1. 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.
72
2. The remote Lync Server 2010 user calls the remote Office Communications Server 2007 R2 user 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 a current IM session. They use desktop sharing and audio/video. 4. The remote Lync Server 2010 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. 5. The remote Office Communications Server 2007 R2 user adds a third user, who is homed on Lync 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 on Office Communications Server 2007 R2 to a current IM session. They use desktop sharing and audio/video. Remote Lync Server 2010 User and Internal Office Communications Server 2007 R2 User Users Remote user who is homed on Lync Server 2010 Internal user who is homed on Office Communications Server 2007 R2
Scenarios 1. 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 IM session. They use desktop sharing, and audio/video. Unscheduled Conferencing Users Internal user who is homed on Office Communications Server 2007 R2 Internal user who is homed on Lync Server 2010
Scenarios 1. 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 on Office Communications Server 2007 R2. 2. A user homed on Lync Server 2010 sets up an unscheduled (Meet Now) A/V conference and invites a user homed on Lync Server 2010 and a user homed on Office Communications Server 2007 R2. 3. A user homed on Office Communications Server 2007 R2 shares the desktop during a conference. 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
73
Users Internal user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Lync Server 2010 Internal user who is homed on Lync Server 2010 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. A remote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, and an internal Lync Server 2010 user join the meeting. A remote Office Communications Server 2007 R2 user and a remote Lync Server 2010 user dial in to the conference.
Scenarios
Dial-in Conference Hosted on Lync Server 2010 Users Internal user who is homed on Lync Server 2010 Remote user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Lync Server 2010 Internal user who is homed on Office Communications Server 2007 R2
Scenarios
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, a remote Lync Server 2010 user, and an internal Office Communications Server 2007 R2 user join the meeting. A remote Office Communications Server 2007 R2 user and a remote Lync Server 2010 user dial in to the conference.
Conference Hosted on Office Communications Server 2007 R2 with Application Sharing Modality Users Internal user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Lync Server 2010 Internal user who is homed on Lync Server 2010 Federated user An Office Communications Server 2007 R2 internal user organizes a conference with application sharing modality. The conference is hosted on Office Communications Server 2007 R2. A remote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, an internal Lync Server 2010 user, and a federated user join the meeting.
Scenarios
74
All users can view the shared desktop or application of the Office Communications Server 2007 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 Modality Users Internal user who is homed on Lync Server 2010 Remote user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Lync Server 2010 Internal user who is homed on Office Communications Server 2007 R2 Federated user A Lync Server 2010 internal user organizes a conference that is hosted on Lync Server 2010 and adds the application sharing modality to the conference. A remote Office Communications Server 2007 R2 user, a remote Lync Server 2010 user, an internal 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.
Scenarios
Person-to-Person Federation Users A federated user
A user who is homed on Lync Server 2010
Scenarios A Lync Server 2010 user calls a federated user. They use IM, audio/video, and desktop sharing. A federated user calls a Lync Server 2010 user. They use IM, audio/video, and desktop sharing.
Voice Users Internal user who is homed on Lync Server 2010 Remote user who is homed on Lync Server 2010 Internal user who is homed on Office Communications Server 2007 R2 Remote user who is homed on Office Communications Server 2007 R2 A Lync Server 2010 user (internal or remote) calls a Office Communications Server 2007 R2 user (internal or remote), puts the call on hold, and then resumes the call. One of the calling parties transfers the call to another user (Lync Server 2010 or Office Communications Server 2007 R2 (internal or remote). An Office Communications Server 2007 R2 user (internal or remote) calls a Lync Server 2010
Scenarios:
75
user (internal or remote). One of the parties transfers the call to a public switched telephone number (PSTN). A PSTN caller calls a Lync Server 2010 user. The Lync Server 2010 user transfers the call to a Office Communications Server 2007 R2 user. A Lync Server 2010 user calls a PSTN and then transfers the call to an Office Communications Server 2007 R2 user. A Lync Server 2010 user sets a call forwarding rule with the call forwarding destination as a Office Communications Server 2007 R2 user. The number is forwarded to the correct destination. A PSTN caller calls a Lync Server 2010 user. The Lync Server 2010 user parks the call, and another Lync Server 2010 user retrieves the call.
Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool
The topics in this section explain how to add a Lync Server 2010 Director and an Edge Server to the pilot pool deployment. The topics provide configuration and verification guidance when running 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 Servers
This topic highlights configuration settings you should be aware of prior to deploying your Lync Server 2010 Edge Server and Director. The deployment and configuration processes for Lync Server 2010 are much different than in previous releases because Lync Server 2010 provides new tools for installation and administration that change the way that you work with Lync Server components. This section only highlights key points you should consider as part of your pilot pool deployment. For detailed steps, see Deploying Edge Servers in the Deployment documentation, which describes the deployment process and also gives configuration information for external user access. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required.
Define a Director Pool
76
1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 0 210, and then click Lync Server Topology Builder. 2. On the welcome page, click Download Topology from Existing Deployment, and th en save a local copy to a file. 3. In the left pane, expand the tree view, right click Director pools, and select New Direc tor Pool. 4. On the Define the Director pool FQDN page, specify the computer fully qualified dom ain name (FQDN) (lync-dir.contoso.net for our example), select the Single compute r pool option, and then click Next. 5. On the Define the file share page, select Use a previously defined file share or Def ine a new file share, and then click Next. Note: The file share assigned to a Director is not actually used, so you can assign th e file share of any pool in the organization. 6. On the Specify the Web Services URL page, specify the FQDN for the Directors Ext ernal Base URL, and then click Finish. The name must be resolvable from Internet D NS servers and point to the public IP address of the Reverse Proxy, which listens for H TTP/HTTPS requests to that URL and proxies it to the External Web Services virtual di rectory on that Director.
As you navigate through the Define New Edge Pool wizard, review the key configuration settings shown in the following steps. Note that only a few pages of the Define New Edge Pool wizard are shown. Define an Edge Pool 1. From Topology Builder, right-click Edge pools and then select New Edge pool.
77

2. An Edge pool can be a Multiple computer pool or Single computer pool.
78
3. On the Select features page, do not enable federation. Federation is currently routed t hrough the legacy Office Communications Server 2007 R2 Edge Server. See the topic Configure Federation Routes and Media Traffic for information on changing the federat ion route to Lync Server 2010 Edge Servers. This setting will be configured in a later p hase of migration.
79
4. Next, continue completing the following wizard pages: External FQDNs, Define the in tenral 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 Serv er 2010 Edge pool.
80
6. On the Associate Front End pools page, do not associate a pool with this Edge pool at this time. External media traffic is currently routed through the legacy Office Commu nications Server 2007 R2 Edge Server. This setting will be configured in a later phase of migration.
81

7. Click Finish and then Publish the topology.
8. Follow the steps in Setting Up the Director in the Deployment documentation to install t he 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 the files on the new Edge Server, configure certificates, and start the services.
Its very important that you follow the guidelines in the topics Deploying Edge Servers and Setting Up the Director in the Deployment documentation. This section merely provided some guidance on configuration settings when installing these server roles. You should now have a legacy Office Communications Server 2007 R2 deployed in parallel with a Lync Server 2010 deployment. Each deployment includes an Edge Server, a Director, a Mediation Server, and a Standard Edition server. The Mediation Server is collocated on the Standard Edition server in Lync Server 2010. It is configured as stand-alone server in Office Communications Server 2007 R2. Federation for each deployment is through the legacy Office Communications Server 2007 R2 Edge Server. Verify that both deployments are running properly, services are started, and you can administer each deployment prior to moving to the next phase.
82
Phase 8: Move from Pilot Deployment into Production

The topics in this section describe tasks you must complete prior to moving your deployment of Lync 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 R2 Migration) 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 Traffic
Federation is a trust relationship between two or more SIP domains that permits users in separate organizations to communicate across network boundaries. After you migrate to your Lync Server 2010 pilot pool, you need to transition from the federation route of your Microsoft Office Communications Server 2007 R2 Edge Servers to the federation route of your Microsoft Lync Server 2010 Edge Servers. Use the procedures that follow to transition the federation route and the media traffic route from your Office Communications Server 2007 R2 Edge Server and Director to your Lync Server 2010 Edge Server and Director, for a single-site deployment. Important: Changing the federation route and media traffic route requires that you schedule maintenance downtime for the Lync Server 2010 and Office Communications Server 2007 R2 Edge Servers. This entire transition process also means that federated access will be unavailable for the duration of the outage. You should schedule the downtime for a time when you expect minimal user activity. You should also provide sufficient notification to your end users. Plan accordingly for this outage and set appropriate expectations within your organization. Important If your legacy Office Communications Server 2007 R2 Edge Server is configured to use the same FQDN 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 Edge Server are not supported. If the legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Office Communications Server 2007 R2 to Lync Server
83
2010, then decommission the Office Communications Server 2007 R2 Edge Server before enabling 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, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper user rights for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required. Remove the Legacy Federation Association from Lync Server 2010 Sites 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 2. Select the option to Download topology from existing deployment and then click O K. 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. 6. Select Federation route in the left pane. 5. Right-click the site and select Edit Properties.
7. Under Site federation route assignment, select Disable to disable the federation route t hrough the BackCompatSite.
84

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 c onfigured for federation and then click Change.
85
4. Click Next and accept the default settings until you get to the Specify External Edge page:
86

Important: This step is very important. You must clear this option to remove the legacy fe deration 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 Communication s Server 2007 / Office Communications Server 2007 R2 Edge has been en abled for federation. This warning is expected and can be ignored.
5. In Specify External Edge, be sure to clear the This Edge pool is used for federatio n and public IM connectivity check box. This will remove the federation association with the BackCompatSite.
8. In the Status column, verify that the value is Success and then click Finish to close t he 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.
87

Configure Certificates on the Lync Server 2010 Edge Server
As shown in the previous figure, the Site federation route assignment is set to Disab led.
1. Export the external Access Proxy certificate, with the private key, from the legacy Offic e Communications Server 2007 R2 Edge Server. 2. On the Lync Server 2010 Edge Server, import the Access Proxy external certificate fro m the previous step. 3. Assign the Access Proxy external certificate to the Lync Server 2010 external interface of the Edge Server. 4. The internal interface certificate of the Lync Server 2010 Edge Server should not be ch anged. Change Office Communications Server 2007 R2 Federation Route to use Lync Server 2010 Edge Server 1. On the Office Communications Server 2007 R2 Standard Edition server or Front End S erver, log on with an account that is a member of the RTCUniversalServerAdmins gr oup. 2. On the Office Communications Server 2007 R2 Standard Edition server or Front End S erver, click Start, then Administrative Tools, then Office Communications Server 2
88
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 o n to the computer with an account that is a member of the RTCUniversalServerAdmi ns group. 2. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 3. Select the option to Download topology from existing deployment and then click O K. 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
89
. 7. Click OK to close the Edit Properties page. 8. From Topology Builder, select the top node Lync Server 2010. 9. From the Actions pane, select Publish Topology and complete the wizard. Configure Lync Server 2010 Edge Server Outbound Media Path 1. From Topology Builder, navigate to the pool below Standard Edition Front End Ser vers 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.
5. Click OK to close the Edit Properties page. Turn on Lync Server 2010 Edge Server Federation
90
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 Ed ge 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) c heck box.
4. Click OK to close the Edit Properties page. 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.
91
Publish Edge Server Configuration Changes 1. From Topology Builder, select the top node Lync Server 2010. 2. From the Actions pane, select Publish Topology and complete the wizard. 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 occ ur during migration to a higher version of the product. In that case, only one Edge S erver would be actively used for federation. Verify that the external DNS SRV record points to the correct Edge Server. If you want to deploy multiple federation Edge Ser ver to be active concurrently (that is, not a migration scenario), verify that all federat ed partners are using Office Communications Server 2007 R2 or later. Verify that the external 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 sen d SIP traffic for external access (usually port 443) and federation (usually port 5061) to the Lync Server 2010 Edge Server, instead of the legacy Edge Server. 3. Next, stop the Office Communications Server Access Edge from each Edge Server machine. 4. From each legacy Edge Server machine, open the Services applet from the Administ rative 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 Users

After transitioning the federation route to the Lync Server 2010 Edge Server and Director, you should perform some functional tests to verify that federation performs as expected. Tests for
92
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 a user on Office Communications Server 2007 R2. Test instant messaging (IM), presenc e, audio/video (A/V), and desktop sharing. 2. Users of each public IM service provider that your organization supports (and for which provisioning has been completed) communicating with a user on Lync Server 2010 an d 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 (lo gging into Office Communications Server 2007 R2 from outside the intranet but without VPN) with a user on Lync Server 2010, and a user on Office Communications Server 2 007 R2. Test IM, presence, A/V and desktop sharing. 5. A user hosted on Lync Server 2010 using remote user access (logging into Lync Serve r 2010 from outside the intranet but without VPN) with a user on Lync Server 2010, an d a user on Office Communications Server 2007 R2. Test IM, presence, A/V and deskt op sharing.
Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 R2 Migration)
You can move users to the new Microsoft Lync Server 2010 deployment by using either Lync Server Control Panel or Lync Server Management Shell. You must meet some requirements to ensure a smooth transition to Lync Server 2010. For details about prerequisites to 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 Office Communications Server 2007 R2 administrative tools to move users from your legacy environment to Lync Server 2010.
Important: The Move-CsLegacyUser cmdlet requires that user names are properly formed and do not have leading or trailing spaces. You cannot move a user account using the MoveCsLegacyUser 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 backend database that is associated with the new pool.
93
Important: Please note that this includes the active meetings created by the legacy user. For example, if a legacy user has configured a my meeting conference, that conference will still be available in the new Lync Server 2010 pool, after the user has been moved. The details 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. Note: Homing users on Lync Server 2010 does not require that you deploy upgraded clients at the same time. New functionality will be available to users only when they have upgraded to the new client software. Post Migration Task After you move users, verify the conferencing policy that is assigned to them. To ensure that meetings organized by users homed on Lync Server 2010 work seamlessly with federated users who are homed on Office Communications Server 2007 R2, the conferencing policy assigned to the migrated users should allow anonymous participants. Conferencing policies that allow anonymous participants have Allow participants to invite anonymous users selected in Lync Server 2010 Control Panel and have AllowAnonymousParticipantsInMeetings set to True in the output from the Get-CsConferencingPolicy cmdlet in the Lync Server Management Shell. For details about configuring conferencing policy by using Lync Server Management Shell, see Set-CsConferencingPolicy in the Lync Server Management Shell documentation. Example of Users Before Migration
The following figure shows users enabled for Office Communications Server 2007 R2 in the Office Communications Server 2007 R2 administrative tools. These users will be moved to Lync Server 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
94
Registrar pool column entry for each user is set to Legacy, which indicates that these users are still homed on Office Communications Server 2007 R2 and have not been moved to Lync Server 2010.

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 RTCUniversalUserAd mins group or a member of the CsUserAdministrators administrative role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 3. Click Users, click Add Filter, build the following query Legacy user Equal to True, an d then click Find. 4. In the search results, select a user. Here, weve selected Chen Yang.
95

Note: Notice that the Registrar pool column shows <Legacy>. This means that the user you have selected is homed on Office Communications Server 2007 R2. 5. Click Action and then click Move selected users to pool. Important: If Move selected users to pool is not available, ensure the account is a mem ber of the CSAdministrator or CSUserAdministrator group. 6. In Move Users, select the Destination registrar pool, which is your Lync Server 2010 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.
To move users by using the Lync Server Management Shell 1. Log onto the computer with an account that is a member of the RTCUniversalUserAd mins group or a member of the CsUserAdministrators administrative role. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell.
96
3. At the command line, type the following: Move-CsLegacyUser Identity user name Target pool_name For example: Move-CsLegacyUser Identity Kate Jordan Target lyncse.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 specified as pool_name in the previous step. The presence of this identity confirms that the us er has been successfully moved.
Important The Move-CsLegacyUser cmdlet may fail with the following error: Move-CsLegacyUser : SetMoveResourceData failed because the user is not provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< Identity "jeff@contoso.net -Target "lync-se.contoso.net" + Categor yInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser
97
) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId : MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLega cyUserCmdlet If you experience this error, see the topic Verify User Replication has Completed for resolut ion.
Move Multiple Users

You can move groups of users to the new Microsoft Lync Server 2010 deployment using the following two methods: Lync Server Control Panel and Lync Server Management Shell. There are requirements that must be met to ensure a smooth transition to Lync Server 2010. For details 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 Office Communications Server 2007 R2 administrative tools to move users from your legacy environment to Lync Server 2010.
Important: The Move-CsLegacyUser cmdlet requires that user names are properly formed and do not have leading or trailing spaces. You cannot move a user account using the MoveCsLegacyUser 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 backend database that is associated with the new pool. Important: This data includes the active meetings created by the legacy user. For example, if a legacy user has configured a my meeting conference, that conference will still be available in the new Lync Server 2010 pool, after the user has been moved. The details 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. Note: Homing users on Lync Server 2010 does not require that you deploy upgraded clients at the same time. New functionality will be available to users only when they have upgraded to the new client software. 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 RTCUniversalUserAd mins group or minimally a member of the CsUserAdministrator administrative role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr
98
ol Panel. For details about the different methods you can use to start Lync Server rol Cont Panel, see Installing and Using Administrative Tools. 3. Click Users, click Add Filter, build the query Legacy user Equal to True, and then cli ck Find. 4. In the search results, select at least two users. 5. Click Action and then click Move selected users to pool. Important: If Move selected users to pool is not available, ensure the account is a mem ber of the RTCUniversalUserAdmins group or a member of the CSAdministr ator or CSUserAdministrator administrative role. 6. In Move Users, select the Destination Registrar pool, which is your Lync Server 201 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 1. Log on to the computer with an account that is a member of the RTCUniversalUserAd mins group or minimally a member of the CsUserAdministrator administrative role. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. At the command line, type the following and replace User1 and User2 with specific us er names you want to move and replace pool_FQDN with the name of the destination pool:
99
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 suc cessfully moved. To move all users at once by using the Lync Server Management Shell 1. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 2. At the command line, type the following: Get-CsUser OnOfficeCommunicationServer | Move-CsLegacyUser Tar get pool_FQDN

3. At the command line, type the following: 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 th e previous step. The presence of this identity confirms that the user has been successf ully moved. Important The Move-CsLegacyUser cmdlet may fail with the following error: Move-CsLegacyUser : SetMoveResourceData failed because the user is not provisioned. At line:1 char:18 + Move-CsLegacyUser <<<< Identity "jeff@contoso.net -Target "lync-se.contoso.net" + Categor yInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser ) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId : MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLega cyUserCmdlet If you experience this error, see the topic Verify User Replication has Completed for resolut ion.
100
Migrate Response Groups

You can migrate response group settings (agent groups, queues, and workflows) that you created on Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. When you migrate Response Group settings, all the configuration settings, audio files, and contact objects are 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. Calls to 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 Lync Server 2010, you need to run a migration cmdlet and then update the URL that users need to sign into and out of their response groups. If the Back End server in your Microsoft Office Communications Server 2007 R2 environment runs on SQL Server 2005, you first need to install the SQL Server 2005 Native Client on the Lync Server 2010 computer where you plan to run the Response Group migration cmdlet. Note: The Response Group migration cmdlet requires that the Response Group application is installed in your Lync Server 2010 pilot pool. You can ensure that Response Group is installed by running the Get-CsService ApplicationServer command. Important: The Response Group migration cmdlet moves settings for the entire pool. You cannot select specific groups, queues, or workflows to migrate.
Note: The following procedure for migrating Response Group settings assumes that you have a one-to-one relationship between Office Communications Server 2007 R2 and Lync Server 2010 pools. If you plan to consolidate or split up pools during your migration and deployment, you need to plan which Office Communications Server 2007 R2 pool maps to which Lync Server 2010 pool. Note: After you run the Response Group migration cmdlet, the settings are still present, but unused, in your Office Communications Server 2007 R2 pool to allow for a potential rollback. After you migrate Response Group, use Lync Server Control Panel or Lync Server Management Shell 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 S QL Server 2005, download the Feature Pack for Microsoft SQL Server 2005 - Decemb er 2008 (SQLNCLI.MSI package) from the Microsoft Download Center at http://go.micr osoft.com/fwlink/?LinkId=204105, and then install it on the computer where you plan to run the Response Group migration cmdlet.
101
2. Log on to the computer with an account that is a member of the Admins RTCUniversalServer group or has equivalent rights. 3. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 4. Run: Move-CsRgsConfiguration Source <source pool FQDN> -Destination <destination pool FQDN> For example: Move-CsRgsConfiguration Source se-r2.contoso.net Destination l ync-se.contoso.net 5. If you deployed the Response Group tab for Microsoft Office Communicator 2007 R2 in your Office Communications Server 2007 R2 environment, remove the tab from the Off ice Communicator 2007 R2 tabs.xml file. Note: Formal agents used the Response Group tab to sign in to their response group s before they could receive calls. If you deployed the Response Group tab, you chose the location for the Office Communicator 2007 R2 tabs.xml file when yo u deployed it.

Note: The URL is typically https://webpoolFQDN/RgsClients/Tab.aspx, where webpo olFQDN is the fully qualified domain name (FQDN) of the web pool that is asso ciated 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 t he URL is available from the Tools menu in Lync 2010. To verify Response Group migration by using Lync Server Control Panel
6. Provide users with the updated URL that agents need to sign into and out of their resp onse groups.
1. Log on to the computer with an account that is a member of RTCUniversalReadOnly Admins group or is minimally a member of the CsViewOnlyAdministrator role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 3. In the left navigation pane, click Response Groups. 4. On the Workflow 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 Serv er 2007 R2 environment are included in the list.
102
6. Click the Group tab, and verify that all the agent groups in your Office s Communication 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 RTCUniversalReadOnly Admins group or is minimally a member of the CsViewOnlyAdministrator role. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft 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 environ ment are included in the list. 5. Run: Get-CsRgsQueue 6. Verify that all the queues in your Office Communications Server 2007 R2 environment are included in the list. 7. Run: Get-CsRgsWorkflow

Run Functional Tests for Response Groups
8. Verify that all the workflows in your Office Communications Server 2007 R2 environme nt are included in the list.
After you migrate your agent groups, queues, and workflows, run some functional tests to verify that 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 2010 A Office Communications Server 2007 R2 user calls the response group on Lync Server 2010. A Lync Server 2010 user calls the response group. An external user calls the response group.
Scenarios:
103
A user calls the response group while the agent is on another call and goes to the queue.
Move Exchange Unified Messaging Contact Objects

To migrate Auto Attendant (AA) and Subscriber Access (SA) contact objects to the new Microsoft Lync Server 2010 deployment, you first move the objects from the legacy Office Communications Server 2007 R2 deployment to the new the Lync Server deployment using the GetCsExUmContact and Move-CsExUmContact cmdlets. On the Exchange Server, you then run the 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 must be a member of the RTCUniversalUserAdmins group and have OU permission to the OU where the contacts objects are stored. OU permission can be granted using the Grant-OUPermission cmdlet. To move contact objects by using the Lync Server Management Shell

Get-CsExUmContact -Filter {RegistrarPool eq "pool1.contoso.net"} | MoveCsExUmContact -Target pool2.contoso.net
1. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 2. For each pool registered with Exchange UM (where pool1.contoso.net is a pool from th e Office Communications Server 2007 R2 deployment and pool2.contoso.net is the po ol from the Lync Server deployment) at the command line, type the following:
To verify that the contact objects are moved, run the Get-CsExumContact cmdlet and confirm 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 Administrat or privileges. 2. Navigate to the ExchUCUtil Windows PowerShell script. In Exchange 2007, ExchUCUtil.ps1 is located at: %Program Files%\Microsoft\Excha nge Server\Scripts\ExchUCUtil.ps1 In Exchange 2010, ExchUCUtil.ps1 is located at: %Program Files%\Microsoft\Excha nge Server\V14\Scripts\ExchUCUtil.ps1 3. If Exchange is deployed in a single forest, type: exchucutil.ps1 Or, if Exchange is deployed in multiple forests, type:
104
exchucutil.ps1 -Forest:" <forest FQDN>" for multiple forest oyme deplnts where 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 ru n exchucutil.ps1. Otherwise, Lync Server will not detect Unified Messaging in t he topology.
Verify that all Exchange UM Contact Objects are removed from the Legacy Pool
Use either the OCSUmUtil tool or the Get-CsExumContact cmdlet to verify that Exchange UM contact objects have been removed from the legacy Office Communications Server 2007 R2 pool. 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) container
For details about using the Get-CsExumContact cmdlet, see Get-CsExUmContact in the Lync Server Management Shell documentation.
105
Phase 9: Complete Post-Migration Tasks

The topics in this section describe tasks that you will need to perform after you have completed your 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.0 Core SDK Configure Trusted application servers Configure the Meeting Join Page Deploy Lync Server 2010 Clients
Migrate Dial-in Access Numbers
Migrating dial-in access numbers requires two steps: running the ImportCsLegacyConfiguration cmdlet (completed earlier in Import Policies and Settings) to migrate dial plans and other dial-in access number settings, and running the MoveCsApplicationEndpoint cmdlet to migrate the contact objects. After you run the ImportCsLegacyConfiguration cmdlet, the migrated dial-in access numbers exist both in your Microsoft Office Communications Server 2007 R2 pool and in your Microsoft Lync Server 2010 pool. During this coexistence period, dial-in access numbers that you created in Office Communications Server 2007 R2 behave differently from dial-in access numbers that you create in Lync Server 2010, as described in this section. After you run Import-CsLegacyConfiguration but before you run MoveCsApplicationEndpoint Dial-in access numbers that you created in Office Communications Server 2007 R2 have the following characteristics: Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number 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 administrative tool.
106
Important: If you make changes to dial-in access numbers in your Office Communications Server 2007 R2 pool, you will need to rerun the Import-CsLegacyConfiguration cmdlet with the ReplaceExisting parameter to apply the same changes to your Lync Server 2010 pool. Re-importing with the ReplaceExisting parameter can overlay other changes you made in your Lync Server 2010 pool. Cannot be viewed in Lync Server Control Panel, but can be viewed in Lync Server Management Shell (if you use the Get-CsDialinConferencingAccessNumber cmdlet with the 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 SetCsDialInConferencingAccessNumber cmdlet with the Priority parameter.
After you run Move-CsApplicationEndpoint Dial-in access numbers that you created in Office Communications Server 2007 R2, but have been moved to Lync Server 2010 have the following characteristics: Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page. Appear on Lync Server 2010 meeting invitations and the dial-in access number 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 Management Shell. Can be re-sequenced within the region by using the SetCsDialinConferencingAccessNumber cmdlet with the Priority parameter.
Dial-in access numbers that you create in Lync Server 2010 Dial-in access numbers that you create in Lync Server 2010 before, during, or after migration have the following characteristics: Do not appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page. Appear on Lync Server 2010 meeting invitations and the dial-in access number page. Cannot be viewed or modified in the Office Communications Server 2007 R2 administrative tool. Can be viewed and modified in Lync Server Control Panel and in Lync Server Management Shell. Can be re-sequenced within the region by using the SetCsDialinConferencingAccessNumber cmdlet with the Priority parameter.
You must finish migrating dial-in access numbers that point to an Office Communications Server 2007 R2 pool before you decommission the Office Communications Server 2007 R2 pool. If you do not complete dial-in access number migration as described in the following procedure,
107
incoming calls to the access numbers will fail. Important: You must perform this procedure prior to decommissioning the Office Communications Server 2007 R2 pool. Note: We recommend that you move dial-in access numbers when network usage is low, in case 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 RTCUniversalServer Admins group and open the Office Communications Server 2007 R2 administrative to ol. 2. In the console tree, right-click the forest node, click Properties, and then click Confere ncing Attendant Properties. 3. On the Access Phone Numbers tab, click Serviced by Pool to sort the access phone numbers by their associated pool, and identify all the access numbers for the pool from which you are migrating. 4. To identify the SIP URI for each access number, double-click the access number to op en the Edit Conferencing Attendant Number dialog box, and look under SIP URI. 5. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 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 numb er to be moved> -Target <FQDN of the pool to which the access nu mber is moving> 7. In the Office Communications Server 2007 R2 Administrative tool, on the Access Pho ne Numbers tab, verify that no dial-in access numbers remain for the Communications Server 2007 R2 pool from which you are migrating. Note: When no more dial-in access numbers point to the Office Communications Ser ver 2007 R2 pool, you can decommission the Office Communications Server 2 007 R2 pool.
Enable Exchange 2010 SP1 Outlook Web App and IM Integration

To 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 Access Server (CAS) server to the Lync Server 2010 topology as a trusted application server.
108
Important There are additional configuration requirements that depend on how your Exchange 2010 SP1 server roles are configured: If your CAS server is not collocated on the same server that is running Exchange 2010 SP1 Unified Messaging (UM), in addition to creating a trusted application pool you must create a trusted application, which can only be done by using Lync Server Management Shell. The trusted application must be assigned a port number on which the application will run. The port must be unique within the trusted application pool. In other words, no other applications that use this port can be defined in the specified pool. This port will not be used, but it must be assigned as described in the Create a trusted application for the Exchange 2010 SP1 CAS server procedure later in this topic. If your CAS server is collocated on the same server that is running Exchange 2010 SP1 UM, and the UM server is servicing a SIP dial plan that is integrated with Lync Server 2010, you only need to 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 RTCUniversalServer Admins group or has the equivalent rights. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. Run the following cmdlet: Get-CsSite

4. Run the following cmdlet:
This 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. New-CsTrustedApplicationPool -Identity <E14 CAS FQDN> ThrottleA sServer $true TreatAsAuthenticated $true ComputerFQDN <E14 CAS FQDN> -Site <Site> -Registrar <Pool FQDN in the site> RequiresReplication $false For details, see New-CsTrustedApplicationPool in the Lync Server Management Shell documentation. Important: If your CAS server is not collocated on the same server that is running Exchan ge 2010 SP1 Unified Messaging (UM), skip the remaining steps in this procedu re and perform the Create a trusted application for the Exchange 2010 SP1 C AS server procedure later in this topic. If your CAS server is collocated on the same server that is running Exchange 2010 SP1 Unified Messaging (UM), com plete the steps in this procedure and do not perform the Create a trusted appli cation for the Exchange 2010 SP1 CAS server procedure later in this topic. 5. Run Enable-CsTopology.
109
6. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 0 210, and then click Lync Server Topology Builder. 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 RTCUniversalServer Admins group or has the equivalent rights. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. If your CAS server is not collocated on the same server that is running Exchange 2010 SP1 Unified Messaging (UM), run the following cmdlet:

4. Run Enable-CsTopology. 6. Select the option to Download Topology from existing deployment.
New-CsTrustedApplication -ApplicationId <AppID String> TrustedApplicationPoolFqdn <E14 CAS FQDN> -Port <available port number> For details, see the topic New-CsTrustedApplication in the Lync Server Management S hell documentation.
5. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 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 might need to perform the following post-migration steps if you customized the following in your Microsoft Office Communications Server 2007 R2 environment:
110
Set the PartitionbyOU WMI property to group Address Book entries by organizational unit (OU). Customize the Address Book normalization rules.
Grouped Address Book Entries If you set the PartitionbyOU WMI property to True to create address books for each OU, you need to set the msRTCSIP-GroupingId Active Directory attribute on users and contacts if you want to continue grouping address book entries. You might want to group address book entries to limit the scope of Address Book searches. To use the msRTCSIP-GroupingId attribute, write a script to populate the attribute, assigning the same value for all of the users that you want to group together. For example, assign a single value for all the users in an OU. Address Book Normalization Rules If you customized Address Book normalization rules in your Office Communications Server 2007 R2 environment, you must migrate the customized rules to your pilot pool. If you did not customize Address Book normalization rules, you have nothing to migrate for Address Book service. The default normalization rules for Lync Server 2010 are the same as the default rules for Office Communications Server 2007 R2. Note: If your organization uses remote call control and you customized Address Book normalization rules, you must perform the procedure in this topic before you can use remote call control. The procedures require membership in the RTCUniversalServerAdmins 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 Addr ess Book shared folder, and copy it to the root of the Address Book shared folder in yo ur Lync Server 2010 pilot pool. 2. Use a text editor, such as Notepad, to open the Company_Phone_Number_Normalizat ion_Rules.txt file. 3. Certain types of entries will not work correctly in Lync Server 2010. Look through the fil e for the types of entries described in this step, edit them as necessary, and save the c hanges to the Address Book shared folder in your pilot pool. Strings that include required whitespace or punctuation cause normalization rules to fai l because these characters are stripped out of the string that is input to the normalizati on rules. If you have strings that include required whitespace or punctuation, you need to modify the strings. For example, the following string would cause the normalization r ule to fail: \s*$\s*\d\d\d\s*$\s*\-\s*\d\d\d\s*\-\s*\d\d\d\d The 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
111
Enable Remote Call Control

Remote call control enables users to control their desktop private branch exchange (PBX) phones by using Microsoft Lync 2010. Enabling remote call control requires five steps. The following table describes where and when these steps occur when you are migrating to Microsoft Lync Server 2010 from a previous version of Office Communications Server.
Step When occurs
Remove legacy trusted server entries
Use the Office Communications Server 2007 R 2 administrative tools to remove legacy trusted application server entries prior to moving them t o Lync Server 2010. When you deploy and configure your Lync Serv er 2010 pilot pool. If you plan to migrate remote call control, this step is a prerequisite to migrati on. After the topology is merged and policies and s ettings are migrated. This is a manual step after the automated migration is complete. The proc edures in this section describe how to perform t hese tasks. When you migrate users. The remote call contr ol setting is migrated along with all the other us er settings. For details about migrating users, s ee Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 R2 Migrat ion). When you deploy Microsoft Lync 2010. Adminis trators can use group policy to apply this setting when they deploy clients. For details, see Depl oy Lync Server 2010 Clients. After the topology is merged and policies and s ettings are migrated. This is a manual step after the automated migration is complete, and appli es only if you customized the normalization rule s. For details about migrating Address Book nor malization rules, see Migrate Address Book.
Configure the remote call control gateway to co mmunicate with the PBX.
Create trusted server and static route entries fo r routing requests to the remote call control gat eway.
Configure users for remote call control.
Configure Lync 2010.
Verify Address Book phone number normalizati on rules, if you customized normalization rules.
To remove a legacy trusted server entry 1. Log on to the computer with an account that is a member of the RTCUniversalServer
112
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 1. Log on to the computer with an account that is a member of the RTCUniversalServer Admins group. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. Run: New-CsTrustedApplicationPool -Identity <FQDN of the new pool> ` [-ComputerFqdn <FQDN of computer if more than one computer in po ol or FQDN is different from pool FQDN>] ` [-Registrar <Service ID or FQDN of Registrar service>] [-Site <S ite ID where pool is homed>] ` [-ThrottleAsServer <$true | $false>] [-TreatAsAuthenticated <$tr ue | $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> Trus tedApplicationPoolFqdn <FQDN of pool where application resides> Port <port number where application runs> -EnableTcp
113
For example: New-CsTrustedApplication ApplicationID co1-ExternalServer-1 Tr ustedApplicationPoolFqdn lync-pool1.contoso.net Port 5060 EnableTcp To create a static route 1. Log on to the computer with an account that is a member of the RTCUniversalServer Admins group. 2. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 3. Run: $tcpRoute = NewCsStaticRoute TCPRoute Destination <IP address of the next hop router> ` Port <port for SIP routing> MatchUri <FQDN of domain suffix th at determines if message is handled by this router> or $tlsRoute = NewCsStaticRoute TLSRoute Destination <FQDN of the next hop server> Port <port for SIP routing> MatchUri <FQDN of domain suffix that determines if message is handled by this rout er> -UseDefaultCertificate $true For example: $tcpRoute = NewCsStaticRoute TCPRoute Destination 192.168.0.24 0 Port 7742 MatchUri *.contoso.net 4. Run: Set-CsStaticRoutingConfiguration Route @{Add=$tcpRoute, $tlsRou te}
Remove Legacy Archiving and Monitoring Servers

If your Office Communications Server 2007 R2 deployment contained an Archiving Server or a Monitoring Server, after migrating to Lync Server 2010, those servers can be removed from the legacy environment provided all users have been removed from any remaining Office Communications Server 2007 R2 pools. You can remove the Archiving Server or Monitoring Server in any sequence. The key requirement is that all users have been removed from any remaining Office Communications Server 2007 R2 pools. You can move users from Office Communications Server 2007 R2 to Lync Server 2010 by following the procedures outlined in the following topics: Move Remaining Users to Lync Server 2010 (Office Communications Server 2007 R2 Migration)
114
Move Multiple Users
After you have confirmed that all users have been removed from any remaining pools, follow the procedure in "Removing Servers and Server Roles" at http://go.microsoft.com/fwlink/?LinkId=205887.
Migrate Mediation Server

The topics in this section describe configuration tasks that you will need to perform after you have completed your migration of Lync Server 2010 Mediation Server. Transitioning the collocated Mediation 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 Server This procedure details the steps to configure the Lync Server 2010 pool to use the Lync Server 2010 Mediation Server, instead of the legacy Office Communications Server 2007 R2 Mediation Server. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required.
Note: For the latest information on finding qualified PSTN gateways, IP-PBXs and SIP Trunking services that work with Lync Server 2010, see "Microsoft Unified Communications Open Interoperability Program" at http://go.microsoft.com/fwlink/?LinkId=206015. Configure Mediation Server Using Topology Builder 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 2. Select the option to Download topology from existing deployment and then click O K. 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 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 th e gateway uses the TLS protocol.
115
Accept the default value of the Listening port for IP/PSTN gateway or enter the e nw 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 new Lync Server 2010 Mediation Server to ensure that the voice routes are pointing to the correct Mediation Server.
Change Voice Routes to use the new Lync Server 2010 Mediation Server This procedure changes the voice routes to use the Lync Server 2010 Mediation Server, instead of the legacy Office Communications Server 2007 R2 Mediation Server. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required. 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 RTCUniversalServer Admins group or a minimally member of the CsVoiceAdministrator administrative rol e. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 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 use W14PSTNRoute.
116
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 Standard Edition server or Front End pool, to a stand-alone Mediation Server for a single-site deployment. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server Deployment documentation. For other configuration changes, only membership in the RTCUniversalServerAdmins group is required.
To transition a collocated Mediation Server to a stand-alone Mediation Server 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 2. Select the option to Download topology from existing deployment and then click O K. 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 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, a nd then click Next. 7. Select the next hop pool to which the new Mediation Server will route inbound calls, an d 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.
117
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 documentat ion 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 t he 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 Access

Microsoft Lync Server 2010 has replaced Communicator Web Access with a new Microsoft Silverlight based client called Microsoft Lync Web App. Depending on the requirements of your organization, you have several options available for migrating Communicator Web Access functionality to Lync Server 2010. Note: All procedures and guidance in this section apply to both Office Communications Server 2007 and Office Communications Server 2007 R2 versions of Communicator Web Access.
Lync Server 2010 only deployment, IM and presence are not required for reach scenarios You do not need to perform any additional migration steps. IM and presence are required for reach scenarios Lync Web App does not support IM and presence. If this is a requirement of your organi zation, you must also maintain a deployed instance of the previous version of Communi cator Web Access in your environment. Because Communicator Web Access can point to a Lync Server pool as a next hop, there is no need to maintain a separate Office Com munications Server pool. Side-by-side deployment If you maintain an Office Communications Server pool deployed alongside a Lync Serve r pool, the user experience will vary depending on which server the user is homed to an d which pool Communicator Web Access is pointing to. For details, see Side-By-Side D eployment 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
118
Communicator Web Access to Lync Server 2010. Note: When Communicator Web Access is deployed, all users who sign in through Communicator Web Access have support for instant messaging (IM) and presence. It does not matter if they are homed in the Office Communications Server pool or the Lync Server pool. Deployment Scenarios If a deployment contains Communicator Web Access server, then all users can access IM and presence 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 Server or Lync Server
The following table describes the behavior for the various deployment scenarios and end user experience.
Scenario Behavior

Communicator Web Access is pointed to th e Lync Server pool All users are homed in the Lync Server poo l Communicator Web Access is pointed to th e Office Communications Server pool Users are split between the Lync Server an d the Office Communications Server pools
All users are homed in the Lync Server poo l
All users will have support for IM and presence through Communicator Web Access and meeti ngs though Lync Web App.
All users will have support for IM and presence through Communicator Web Access and meeti ngs through Lync Web App.
Lync Server homed users will have Reach for I M and presence through Communicator Web A Communicator Web Access is pointed to th ccess. These users will use the Lync Web App e Office Communications Server 2007 R2 p for meeting access. ool. Office Communications Server homed users wil l have Reach IM and presence using Communi cator Web Access as long as Office Communic ations Server pool is running. These users will use Communicator Web Access for meeting ac cess. If the user has migrated and joins or creates a new conference using Meet Now (JOIN Launch er link), the user will join the meeting using Lyn c reach. If the conference has yet to migrate, b ut the user has, the user will join the meeting us ing Communicator Web Access.
119
If the user has not been migrated, the new eren confce will be created on the Office Communic ations Server 2007 R2 pool, and the user will u se Communicator Web Access to join the confe rence. The user should also be able to join a co nference created on Lync Server 2010 using th e reach join Launcher link. If using Communicator Web Access to join a co nference, the user will have the IM and Presenc e features available. If joining the conference u sing the Reach client, the IM and Presence feat ure is not available. Users are split between the Lync Server an d the Office Communications Server pools Communicator Web Access is pointed to th e Lync Server pool. Lync Server homed users will have Reach IM a nd presence support using Communicator Web Access as long as the Lync Server pool is runni ng and will have meeting through Lync Web Ap p. Office Communications Server homed used will have both IM and presence and meeting suppo rt using Communicator Web Access. If the user has migrated and joins or creates a new conference using Meet Now (JOIN Launch er link), the user will join the meeting using Lyn c reach. If the conference has yet to migrate, b ut the user has, the user will join the meeting us ing Communicator Web Access. If the user has not been migrated, the new conf erence will be created on the Office Communic ations Server 2007 R2 pool, and the user will u se Communicator Web Access to join the confe rence. The user should also be able to join a co nference created on Lync Server 2010 using th e reach join Launcher link. If using Communicator Web Access to join a co nference, the user will have the IM and Presenc e features available. If joining the conference u sing the Reach client, the IM and Presence feat ure is not available.
Repoint Communicator Web Access to Lync Server 2010 The following procedure describes how to point Communicator Web Access to the Microsoft Lync Server 2010 pool.
120
Note: The procedure in this section applies to both Office Communications Server 2007 and Office Communications Server 2007 R2 versions of Communicator Web Access. Note: You must perform this procedure before you completely remove Office Communications Server 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 me mber of the local Administrators group and the RTCUniversalServerAdmins group. 2. Click Start, point to Administrative Tools, and then click Communicator Web Acces s. 3. In the console pane, expand the name of the computer that hosts the virtual server for which you want to specify a next hop server, right-click the name of the virtual server, a nd then click Properties. 4. In the Properties dialog box, on the Next Hop tab, select a server or server pool from t he 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 Managed API (UCMA) 2.0 Core SDK
Microsoft Lync Server 2010communications software works with Microsoft Unified Communications Managed API (UCMA) 3.0 Core SDK. If you have external applications built on UCMA 2.0 (which shipped with Office Communications Server), you can run these applications in an environment that includes servers running Lync Server 2010. If you run a UCMA 2.0 application, homed on an Office Communications Server pool, you can enable 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 deployment to Lync Server 2010 when the Topology Builder Merge wizard is run. After the merge, the trusted service entries exist on both the Office Communications Server pool and the Lync Server 2010 pool, and no further steps are needed for coexistence. Be sure to note that this copies only the trusted service entries and route-related settings.
Configure Trusted application servers

In a mixed environment, if you create a new trusted application server after merging the legacy Office Communications Server topology with Lync Server 2010, and you define a new trusted
121
application server using Topology Builder, you must set the next hop pool to be a Lync Server 2010 pool. In a merged environment, both the legacy Office Communications Server pool and the Lync 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, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Lync Server 2010 Standard Edition server 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 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 2. Select the option to Download topology from existing deployment and then click O K. 3. In the Save Topology As dialog box, select the Topology Builder file you want to use, and click Save.

6. Click Next.
4. In the right pane, right click Trusted application servers and click New Trusted Appli cation Pool. 5. Enter the Pool FQDN of the trusted application pool and select whether it will be a sing le-server or multiple-server. 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.
122

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 associat ed with the correct Front End pool.
Configure the Meeting Join Page

You can control the Microsoft Lync Server 2010 clients that are available for joining scheduled Lync Server 2010 meetings by configuring the meeting join page. When a user clicks a meeting link in a meeting request, the meeting join page detects whether a Lync Server client is already installed on the users computer. If a client is already installed, the default client opens and joins the meeting. If a client is not installed, the meeting join page displays options for joining the meeting with alternate clients. The meeting join page always contains the option to use Microsoft Lync Web Appcommunications software. In addition to this option, you can decide whether to show links for downloading Microsoft Lync 2010 Attendee or using a previous version of Microsoft Office Communicator (Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007). The meeting join scenarios are as follows:
123
If Microsoft Lync 2010 or Microsoft Lync 2010 Attendant is installed, the client starts and joins the 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 the following 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 using the Microsoft Lync Server 2010 Control Panel (the Web Service page in the Security group). You can also configure the same settings by using the New-CsWebServiceConfiguration or SetCsWebServiceConfigurationLync Server Management Shell cmdlets with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters. To configure the meeting join page by using the Lync Server 2010 Control Panel 1. Open a browser window, and then enter the Admin URL to open the Lync Server Contr ol Panel. For details about the different methods you can use to start Lync Server Cont rol Panel, see Installing and Using Administrative Tools. 2. In the left navigation bar, click Security. 3. Click Web 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 2 010 Attendee. 5. Select or clear the Show the link for user to join meeting using legacy client check box, depending on whether you want users to be able to join meetings by using a previ ous version of Communicator.
To configure the meeting join page by using Lync Server 2010 Management Shell 1. Start the Lync Server Management Shell: Click Start, click All Programs, click Micros oft Lync Server 2010, and then click Lync Server Management Shell. 2. Run the following cmdlet: Get-CsWebServiceConfiguration This cmdlet returns the web service configuration settings. 3. Run the following command, with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters set to True or False, depending on your p reference (for details about the parameters for this cmdlet, see the Lync Server Manag ement Shell documentation): Set-CsWebServiceConfiguration -Identity global ShowDownloadCommunicatorAttendeeLink $True -
124
ShowJoinUsingLegacyClientLink $True
Deploy Lync Server 2010 Clients

After 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 with the 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 client bootstrapping policies or if you want to set new 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 using Lync Server Control Panel, Lync Server Management Shell, or both. For details, see Key Client Policies and Settings and Migrating User Settings to Lync Server 2010 in the Planning documentation. 4. Deploy the latest version of Lync Server 2010 clients along with the latest cumulative updates. For details, see Deploying Clients and Devices in the Deployment documentation. 5. (Optional) If your organization requires Microsoft Lync 2010 enhanced presence privacy mode, after migration is complete, define a Client Version Policy Rule to prevent earlier client versions from signing in. Then, enable enhanced presence privacy mode. Important: Do not enable Lync 2010 enhanced presence privacy mode until every user on a given 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 integration with your phone system option in the Phone integration section in Microsoft Lync 2010.
Phase 10: Decommission Legacy Site

The following topics provide guidance in decommissioning pools, deactivating and removing servers and pools from a legacy deployment of Office Communications Server 2007 R2. Not all of the procedures listed in this section are required. Read the information in each of these topics to determine which decommissioning procedure to use.
In This Section
Decommissioning Servers and Pools Remove BackCompatSite
125
Decommissioning Servers and Pools

The following webpages contain details about decommissioning procedures for Communications Server 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 BackCompatSite
After all pools are deactivated and all Edge Servers have been uninstalled, run the Topology Builder Merge wizard to remove the BackCompatSite. To successfully publish, enable, or disable a topology when adding or removing a server role, you should be logged in as a user who is a member of the RTCUniversalServerAdmins and Domain Admins groups. It is also possible to delegate the proper permissions for adding server roles. For details, see Delegate Setup Permissions in the Standard Edition server or Enterprise Edition server Deployment documentation. For other configuration changes, only membership in the 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.
1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2 010, and then click Lync Server Topology Builder. 2. Select the option to Download topology from existing deployment and then click O K. 3. In the Save Topology As dialog box, select the Topology Builder file you want to use, and click Save.
6. On the Specify Legacy Edge page, ensure that list of Edge Servers is empty. If the li st is not empty, use the Remove button to remove all the legacy Edge Servers, and th en click Next.
126

7. On the Specify Internal SIP port setting page, click Next. Notes: On the Invoke Merge page you may see the following warning: Total number of warnings is 1
8. On the Summary page, click Next to begin merging the topologies to remove the lega cy site.
Check for errors, warnings, and details in the log file at the following location: %temp%\To pologyBuilder\[DATE-TIME]\MergeTopologyInvoke.log No Office Communications Server 2007 / Office Communications Server 2007 R2 Edge ha s 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 server s are listed. 12. Right-click the BackCompatSite, and then click Delete.
127
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 2007 R2 pools to Lync Server 2010 pools using the Lync Server Management Shell, and the associated migration cmdlets. The topic Create a Custom Edge Server Input File defines an example Edge Server input file, and then describes in detail the various parameters of that file and also the necessary cmdlets that must be run to complete the migration. This section is optional and replaces running the Topology Builder Merge wizard procedure, described in Phase 4: Merge Topologies.
In This Section
Define Edge Server Input File Create a Custom Edge Server Input File Run Migration Cmdlets
Define Edge Server Input File
In Microsoft Office Communications Server 2007 R2, Edge Server information is not stored in WMI. As a result, the Merge-CsLegacyTopology cmdlet cannot retrieve information about your Edge Servers. If you have Office Communications Server 2007 R2 Edge Servers that need to be migrated, then you must create a custom XML file that contains your legacy Edge Server information. To do so, it is recommended that you copy the code in the attached sample and modify the relevant parameters to match your deployment. A copy of this code (input.xml) is included in the Migration folder. For a detailed explanation of the parameters and details about authoring 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"/>
128
<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 Server Edit the input.xml file mentioned in the previous section and make the following changes listed below: Replace edgeint.fqdn with the Office Communications Server 2007 R2 Edge Server internal FQDN.
Replace externalDP.fqdn with the Office Communications Server 2007 R2 Edge Server external Data Proxy FQDN. Replace node1.fqdn with the Office Communications Server 2007 R2 Edge Server internal FQDN. Replace anothernode1.fqdn with the additional Office Communications Server 2007 R2 Edge Server internal FQDN. Replace director.fqdn.com with the Director or pool that is the next hop from the Office Communications 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 File

The previous topic, Define Edge Server Input File, defined the building blocks for the input file required to merge the legacy topology using the Lync Server Management Shell. This topic dives deeper into the layout and purpose of the input.xml file. This topic explains the various parameters 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"?>
129
<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"> <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 XML declaration: <?xml version="1.0" encoding="utf-8"?> Note: Although it is optional, the XML declaration helps avoid any confusion regarding the version or encoding type used in the file. After the XML declaration you should then insert the <TopologyInput> element, like so: <TopologyInput xmlns="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 not take place. In turn, that could cause Merge-CsLegacyTopology to try and merge a poorlyformed XML file. Because this is an XML file, it is important that this be a well-formed XML file. As a 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
130
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 components deployed 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"?> <TopologyInput xmlns="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:

Lync Access Edge ServerPreviously known as the Access Proxy server, the Access Edge Server is responsible for handling all SIP traffic that crosses your organizations firewall. If your topology includes an Access Edge Server, you need to add this attribute to the <EdgeCluster> element: AP="true" Web Conferencing Edge ServerThe web Conferencing Edge Server (also known as the Data Proxy server) relays traffic between the A/V Conferencing Server and external clients. If your topology includes a web Conferencing Edge Server, you need to add this attribute to the <EdgeCluster> element: DP="true" A/V Edge ServerThe A/V Edge Server (also known as the Media Relay server) provides a single connection point that enables incoming and outgoing media traffic to help firewalls and Network Address Translation devices. If your topology includes an A/V Edge 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 legacy domain. For Office Communications Server 2007 R2, use this attribute and attribute value: Version="OCS2007R2"
<EdgeCluster>The <EdgeCluster> element is where you define the different Edge Server roles in your existing Office Communications Server topology. There are three roles you need to concern yourself with:
131
Finally, if you have enabled federation in Office Communications Server you should add FederationEnabled 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 names for both your internal Edge Server load balancer and your external Edge Server load balancers. 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 Edge Server (note that this should be the servers internal name). For example: <Machine InternalFqdn="node1.fqdn " /> <Ports>Use the <Ports> element to indicate the ports used by your Edge Servers. An APPort indicates an Access Edge Server, a DPPort indicates a web Conferencing Edge Server, and an MRPort indicates a Media Relay Server. Be sure and distinguish between internal 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 fully qualified domain name of your Edge Servers next hop server: <DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /> If the next hop server is a Director, you must add the attribute 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 the Office 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"/>
132
</Machines> <Ports InternalAPPort="5061" InternalDPPort="8057" ExternalDPPort="443"/> <DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /> </EdgeCluster> </EdgeClusters> All thats left now is to add the <RegistrarClusterPort> element; this is the section of the XML file where 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 look like 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 is an 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"?> <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"/> <Machine InternalFqdn = "anothernode1.fqdn"/> </Machines> <Ports InternalAPPort="5061" InternalDPPort="8057" ExternalDPPort="443"/> <DirectorOrEdgeNextHop Fqdn="director.fqdn.com " /> </EdgeCluster> </EdgeClusters>
133
<RegistrarClusterPort EnableAutoDiscoveryOfPorts = "false" Port = "5065" /> </TopologyInput>
Run Migration Cmdlets

The 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 and configuration settings from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010. This cmdlet creates an output file that contains the merged information from Office Communications Server 2007 R2. This file is then used to publish information to the Lync Server 2010Central Management store. Additionally, the Merge-CsLegacyTopology cmdlet allows you to input an XML file that contains Edge Server information. If you do not plan to import Edge Server information, remove the -UserInputFileName D:\input.xml parameter from Step 2 in the following procedure. Important: Before running any of the migration cmdlets, be sure the account used is a member of the RTCUniversalServerAdmins group. The steps to migrate are:
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: Merge-CsLegacyTopology -TopologyXmlFileName D:\output.xml UserInputFileName D:\input.xml Where 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 Server input.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 setting name includes characters that are being replaced with an underscore. You can safely
134
ignore this warning. This policy setting name is a default policy that was included with Office Communications Server 2007 R2. Lync Server 2010 will import this policy but replace 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 Pilot Pool to Legacy Edge Servers. Now that the merge has completed you can use Topology Builder and Lync Server Control Panel to administer the pool and view the overall side-by-side topology. For additional steps that you should run after migration has completed, see Phase 6: Verify Your Pilot Migration. See Also Define Edge Server Input File
Create a Custom Edge Server Input File
135

Ls Migrate Ocs2007 r2

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ls Migrate Ocs2007 r2

Caricato da

Copyright:

Formati disponibili

Migrating from Microsoft Office Communications Server 2007 R2 to Microsoft Lync Server 2010

Microsoft Lync Server 2010

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

Migration from Office Communications Server 2007 R2 to Lync Server 2010

NON-ACTIVATED VERSION www.avs4you.com

Before You Begin the Migration

NON-ACTIVATED VERSION www.avs4you.com

Migration Process Migration Phases Planning for Client Migration

NON-ACTIVATED VERSION www.avs4you.com

Planning for Client Migration

NON-ACTIVATED VERSION www.avs4you.com

Migrating User Settings to Lync Server 2010 Client Interoperability

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

The following information does not move to the new server:

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

AbsUseFallback DisablePC2PCVideo DisableRCCForwarding EnableUPNP MaxAudioVideoBitRate

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

BlockConversationFromFederatedContacts CalendarStatePublicationInterval CustomStateURL DisableCalendarPresence DisableEmailComparisonCheck DisableEmoticons DisableFederatedPromptDisplayName

DisableFreeBusyInfo DisableHandsetOnLockedMachine DisableHTMLIM DisableInkIM

DisableOnlineContextualSearch DisablePhonePresence DisablePICPromptDisplayName

NON-ACTIVATED VERSION www.avs4you.com

Disables publishing meeting subject and locatio n information.

DisablePresenceNote DisableRTFIM DisableSavingIM EnableAppearOffline EnableEventLogging EnableSQMData EnableTracing EnableURL MAPIPollInterval

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

NON-ACTIVATED VERSION www.avs4you.com

CustomLinkInErrorMessages DisableContactCardOrganizationTab DisableFeedsTab DisablePoorDeviceWarnings DisablePoorNetworkWarnings

DisplayPhoto DisplayPublishedPhotoDefault EnableDelegation EnableDiagnosticsLogsCollection

NON-ACTIVATED VERSION www.avs4you.com

PhotoUsage PolicyEntry SearchPrefixFlags

ShowManagePrivacyRelationships ShowRecentContacts ShowSharepointPhotoEditLink

NON-ACTIVATED VERSION www.avs4you.com

NON-ACTIVATED VERSION www.avs4you.com

AbsInsideURL AbsOutsideURL Portrange\MaxMediaP ort Portrange\MinMediaP ort Portrange\Enabled

None None None None None AllowExternalUserControl EnableDataCollaboration

CsConferencingPolicy; AllowIPAudio, AllowIPVid CsUser eo; AudioVideoDisabled

IMWarning MRASServerURI PC2PCAVEncryption msRTCLine TelephonyMode

IMWarning mrasURI ucPC2PCAVEncr yption line TelephonyMode

ExUMEnabled DisableSimultaneous Ringing VoicemailURI

AllowSimultaneou CsVoicePolicy sRinging VoicemailURI None

NON-ACTIVATED VERSION www.avs4you.com

Microsoft Lync 2010 Attendee

NON-ACTIVATED VERSION www.avs4you.com

2007 R2 release of Microsoft Office Communic ator Mobile

Lync Server 2010 Clients

NON-ACTIVATED VERSION www.avs4you.com

The following information does not move to the new server:

The following tables describe two conferencing interoperability scenarios:

Previous Client Versions and Lync Server 2010 Meetings

Before user is moved t o Lync Server 2010

Supported if enabled. F or details, see Migratio n Considerations for M eetings.

NON-ACTIVATED VERSION www.avs4you.com

4...* 4...* 4...* 4...*