4.5 Domain Upgrade Scenarios

This section describes several scenarios in which one or more Windows NT domains are upgraded to Active Directory domains using the in-place upgrade procedure defined by Microsoft. If your site is not using this procedure, see Domain Migration Scenarios.

NOTE: In this section, references to upgrading a domain refer to upgrading the primary domain controller of that domain.

Upgrading a Single Domain

Use this procedure if all ClearCase users, groups, and hosts are members of a single Windows NT domain:

1. Prepare ClearCase LT hosts as described in Preparing ClearCase Hosts.

2. If you do not have a backup domain controller online during the upgrade, stop ClearCase on the ClearCase LT server to prevent ClearCase operations during the upgrade process.

3. Use the procedures defined by Microsoft to perform an in-place upgrade of the Windows NT domain to an active directory domain.

4. After the upgrade of the primary domain controller is complete, shut down and restart all ClearCase LT hosts.

Upgrading a Master Domain and Its Resource Domains

Use this procedure if all ClearCase users and groups are members of a single Windows NT domain (the master domain) that is trusted by one or more Windows NT resource domains to which ClearCase hosts belong.

To upgrade a master domain and its resource domains:

1. Upgrade the master domain as described in Upgrading a Single Domain.

2. Upgrade each resource domain as described in Upgrading a Single Domain. Configure the upgraded resource domain as a child of the upgraded master domain.

3. After the upgrade of a resource domain is complete, shut down and restart all ClearCase LT hosts in that resource domain.

Upgrading Multiple Master and Resource Domains

Use this procedure if ClearCase users and groups are members of more than one Windows NT domain and you are using proxy groups to enable users from these domains to access a common set of VOBs and views. The domains can include resources as well as users and groups or can be master domains trusted by resource domains.

After the upgrade is complete, we recommend converting the Active Directory domains to native mode so that you can use an Active Directory universal group to eliminate the need for proxy groups and domain mapping.

To upgrade multiple master and resource domains:

1. Prepare ClearCase LT hosts as described in Preparing ClearCase Hosts.

2. If you do not have a backup domain controller online for each of the master and resource domains during the upgrade, stop ClearCase on the ClearCase LT server to prevent ClearCase operations during the upgrade process.

3. Use the procedures defined by Microsoft to perform an in-place upgrade of the first Windows NT master domain to an Active Directory domain. Upgrade the domain in which the ClearCase users group is defined before upgrading the domains in which the proxy groups are defined.

4. Upgrade the remaining master domains.

5. After the master domains have been upgraded, you may begin to upgrade the resource domains. As long as you do not alter existing trust relationships between domains that have been upgraded and those that have not, you may upgrade the resource domains in any order and on any schedule that is appropriate for your organization. We recommend making all of the upgraded domains members of the same forest, which will allow you to take advantage of Active Directory universal groups, as described in Converting Proxy Groups.

6. After the upgrade of a resource domain is complete, shut down and restart all ClearCase LT hosts in that resource domain.

7. After all domains have been upgraded and the Active Directory domain has been converted to native mode, follow the procedure described in Converting Proxy Groups to eliminate proxy groups and domain mapping.

Converting Proxy Groups

Use the following procedure to replace the proxy groups required in a Windows NT domain environment with a ClearCase users group that is an Active Directory universal group. The universal group includes the groups formerly used as proxy groups.

NOTE: You can only use this procedure in an Active Directory domain that is operating in native mode. The ClearCase users group and the proxy groups must all exist in the same forest.

1. Use Active Directory management tools to rename the ClearCase users group in the primary ClearCase domain. For example, the ATLANTA\clearusers group created in the procedure described in Using Proxy Groups and Domain Mapping in Windows NT Domains could be renamed to ATLANTA\clearusers_Atlanta.

2. Use Active Directory management tools to create a new (universal) ClearCase users group. We suggest keeping the name the same (ATLANTA\clearusers in our example), so that users do not have to change the value of their CLEARCASE_PRIMARY_GROUP environment variable.

3. Use Active Directory management tools to add the former proxy groups (BOSTON\clearusers_Boston and CUPERTINO\clearusers_Cupertino in our example) and the group you renamed in Step #1 of this procedure as members of the new (universal) ClearCase users group.

4. Disable domain mapping on all ClearCase LT client and server hosts. To disable domain mapping on a ClearCase LT host, use a registry editor to navigate to the registry key HKEY_CURRENT_USER\SOFTWARE\Atria\ClearCase\CurrentVersion, and then remove the DWORD value DomainMappingEnabled. (Some ClearCase LT hosts may store this value in HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion.)

5. Shut down and restart all ClearCase LT client and server hosts.