Export (0) Print
Expand All

Phase 7: Move Production Users

Communications Server 2007 R2

Topic Last Modified: 2009-07-01

By default, users who are homed on Office Communications Server 2007 can be enabled for enhanced presence, but Office Communicator 2007 is required for users to take advantage of this feature. Users who are moved from a Live Communications Server 2005 Service Pack 1 (SP1) server to an Office Communications Server 2007 can use the Microsoft Office Communicator 2005 client. However, when a user does this, she cannot take advantage of the enhanced presence and A/V conferencing features included with Office Communications Server 2007.

After a user who is enabled for enhanced presence has signed in by using Office Communicator 2007, that user can no longer use Office Communicator 2005 or sign in to Live Communications Server 2005 with SP1. Additionally, such a user can no longer sign in to Communicator Web Access (2005 release) or to Communicator Mobile (2005 release).

Dd819978.important(en-us,office.13).gifImportant:
If you enable enhanced presence for a user and the user signs in to Office Communications Server 2007 using the Communicator 2007 client, the user account is converted to use enhanced presence. The user is then no longer able to sign in to Live Communications Server 2005 SP1 and cannot use any previous version of Office Communicator, Communicator Web Access, or Communicator Mobile to sign in.

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.

Dd819978.note(en-us,office.13).gifNote:
Homing the user on Office Communications Server 2007 R2 does not require that you deploy upgraded clients at the same time. New functionality will be available to users only when they have the new client software. For details about user experience during this phase, see User Experience during Phase 7 of Migration.

If you have concerns about the user data in the Live Communications Server database, export the user data by using the Dbimpexp.exe tool in Live Communications Server.

  • You must use the Live Communications Server version of Dbimpexp.exe to perform this action. The correct version is located at c:\Program Files\Microsoft LC 2005\Server\Support\DBimpexp.exe. You can use this exported data to import user data in the event that you must force a user move. For details about the use of the Live Communications Server 2005 Dbimpexp tool, see Step 2.5 Export User Data from Live Communications Server 2005 with SP1 at http://go.microsoft.com/fwlink/?LinkId=148539.
  • After you have moved the users to the new pool, you must wait for the User Replicator (UR) to complete. In the Office Communications Server event log, the system logs event 30024 to indicate that UR is complete. After you have verified that the UR is complete, you can use the Office Communications Server 2007 R2 version of Dbimpexp.exe to import the user data into the new back-end database. The correct version of the Office Communications Server 2007 R2 Dbimpexp.exe is located at C:\ Program Files\Common Files\Microsoft Office Communications Server 2007 R2\Support \DBimpexp.exe. For details about using the Office Communications Server 2007 R2 Dbimpexp.exe tool, see Removing Servers and Server Roles, Removing Enterprise Pools, and Decommissioning Servers and Pools in the Administering Office Communications Server 2007 R2 documentation.

You can also move users from the Unassigned Users node to an Enterprise pool or Standard Edition server. The Unassigned Users node contains all users who 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 using their Communications Server account.

For details about the user experience during this phase, see User Experience during Phase 7 of Migration.

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

  2. In the console tree, expand the forest node, and then navigate to the Microsoft Live Communications Server Standard Edition server or Enterprise pool that contains the user accounts that you want to move.

  3. Expand the Earlier server versions node, expand the pool name for the Enterprise pool or Standard Edition server, and then do one of the following:

    • To move all users in this node, in the console tree, click Users, 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.
  4. In the Move Communications Server Users Wizard, specify the following:

    • The Enterprise pool or Standard Edition server to which you want to move the user.
    • 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 pool is unavailable, user-specific information is lost, including contact information, Allow and Block data, meeting data, and enhanced presence data. If you choose Force User Move, you will still be able to import the users’ data if needed.

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

  2. Navigate to the appropriate container that has the users you wish to move to the new pool, and then do one of the following:

    • To move all users in this node, in the console tree, click the user container, right-click the user container, and then click Move Communications Server Users.
    • To move only specific users, in the console tree, 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. In the Move Communications Server Users Wizard, specify the following:

    • The Enterprise pool or Standard Edition server to which you want to move the user.
    • 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 pool is unavailable, user-specific information is lost, including contact information, Allow and Block data, meeting data, and enhanced presence data. If you choose Force User Move, you will still be able to import the users data if needed.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft