You can move users to the new Office Communications Server 2007 R2 deployment by using either the Office Communications Server 2007 R2 snap-in or by using the Active Directory Users and Computers snap-in. If you use the Active Directory Users and Computers snap-in, the Office Communications Server 2007 R2 snap-in must be installed on the same computer.

When you move a user to an Office Communications Server 2007 R2 pool, the data for the user is moved to the back-end database that is associated with the new pool.

Note:
Homing the user on Office Communications Server 2007 R2 does not require that you deploy upgraded clients at the same time. Office Communicator 2007 will interoperate with Office Communications Server 2007 R2, but only with the feature set of Office Communications Server 2007. New functionality will be available to users only when they have the new client software For details on user experience during this phase, see User Experience During Phase 5.

To move users by using the Office Communications Server 2007 R2 snap-in

  1. Open the Office Communications Server 2007 R2 snap-in.

  2. In the console tree, expand the Forestnode.

  3. Expand Earlier server versions.

  4. Expand the pool name for the Enterprise pool or Standard Edition server that homes the users that you want to move, and then do one of the following:

    • To move all users in this node, right-click Users, and then click Move Users.

    • To move only specific users, in the console tree, click Users. In the details pane, select the users that you want to move, right-click the selection, and then click Move Users.

  5. Complete the Move Communications Server Users Wizard, specifying the following:

    • The Enterprise pool or Standard Edition server to which you want to move the selected users.

    • Whether to force the move if the server or pool to which you are moving the user is unavailable. If you select this option and the server or pool is unavailable, user-specific information is lost, including contact information, Allow and Block data, meeting data, and enhanced presence data. If you force the move, you will still be able to manually import the user data after the pool becomes available.

You can also move users from the Unassigned Users node to an Enterprise pool or Standard Edition server. The procedure is the same as that just described for moving users who are assigned to a Standard Edition server or Enterprise pool. The Unassigned Users node contains all user accounts that are enabled for Office Communications Server but are not currently assigned to a valid Standard Edition server or Enterprise pool. If the server or pool that a user is assigned to is deactivated or removed from the Office Communications Server environment, the pool assignment becomes invalid, and the user account is added to Unassigned Users. Unassigned users cannot sign in by using their Communications Server account.

To move users by using the Active Directory Users and Computers snap-in

  1. On a computer that has the Office Communications Server 2007 R2 administrative tools installed, open the Active Directory Users and Computers snap-in.

  2. Locate the container that has the user accounts you want to move, and then do one of the following:

    • To move all users in the container, right-click the container, and then click Move Communication Server Users.

    • To move only specific users, click the container that has the users you want to move. In the details pane, select the users that you want to move, right-click the selection, and then click Move Communications Server Users.

  3. Complete the Move Communications Server Users Wizard, specifying the following:

    • The Enterprise pool or Standard Edition server to which you want to move the selected users.

    • Whether to force the move if the server or pool to which you are moving the user is unavailable. If you select this option and the server or pool is unavailable, user-specific information is lost, including contact information, Allow and Block data, meeting data, and enhanced presence data. If you force the move, you will still be able to manually import the user data after the pool becomes available.