Export (0) Print
Expand All

Move Multiple Users (Communications Server 2007 Migration)

Lync Server 2010
 

Topic Last Modified: 2011-04-11

You can move groups of users to the new Microsoft Lync Server 2010 deployment by using the following two methods: Lync Server 2010 Control Panel and Lync Server Management Shell. You must meet certain requirements to ensure a smooth transition to Lync Server 2010. For details, see Configure Clients for Migration (Office Communications Server 2007 Migration) .

importantImportant:
  • You cannot use the Active Directory Users and Computers snap-in or the Microsoft Office Communications Server 2007 administrative tools to move users from your legacy environment to Lync Server 2010.
  • 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 by using the Move-CsLegacyUser cmdlet if it contains leading or trailing spaces.

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

noteNote:
  • 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 pool.
  • 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.

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

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

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

    Migration Select URL dialog box
  4. Click Users, click Add Filter, build the query Legacy user Equal to True, and then click Find.

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

  6. Click Action, and then click Move selected users to pool.

    importantImportant:
    If Move selected users to pool is not available, ensure that the account is a member of the RTCUniversalUserAdmins group or assigned to the CSAdministrator or CSUserAdministrator administrative role.
  7. In Move Users, select the Destination registrar pool, which is your Lync Server 2010 pool, and then click OK.

  8. 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.

    Lync Server Control Panel Users Search page

    For details about the cmdlets described in this section, run:

    Get-Help <cmdlet name> -Detailed
    

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

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

  3. At the command line, type the following, replacing User1 and User2 with specific user names you want to move, and replacing pool_FQDN with the destination pool name:

    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 was successfully moved.

  1. Log on to the computer where Topology Builder is installed as a member of the Domain Admins group and the RTCUniversalServerAdmins group.

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

  3. At the command line, type the following:

    Get-CsUser -OnOfficeCommunicationServer | Move-CsLegacyUser -Target "pool_FQDN"
    
    noteNote:
    The above cmdlet will move all users on Office Communications Server 2007, regardless of which pool they belong to. To move all users on a specific pool, use the Filter parameter.
    Get-CsUser -OnOfficeCommunicationServer -Filter {HomeServer -eq "CN=LC Services,CN=Microsoft,CN=ocs2007pool,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System,DC=contoso,DC=net"}
  4. At the command line, type the following, where user name is the name of a legacy user:

    Get-CsUser "user name"
    

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

    importantImportant:
    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" + CategoryInfo : InvalidOperation: (CN=Jeff Ander...contoso,DC=net:OCSADUser) [Move-CsLegacyUser], MoveUserException + FullyQualifiedErrorId : MoveLegacyUserError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsLegacyUserCmdlet
    If you experience this error, see Verify User Replication has Completed (Office Communications Server 2007 Migration).
 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft