Manually Migrating Users to Another Domain


Updated: April 1, 2008

Applies To: Groove Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2007-07-09

This section provides a basic migration procedure for manually migrating users from one domain to another on the same server or from Groove Enterprise Services. Use this approach if domain members are running Groove 3.1 or earlier, or if the Groove Manager server administrator has not configured your site with the requisite auto-account configuration capabilities. The manual migration procedure requires users to input new account configuration codes, and it requires administrators to create a new domain group structure in the target domain, then migrate users group by group to the newly defined management domain groups. The migration must be performed on each group and subgroup in order to preserve the policy templates, and relay server sets assigned to each group.

For information about automating domain migration, see Automatically Migrating Users to Another Domain.

To manually migrate users from one domain to another, follow these steps for each group and subgroup in the domain:
  1. Address the requirements listed in Before You Begin Migrating Users.

  2. To avoid disabling devices and identities, or otherwise interrupting collaboration during the domain transition, consider adjusting domain policies for members that you intend to migrate, as follows:

  3. From the source domain:

  4. Select the identity policy template assigned to members that you intend to migrate, click the Member Policies tab, and clear the following policy (if it is selected): Identities may only be used on a managed device in this domain, then click Save Changes.

  5. Select the device policy template for the members that you intend to migrate, click the Account Policies tab, and clear the following policy (if it is selected): Members can only use managed identities from this domain on devices in this domain, then click Save Changes.

  6. From the source domain, then the target domain:

  7. Consider whether to temporarily ‘loosen’ your user verification policy for the domain during the migration period when some members will be active in the target domain while others remain pending. To edit authentication policies, select an identity policy template for the domain, click the Security Policies tab, and change the User Verification Policy settings as needed, then click Save Changes.

  8. Remember to allow time for clients to be updated with policy changes.

  9. On the server where the source domain is located (the Groove Enterprise Services site, if you are migrating members from a hosted services environment to an onsite server), go to the Groove Manager administrative Web site and export each group member list from the domain to an .xml or .csv file, as described in Exporting Domain Members.

  10. On the server where the new (or target) domain is located (the onsite Groove Manager server, if you are migrating members from a hosted services to an onsite server environment), go to the Groove Manager administrative Web site and update the policy templates and relay server sets as needed.

  11. From the target domain, create the required group hierarchy. See Adding Groups to a Domain, for information about creating domain groups.

  12. From the target domain, select the domain’s top-level Members group (or any of its sub-groups) in the navigation pane. The Members page appears.

  13. From the target domain Members page, add the users to the target domain group on the Groove Manager, as described in Adding Multiple Members from an .XML File” or Adding Multiple Members from a .CSV File.

  14. From any device, login to the Groove Manager, select the target domain group, and download the Groove Manager device registry key, as described in Registering User Devices with the Groove Manager. Apply this key to the Windows registry of any device that you intend to manage in the target domain group.

  15. Shut down Groove and restart the client devices to process the registry updates.

  16. From the target domain, send managed account configuration codes to each user that you are migrating, as described in Enabling Groove Account Configuration.

  17. Ensure that Groove users do the following:

  18. Launch Groove on each client device.

  19. Click Help from the Groove menu and select Configure Account.

  20. Copy the 25-character account configuration code for each managed identity from the e-mail into the account configuration code field.

  21. Click Finish to activate Groove on the device.

  22. At the end of this process, the Groove user has a managed Groove identity in the target domain.

  23. If you wish, reset the device and identity policies that you turned off earlier in this procedure.

  24. You can terminate the old domain or discontinue from hosted Groove services, depending on your previous setup.