1 C H A P T E R 1 2 Restructuring Active Directory Domains Within a Forest Restructuring Active Directory directory service domains within a forest with the goal of reducing the number of domains allows you to decrease the administrative overhead for your organization by reducing replication traffic, reducing the amount of user and group administration that is required, and simplifying the administration of Group Policy. If users change positions or move between locations, you might also move objects between forests on a regular basis. The process for restructuring Active Directory domains within a forest differs from the process of restructuring Active Directory domains between forests and requires careful planning and testing. In This Chapter Overview of Restructuring Active Directory Domains Within a Forest Preparing to Restructure Active Directory Domains Within a Forest Migrating Domain Objects Between Active Directory Domains Completing Post-Migration Tasks Additional Resources Related Information u For more information about designing the Active Directory logical structure, see Designing the Active Directory Logical Structure in this book. u For more information about designing the Active Directory site topology, see Designing the Site Topology in this book. u For more information about creating an Active Directory forest, see Deploying the Windows Server 2003 Forest Root Domain in this book.
2 574 Chapter 12 Restructuring Active Directory Domains Within a Forest Overview of Restructuring Active Directory Domains Within a Forest The most efficient Active Directory design includes the smallest possible number of domains. By minimizing the number of domains running the Microsoft Windows Server 2003, Standard Edition; Microsoft Windows Server 2003, Enterprise Edition; and Microsoft Windows Server 2003, Datacenter Edition operating systems, you can reduce administrative costs and increase the efficiency of your organization. You might need to restructure domains within your forest if, for example, your organization closes a regional office location, and the regional domain for that location is no longer needed. You might also restructure domains within your forest if you upgrade your network infrastructure, thereby increasing your bandwidth capacity and your replication capacity and enabling you to reduce the size of your Active Directory logical structure. The process of restructuring Active Directory domains within a forest is similar to the process of migrating accounts between domains. When you migrate accounts and resources between domains, you migrate objects from the source domain to the target domain without decommissioning the source domain. When you restructure Active Directory domains, you eliminate the source domain from the forest after you complete the migration of all domain objects. Before you begin the process for restructuring Active Directory domains within a forest, ensure that the source and target domains are operating at the Microsoft Windows 2000 native or Windows Server 2003 domain functional level. Restructuring source domains that are operating at the Windows 2000 mixed domain functional level, which can include domain controllers that are running Microsoft Windows NT 4.0, is not recommended. After you complete the process for restructuring Active Directory domains within a forest, you can reduce overhead and simplify administration in your organization. Note For a list of the job aids that are available to assist you in restructuring Active Directory domains within a forest, see Additional Resources later in this chapter.
3 Overview of Restructuring Active Directory Domains Within a Forest 575 Process for Restructuring Active Directory Domains Within a Forest Restructuring Active Directory domains within a forest requires careful planning and preparation. To maintain user access to resources during the process of restructuring domains, you must perform the migration steps in a specific order. Figure 12.1 shows the process for restructuring Active Directory domains within a forest. Figure 12.1 Restructuring Active Directory Domains Within a Forest Prepare to restructure Active Directory domains within a forest Migrate domain objects between Active Directory domains Complete postmigration tasks Background Information for Restructuring Active Directory Domains Within a Forest Restructuring Active Directory domains within a forest involves migrating accounts and resources from the source domains to the target domains. Unlike the process for restructuring Active Directory domains between forests, when you restructure domains within a forest, the migrated objects no longer exist in the source domain. Additionally, migrating user accounts, resources, and groups requires special consideration when you restructure Active Directory domains within a forest because of the containment rules that apply to Active Directory groups. For these reasons, the challenge when you restructure Active Directory domains within a forest is to ensure that users have continuous access to resources during the migration process.
4 576 Chapter 12 Restructuring Active Directory Domains Within a Forest Active Directory Migration Tool The Active Directory Migration Tool (ADMT) version 2 allows you to migrate objects within Active Directory forests. ADMT includes wizards that automate migration tasks such as migrating users, groups, service accounts, computers, and trusts, and performing security translation. ADMT is available in the Admigration.msi file in the \i386\admt directory on the Windows Server 2003 operating system CD. You can perform ADMT tasks by using the ADMT console, a command line, or a script. When running ADMT at the command line, it is often more efficient to use an option file to specify command-line options. You can use the ADMT option file reference shown in Listing 12.1 to assist you in creating option files. Examples of command-line syntax are provided for each task that you must perform to restructure the domains within the forest. Listing 12.1 lists common options that apply to several migration tasks. Each type of migration task has a section that lists options that are specific to that task. The section name corresponds to the task name when you run ADMT at the command line. Items can be commented out with a semi-colon. In Listing 12.1, the default values are commented out. When running ADMT at the command line, you do not need to include an option in your command if you want to accept the default value. In this chapter, however, tables are provided for reference. The tables list the command-line equivalent of each option that is shown in the corresponding ADMT console procedure, including those where you are accepting the default value. Listing 12.1 ADMT Option File Reference [Migration] ;TestMigration=No ;IntraForest=No SourceDomain="source_domain_name" ;SourceOu="source_ou_path" TargetDomain="target_domain_name" TargetOu="target_ou_path" ;RenameOption=Dont ;RenamePrefixOrSuffix="" ;PasswordOption=Complex ;PasswordServer="" ;PasswordFile="" ;ConflictOptions=Ignore ;ConflictPrefixOrSuffix="" ;UserPropertiesToExclude="" ;InetOrgPersonPropertiesToExclude="" ;GroupPropertiesToExclude="" ;ComputerPropertiesToExclude="" (continued)
5 Overview of Restructuring Active Directory Domains Within a Forest 577 Listing 12.1 ADMT Option File Reference (continued) [User] ;DisableOption=EnableTarget ;SourceExpiration=None MigrateSIDs=Yes ;TranslateRoamingProfile=No ;UpdateUserRights=No ;MigrateGroups=No ;UpdatePreviouslyMigratedObjects=No ;FixGroupMembership=Yes ;MigrateServiceAccounts=No ;UpdateGroupRights=No [Group] MigrateSIDs=Yes ;UpdatePreviouslyMigratedObjects=No ;FixGroupMembership=Yes ;UpdateGroupRights=No ;MigrateMembers=No ;DisableOption=EnableTarget ;SourceExpiration=None ;TranslateRoamingProfile=No ;MigrateServiceAccounts=No [Security] TranslationOption=Add ;TranslateFilesAndFolders=No ;TranslateLocalGroups=No ;TranslatePrinters=No ;TranslateRegistry=No ;TranslateShares=No ;TranslateUserProfiles=No ;TranslateUserRights=No ;SidMappingFile="SidMappingFile.txt" For a file that includes common options that are available for ADMT, see ADMT Option File Reference (DSSRENT_3.txt) on the Microsoft Windows Server 2003 Deployment Kit companion CD (or see ADMT Option File Reference on the Web at
6 578 Chapter 12 Restructuring Active Directory Domains Within a Forest When running ADMT from the command line, it is often more efficient to use an include file to list the users, groups, or computers that will be migrated. For example, to migrate a small number of computers, you might type each computer name at the command line, using the /N option as follows: ADMT COMPUTER /N computer_name1 computer_name2 /IF:YES /SD: source_domain /TD: target_domain /TO: target_ou Computer_name1 and computer_name2 are the names of computers in the source domain that you are migrating in this batch. If you have a large number of users, groups, or computers to migrate, you can list them in an include file. For example, to create an include file for a batch of computers, create a plain text file and list the computer names, each name on a separate line. Then specify the include file name with the /F option, as follows: ADMT COMPUTER /F includefile_name /IF:YES /SD: source_domain /TD: target_domain /TO: target_ou ADMT supports the use of American National Standards Institute (ANSI) or standard Unicode files for option files and include files. To specify the names of users, groups, or computers, use one of the following conventions: u u u u The Security Accounts Manager (SAM) account name. Note that to specify a computer name in this format, you must append a $ to the computer name. For example, to specify a computer with the name Workstation01, use Workstation01$. The Windows NT 4.0 account name. This includes the domain name and the SAM account name. For example, the Windows NT 4.0 account name of a computer named Workstation01 that is in the Asia domain is Asia\ Workstation01$. The relative distinguished name (also known as RDN). For example, cn= Workstation01. The canonical name. This can be specified as DNS domain name/ou_path/object_name, or ou_path/object_name; for example, Asia.trccorp.treyresearch.net/Computers/ Workstation01 or Computers/Workstation01. For a complete list of all available ADMT options and syntax, run ADMT, and then select Help on the menu. The sample scripts provided in this chapter reference the symbolic constants that are defined in the AdmtConstants.vbs file. Listing 12.2 shows the ADMT constants VBScript file.
8 580 Chapter 12 Restructuring Active Directory Domains Within a Forest Listing 12.2 ADMT Scripting Constants (continued) Report Type Const admtreportmigratedcomputers = 1 Const admtreportexpiredcomputers = 2 Const admtreportaccountreferences = 3 Const admtreportnameconflicts = 4 Const admtnone = 0 Const admtdata = 1 Const admtfile = 2 Const admtdomain = 3 Const admtrecurse = &H0100 Const admtflattenhierarchy = &H0000 Const admtmaintainhierarchy = &H0200 For a script file that includes the constants that are available for ADMT scripts, see ADMT Scripting Constants (AdmtConstants.vbs) on the Windows Server 2003 Deployment Kit companion CD (or see ADMT Scripting Constants on the Web at The constants are also provided on the Windows Server 2003 operating system CD, in the TemplateScript.vbs file in the \i386\admt directory. Closed Sets and Open Sets When you restructure Active Directory domains within a forest, you must be concerned with two types of closed sets. The first type is users and groups, and the second type is resources and local groups. The first type of closed set includes user accounts, all the global groups to which the users belong, and all the other members of the global groups. Because global groups are limited to members of the domain where the global group exists, if you migrate a user account to a new domain but do not migrate the global groups to which the user belongs, the user is no longer a valid member of those global groups and cannot access resources that are based on membership in those global groups. Therefore, when you are moving accounts between domains in a forest, it is necessary to move closed sets so that users retain access to their resources.
9 Overview of Restructuring Active Directory Domains Within a Forest 581 Built-in accounts (such as Administrators, Users, and Power Users) and well-known accounts (such as Domain Admins and Domain Users) cannot be ADMT migration objects. However, migrating these groups in closed sets is not a common problem because using them in access control lists (ACLs) or membership in domain local groups is not an effective way to assign resource permissions. When you migrate users, ADMT makes the user a member of the domain users group in the target domain but does not maintain permissions for other built-in groups, such as Server Operators, Backup Operators, or well-known groups, such as Domain Admins. If you have used built-in or well-known groups to assign resource permissions, you must reassign those permissions to a new domain local group before you begin the migration. Reassigning permissions includes the following steps: 1. Create a new domain local group in the source domain. 2. Create a new global group in the source domain that contains users who need access to the resource. 3. Add the new global group to the domain local group. 4. Run security translation by using a SIDmapping file that maps the well-known group to the new domain local group (created in the first step) on all resources that assign permissions using well-known groups. For information about performing a security translation by using a SIDmapping file, see Translate Security by Using a SIDmapping File later in this chapter. In small domain environments that have few global groups, you might be able to identify closed sets of users and groups. If you can identify closed sets, you can migrate users and groups at the same time. In a large domain environment, a user can belong to a number of global groups; therefore, it is difficult to identify and migrate only closed sets of users and groups. For this reason, it is best to migrate groups before you migrate user accounts. For example, User 1 belongs to global groups Global A and Global B and is a member of Domain 1. If an administrator moves User 1 and Global A to Domain 2, these accounts no longer exist in Domain 1; they exist only in Domain 2. Global B group remains in Domain 1. This creates an open set, or a set that includes users and groups in more than one domain. Because global groups can only contain members from the domain where the global group exists, the membership of User 1 in Global B is no longer valid, and User 1 can no longer access resources based on membership in Global B. Therefore, it is best to migrate both global groups before you migrate User 1.
10 582 Chapter 12 Restructuring Active Directory Domains Within a Forest If you are migrating an open set of objects in an environment where the functional level for both the source domain and the target domain is Windows 2000 native or higher, ADMT transforms the global group into a universal group so that it can contain users from other domains and retain the group membership. When the set becomes a closed set, ADMT changes the group back to a global group. The benefit of this process is that ADMT ensures that all closed set problems are resolved. However, replication of the global catalog is affected while the groups are universal groups because membership is copied to the global catalog. Note If the functional level of the source domain is Windows 2000 mixed, ADMT cannot transform the global group into a universal group because universal groups cannot exist at that functional level. Even if the target domain is in native mode, however, users in mixed mode domains would not get the SIDs of universal groups in their access tokens, if the groups are from outside the domain. Therefore, ADMT creates a copy of the global group in the target domain and adds all migrated users to the copy of that group. This group has a new security identifier (SID) and no SID history. This method does not preserve access to resources unless you run the ADMT Security Translation Wizard in Add mode to update permissions, which delays and complicates the migration process. For this reason, it is not recommended that you restructure domains that are operating at the Windows 2000 mixed functional level or the Windows Server 2003 interim domain functional level. The second type of closed set is resources and local groups. In most cases, resources have permissions assigned to computer local groups or domain local groups. Because computer local groups are migrated when you migrate the computer, these groups are a natural closed set. However, domain local groups can be used on multiple computers to assign permissions. In this case, you can either migrate all the computers that use the domain local group at the same time the domain local group is migrated to the target domain, or you can manually change the domain local group to a universal group and then migrate the universal group. Changing the domain local group to a universal group is a manual process because ADMT does not automatically perform this task. Although this change can affect the size of your global catalog, over a limited time period, it is an effective way to migrate resources and domain local groups as a closed set. SID History SID history enables you to maintain user access to resources during the process of restructuring Active Directory domains. When you migrate an object to another domain, the object is assigned a new SID. Because you assign permissions to objects based on SIDs, when the SID changes, the user loses access to that resource until you can reassign permissions. When you use ADMT to migrate objects between domains, the SID history is automatically retained. In this way, the SID from the source domain remains as an attribute of the object after the object is migrated to the target domain.
11 Preparing to Restructure Active Directory Domains Within a Forest 583 For example, an organization that is restructuring its Active Directory domains moves universal and global groups from a source domain to the target domain before moving user accounts. Because this is a migration within a forest and the functional level of the source domain is Windows 2000 native, these groups cease to exist in the source domain and exist only in the target domain. Because the SID history of both users and groups is migrated, the users continue to have access to resources in the source domain based on their membership in a group that exists in the target domain. Resource Assignment to Groups The most effective way to assign permissions to resources is to assign users to global groups, place global groups within domain local groups, and then assign permissions to the domain local groups. Assigning permissions to resources in this way simplifies the migration process. Terms and Definitions The following terms apply to the process for restructuring Active Directory domains within a forest. Migration The process of moving an object from a source domain to a target domain, while preserving or modifying characteristics of the object to make it accessible in the new domain. Domain Restructure A migration process that involves changing the domain structure of a forest. A domain restructure can involve either consolidating or adding domains, and can take place between forests or within a forest. Domain Consolidation A restructuring process that involves eliminating Windows NT 4.0 or Active Directory domains by merging their contents with that of other domains. Preparing to Restructure Active Directory Domains Within a Forest Careful planning is an important part of restructuring Active Directory domains. Completing the necessary preparatory tasks before you restructure Active Directory domains enables you to reduce the effect on users of migrating objects from source to target domains. To prepare for the restructuring process, the Active Directory deployment team must obtain the necessary design information from the Active Directory design team.
12 584 Chapter 12 Restructuring Active Directory Domains Within a Forest Figure 12.2 shows the steps that are involved in preparing to restructure Active Directory domains within a forest. Figure 12.2 Preparing to Restructure Active Directory Domains Within a Forest Prepare to restructure Active Directory domains within a forest Migrate domain objects between Active Directory domains Design the new Active Directory forest structure Assign domain object roles and locations Plan for group migration Complete postmigration tasks Plan for service account transitioning Plan for test migrations Create a rollback plan Create an end-user communication plan Create migration account groups Install ADMT
13 Preparing to Restructure Active Directory Domains Within a Forest 585 Design the New Active Directory Forest Structure Evaluate the domain structure of your existing Active Directory forest, and then identify the domains that you want to restructure by consolidating them with other domains. To design your new Active Directory forest structure, you must identify the source domain that you will migrate objects from and the target domains where you will place those objects. You must also evaluate the structure of the target domain. Identify the Target and Source Domains The source domain or domains are the domains that you want to migrate objects from and that you plan to decommission. When you restructure Active Directory domains, it is best to migrate the smallest possible number of objects. When you select source domains, identify the domains that have the fewest objects to migrate. Evaluate the OU Structure of the Target Domain Identify the organizational units (OUs) from the source domain that you need in the target domain, and then determine whether you need to create new OUs in the target domain. You can migrate the OU structure when you migrate users, groups, or computers if you are using ADMT in command-line or scripting mode. The OUs are always copied between the domains and are not deleted in the source domain. To successfully migrate an OU, a source OU and a target OU must be specified in ADMT and the target OU must exist. All objects in the source OU and all sub-ous are migrated. The specified source OU itself is not migrated. The migrated objects and sub-ous are migrated to the target OU. For more information about creating an OU structure, see Designing the Active Directory Logical Structure in this book. Assign Domain Object Roles and Locations Use a domain object assignment table to document object roles and locations. In the domain object assignment table, include the domain objects that exist in the source domain and their planned roles and locations in the target domain. For a worksheet to assist you in creating a domain object assignment table, see Domain Object Assignment Table (DSSRERA_1.doc) on the Windows Server 2003 Deployment Kit companion CD (or see Domain Object Assignment Table on the Web at
14 586 Chapter 12 Restructuring Active Directory Domains Within a Forest For example, Contoso Corporation plans to migrate their Africa domain objects to their EMEA domain. The design team creates a domain object assignment table that includes every group, user, and computer that needs to be migrated from the Africa domain to the EMEA domain. The completed table permits the organization to assess the amount of work and time that is required to complete the migration of the Africa domain. Figure 12.3 shows the domain object assignment table that the Contoso design team created. Figure 12.3 Example of a Domain Object Assignment Table
15 Preparing to Restructure Active Directory Domains Within a Forest 587 Plan for Group Migration Unless you can identify closed sets when you are restructuring Active Directory domains within a forest, it is recommended that you migrate groups and users separately to ensure that users continue to have access to required resources. Table 12.1 lists each type of group and where the group is physically located. Table 12.1 Location of Each Group Type Group Type Global Group Universal Group Domain Local Group Active Directory Active Directory Active Directory Location Computer Local Group Database of the local computer Each type of group is migrated differently based on the group s physical location and its rules for group membership. Global, universal, and domain local groups are migrated by using ADMT and can be transformed into universal groups for the duration of the migration if you are not migrating closed sets. You can update computer local group membership by running security translation. Each group type has different rules for membership and serves a different purpose. This affects the order that the groups are migrated from the source to the target domains. Table 12.2 summarizes the groups and their membership rules. Table 12.2 Groups and Membership Rules Type of Group Universal groups Global groups Domain local groups Rules and Membership Universal groups can contain members from any domain in the forest and replicate group membership to the global catalog. For this reason, they can be used for administrative groups. When you restructure domains, migrate universal groups first. Global groups can include only members from the domain to which they belong. ADMT automatically changes the global group in the source domain to a universal group when it is migrated to the target domain if the functional level of both domains is Windows 2000 native or higher. ADMT automatically changes universal groups back to global groups after all members of the group are migrated to the target domain. Domain local groups can contain users from any domain. They are used to assign permissions to resources. When you restructure domains, you must migrate domain local groups when you migrate the resources to which they provide access, or you must change the group type to universal group. This minimizes the disruption in user access to resources.
16 588 Chapter 12 Restructuring Active Directory Domains Within a Forest Plan for Service Account Transitioning Most services run within the context of the Local System account and because of this, they do not need any maintenance when they are migrated to a different domain. Some services, however, run in the context of a user account instead of the Local System account. Service account transitioning refers to the process of identifying, migrating, and updating services that run in the context of user accounts. This process has three steps. First, start ADMT on a Windows Server 2003 based member server in the target domain, and then run the Service Account Migration Wizard. The Service Account Migration Wizard sends an agent to a computer that you specify in the wizard and identifies all services on the computer that are running in the context of a user account. The wizard only identifies service accounts that are running in the context of a user account and saves the information in the ADMT database; it does not actually migrate the accounts. The next step, which can occur later in the transition process, is to migrate the accounts by using the User Account Migration Wizard when you migrate the other user accounts. For information about installing and initializing ADMT, see Install ADMT later in this chapter. The Service Account Migration Wizard checks every service on a computer to identify services that run in the context of a user account. It is possible to create a security hole during the migration of service accounts if someone who is not a service administrator enters an account with administrative permissions in the source domain but uses an invalid password on their computer to start the service. The service will not start before the account migration, because the password is not correct, but it will work after migration because ADMT resets the password of the service account and configures all services that are using that service account with the new password. To eliminate this possible security problem, it is important to include in the Service Account Migration Wizard only those servers that are managed by trusted administrators. Do not use the Service Account Migration Wizard to detect service accounts on computers that are not managed by trusted administrators, such as workstations. If you do not identify and transition a trusted computer that therefore does not get its service account updated, you will need to manually set the new password created by ADMT. To do this, obtain the password from the Password.txt file, and then manually enter that account and password information for the service on the computer that did not get transitioned. When the accounts that the Service Account Migration Wizard identifies in the ADMT database as running in the context of a user account are migrated to the target domain, ADMT grants each account the right to log on as a service.
17 Preparing to Restructure Active Directory Domains Within a Forest 589 To run the Service Account Migration Wizard 1. In ADMT, start the Service Account Migration Wizard. 2. Complete the wizard by using the information in Table Table 12.3 Using the Service Account Migration Wizard Wizard Page Domain Selection Update Information Service Account Selection Service Account Information Action In the Source domain box, type or select the NetBIOS or DNS name of the source domain. In the Target domain box, type or select the NetBIOS or DNS name of the target domain. Click Yes, update the information. Click Add. In the Select Computers list box, select all servers that have service accounts. Click OK, and then click Next. Select any user accounts that do not need to be marked as service accounts in the ADMT database, and then click Skip/Include to mark the accounts as Skip. The wizard connects to the selected computers, and then sends an agent to check every service on the remote computers. The Service Account Information page lists the services that are running in the context of a user account and the name of that user account. ADMT notes in its database that these user accounts need to be migrated as service accounts. If you do not want a user account to be migrated as a service account, select the account, and then click Skip/Include to change the status from Include to Skip. You use Update SCM to update the Service Control Manager with the new information. Unless you have a failure in reaching a computer to update the service, the Update SCM button is not available. If you have a problem updating a service account after the account was identified and migrated, ensure that the computer that you are trying to reach is available, and then restart the Service Account Migration Wizard. In the wizard, click Update SCM to try to update the service. If you ran the Service Account Migration Wizard previously and the Update SCM button is not available, examine the ADMT log files to determine the cause of the problem. After you correct the problem and the agent can connect successfully, the Update SCM button becomes available.
18 590 Chapter 12 Restructuring Active Directory Domains Within a Forest Plan for Test Migrations You can create a pilot for the migration process by migrating users and the global groups of which they are members to the target domain. However, unless you are migrating a closed set of users and groups in your pilot, the global groups will become universal groups and replicate their membership to the global catalog for the duration of the migration process. Use a test lab that simulates your production environment to test your migration process and to resolve any issues before you begin to restructure your Active Directory domains. Continue to test your migration process until you correct as many errors as possible. Make sure that you test user access to resources after each step of the migration. If users do not have access to resources during the migration process, the migration is not successful. For more information about setting up a pilot to test migration, see Restructuring Windows NT 4.0 Domains to an Active Directory Forest in this book. Create a Rollback Plan After you begin the migration process, you cannot roll back the changes that you make to the Active Directory domains in your forest. Because accounts are moved and not copied from one domain to another when you restructure domains, the changes are not reversible. If your plans change after you begin the migration process, the only way to return your source domain is to remigrate the accounts. Create a rollback plan in case you need to remigrate accounts after you have begun to restructure your domains. To create a rollback plan, select the method that you will use to remigrate accounts. You can use the ADMT wizards to remigrate accounts from the target domain back to the source domain. In this case, the original target domain becomes the new source domain, and the original source domain becomes the new target domain. Follow the same steps in the wizards that you used earlier to migrate the accounts. If you remigrate the accounts, the objects that have been migrated to the target domain and then remigrated to the source domain will have new SIDs. However, they will have the original SID in their SID history so they will not be identical to the accounts before the migration, but they will have the same functionality. Another option for remigrating accounts is to use the Undo Wizard in ADMT. The Undo Wizard uses fewer steps than the other ADMT wizards to remigrate accounts back to their original domain. However, the Undo Wizard only remigrates accounts that were originally migrated by using the User Account Migration Wizard, the Group Account Migration Wizard, and the Computer Account Migration Wizard. It does not undo changes that were made by the Service Account Migration Wizard or the Security Translation Wizard. The Undo Wizard only reverses the last operation that was performed.
19 Preparing to Restructure Active Directory Domains Within a Forest 591 If you want to reverse a service account migration, you must enumerate the services again, and then remigrate the service accounts by reversing the target and source domains. If you use scripts to perform the original migration, using scripts to remigrate accounts is the fastest method to roll back the changes. Simply reverse the objects used for the source and target domains in the script to remigrate the objects. Note If the functional level of the original source domain is Windows 2000 mixed, you cannot use a rollback method to undo the changes and migrate the accounts back to the source domain. A remigration requires that the original source domain becomes the target domain, and the functional level of the target domain must be Windows 2000 native or Windows Server For this reason, it is not recommended that you restructure domains that are operating at the Windows 2000 mixed functional level or the Windows Server 2003 interim domain functional level. After you create your rollback plan, make sure to test it to identify and correct any problems before you begin to restructure your Active Directory domains. Create an End-User Communication Plan Develop a plan to inform all affected users about the upcoming account migration, to ensure that they understand their responsibilities, the impact of the migration, and who to contact for help and support. Before you begin the user migration process, send a notice to all users who are scheduled to be migrated. Because you typically migrate users in batches of approximately one hundred users at a time, it is also helpful to send a final notice to the users in each batch 2-3 days before their batch is scheduled. If your organization maintains an intranet, publish the account migration schedule and the information contained in the user mail on an easily accessible Web page. Include the following information in your end-user communication. General information Alert users to the fact that their user accounts are scheduled to be migrated to a new domain. Point users to a Web page or internal resource where they can find additional information, and view a migration schedule. Inform users of their new domain name. Be sure to let them know that their account passwords will not change. Let them know that the original domain account will be disabled immediately following the migration, and the disabled account will be deleted after a specified period of time. This is not needed if users use User Principal Names (UPNs) to log on.
20 592 Chapter 12 Restructuring Active Directory Domains Within a Forest Impact Make sure that users understand that when their account is migrated, it is possible that they could be unable to access some resources, such as Web sites, shared folders, or resources that are not widely used by individuals in their group or division. Provide information to users about who to contact for assistance in regaining access to required resources. Logon status during migration Make sure that users understand that during the migration process, they will be unable to log on to the domain or access or other resources. Be sure to specify the period of time for which they will be unable to log on. Premigration steps Alert users to any steps that they need to complete before the migration process begins. For example, they must decrypt files encrypted by means of Encrypted File System (EFS). Failure to decrypt encrypted files will result in loss of access to encrypted files following the migration. Expected changes Describe other changes that users can expect to experience following the migration, such as changes in use of smart cards, secure mail, or instant messaging if applicable. Scheduling and support information Provide information about where users can go to find more information; for example, an internal Web site where you post information about the migration. Also, provide information about who to contact if a user has a conflict with the date scheduled for the migration. Create Migration Account Groups To migrate accounts and resources within a forest, you must establish an account migration group and a resource migration group with the appropriate credentials. You must then add the accounts that will be performing the ADMT migrations to the account migration and resource migration groups, as appropriate. Because ADMT requires only a limited set of permissions, creating separate migration groups allows you to simplify administration by creating the groups, assigning the appropriate permissions, and then adding the necessary administrators to those groups. If the migration tasks for your organization are distributed across more than one administrative group, create separate migration groups for each administrative group that performs the migration.
21 Preparing to Restructure Active Directory Domains Within a Forest 593 To simplify administration, create a single migration group in the source domain and a single migration group in the target domain for all objects. Assign the required permissions to modify objects such as users, global groups, and local profiles according to Table The user who is running ADMT must be an administrator on the computer where ADMT is installed. In the target domain, use a group with delegated control of the computer OU and the user OU. You might want to use a separate group for the migration of workstations if this migration process is delegated to administrators who are in the same location as the workstations. Use the information in Table 12.4 to determine the credentials that are required for your migration. Table 12.4 Migration Account Group Credentials Migration Object User/Group Computer Profile (needed for Windows NT 4.0 computers only) Credentials Necessary in Source Domain Local administrator or domain administrator, or delegated rights to delete the objects in the source OU Domain administrator or delegated rights to delete the objects in the source OU and member of Administrators group on each computer Local administrator or domain administrator Credentials Necessary in Target Domain Delegated control of the user OU or the group OU and local administrator on the computer where ADMT is installed Delegated control on the computer OU and local administrator on the computer where ADMT is installed Delegated control on the computer OU and local administrator on the computer where ADMT is installed Install ADMT If you have not installed and initialized ADMT in your environment, you must install and run ADMT on a member server or domain controller in the target domain or the source domain. To install ADMT in the target domain or the source domain 1. Log on to a member server or domain controller in the domain by using your ADMT migration account. 2. Insert the Windows Server 2003 CD into the CD-ROM drive, and then locate the \i386\admt folder. 3. Double-click admigration.msi. Initialize ADMT by running a test migration of your global groups.
22 594 Chapter 12 Restructuring Active Directory Domains Within a Forest To initialize ADMT by running a test migration of a global group 1. In the ADMT console, select the Group Account Migration Wizard. 2. Complete the Group Account Migration Wizard by using the information provided in Table Accept default settings if no information is specified. Table 12.5 Migrating Global Groups by Using the Group Account Migration Wizard Wizard Page Test or Make Changes Domain Selection Group Selection Organizational Unit Selection Group Options Naming Conflicts Action Click Test the migration settings and migrate later? In the Source domain box, type the source domain name. In the Target domain box, type the target domain name. Click Add. In the Select Groups dialog box, select a group. Click Browse. In the Browse for Container dialog box, locate the target OU. Click Do not rename accounts. Click Ignore conflicting accounts and don t migrate. 3. After the wizard runs, click View Log, and then review the migration log for any errors. Example: Preparing to Restructure Active Directory Domains Contoso Corporation upgraded its hardware to increase its network bandwidth and the amount of replication traffic that it can support. As a result, the company is consolidating the Africa domain into the EMEA domain. The Africa domain is the source domain and the EMEA domain is the target domain for the migration. The organization needs to migrate a total of 1,800 users from the Africa domain to the EMEA domain. In addition to the user accounts, they must also migrate resources such as workstations, servers, and groups. Because Contoso Corporation is a large organization with many global groups, closed sets are difficult to identify, so the company decided to migrate global groups as universal groups. They can do this because the infrastructure of the corporation can handle the increased replication of the universal groups and because both the Africa and EMEA domains are operating at the Windows 2000 native functional level. The company created identical OU structures in the Africa and EMEA domains; therefore, they do not need to create a new OU structure or migrate OUs. Contoso Corporation created a list of computers that run service accounts, so that it can use the Service Account Migration Wizard to identify services that run in the context of user accounts. The company is most concerned about a set of accounts that access a Microsoft SQL Server database. Access to this database is an important part of their business.
23 Migrating Domain Objects Between Active Directory Domains 595 The company decides to use ADMT as its migration tool and to use the wizards. The company installs ADMT and creates two account migration groups to use for the migration process. They assign high-level permissions to the first group, and then add the appropriate deployment team members to that group. The centralized deployment team will use this account to migrate users. They assign workstation and local resource permissions to the second group. The deployment team will use the second group to migrate resources at the remote locations. Migrating Domain Objects Between Active Directory Domains Restructuring Active Directory domains within a forest involves migrating domain objects in a specific order to ensure that users maintain access to resources. Figure 12.4 shows the process for migrating domain objects between Active Directory domains. Figure 12.4 Migrating Domain Objects Between Active Directory Domains Prepare to restructure Active Directory domains within a forest Migrate domain objects between Active Directory domains Complete postmigration tasks Migrate groups Migrate service accounts Migrate user accounts Translate local user profiles Migrate workstations and member servers Migrate domain local groups
24 596 Chapter 12 Restructuring Active Directory Domains Within a Forest Migrate Groups To protect your system against the problem of open sets when you restructure Active Directory domains within a forest, migrate groups before you migrate the user accounts that are members of those groups. If you only migrate groups when you migrate users, you might not migrate nested groups, thereby creating an open set. Migrate universal groups first, followed by global groups. Migrate domain local groups when you migrate the resources (domain controllers and member servers) on which they are used to assign permissions. Computer local groups migrate with the computer. Migrate Universal Groups Migrate universal groups, without migrating users who are members of these groups at the same time, from the source domain to the target domain. Migrating universal groups without the users helps to protect against the problem of open sets. SID history allows group members to continue to have access to resources based on universal group membership. When you migrate universal groups to the target domain, they cease to exist in the source domain. You can migrate universal groups by using the Group Account Migration Wizard or by using a script. To migrate universal groups without members u Note If you are migrating a small number of universal groups, you can migrate universal groups at the same time that you migrate global groups. Complete the Group Account Migration Wizard by using the information provided in Table Table 12.6 Using the Group Account Migration Wizard to Migrate Universal Groups Wizard Page Action Test or Make Changes Domain Selection Click Migrate Now? In the Source domain box, type the NetBIOS or DNS name of the source domain or select the name from a list. In the Target domain box, type the NetBIOS or DNS name of the target domain. If ADMT includes the names of the source and target domains, ensure that they are correct. (continued)
25 Migrating Domain Objects Between Active Directory Domains 597 Table 12.6 Using the Group Account Migration Wizard to Migrate Universal Groups (continued) Wizard Page Group Selection Organizational Unit Selection Group Options Naming Conflicts Action Click Add. In the Select Groups dialog box, select all universal groups that you want to migrate, click Add, and then click OK. Type the name of the OU, or click Browse. In the Browse for Container dialog box, find the container in the target domain that you want to move the universal groups into, and then click OK. The Migrate Group SIDs to target domain and Fix Group Membership check boxes are checked and appear dimmed. Click Do not rename accounts. Ensure that no other options are selected. Click Ignore conflicting accounts and don t migrate. To migrate universal groups by using a script u Use Listing 12.3 to prepare a script that incorporates ADMT commands and options for migrating groups within a forest. Listing 12.3 Migrating Groups Within a Forest <Job id="migratinggroupswithinforest"> <Script language="vbscript" src="admtconstants.vbs"/> <Script language="vbscript"> Option Explicit Dim objmigration Dim objgroupmigration Create instance of ADMT migration objects. Set objmigration = CreateObject("ADMT.Migration") Set objgroupmigration = objmigration.creategroupmigration Specify general migration options. (continued)
26 598 Chapter 12 Restructuring Active Directory Domains Within a Forest Listing 12.3 Migrating Groups Within a Forest (continued) objmigration.intraforest = True objmigration.sourcedomain = "source domain" objmigration.sourceou = "source container" objmigration.targetdomain = "target domain" objmigration.targetou = "target container" Migrate specified group objects. objgroupmigration.migrate admtdata, Array("group name1","group name2") Set objgroupmigration = Nothing Set objmigration = Nothing </Script> </Job> For a sample script to assist you in migrating groups, see Migrating Groups Within a Forest (DSSRERA_2.wsf) on the Windows Server 2003 Deployment Kit companion CD (or see Migrating Groups Within a Forest on the Web at Migrate Global Groups Migrate global groups, without members, from the source domain to the target domain to protect against the problem of open sets. After global groups are migrated to the target domain, they cease to exist in the source domain if the source domain has a functional level of Windows 2000 native or higher. Because global groups only contain members from their own domain, they cannot be migrated from one domain to another. ADMT changes global groups to universal groups when they are migrated. The universal group in the target domain retains the SID history of the global group in the source domain, which enables users to continue to access resources in the source domain after the global groups are migrated. ADMT changes the universal groups back to global groups after all members of the global group are migrated from the source domain to the target domain. You do not need to include built-in and well-known global groups in your migration. Built-in and well-known groups already exist in the target domain. If a built-in or well-known global group is selected for migration, ADMT does not migrate it; instead, ADMT makes a note in the log and continues to migrate other global groups. The procedure for using the Group Account Migration Wizard to migrate global groups is the same as that for migrating universal groups. For more information about the procedure for migrating global groups and universal groups, see Migrate Universal Groups earlier in this chapter.
ADMT v3 Migration Guide Microsoft Corporation Published: November 2006 Abstract This guide explains how to use the Active Directory Migration Tool version 3 (ADMT v3) to restructure your operating environment.
How to monitor AD security with MOM A article about monitor Active Directory security with Microsoft Operations Manager 2005 Anders Bengtsson, MCSE http://www.momresources.org November 2006 (1) Table of
Dell Migration Manager for Active Directory 8.11 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished
8.3 Competitive Comparison vs. Microsoft ADMT 3.1 Copyright Quest Software, Inc. 2009. All rights reserved. This guide contains proprietary information, which is protected by copyright. The software described
3 CHAPTER THREE Managing Groups Objectives This chapter covers the following Microsoft-specified objectives for the Managing Users, Computers, and Groups section of the Managing and Maintaining a Microsoft
Websense Support Webinar: Questions and Answers Configuring Websense Web Security v7 with Your Directory Service Can updating to Native Mode from Active Directory (AD) Mixed Mode affect transparent user
Course 6425B: Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services Length: 5 Days Language(s): English Audience(s): IT Professionals Level: 200 Technology: Windows Server
Course 6425B: Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services About this Course This five-day instructor-led course provides to teach Active Directory Technology Specialists
If you have set up a domain controller previously with Windows 2000 Server, or Windows Server 2003, then you would be familiar with the dcpromo.exe command also be used to set up a Domain Controller on
2.0 Quick Start Guide Copyright Quest Software, Inc. 2007. All rights reserved. This guide contains proprietary information, which is protected by copyright. The software described in this guide is furnished
Mary I. Hubley, MaryAnn Richardson Technology Overview 25 September 2003 Windows Server 2003 Active Directory: Perspective Summary The Windows Server 2003 Active Directory lies at the core of the Windows
70-640 R4: Configuring Windows Server 2008 Active Directory Course Introduction Course Introduction Chapter 01 - Installing the Active Directory Role Lesson: What is IDA? What is Active Directory Identity
8.7 User Guide 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This document contains proprietary information protected by copyright. The software described in this document is furnished under a software
Configuring Windows Server 2008 Active Directory Course Number: 70-640 Certification Exam This course is preparation for the Microsoft Technical Specialist (TS) exam, Exam 70-640: TS: Windows Server 2008
Microsoft Virtual Labs Active Directory New User Interface 2 Active Directory New User Interface Table of Contents Active Directory New User Interface... 3 Exercise 1 User Management and Saved Queries...4
Course: WIN310 Student Lab Setup Guide Microsoft Windows Server 2003 Network Infrastructure (70-291) ISBN: 0-470-06887-6 STUDENT COMPUTER SETUP Hardware Requirements All hardware must be on the Microsoft
Managing Groups 4-1 Module 4 Managing Groups Contents: Lesson 1: Overview of Groups 4-3 Lesson 2: Administer Groups 4-24 Lab A: Administer Groups 4-36 Lesson 3: Best Practices for Group Management 4-41
253 CHAPTER 9 Designing the Active Directory Structure Microsoft Windows 2000 Server includes a directory service called Active Directory. The Active Directory concepts, architectural elements, and features
Step-by-Step Guide to Setup Instant Messaging (IM) Workspace Datasheet CONTENTS Installation System requirements SQL Server setup Setting up user accounts Authentication mode Account options Import from
Islamic University of Gaza College of Engineering Computer Department Computer Networks Lab Introduction to Administering Accounts and Resources Prepared By: Eng.Ola M. Abd El-Latif Mar. /2010 0 :D Objectives
SyAM Management Utilities and Non-Admin Domain Users Some features of SyAM Management Utilities, including Client Deployment and Third Party Software Deployment, require authentication credentials with
Reading Read over the Active Directory material in your Network+ Guide I will be providing important materials Administering Active Directory If you don t understand certain concepts, please ask for help!
SMART Active Directory Migrator Desired End State and Project Prerequisites uthor Title Table of Contents Introduction... 3 Purpose... 3 About SMART Active Directory Migrator... 3 Components of SMART AD
Lesson Plans LabSim for Microsoft s Implementing a Server 2003 Active Directory Infrastructure (Exam 70-294) Table of Contents Course Overview... 2 Section 1.1: Introduction to Active Directory... 3 Section
Setting up Active Directory Domain Services Tom Brett CREATING A SINGLE DOMAIN FOREST Once you have Windows Server 2008 R2 installed, it s pretty easy to create a domain you simply run the domain controller
MIGRATING TO AVALANCHE 5.0 WITH MS SQL SERVER This document provides instructions for migrating to Avalanche 5.0 from an installation of Avalanche MC 4.6 or newer using MS SQL Server 2005. You can continue
Using Logon Agent for Transparent User Identification Websense Logon Agent (also called Authentication Server) identifies users in real time, as they log on to domains. Logon Agent works with the Websense
Administering Group Policy with Group Policy Management Console By Jim Lundy Microsoft Corporation Published: April 2003 Abstract In conjunction with Windows Server 2003, Microsoft has released a new Group
RSA Authentication Manager 7.1 Microsoft Active Directory Integration Guide Contact Information Go to the RSA corporate web site for regional Customer Support telephone and fax numbers: www.rsa.com Trademarks
Chapter 3: Building Your Active Directory Structure Page 1 of 46 Chapter 3: Building Your Active Directory Structure Objectives Now that you have had an introduction to the concepts of Active Directory
Managing Users with Local Security and Group Policies 573. Disable user or computer settings in GPOs Each GPO consists of a user and a computer section. If there are no settings in either of those sections,
Mastering Active Directory Migrations: Controlling Critical Issues Use the right combination of tools and processes to protect your core network operating system during this critical process Abstract With
Creating logon scripts You can use logon scripts to assign tasks that will be performed when a user logs on to a particular computer. The scripts can carry out operating system commands, set system environment
CHAPTER 6 In this chapter, you do the following tasks in the order listed: 1. Determine the Exchange server that Cisco Unity will connect with, known as the partner Exchange server. See the Determining
Chancery SMS Version 5.4 or Higher Active Directory Integration Guide Revised September 2005 CSL - 12458 The Chancery SMS Documentation Team: Joanna Denford, Linda MacShane, Sarah Hewson, Karin Jensen,
AD RMS Step-by-Step Guide Microsoft Corporation Published: March 2008 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide provides instructions for setting up a test environment to
Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services Course Number: 6425C Course Length: 5 Days Course Overview This five-day course provides in-depth training on implementing,
User Guide NetIQ Domain Migration Administrator TM May 2012 THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE
VERITAS Backup Exec TM 10.0 for Windows Servers Quick Installation Guide N134418 July 2004 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software
Best Practices for an Active Directory Migration Written by Derek Melber, MCSE, MVP, president, BrainCore.Net AZ, Inc. Abstract This white paper details the major challenges of Microsoft Active Directory
Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services Introduction This five-day instructor-led course provides in-depth training on configuring Active Directory Domain Services
Deploying System Center 2012 R2 Configuration Manager This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Notes: STATISTICA VERSION 9 STATISTICA ENTERPRISE INSTALLATION INSTRUCTIONS FOR USE WITH TERMINAL SERVER 1. These instructions focus on installation on Windows Terminal Server (WTS), but are applicable
Menu INTRODUCTION...2 HOW DO I DEPLOY MYUSBONLY ON ALL OF MY COMPUTERS...3 ADMIN KIT...4 HOW TO SETUP A LOGON SCRIPTS...5 Why would I choose one method over another?...5 Can I use both methods to assign
Installation and Configuration Guide BlackBerry Resource Kit for BlackBerry Enterprise Service 10 Version 10.2 Published: 2015-11-12 SWD-20151112124827386 Contents Overview: BlackBerry Enterprise Service
CHAPTER 9 Changing Passwords in Cisco Unity 8.x This chapter contains the following sections: Changing Passwords for the Cisco Unity 8.x Service Accounts (Without Failover), page 9-1 Changing Passwords
1 Chapter 8 WORKING WITH COMPUTER ACCOUNTS Chapter 8: WORKING WITH COMPUTER ACCOUNTS 2 CHAPTER OVERVIEW Describe the process of adding a computer to an Active Directory domain Create and manage computer
Module 4: Implementing User, Group, and Computer Accounts Contents Overview 1 Lesson: Introduction to Accounts 2 Lesson: Creating and Managing Multiple Accounts 8 Lesson: Implementing User Principal Name
Dell Migration Manager for Active Directory 8.11 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished
Administrator Guide Reference Outpost Network Security Office Firewall Software from Agnitum Abstract This document provides information on deploying Outpost Network Security in a corporate network. It
MS-6425C - Configuring Windows Server 2008 Active Directory Domain Services Table of Contents Introduction Audience At Clinic Completion Prerequisites Microsoft Certified Professional Exams Student Materials
AVG Business SSO Connecting to Active Directory Contents AVG Business SSO Connecting to Active Directory... 1 Selecting an identity repository and using Active Directory... 3 Installing Business SSO cloud
VERITAS Backup Exec 9.1 for Windows Servers Quick Installation Guide N109548 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes
CHAPTER 6 Installing Exchange and Extending the Active Directory Schema for Cisco Unity 8.x In this chapter, you do the following tasks in the order listed: 1. Install Exchange on the Cisco Unity server,
How the Active Directory Installation Wizard Works - Directory Services: Windows Serv... Page 1 of 18 How the Active Directory Installation Wizard Works In this section Active Directory Installation Wizard
UNIT 5 ADDITIONAL PROJECTS BEFORE YOU BEGIN The RODC must be configured to use the RWDC as its Preferred DNS Server. Active Directory is installed on the RWDC. The RODC must be a member server within the
Managing user roles in SCVMM How to Create a Delegated Administrator User Role... 2 To create a Delegated Administrator user role... 2 Managing User Roles... 3 Backing Up and Restoring the VMM Database...
NE-6425C Configuring and Troubleshooting Windows Server 2008 Active Domain Services Summary Duration Vendor Audience 5 Days Microsoft IT Professionals Published Level Technology 02 June 2011 200 Windows
MOC 6436A: Designing Active Directory Infrastructure and Services in Windows Server 2008 Course Number: 6436A Course Length: 5 Days Course Overview At the end of this five-day course, students will learn
ILTA 2013 - HAND 6B Upgrading and Deploying Windows Server 2012 In the Legal Environment Table of Contents Purpose of This Lab... 3 Lab Environment... 3 Presenter... 3 Exercise 1 Add Roles and Features...
Operating System File and Printer Sharing with Microsoft Windows Microsoft Corporation Published: November 2003 Abstract File and printer sharing in Microsoft Windows allows you to share the contents of
Passwordstate Installation Instructions This document and the information controlled therein is the property of Click Studios. It must not be reproduced in whole/part, or otherwise disclosed, without prior
NETWRIX PASSWORD MANAGER ADMINISTRATOR S GUIDE Product Version: 6.1 February/2012 Legal Notice The information in this publication is furnished for information use only, and does not constitute a commitment
8.7 Target Exchange 2010 Environment Preparation 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This document contains proprietary information protected by copyright. The software described in this document
Microsoft EXAM - 70-413 Designing and Implementing a Server Infrastructure Buy Full Product http://www.examskey.com/70-413.html Examskey Microsoft 70-413 exam demo product is here for you to test the quality
Course: WIN310 Student Lab Setup Guide Summer 2010 Microsoft Windows Server 2003 Network Infrastructure (70-291) ISBN: 0-470-06887-6 Published by Wiley & Sons 1 STUDENT COMPUTER SETUP Hardware Requirements
OneStop Reporting 3.7 Installation Guide Updated: 2013-01-31 Copyright OneStop Reporting AS www.onestopreporting.com Table of Contents System Requirements... 1 Obtaining the Software... 2 Obtaining Your
d229466 Ch01.F 1/22/03 10:03 AM Page 11 CHAPTER 1 Basic Windows 2000/ Windows 2000 Server Installation and Configuration This chapter steps you through the installation process of your Windows-based Tiger
Security and Rights Delegations for the Password Reset PRO Master Service Applies to software versions 2.x.x and 3.x.x Password Reset PRO Master Service Delegated rights required for running the Password
Installing Windows Rights Management Services with Service Pack 2 Step-by- Step Guide Microsoft Corporation Published: October 2006 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide
Chapter 10 Managing Group Policy MICROSOFT EXAM OBJECTIVES COVERED IN THIS CHAPTER: Implement and troubleshoot Group Policy. Create a Group Policy object (GPO). Link an existing GPO. Delegate administrative
Agency Pre Migration Tasks This document is to be provided to the agency and will be reviewed during the Migration Technical Kickoff meeting between the ICS Technical Team and the agency. Network: Required
EMC Celerra Network Server Release 5.6.47 Using Windows Administrative Tools with Celerra P/N 300-004-139 REV A02 EMC Corporation Corporate Headquarters: Hopkintons, MA 01748-9103 1-508-435-1000 www.emc.com
C H A P T E R 4 Planning Domain Controller Capacity Planning domain controller capacity helps you determine the appropriate number of domain controllers to place in each domain that is represented in a
3 CHAPTER THREE Planning and Implementing an OU Structure Terms you ll need to understand: Organizational unit (OU) Delegation of control Group Policy Security group Linked policies Techniques/concepts
SEER Enterprise Shared Database Administrator s Guide SEER for Software Release 8.2 SEER for IT Release 2.2 SEER for Hardware Release 7.3 March 2016 Galorath Incorporated Proprietary 1. INTRODUCTION...
Implementing Domain Name Service (DNS) H C A 1 P T E R ITINERARY Objective 1.01 Objective 1.02 Objective 1.03 Install and Configure DNS for Active Directory Integrate Active Directory DNS Zones with Existing
MCTS Guide to Microsoft Windows 7 Chapter 13 Enterprise Computing Objectives Understand Active Directory Use Group Policy to control Windows 7 Control device installation with Group Policy settings Plan
Welcome to Support Express by Shakambaree Technologies Pvt. Ltd. Introduction: This document is our sincere effort to put in some regular issues faced by a Digital Signature and USB Token user doing on
About this Course Configuring and Troubleshooting Windows This five-day instructor-led course provides in-depth training on implementing, configuring, managing and troubleshooting Active Directory Domain
Course 6425C: Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services Course Details Course Outline Module 1: Introducing Active Directory Domain Services This module provides
White Paper CONFIGURING ACTIVE DIRECTORY IN LIFELINE CONTENTS Introduction 1 Audience 1 Terminology 1 Test Environment 2 Joining a Lenovo network storage device to an AD domain 3 Importing Domain Users
Active Directory About this Course This five-day instructor-led course provides in-depth training on implementing, configuring, managing and troubleshooting (AD DS) in and R2 environments. It covers core
Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide Microsoft Corporation Published: May 2010 Abstract This guide describes the steps for configuring Remote Desktop Connection
Cisco Security Agent Protection Series: Enabling LDAP for CSA Management Center SSO Authentication For CSA 5.2 Versions 184.108.40.206 and up Fred Parks Systems Consultant 3/25/2008 2008 Priveon, Inc. www.priveonlabs.com
Setup Guide for AD FS 3.0 on the Apprenda Platform Last Updated for Apprenda 6.0.3 The Apprenda Platform leverages Active Directory Federation Services (AD FS) to support identity federation. AD FS and