Migrating SharePoint Workspace users to Groove Server Manager
Applies to: SharePoint Workspace 2010, Groove Server 2010
Topic Last Modified: 2010-09-01
This article describes how to migrate SharePoint Workspace user accounts to a new Groove Server Manager system. Active Directory integration with Microsoft Groove Server 2010 Manager facilitates the process of migrating Microsoft SharePoint Workspace users from one management domain to another. If you need to move SharePoint Workspace users from one management domain to another you can use the Groove Server Manager auto-migration feature. If your Groove management setup does not meet the prerequisites for auto-migration or if you are using client software that is older than Office Groove 2007, you can manually migrate users from one management domain to another. Automatic domain migration facilitates the task of migrating members of a Groove Manager 2007 domain or group to another Manager server. This method requires minimal SharePoint Workspace user interaction and eliminates the administrative overhead of migrating users manually and then sending account configuration codes to users.
For information about how to upgrade a Manager server to Groove Server 2010 Manager without Active Directory, see Upgrading Groove Server Manager.
In this article:
Before you begin
Migrating SharePoint Workspace accounts from a Groove Server 2007 Manager to a Groove Server 2010 Manager with Active Directory
Migrating SharePoint Workspace accounts from one Active Directory-integrated Groove Server 2010 Manager to another
Moving unmanaged SharePoint Workspace accounts to Groove Server 2010 Manager with Active Directory
Manually migrating SharePoint Workspace accounts from one Groove Server Manager to another
Migration administration
Before you begin
Before you start to migrate SharePoint Workspace users to another domain, address the prerequisites and conditions listed in the following table, depending on your selected migration method.
| Requirements and Conditions | For Automatic Domain Migration | For Manual Domain Migration |
|---|---|---|
Server requirements |
For information about auto-account configuration and restoration, see Automate SharePoint Workspace account configuration/restoration. |
Ensure that a destination Groove Server Manager has been installed as described in Install and configure Groove Server 2010 Manager. Note Make sure to define a unique DNS-formatted domain name for the destination system. Do not use the same domain name that was used for the source system. |
Client requirements |
Ensure that Microsoft SharePoint Workspace 2010 is installed on client computers. |
Ensure that Microsoft SharePoint Workspace 2010 is installed on client computers. |
RBAC requirements |
If Role-Based Access Control is enabled, as recommended, ensure that you have the necessary role for your task. Minimum roles on the source Manager server are as follows:
Minimum roles on the destination Manager server are as follows:
|
If Role-Based Access Control is enabled, as recommended, ensure that you have the necessary role for your task. Minimum roles on the source Manager server are as follows:
Minimum roles on the destination Manager server are as follows:
|
Temporary conditions |
If the migration involves many clients, notify SharePoint Workspace users that contact search results may be incomplete and contact authentication may appear incorrect temporarily until all users are migrated. You can adjust policies to ease this condition, as described in the following procedures for automatic and manual domain migration. |
If your migration will occur over a significant time period, notify SharePoint Workspace users that contact search results may be incomplete and contact authentication may appear incorrect temporarily until all users are migrated. You can adjust policies to ease this condition, as described in the following procedures for automatic and manual domain migration. |
Migrating SharePoint Workspace accounts from a Groove Server 2007 Manager to a Groove Server 2010 Manager with Active Directory
This section describes how to use an automated domain migration procedure to migrate managed SharePoint Workspace users from a Groove Server 2007 Manager system to a Groove Server 2010 Manager system in an Active Directory environment.
To migrate SharePoint Workspace accounts from a Groove Server 2007 Manager to a Groove Server 2010 Manager with Active Directory
Address the requirements listed in Before you begin.
Make sure that both the source and destination Manager domains are integrated with the same forest in Active Directory.
Back up the existing Groove Server Manager database that resides on the SQL Server.
Assemble the list of 2007 Manager domain members that you want to migrate. You can create the list by exporting members to an .xml or .csv file from the Manager server, as described in Managing SharePoint Workspace users.
Use the member list together with a provided Windows PowerShell or Visual Basic Scripting Edition (VBS) script, to assign the appropriate Active Directory members to the Groove Server 2010 Manager system, as described in Create a SharePoint Workspace user directory for Groove Server Manager. After you have completed the steps in the procedure, the new Manager server will be updated with pending members during periodic synchronization with Active Directory. Pending members will change to active members after you migrate them as described in the next sequence of steps.
To avoid disabling devices and identities, or otherwise interrupting collaboration during the domain transition, consider adjusting management domain policies for members that you intend to migrate on the source and then destination domain, as follows:
Consider cross-certifying the source and destination domains, as described in Cross-certifying Groove Server Manager domains.
Consider adjusting the user verification policy to avoid disabling accounts or otherwise interrupting collaboration during the domain transition, as described in Setting SharePoint Workspace user verification policy. Loosening this policy is recommended during the migration period when some members will be active in the destination domain while other members remain pending.
Note
Remember to leave time for clients to be updated with policy changes.
On the server where the destination domain is located, log on to the Groove Server Manager administrative Web site and update the policy templates and Relay server pools as needed.
On the server where the source domain is located, select the Manager server domain, click Domain Properties, click the Advanced Settings button, and then select Enable migration to a new Groove Manager domain. Requires Groove 2007 or later..
From the source domain, log on to the Groove Server Manager administrative Web site, select Members or another group, click the Manage Members drop-down menu in the toolbar, and then select Migrate Members.
From the source domain Migrate Members page, select one of the following options:
Choose this Migration option: To achieve the following: Selected members
To migrate selected members to another domain.
Domain members (new and existing)
To migrate all members in the domain to another domain.
Group members (new and existing)
To migrate all members in the current group to another domain.
From the source domain Migrate Members page, type the Manager URL in the Destination Groove Manager Server URL field and then click OK. The destination server must be a Groove Server 2010 Manager or Groove Manager 2007 version that supports auto account configuration.
Note
If you already configured migration at a higher level (for example, to specify a common destination server for all domain members before assigning them to destination groups), the Manager URL will appear in this field by default.
Note
Members can be marked for migration regardless of status (active, pending, or disabled), but only active members can be migrated. Any members that are added to the old domain later will be marked for migration.
You have now marked members for migration and the Manager server’s automatic account configuration feature will update client accounts so that they can authenticate to the new Manager server.
Update the account configuration item in the Group Policy Object to point to the new Manager server, as described in Automate SharePoint Workspace account configuration/restoration. When each user logs on to SharePoint Workspace, the client is re-directed to the new Manager server. Upon contact with the new server, each user becomes an active member of the destination domain.
From the source domain, confirm that migrated members show a Migrated status on the Members page.
From the destination domain, confirm that logged-on SharePoint Workspace users show an Active status on the Members page.
Optionally, reset the device and identity policies that you turned off at the start of this procedure.
When migration is complete, you can close the old domain on the source server.
For more information about member migration, see Migration administration.
You can check the status of migrating members, from the Members page in the original or source domain.
Migrating SharePoint Workspace accounts from one Active Directory-integrated Groove Server 2010 Manager to another
The process of migrating SharePoint Workspace accounts from one Groove Server 2010 Manager system to another can be done on the Active Directory server, providing that the migration occurs within the same Active Directory forest. This procedure does not apply to migration across Active Directory forests. To migrate SharePoint Workspace accounts across forests, use the manual procedure that is described in Manually migrating SharePoint Workspace accounts from one Groove Server Manager to another.
To migrate SharePoint Workspace accounts from one Active Directory-integrated Groove Server 2010 Manager system to another
Address the requirements listed in Before you begin.
Make sure to integrate the destination Groove Server Manager domain that uses the same Active Directory forest as the source Groove Server Manager.
Use a provided Windows PowerShell or Visual Basic Scripting Edition (VBS) script to direct Active Directory members to the new Groove Server 2010 Manager system, as described in Create a SharePoint Workspace user directory for Groove Server Manager.
Update the account configuration item in the Group Policy Object to point to the new Manager server, as described in Automate SharePoint Workspace account configuration/restoration. When each user logs on to SharePoint Workspace, the client will be re-directed to the new Manager server. Upon contact with the new server, each user becomes a member of the destination domain, with a status of Active on the Members page. On the source domain, migrated members show a status of Migrated.
For more information about member migration, see Migration administration.
Moving unmanaged SharePoint Workspace accounts to Groove Server 2010 Manager with Active Directory
This procedure describes how to use the Groove Server Manager automatic account configuration capability to migrate unmanaged SharePoint Workspace accounts to a Groove Server 2010 Manager system without disrupting the client work environment. This process converts unmanaged SharePoint Workspace user accounts to managed accounts, preserving existing workspaces and content. No end-user input is necessary.
To move unmanaged SharePoint Workspace accounts to Groove Server 2010 Manager with Active Directory
Review the requirements in Before you begin.
Make sure that the following conditions are met:
The unmanaged SharePoint Workspace users are members of an Active Directory.
The destination Manager server domain is integrated with the Active Directory forest of which the unmanaged SharePoint Workspace users are members.
Each SharePoint Workspace account has a single identity. Accounts that have multiple identities are not supported in SharePoint Workspace 2010 and cannot be migrated.
Logon to the destination Groove Server Manager administrative Web site and import the SharePoint Workspace client information from the Active Directory forest to Groove Server 2010 Manager, as described in Create a SharePoint Workspace user directory for Groove Server Manager.
Configure the destination Groove Server 2010 Manager system for automatic account configuration, as described in Automate SharePoint Workspace account configuration/restoration. This process uses a Group Policy object (GPO) to update unmanaged SharePoint Workspace clients that have the name of a destination Manager server. The GPO update directs those clients to migrate to the new Manager server.
Allow time for the Manager server to synchronize with Active directory or start the Groove Server 2010 Manager Directory Integration service to expedite synchronization.
When each user logs on to SharePoint Workspace, the client will contact the assigned Manager server. Upon contact with the new server, each user becomes an active member of the Manager server domain and is subject to its management policies and Relay server assignments. Their previous workspaces and content remain in their converted accounts.
For more information about member migration, see Migration administration.
Manually migrating SharePoint Workspace accounts from one Groove Server Manager system to another
This section provides a basic migration procedure for manually migrating SharePoint Workspace users from one Manager server to another, retaining their access to existing workspaces and content. This procedure is most suitable for setups where Active Directory is not integrated with Groove Server 2010 Manager.
For information about how to automate domain migration, see Migrating SharePoint Workspace accounts from a Groove Server 2007 Manager to a Groove Server 2010 Manager with Active Directory or Migrating SharePoint Workspace accounts from a Groove Server 2007 Manager to a Groove Server 2010 Manager with Active Directory.
To manually migrate users from one Groove Server Manager system to another, follow these steps for each group in the domain
Address the requirements listed in Before you begin.
To avoid disabling devices and identities, or otherwise interrupting collaboration during the domain transition, consider adjusting management domain policies for members that you intend to migrate on the source and then destination domain, as follows:
Consider cross-certifying the source and destination domains, as described in Cross-certifying Groove Server Manager domains.
Consider adjusting the user verification policy to avoid disabling accounts or otherwise interrupting collaboration during the domain transition, as described in Setting SharePoint Workspace user verification policy. Loosening this policy is recommended during the migration period when some members will be active in the destination domain while other members remain pending.
Note
Remember to leave time for clients to be updated with policy changes.
From the Manager server where the source domain is located, log on to the Groove Server Manager administrative Web site and export the member list to an .xml or a .csv file, as described in Managing SharePoint Workspace users.
From the Manager server where the destination domain is located, log on to the Groove Server Manager administrative Web site and update the policy templates and Relay server pools as needed. For information about how to configure policy templates and Relay server pools, see Operations for Groove Server 2010 Manager.
From the destination server, select Members or another group in the navigation pane. The Members page appears.
From the destination server Members page, import the users to the destination domain on the Groove Manager, as described in Manually creating a SharePoint Workspace user directory for Groove Server Manager.
From the destination server Members page, send account configuration codes to migrating members, as described in Manually delivering SharePoint Workspace account configuration codes.
From the destination domain, confirm that logged-on SharePoint Workspace users show an Active status on the Members page.
From the source domain, confirm that migrated SharePoint Workspace users show a Migrated status on the Members page.
If you want, reset the identity policies that you turned off earlier in this procedure.
Optionally, close the old domain.
For more information about member migration, see Migration administration.
Migration administration
This section provides information about how to perform the following migration tasks:
Search for members of a specific migration status
Monitor migration events
Cancel migration
To search for members of a specific migration status
Log on to the Groove Server Manager administrative Web site for the source domain. Click Members or another group. A list of active, pending, and disabled members appears; migrated members will not appear. Only Active Members can be migrated.
To search for members of a specific migration status, click Advanced Search, and then select one of the following options:
Members who are pending domain migration - To find Pending Migration domain members. These are members marked for migration but not yet active in the destination domain.
Members who have already migrated to another domain - To find migrated domain members. These are members who have logged into SharePoint Workspace after they have been marked for migration and who are now active members of the destination domain.
The search displays a filtered list of members pending migration or of migrated members, depending on your selection. For members that are pending migration, the list shows the date that each member was marked for migration, destination server URL, and each member’s last SharePoint Workspace contact date. For migrated members, the list shows the date of migration, destination server URL, and destination domain name for each member.
Clicking a member displays the member’s Account Information page and migration details, including the following:
Member’s migration status - Pending Migration or Migrated
New Manager server URL
New Manager domain name
Date since marked for migration, or Date migrated
The automatic domain migration feature reports migration-related events to the Server log.
To see migration-related events:
Log on to the Groove Server Manager administrative Web site for the source domain.
Click the Reports tab for the domain.
Select Server Log from the Reports drop-down menu.
To cancel domain migration
If the Manager domain is integrated with an Active Directory forest, cancel migration from Active Directory by resetting the Groove Manager server URI attribute back to the source domain. The following Manager-server based steps do not apply.
If the Manager domain is not integrated with an Active Directory forest, log on to the Groove Server Manager administrative Web site for the source domain and follow the remaining steps in this procedure.
Click Members or another group to display the members list.
Click the Manage Members drop-down menu in the toolbar and select Stop Member Migration.
Choose a Stop Migration option, as described in the following table, and then click OK. Based on your selection, members marked for migration will not be migrated:
Choose this Stop Migration option: To achieve the following: Selected members
To stop selected members from migrating to another domain.
Domain members (new and existing)
To stop all members in the domain from migrating to another domain.
Group members (new and existing)
To stop all members in the current group from migrating to another domain.