Domain migration scenarios
If a domain upgrade is impossible, you can use a domain migration process.
A domain migration process uses Microsoft tools to populate a native-mode Active Directory domain with user, group, and resource accounts that have been cloned from existing accounts in a Windows NT domain. Both types of domain can operate in parallel and, if the appropriate trust relationships exist between the Windows NT and Active Directory domains, users and groups in either type of domain have equivalent HCL VersionVault access rights.
Migration can take place over an extended period, if necessary. When all user and group accounts
are migrated to the Active Directory domain, the migration process can be completed and the
Windows NT domains can be decommissioned. After a migration, all users, groups, and hosts have
new SIDs. This has several implications:
- After an HCL VersionVault host has become a member of an Active Directory domain, you must reconfigure the host’s albd_server to log on as the HCL VersionVault server process user account that exists in the Active Directory domain. The name of the account might be the same, but the user and group SIDs have changed.
- VOB storage directories must be reprotected so that they include the new SIDs of the VOB owner in the directory ACL.
- VOB databases must be updated with the new SIDs. The vob_sidwalk utility replaces old SIDs with new ones. For more information, see Using vob_sidwalk to change or update VOB users and groups and the vob_sidwalk reference page.