Converting proxy groups
About this task
Use the following procedure to replace the proxy groups required in a Windows NT® domain
environment with a
DevOps Code ClearCase® users group that is an Active
Directory universal group. The universal group includes the groups formerly used as proxy groups.
Note: You can use this procedure only in an Active Directory domain that is operating in native
mode. The DevOps Code ClearCase® users group and all the
proxy groups must exist in the same forest.
Procedure
- Use Active Directory management tools to rename
the DevOps Code ClearCase® users
group in the primary DevOps Code ClearCase® domain.
For example, the ATLANTA\clearusers group created in the procedure in Using proxy groups and domain mapping in Windows NT domains could be renamed to ATLANTA\clearusers_Atlanta.
-
Use Active Directory management tools to create a new (universal) DevOps Code ClearCase® users group.
Keep the same name (ATLANTA\clearusers in our example), so that users do not have to change the value of their CLEARCASE_PRIMARY_GROUP environment variable.
- Use Active Directory management tools to add the former proxy groups (BOSTON\clearusers_Boston and CHICAGO\clearusers_Chicago in our example) and the group you renamed in Step 1 as members of the new (universal) DevOps Code ClearCase® users group.
-
Disable domain mapping on all DevOps Code ClearCase® client and server hosts.
To disable domain mapping on a DevOps Code ClearCase® 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 DevOps Code ClearCase® hosts might store this value inHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Atria\ClearCase\CurrentVersion.) - Shut down and restart all DevOps Code ClearCase® client and server hosts.