Topic Last Modified: 2011-04-11

You can move a pilot user to the new Microsoft Lync Server 2010 deployment by using the following two methods: Microsoft Lync Server 2010 Control Panel and Lync Server Management Shell. For details about moving users by using the Lync Server Management Shell, see Move a User by Using the 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 (Office Communications Server 2007 Migration).

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.

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 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.
To move a user by using the Lync Server Management Shell
  1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or assigned to the CSAdministrator or 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:

    Copy Code
    Get-CsUser -OnOfficeCommunicationServer

    Using a legacy user’s SIP address as a parameter, run the Move-CsLegacyUser cmdlet.

    Copy Code
    Move-CsLegacyUser -Identity "sip address" -Target "pool_FQDN"

    For example, to move a legacy user to the pilot pool, run:

    Copy Code
    Move-CsLegacyUser -Identity "" -Target ""
  4. At the command line, type the following:

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

    For details about the Get-CsUser cmdlet, run:

    Copy Code
    Get-Help Get-CsUser -Detailed
  5. By using the Lync Server Control Panel, you can also verify that these users have been moved by viewing the Registrar pool column.

    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 "" -Target "" + 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).