Assigning Object Locations and Roles

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

Assign your migration objects locations and roles in the target domain. It is useful to create object assignment tables in which to document the assignments for all of the objects that you are migrating. Create one table for account objects, such as users, groups, and service accounts, and one table for resource objects, such as workstations, profiles, and domain controllers. In your tables, list the source and target locations for all objects to be migrated.

Before you create your account object assignment table, determine whether the domain organizational unit (OU) structures for the source and target domains are the same. If the OU structures are not the same, you must identify the source and target OU in your object assignment tables.

For a worksheet to assist you in creating an account object assignment table, see "User and Group Object Assignment Table" (DSSREER_1.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "User and Group Object Assignment Table" on the Web at https://www.microsoft.com/reskit).

Figure 11.4 shows an example of an object assignment table for users and groups.

Figure 11.4   Example of a User and Group Object Assignment Table

Creating a resource object assignment table also involves identifying the source and target OU for each object and noting the physical location and role in the target domain. For a worksheet to assist you in creating a resource object assignment table, see "Resource Object Assignment Table" (DSSREER_2.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Resource Object Assignment Table" on the Web at https://www.microsoft.com/reskit).

Figure 11.5 shows an example of a resource object assignment table.

Figure 11.5   Example of a Resource Object Assignment Table