Export (0) Print
Expand All

Create a migration table

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To create a migration table

  1. Open Group Policy Management.

  2. In the console tree, double click the forest from which you want to create a migration table.

  3. Right-click Domains and then click Open Migration Table Editor

    - or -

    Right-click Group Policy Objects, and then click Open Migration Table Editor.

  4. Specify a source you want to include in the migration table by doing the following:

    1. Under Source Name, type the source name or right-click the cell and click Browse to find and then specify the object type, location and name.

      If you enter the source name manually, you must type the exact name of the User, Computer, Group or UNC Path referenced in the source GPO. For example, TestDomain\PolicyAdmins or \\server1\publicshare. The type of the source name must match the source type specified in the migration table.

      Security principals can be specified using any of the following formats:

      UPN. For example, someone@testdomain.com.

      SAM. For example, testdomain\someone.

      DNS. For example, testdomain.com\someone.

      Free text. For example, someone. You must specify the type as Free Text or SID in this case.

      SID. For example, S-1-11-111111111-111111111-1111111111-1112. You must specify the type as Free Text or SID in this case.

    2. Under Source Type specify the type of source in the cell adjacent to the source name cell by using the drop down list and selecting the appropriate type. If you have used Browse to find the source name, the source type is entered by default.

    3. Under Destination Name, type the destination name or right-click the cell adjacent to the source name and source type cells, and then do one of the following:

      Click Browse to find a user, computer or group

      - or -

      Point to Set Destination, and then click the appropriate selection. You cannot use the No Destination option for UNC paths.

  5. Repeat step 4 for each source you want to include in the migration table.

  6. On the menu, click File, and then click Save.

  7. Specify the location where you want to save the migration table, and then click Save.

Notes

  • You can use the migration table editor to check that destination entries can be resolved. This is important to know before you copy or import a GPO, because if there are unresolvable destination entries in the migration table, then the copy or import operation might fail. To validate your migration table, from the Tools menu, click Validate.

  • You can auto-populate a migration table by scanning one or more GPOs or backup GPOs to extract all references to security principals and UNC paths, and automatically enter these items into the table as source name entries.

    To auto-populate a migration table from a GPO:

    1. From the Tools menu, click Auto-populate from GPO.

    2. In the Look in this domain box, select the domain that contains the GPO.

    3. In the Group Policy objects box, click the GPO or GPOs from which you want to populate the migration table, check Include security principals from the DACL on the GPO during scan if appropriate, and then click OK.

    To auto-populate a migration table from a backup GPO:

    1. From the Tools menu, click Auto-populate from Backup.

    2. In the Backup location box, type the path to the folder that contains the backup GPO, or click Browse to locate the folder.

    3. In the Backed up GPOs box, select one or more backed up GPOs, check Show only the latest version of each GPO or Include security principals from the DACL on the GPO during scan if appropriate, and then click OK.

    To complete the migration table for either scenario, you only need to adjust the destination values. By default, the destination name for each entry will be set to Same as source when you use either of the Populate options.

  • Performing this task does not require you to have administrative credentials.

  • You can also perform this procedure or a related task by using one or more of the sample scripts included with Group Policy Management. For more information, see "Scripting Group Policy tasks" in Related Topics.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft