Microsoft Live Communications Server to Microsoft …



[pic]

Microsoft Live Communications Server 2005 SP1 to Microsoft Lync Server 2010 Migration Strategy

Microsoft Lync Server 2010

Published: September 2011

Author: Sekou Page

Technical Reviewers: Andrew Sniderman, Jens Trier Rasmussen, Cezar Ungureanasu,

and Iyaz Allah Baksh

Abstract: This white paper outlines a migration strategy for migrating from Microsoft Live Communications Server 2005 Service Pack 1 (SP1) to Microsoft Lync Server 2010 communications software. As part of this strategy, this white paper introduces a newly supported scenario for interim coexistence of clients running Office Communicator 2005 and Lync 2010. Given that there is no supported migration path directly from Live Communications Server 2005 SP1 to Lync Server 2010, the proposed migration strategy requires you to perform several interim steps to move users to Lync Server 2010.

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.

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.

Copyright © 2011 Microsoft Corporation. All rights reserved.

Contents

Migration Planning Summary 1

Migration Strategies 1

Tri-existence support 2

Live Communications Server 2005 SP1 Support for Office Communicator Web Access and BlackBerry 3

Choosing the Migration Path 4

Migration Guidelines 6

Migration Process 6

Preparation 7

Tested Software Versions 7

Migration Phase 1: Migration to Office Communications Server 2007 R2 7

Migrating Global Settings 8

Pointing DNS SRV to a Server Running Office Communications Server 2007 R2 8

Cleaning Up Self Contacts 8

Remove Live Communications Server Administration Tools 9

Rollback Plan 9

Migration Phase 2: Migration to Lync Server 2010 10

Lync 2010 Attendee 10

ShowManagePrivacyRelationships 10

DNS SRV Record 11

Lync Server Migration 11

Step 1: Deploy Lync 2010 to Clients 11

Step 2: Enable Enhanced Presence 11

Step 3: Run Test-CsRegistration 12

Step 4: Move Users to Lync Server 12

Step 5: Users Sign In to Lync Server 12

Rollback Plan 12

Risk Mitigation 13

Known Issues 13

Migration Planning Summary

This white paper outlines a migration strategy for migrating from Microsoft® Live Communications Server 2005 Service Pack 1 (SP1) to Microsoft Lync™ Server 2010 communications software. As part of this strategy, this white paper introduces a newly supported scenario for interim coexistence of clients running Office Communicator 2005 and Lync 2010. Given that there is no supported migration path directly from Live Communications Server 2005 SP1 to Lync Server 2010, the proposed migration strategy requires you to perform several interim steps to move users to Lync Server 2010. At a high level, the migration strategy takes the following phased migration approach:

1. Validate the existing environment as an updated and stable Live Communications Server 2005 SP1 environment with the latest updates installed and all clients are running Office Communicator 2005.

2. Migrate the Live Communications Server 2005 SP1 environment to an interim Office Communications Server 2007 R2 environment, leaving all clients running Office Communicator 2005.

3. Decommission all Live Communications Server 2005 SP1 server infrastructure.

4. Upgrade clients to Lync 2010.

5. Move users from the interim Office Communications Server 2007 R2 environment to a Lync Server 2010 environment, upgrading all clients to Lync 2010.

6. Decommission the Office Communications Server 2007 R2 environment.

It is important to note that the final move of clients to Lync Server 2010 requires an update of the account to support enhanced presence. After users have been moved to Lync Server 2010, clients running Office Communicator 2005 cannot sign in.

This document does not discuss or support a strategy in which servers running Live Communications Server 2005 SP1 and servers running Lync Server 2010 coexist. Deploying the Lync Server 2010 topology into an environment that consists of servers running Live Communications Server 2005 SP1 is not supported. The strategy discussed in this document is for organizations that want to preserve data (for example, contact objects) contained within the Live Communications Server 2005 SP1 environment as they migrate to Lync Server 2010 and allow for a coexistence of clients running Office Communicator 2005 with clients running Lync 2010. If data preservation is not a requirement, you can move directly from Live Communications Server 2005 SP1 to Lync Server 2010 by fully decommissioning the Live Communications Server 2005 SP1 environment and then setting up a new Lync Server 2010 environment.

Migration Strategies

The migration strategies that we use for the Live Communications Server 2005 SP1 to Lync Server 2010 migration focus on minimizing the impact to end users and ensuring supportability of the solution. Because Live Communications Server 2005 SP1 and Lync Server 2010 cannot coexist, an interim Office Communications Server 2007 R2 environment is required. The following table summarizes some of the related migration strategies that we’ll use as part of the Live Communications Server 2005 SP1 to Lync Server 2010 migration.

Migration Strategies for Live Communications Server 2005 SP1 to Lync Server 2010 Migration

|Requirement |Strategy |Notes |

|Minimize client upgrades |Move user accounts to Office Communications | |

| |Server 2007 R2 and capitalize on backward | |

| |compatibility. | |

|Deploy Office Communications Server 2007 R2 |Upgrade Windows Messenger 5.1 clients to |Windows Messenger 5.1 clients are not |

|to support migration path |Communicator 2005. |supported for use with Office Communications|

| | |Server 2007 R2. |

|Support phased migration |Simultaneously upgrade clients and move user|Need to update enhanced presence on |

| |accounts to Lync Server in batches. |accounts. |

|Accelerate migration to Lync Server 2010 |Use approved methods to programmatically |Client migrations may slow down the |

| |move from Live Communications Server 2005 |migration process. |

| |SP1 to Lync Server. | |

|Minimize support issues for migration |Move all users from Live Communications |There is a potential for support issues |

| |Server 2005 SP1 to Office Communications |during a prolonged period of coexistence. |

| |Server 2007 R2 as a single operation to | |

| |minimize coexistence issues between Live | |

| |Communications Server 2005 SP1 and Office | |

| |Communications Server 2007 R2 homed users. | |

| |Minimize duration of Office Communications | |

| |Server 2007 R2/Lync Server infrastructure | |

| |and Office Communicator/Lync Server client | |

| |coexistence. | |

|Limit Announcement of Lync 2010 features |Only Lync Server users are enabled for and | |

| |made aware of new Lync 2010 features. | |

|Ensure supportability of solution |Decommission Live Communications Server 2005|Windows Messenger 5.1 blocked by Office |

| |SP1 prior to Lync Server deployment. Upgrade|Communications Server 2007 R2 client filter.|

| |Windows Messenger 5.1 clients to Office | |

| |Communicator 2005. | |

Tri-existence support

The current support statements indicate that tri-existence (that is, three Live Communications Server 2005 SP1/Office Communications Server 2007 R2/Lync Server client and/or server versions) is not supported. The strategy documented in this white paper supports dual existence of server versions and dual existence of client versions only. This strategy is limited to three total versions of products in the environment, but never three versions of any server or client at a time. The following table outlines both known and supported coexistence, including new options based on the migration strategy documented in this white paper. The highlighted option reflects the scenario that is considered in this document.

Known and Support Server and Client Coexistence Scenarios

|Servers |Windows Messenger 5.1/ |Office Communicator |Office Communicator |Office Communicator |

| |Office Communicator 2005 |2005/Office Communicator |2005/Office Communicator |2005/Lync 2010 |

| | |2007 |2007 R2 | |

|Live Communications Server |Supported |Not supported |Not supported |Not supported |

|2005 SP1 | | | | |

|Live Communications Server |Not supported |Supported |Not supported |Not supported |

|2005 SP1 /Office | | | | |

|Communications Server 2007 | | | | |

|Live Communications Server |Not supported |Not supported |Supported |Not supported |

|2005 SP1 /Office | | | | |

|Communications Server 2007 | | | | |

|R2 | | | | |

|Office Communications |Not supported |Supported |Not supported |Not supported* |

|Server 2007/Lync Server | | | | |

|2010 | | | | |

|Office Communications |Not supported |Not supported |Supported |Supported** |

|Server 2007 R2/ Lync Server| | | | |

|2010 | | | | |

* Scenario excluded by Microsoft.

** Scenario covered in this document.

Note   The Live Meeting client is not supported with Office Communicator 2005 and Lync 2010. For purposes of the scenario described in this document, including Live Meeting would result in tri-existence of client versions. As a result, this also means that Office Communications Server 2007 R2 web conferencing should not be deployed as part of the migration.

Live Communications Server 2005 SP1 Support for

Office Communicator Web Access and BlackBerry

Live Communications Server 2005 SP1 supported BlackBerry clients through the deployment of Office Communicator Web Access. Environments that use Office Communicator Web Access either to support BlackBerry users or for direct use of the Office Communicator Web Access client for instant messaging (IM) need to consider the impact on services and migration before moving to Lync Server 2010. The use of Office Communicator Web Access (2007 R2 release) is not recommended because it does not provide the necessary support for BlackBerry Enterprise Server and because it permanently converts users to enhanced presence mode, making the use of clients running Office Communicator 2005 impossible. We recommend that you use the latest version of BlackBerry Enterprise Server, which natively supports connectivity to Lync and Office Communications Server 2007 R2, to support BlackBerry users. Make sure the version of BlackBerry Enterprise Server that you deploy does not impact enhanced presence by contacting Research In Motion.

At the time of this document there is no web client for IM and presence for Lync Server 2010. If your organization requires this capability, you may want to delay your migration until these features are available. Your organization may also choose to deploy Office Communications Server 2007 R2 Communicator Web Access and mitigate the risk of users who are still using Communicator 2005 being converted to enhanced presence mode before they are fully migrated to Lync Server 2010. If your organization is running Exchange Server 2010, you may also consider using the IM integration that is available in Outlook Web App. For details about Outlook Web App and Lync Server 2010 or Office Communications Server 2007 R2 integration, see “Managing Outlook Web App and Instant Messaging Integration” in the TechNet Library at . At the time of this document, there are differences between Lync Server 2010 features available through Outlook Web App and Communicator Web Access that should be evaluated to determine whether Outlook Web App meets your organization’s requirements.

Note   Both Office Communications Server 2007 R2 Communicator Web Access and Outlook Web App require enhanced presence and would make IM features available to users who are migrated but no longer need to use Communicator 2005. Communicator 2005 users who require access both to the Office Communicator 2005 client and web-based IM will no longer be able to access a web IM client during the migration. If web-based IM is critical, we recommend that you to target these users for an earlier stage of the initial migration to Office Communications Server 2007 R2 that also deploys support for Communicator Web Access or Office Web App. Deploying Office Communications Server 2007 R1 Communicator Web Access is not supported with this strategy because it would result in tri-existence of server versions. Only Office Communications Server 2007 R2 Communicator Web Access or Outlook Web App is supported with Lync Server 2010.

Choosing the Migration Path

The following decision tree outlines the method for determining the optimal strategy for migration. It is important to note that the strategy does not consider BlackBerry or Live Communications Server 2005 SP1 Office Communicator Web Access as critical components, and they will be decommissioned as part of the migration. They will be enabled at a later time for Lync Server users who are using the latest version of BlackBerry Enterprise Server that supports direct integration with Lync. Also, it is important to note that there are additional steps required when Office Communicator Web Access and web conferencing coexistence is required.

[pic]

Migration path decision tree

Note   Edge scenarios were not validated in this process; specifically, the validation of remote Live Communications Server 2005 client functionality.

Migration Guidelines

Active Directory® Domain Services provides the user account store for both the pre-migration and final environments. Data stored in Active Directory will be preserved. Additional data is contained within Microsoft SQL Server® databases. The server running Live Communications Server 2005 SP1 has a local Microsoft SQL Server Desktop Engine (MSDE) database that primarily contains contact data and user settings (for example, allow/block lists and notes). It is critical to note that during the migration user notes will be lost. All other data is expected to be preserved. The results of the particular scenario tested here (that is, Office Communications Server 2007 R2 migration strategy without Office Communicator Web Access or conferencing requirement) are included in the known issues list at the end of this document.

We recommend that the lab environment resemble production as closely as possible. This includes importing production data into the lab to provide a realistic representation of user contacts, lists, and other data. You can prepare the lab using the DBImpExp.exe tool to transfer user data between Live Communications Server 2005 SP1 databases.

To prepare Office Communications Server 2007 R2 as the interim environment, we recommend that you move global settings from the System container to the Configuration partition in Active Directory. Although not required for Lync Server 2010, by performing this step you ensure that you are following recommended best practices for moving this data.

Also, you should not deploy Office Communications Server 2007 R2 conferencing because of the lack of support for Office Live Meeting as a third client version, which would result in a tri-existence client scenario. If your organization requires web conferencing features, we recommend that you deploy only Lync 2010 Attendee with Lync Server 2010 for web conferencing.

Migration Process

The migration to Lync Server 2010 includes the following steps:

1. Resolve and mitigate any issues in the existing Live Communications Server 2005 SP1 environment.

2. Apply necessary updates to the environment as needed.

3. Upgrade Windows Messenger 5.1 clients to Office Communicator 2005 (build number 1.0.559.232).

4. Move Active Directory real-time communications (RTC) data from System container to Configuration container.

5. Deploy the Office Communications Server 2007 R2 environment.

6. Configure relevant Office Communications Server 2007 R2 policies to match the Live Communications Server 2005 SP1 deployment that you have in production.

7. Modify the Domain Name System (DNS) SRV record for automatic sign-in to point to the server running Office Communications Server 2007 R2.

8. Move user accounts from Live Communications Server 2005 SP1 to Office Communications Server 2007 R2.

9. Use the Office Communications Server 2007 R2 Windows Management Instrumentation (WMI) script to clean up self contact for users.

10. Decommission the Live Communications Server 2005 SP1 environment.

11. Remove Live Communications Server Administration Tools.

12. Deploy Lync 2010 Attendee to use for web conferencing.

13. Deploy the Lync Server 2010 environment.

14. Enable the ShowManagePrivacyRelationships parameter on the Set-CsClientPolicy cmdlet to enable blocked contact/domain management.

15. Configure relevant Lync Server client policies.

16. Modify the DNS SRV record to point to Lync Server.

17. Migrate users to Lync Server and upgrade clients at the same time, as follows:

o Deploy Lync Server clients running Lync 2010 to users.

o Modify user accounts to enable enhanced presence using Active Directory Users and Computers.

o Run the Test-CSRegistration cmdlet for all target users.

o Move users to Lync Server.

o Users sign in with clients running Lync 2010.

Preparation

We strongly recommend that you back up your environments, including dumps of data using DBImpExp.exe for contact data. You should configure backups using DBImpExp.exe during each phase of the migration for the pools where users are homed.

Tested Software Versions

• Live Communications Server 2005 SP1

• Office Communicator 2005 (build 1.0.559.232)

• Office Communications Server 2007 R2 (build 6907.225)

• Lync 2010 (Cumulative Update 2, build 7577.275)

• Lync Server 2010 (Cumulative Update 2, build 7577.139)

Migration Phase 1: Migration to Office Communications Server 2007 R2

The first phase of the migration involves moving all user accounts to a backend server running Office Communications Server 2007 R2. In general, you should do this using known and established procedures for migration, which will not be covered in this document. For details, see “Migration from Live Communications Server 2005” in the TechNet Library at . Note that client upgrades are not required as part of the strategy in this document and that enhanced presence should not yet be enabled for Office Communications Server 2007 R2 scenarios. Steps that may be different from the standard migration approach or that merit explanation will be covered in this document. The steps that you’ll perform during this phase are as follows:

1. Resolve and mitigate any issues in the existing Live Communications Server 2005 SP1 environment.

2. Upgrade legacy Windows Messenger 5.1 clients to Office Communicator 2005 (build 1.0.559.232).

3. Apply necessary updates to the environment as needed.

4. Migrate global settings from the System container to the Configuration container.

5. Deploy the Office Communications Server 2007 R2 environment.

6. Configure relevant Office Communications Server 2007 R2 policies to match the Live Communications Server 2005 SP1 deployment that is in production.

7. Modify the DNS SRV record for automatic sign-in to point to a server running Office Communications Server 2007 R2.

8. Move user accounts from Live Communications Server 2005 SP1 to Office Communications Server 2007 R2.

9. Use the Office Communications Server 2007 R2 WMI script to clean up self contact for users.

10. Decommission the Live Communications Server 2005 SP1 environment.

11. Remove Live Communications Server Administration Tools.

Migrating Global Settings

To migrate global settings, you can use the Office Communications Server 2007 R2 Global Settings Migration Tool. For details, see “Using the Global Settings Migration Tool to Move to Configuration Container” in the TechNet Library at .

Pointing DNS SRV to a Server Running Office Communications Server 2007 R2

Note that in many environments, Live Communications Server 2005 SP1 may have been configured for non-secure SIP traffic (that is, Transmission Control Protocol or TCP 5060). We recommend that you take this opportunity to change everyone over to secure SIP (that is, Transport Layer Security or TLS 5061).

Cleaning Up Self Contacts

By default, Windows Messenger 5.1 puts a contact for a particular user in their Contacts list. This results in users seeing themselves in their Contacts list (that is, a “self contact”). After he or she is on the Contacts list, this user cannot be removed using other clients. In addition, after you migrate the user to Lync Server 2010 the “self contact” is no longer visible, but the data is still in the database. Although there is no known effect of keeping this self contact in the database, as a precaution for any environment that contained Live Communications Server 2005 SP1 where Windows Messenger 5.1 may have been used, we recommend that you clean up this entry. In addition, even if it is unknown whether Windows Messenger 5.1 clients were used, we recommend that you run a script to clean up any potential instances of this issue as a precaution for any Live Communications Server 2005 SP1 environment. It is important to note that management of contacts from the server side is only possible at the time of this document by using Office Communications Server 2007 R2 WMI, which is supported for servers running Office Communications Server 2007 R2, but not servers running Lync Server 2010. As a result, you can only remove self contacts using the following scripts while users are on the Office Communications Server 2007 R2 pool prior to migrating them to Lync Server 2010.

Clean Self Contact for a Single User

#Script Name: CleanSelfContactWithPrompt.ps1

#This script will prompt for a target user for which to clean the “Self” contact.

#Prompt for User

Write-Host “Self-Contact Cleanup Script.”

$URI=Read-Host “Enter Sip Address”

#Get User Information

$Query="Select * from MSFT_SIPESUserSetting where PrimaryURI = 'sip:$URI'"

$User = Get-WmiObject -Query $Query

$UserInstanceID = $User.InstanceID

#Get the contact on the user's contact list

$Contact = (Get-WmiObject -Query "Select * from MSFT_SIPESUserContactData where UserInstanceID = '$UserInstanceID'" | Where {$_.SIPURI -like "sip:$URI"})

#Delete the contact if it exists

if ($Contact -ne $null) { #The contact is on the user's contact list

$Contact.Delete()

}

elseif ($Contact -eq $null) { #The contact is not on the user's contact list

Write-Host "The contact does not exist on the user's contact list"

}

Clean Self Object for List of Users

#Script Name: CleanSelfContactsFromCsv.ps1

#Create a file called migrateusers.csv with the heading (first row) called “SipAddress” and place in the same directory where this script is stored.

$OCSUsers=Import-Csv migrateusers.csv

foreach ($User in $ocsusers) {

$URI=$user.SipAddress

$Query="Select * from MSFT_SIPESUserSetting where PrimaryURI = 'sip:$URI'"

$User = Get-WmiObject -Query $Query

$UserInstanceID = $User.InstanceID

$Contact = (Get-WmiObject -Query "Select * from MSFT_SIPESUserContactData where UserInstanceID = '$UserInstanceID'" | Where {$_.SIPURI -like "sip:$URI"})

if ($Contact -ne $null) {

$Contact.Delete()

}

elseif ($Contact -eq $null) {

Write-Host "The contact does not exist on the user's contact list"

}

}

Remove Live Communications Server Administration Tools

We strongly recommend that you remove Live Communications Server Administration Tools from the environment due to a known issue when Lync Server 2010 is introduced into the environment. By default, when the Office Communications Server 2007 R2 migration has completed Live Communications Server Administration Tools would normally present an administrator with options that are not available, making the use of Live Communications Server Administration Tools impossible. However, after you add servers running Lync Server 2010 to the environment, Live Communications Server Administration Tools become available again, they can detect servers running Lync Server 2010, and allow these servers to be used to provision users. In addition, should an administrator use Live Communications Server Administration Tools to view the properties of a user account homed on the server running Office Communications Server 2007 R2, the administrator is notified that there is no valid pool assigned to the user and the administrator is prompted to select one of the available servers running Lync Server 2010 only. Both provisioning of a new user and modifying an existing user using Live Communications Server Administration Tools on a server running Lync Server 2010 results in broken user accounts that have msRTCSIP-UserEnabled set to False.

Rollback Plan

In general, rollback guidance provided in this document is based on recommendations in the established documentation for migrating from Live Communications Server 2005 SP1. The migration of global settings from the System container to the Configuration container is a recommended step and has limited rollback options. However, during migration to Office Communications Server 2007 R2 you can move users back to the server running Live Communications Server 2005 SP1, if necessary. If for some reason enhanced presence was enabled during an Office Communications Server 2007 R2 migration and a user logs on with a rich client (that is, disabling the use of Live Communications Server 2005 SP1), you can delete the user account from Office Communications Server 2007 R2, re-enable the user account, and then import contacts from backup using DBImpExp.exe.

Migration Phase 2: Migration to Lync Server 2010

The second phase of the migration occurs after all servers running Live Communications Server 2005 SP1 have been removed from the environment, and only Live Communications Server clients and servers running Office Communications Server 2007 R2 remain. Once again, we’ll use established procedures for migration from Office Communications Server 2007 R2 and we will not cover then in this document. For details, see “Migration from Office Communications Server 2007 R2 to Lync Server 2010” in the TechNet Library at . However, you should follow the client upgrade recommendations outlined in this document. The Lync Server environment should be brought online to the point of coexistence only to allow for you to perform the additional steps outlined in the following list. Steps that may be different from the standard migration approach or that merit explanation are covered in this document. The steps that you’ll perform during this phase are as follows:

1. Deploy the Lync Server 2010 environment.

2. Deploy Lync 2010 Attendee to use for web conferencing.

3. Enable the ShowManagePrivacyRelationships parameter on the Set-CsClientPolicy cmdlet to enable blocked contact/domain management.

4. Configure relevant Lync Server client policies.

5. Modify the DNS SRV record to point to Lync Server.

6. Migrate users to Lync Server and upgrade clients at the same time as follows:

o Deploy Lync Server clients running Lync 2010 to end users.

o Modify user accounts to enable enhanced presence using Active Directory Users and Computers.

o Run the Test-CSRegistration cmdlet for all target users.

o Move users to Lync Server.

o Users sign in with clients running Lync 2010.

Lync 2010 Attendee

If you need to provide web conferencing, you can deploy Lync 2010 Attendee to enable web conferencing. We assume that most deployments where you intend to use Lync Server 2010 for web conferencing will probably want to use Office Communications Server 2007 R2 or Lync Server 2010. However, since tri-existence of clients is not supported, deploying Office Communications Server 2007 R2 dial-in conferencing (that is, by using the Live Meeting client) is not supported in this migration strategy. As a result, you can only use web conferencing when Lync Server is deployed. By deploying the Lync 2010 Attendee client in advance of the Lync Server client migration, you ensure a more smooth experience for users who have not yet been upgraded to using Lync 2010 to join meetings. It is important to note that Lync 2010 Attendee joins Lync Server conferences anonymously and, as a result, does not cause a change to enhanced presence, which would block the use of Office Communicator 2005. However, this means that you should prevent the use of Lync Web App as an authenticated user to avoid issues with blocking Office Communicator 2005. By deploying Lync 2010 Attendee, you further limit the chance that your organization will use Lync Web App at all. However, this does not address risk from corporate users joining on machines without Lync 2010 Attendee. We recommend that your organization provide training to mitigate risk or delay of conferencing deployment until all users are migrated to the new Lync Server environment.

ShowManagePrivacyRelationships

The ShowManagePrivacyRelationships client policy option should be set to True during the migration from Live Communications Server 2005 SP1 to enable end users to manage their block lists. In Live Communications Server 2005 SP1, users had full access to manage their allow/block lists, including for users not in their Contacts list. In addition to user objects, entire domains could be blocked by end users. After migrating to Lync Server, these settings will not be visible for blocked users who are not on their Contacts list and for domains at all. To prevent support issues resulting from users reporting they are not receiving messages from users they do not realize they have blocked, we recommend that you set ShowManagePrivacyRelationships to True to allow users to manage and view these settings using Set-CsClientPolicy. You need to set this cmdlet parameter using the Lync Server Management Shell. For example, to set ShowManagePrivacyRelationships to True for all client policies, run the following command at Lync Server Management Shell command prompt:

Get-CsClientPolicy | Set-CsClientPolicy – ShowManagePrivacyRelationships $True

For details, see “Set-CsClientPolicy” in the TechNet Library at . Your organization may need to provide user training to show end users how to access these settings in their clients running Lync 2010.

DNS SRV Record

We recommend that you to point the DNS SRV record to Lync Server prior to moving clients to Lync Server to ensure that anonymous users are able to join meetings.

Lync Server Migration

When the Lync Server migration is complete, it is critical that you perform multiple steps as close in time as possible to minimize disruption in service for end users. The migration method used here supports migration of users in batches and as a result the migration should be staged according to the ability of the organization to perform client upgrades to Lync 2010.

Step 1: Deploy Lync 2010 to Clients

We recommend that your organization deploy Lync 2010 to clients first. If this step is not successful you need to stop the process because proceeding with the remaining steps would result in users not being able to sign in. You should perform client deployment using methods familiar to your organization that can be tracked and audited. We recommend that your organization make a manual installation method available in case client deployment fails for a subset of users.

Step 2: Enable Enhanced Presence

You can enable enhanced presence by using Active Directory Users and Computers or by running a script. Note that you can complete this step in advance while users still are using Office Communicator 2005. However, there is risk if clients running Office Communicator 2005 try to sign in with a rich client. Enhanced presence only affects the use of Office Communicator 2005 after a user has used a rich client (for example, Office Communicator 2007 R2, Office Communicator Web Access (2007 R2 release), Lync 2010, or Lync Web App) to sign in. The following scripts provide examples of how you can enable enhanced presence for users.

Enable Enhanced Presence for a Single User

#Script Name: EnableEnhancedPresenceWithPrompt.ps1

$URI = Read-Host "Enter SIP Address"

$Query = "Select * From MSFT_SIPESUserSetting Where PrimaryUri = '$URI'"

$User = Get-WMIObject -Query $Query

$User.EnabledForEnhancedPresence = $True

[void] $user.Put()

Enable Enhanced Presence for a List of Users

#Script Name: EnableEnhancedPresencefromCsv.ps1

#Create a file called migrateusers.csv with the heading (first row) called “SipAddress” and place in the same directory where this script is stored.

Import-Csv migrateusers.csv | foreach {

$Query = "Select * From MSFT_SIPESUserSetting Where PrimaryUri = '$_.SipAddress'"

$User = Get-WMIObject -Query $Query

$User.EnabledForEnhancedPresence = $True

[void] $user.Put()

}

Step 3: Run Test-CsRegistration

Test-CSRegistration is a synthetic transaction that simulates a user logging on. Note that after you run this command, users can no longer use Office Communicator 2005. This command does not require that you use the target user’s credentials, but it does require that the user running the command have RTCUniversalServerAdmins user rights. The following is an example of the syntax required to run this command for a particular user. This command must be run for every user before they can sign in with the client running Lync 2010. Note that you must run this command on a server that has a certificate (for example, a Front End Server, not a Monitoring Server).

Syntax:

Test-CSRegistration –UserSIPAddress –TargetFQDN

Example:

Test-CSRegistration –UserSIPAddress bob@ –TargetFQDN ocs.contoso.local

For details about Test-CSRegistration, see “Test-CsRegistration” in the TechNet Library at .

Test Lync Server Registration for a List of Users

#Script Name: CSRegistrationFromCsv.ps1

#Create a file called migrateusers.csv with the heading (first row) called “SipAddress” and place in the same directory where this script is stored.

Import-Csv migrateusers.csv | foreach {

$UserInfo=Get-CsUser $_.SipAddress

Test-CSRegistration –UserSIPAddress $_.SipAddress –TargetFQDN $UserInfo.RegistrarPool

}

Step 4: Move Users to Lync Server

Moving users to Lync Server is a part of the standard migration process and you can do this by using any of the documented methods, including the Lync Server Control Panel or the Windows PowerShell® command line interface. For details, see “Move Multiple Users” in the TechNet Library at .

Step 5: Users Sign In to Lync Server

Migrated users should now be able to sign in to Lync Server using their newly deployed clients running Lync 2010.

Rollback Plan

The standard options for rolling back a Lync deployment apply here as well. One item of note is that after you run Test-CSRegistration, the only option for rollback would be to disable the user on Lync Server, re-enable the user on Office Communications Server 2007 R2, and then restore contacts from backup by using DBImpExp.exe.

Risk Mitigation

The overall risks with the migration strategy from Live Communications Server 2005 SP1 to Lync Server 2010 are based on scenarios in which there are issues during the migration and the migration is only partially completed. One scenario is that a user receives the client upgraded to Lync 2010, but their account has not been migrated to Lync Server 2010. The ideal way to mitigate this risk is to ensure that you move users in batches and that you use the same lists for the client upgrades and user moves. You can use scripts to quickly enable a user in this scenario. As a result, there is minimal risk.

A second scenario is for users who don’t get an upgraded client running Lync 2010, but for some reason their account was already moved to Lync Server 2010. In this case, the account cannot easily be moved back to the Office Communications Server 2007 R2 pool so that it allows the user to use a Live Communications Server client. If absolutely required, you can delete user accounts from Lync Server 2010 or Office Communications Server 2007 R2, and then re-enable them on Office Communications Server 2007 R2. However, note that newly created Office Communications Server 2007 R2 accounts will have enhanced presence enabled. Additional risk is introduced with the potential scenario of the user accidentally uses a rich client and disables Office Communicator 2005 again. Instead, we recommend that your organization either push the clients running Lync 2010 to these users or make Lync 2010 available for manual installation.

In general, we recommend that you minimize the transition period. We recommend a coexistence period of a few weeks (for example, two weeks) to minimize support and interoperability issues.

Known Issues

The following table lists the known issues found using Office Communicator 2005 and Lync 2010 on an Office Communications Server 2007 R2 or Lync Server 2010 infrastructure.

Known Issues List

|  |Issue |Description |Workaround |

|1 |Office Communicator attendees in a Lync |When a conference is hosted on the Lync |Educate users and help desk that the Lync |

| |2010 hosted IM conference cannot add users |Server 2010 conferencing server, Office |Server users need to add attendees. |

| |to the IM conference |Communicator attendees cannot add | |

| | |participants. | |

|2 |Office Communicator users cannot join |Lync Web Access fails on authentication for|Use Lync 2010 Attendee. If Lync 2010 |

| |application share via Lync 2010 Attendee |users still on Office Communications Server|Attendee is deployed, it starts |

| | |2007 R2. |automatically, bypassing Lync Web Access. |

| | | |This is not an expected behavior.. |

|3 |Office Communicator users see incomplete |When a conference is initiated by a Lync |Provide user education and training. This |

| |roster in Lync 2010 hosted IM conferences |2010 user and is hosted on the Lync Server |is an expected behavior. This is confirmed |

| | |conferencing server for IM, Office |as an expected behavior in the Office |

| | |Communicator users see only two |Communications Server 2007 R2 migration |

| | |participants—themselves and the organizer. |scenario too. |

|4 |Office Communicator application sharing |Live Communications Server 2005 SP1 and |Lync Server users can determine who is able|

| |does not work with Lync 2010 users |Office Communicator use NetMeeting for |to participate in application share by |

| |See also: Issues 1 and 2 in this table |application sharing, but NetMeeting is not |viewing the double arrow icon. |

| | |supported in Lync Server. | |

|5 |Live Communications Server 2005 SP1 notes |Users’ set notes are lost when users are |You can reset notes after migration is |

| |lost in migration |migrated from Live Communications Server |complete. See also: Issue 6 in this table. |

| | |2005 SP1 to Lync Server 2010. | |

|6 |Live Communications Server 2005 SP1 notes |Live Communications Server 2005 SP1 users |None. |

| |are not visible to Lync Server users |can see notes set by Lync Server 2010 | |

| | |users, but Lync Server users cannot see | |

| | |notes set by Live Communications Server | |

| | |users. | |

|7 |Live Communications Server 2005 SP1 block |Contact or domain blocks set by users are |Configure the |

| |access control lists (ACLs) are not visible|not visible for editing in default Lync |ShowManagePrivacyRelationships parameter of|

| |in the default Lync Server client view |Server client view. |the Set-CsClientPolicy cmdlet to show this |

| |after migration | |and allow user modification. End user |

| | | |training may be required to show users how |

| | | |to manage these lists in the Lync Server |

| | | |client. |

|8 |Self entry on buddy list is displayed after|Users who are using Windows Messenger 5.1 |You can use WMI to clean up this issue |

| |migration (artifact from Windows Messenger |see themselves on their buddy list. |before migration. |

| |5.1) | | |

|9 |Office Communicator remains in conference |For Lync Server hosted conferences, Office |Provide user education and training. This |

| |after completion |Communicator users are still displayed in |is an expected behavior. |

| |See also: Issue 3 in this table |the conference, along with the organizer | |

| | |after completion. They can still send | |

| | |instant messages but no one is active in | |

| | |the conference. | |

|10 |After Office Communications Server 2007 R2 |New users provisioned on Office |Mitigate this risk by deploying Lync 2010 |

| |migration: user accounts are created with |Communications Server 2007 R2 are created |Attendee and user education to ensure that |

| |enhanced presence enabled |with enhanced presence enabled. Although |they use anonymous join. If possible, try |

| | |Live Communications Server clients can sign|to minimize the number of new users created|

| | |in, there is risk that if these users use a|during the transition period. |

| | |rich client they will be permanently | |

| | |converted to enhanced presence, making Live| |

| | |Communications Server clients unusable. | |

| | |This includes joining as an authenticated | |

| | |user to a meeting through Lync Web Access | |

| | |(that is, if your organization is using | |

| | |Lync Server web conferencing). | |

|11 |Live Communications Server Administration |Live Communications Server Administration |Remove Live Communications Server |

| |Tools break users in Lync Server |Tools become active again after Lync Server|Administration Tools from the environment. |

| |environment |is introduced. Note that these tools are |To fix broken user accounts, start Active |

| | |inactive in the Office Communications |Directory Users and Computers on the server|

| | |Server 2007 R2 environment, but can be used|running Office Communications Server 2007 |

| | |in error to improperly enable or configure |R2 and apply the Delete Communications |

| | |users when Lync Server 2010 is introduced |command. Then, re-enable the user and |

| | |into the environment. For existing users, |restore contacts from backup, if necessary.|

| | |administrators are told that the user is | |

| | |homed on an invalid server and are prompted| |

| | |to select a Lync Server. This results in | |

| | |broken user accounts. msRTCSIP-UserEnabled | |

| | |is set to FALSE for accounts created. | |

Note   Edge scenarios are not in scope for this document; specifically, validation of remote Live Communications Server 2005 client functionality.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download