Migrating individual hosts

When all users and groups have been migrated and no users are required to log on to the Windows NT domain, migrate HCL VersionVault hosts to the Active Directory domain.

1. Stop HCL VersionVault on the host.
2. Use the procedures defined by Microsoft to migrate the host to the Active Directory domain.
3. Reconfigure each HCL VersionVault host so that its albd_server logs on as the (migrated) HCL VersionVault server process user in the Active Directory domain.
   You can do this by reinstalling HCL VersionVault on the host and specifying the new account, or you can do it manually, as described in Defining required domain accounts manually.
4. If the host is a VOB server that will be also accessed by clients running Linux or the UNIX system, reset the credentials mapping domain in the Options page of the VersionVault program in Control Panel. The credentials mapping domain must be one in which user and group account names match those of users on Linux or the UNIX system that will access VOBs on this server.
5. Restart HCL VersionVault on the host.
6. Reprotect any VOB and view storage on the host.
   To do so, run the fix_prot utility on each VOB or view storage directory as shown in this example:

   versionvault-home-dir\etc\utils\fix_prot –replace storage-dir-pname

   In this example, storage-dir-pname is the pathname to the VOB or view storage directory.
7. Update VOB databases with the new SIDs that represent the cloned user and group accounts.
   1. Log on to the VOB server host as the VOB owner or privileged user.
   2. Lock the VOB for all users except yourself (–nusers you).
   3. 
      
      Replace the old SIDs with the new ones. Run vob_sidwalk. In this example, vob-tag is the VOB tag of the VOB you are updating and SIDfile-path is the name of a file in which vob_sidwalk logs the changes it makes:

      versionvault-home-dir\etc\utils\vob_sidwalk –s –execute vob-tag SIDfile-path

      For additional details about how vob_sidwalk remaps SIDs, see Using vob_sidwalk to change or update VOB users and groups.
   4. Unlock the VOB.