EMC Documentum Content Server Installation Owner Change

Approach 1:

To change the installation owner on Windows NT:

1. Log in as the Windows NT administrator.
2. Stop services for all repositories and connection brokers.
3. Stop all Content Servers on the host.
4. Stop all connection brokers on the host.
5. Set the value for the new installation owner in the install_owner parameter in the
   server.ini file located at %DOCUMENTUM%\dba\config\repository_name\server.ini.
6. Change the permissions in the data, dba, product, and share subdirectories of the
   DOCUMENTUM installation root directory:

a.      In Windows Explorer, select the directory.

b.      Right‑click the directory to display a menu and select Properties from the menu.

c.       Select the Security tab on the Properties dialog box.

d.      Click Add to add the new installation owner to the list of those with permissions
on the directory. You are prompted for the new owner¿s domain.

e.      Give the new owner Full Control permission.

f.        Check Replace Permissions on Subdirectories and Replace Permissions on
Existing Files.

g.      Delete the old installation owner from the list of those with access permission
on the directory.

h.      Click OK.

7. Edit the Registryto reflect the change in ownership:

a.      In the following key: HKEY_LOCAL_ MACHINE\SOFTWARE\Documentum\Server\version_No

i. Change the value of DM_DMADMIN_USER to the new owner.
ii. If the new owner is in a different domain, change the value of
DM_DMADMIN_DOMAIN to the domain of the new owner.

b.      In the following key: HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\DmServerdocbasename,
change the install_owner parameter in the value for Imagepath to the new owner

8. For each repository in the installation, use regedt32 to change the security permission
   on the following Registry keys:

¿ HKEY_LOCAL_MACHINE\SOFTWARE\Doumentum\Server\version_No.
¿ HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Documentum
¿ HKEY_LOCAL_MACHINE\SOFTWARE\Doumentum\Docbases\docbase_
name

a.      Select the key and right‑click it to display a menu.

b.      Select Security > Permissions.

c.       Add the new installation owner with Full Control.

d.      Delete the old installation owner.

9. For each Content Server, set the appropriate startup information:

e.      Select Control Panel > Services.

f.        Select the Service: Documentum Docbase docbase_name.

g.      In the Startup dialog box, type the new owner and owner¿s password under
Log On As: this account.

10. Move the Documentum and Documentum docbase docbase_name in the
    Start menu from WinNT\Profiles\old_owner\Start Menu\Programs\ to
    WinNT\profiles\new_owner\Start Menu\Programs.
11. Update the r_install_owner and r_install_domain parameters in the server_config
    object to reflect the new installation owner.
12. Restart Windows NT.

Approach 2:

1. Obtain [new install owner] credentials. Validate that the new account has the following privileges:
• Act as part of the operating system,
• Create a token object,
• Increase quotas,
• Log in as a service,
• Log in locally,
• Replace a process‑level token.
2. Login to DA as dmadmin.  For the [repository] and the [global registry repo]:
• Click Storage in the navigation tree and select the storage_01 object.
• Right-click the storage_01 object and select Properties.
• Note the File System Path. Eg: C:\Documentum\data\[Docbase Name]\content_storage_01
• Log out.
3. Log onto Documentum server as [old install owner].
4. Stop all Documentum services:
• Documentum Docbroker Service,
• Documentum Docbase Service [repository name],
• Documentum Docbase Service [global registry repo] if necessary,
• Documentum Java Method Server.
5. Change the logon user for each Documentum process listed in step 4 to the [new install owner].
• Open the Services control panel.
• Right-click the service, and choose Properties.
• Switch to the Log On tab.
• Enter new installation owner credentials.
• Click Apply, and then OK.
6. Edit the install_owner parameter in the %DOCUMENTUM%\dba\config\[repository name]\server.ini file to reference the new installation owner.

                        install_owner = [new install owner]

7. Repeat step 6 for the [global registry repo] if necessary.
8. Change permissions on the %DOCUMENTUM% directory and all subdirectories.
• In Windows Explorer, select the %DOCUMENTUM% directory.
• Right-click and choose Properties.
• Switch to Owner tab.
• Click the ‘Other Users or Groups’ button, add the [new install owner].  Click OK.
• Select [new install owner], check ‘Replace owner on subcontainers and objects’, and click the Apply button.
• Switch to the Security tab.
• Click the Advanced button.
• Click the Add button, add the [new install owner] and give it Full Control permissions. Click OK.
• On the Permissions tab, select the [new install owner], check the ‘Replace permission entries on all child objects with entries shown here that apply to child objects’ checkbox, and click the Apply button.
• Click Yes on the warning dialog.
• The system will update the security definitions for all files and folders in the %DOCUMENTUM% directory. This could take while.
• Click OK and close the Properties dialog.
9. Repeat step 8 for the File System Paths noted in step 2 if they are not included in the %DOCUMENTUM% folder structure.
10. Update Registry entries.
• Open the Registry using RegEdit.
• HKEY_LOCAL_MACHINE\SOFTWARE\Win6432Node\Documentum\Server\6.6
• Change the value of DM_DMADMIN_USER to [new install owner].
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[repository name]
• Change the value of ImagePath to contain –install_owner [new install owner].
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[global registry repo]
• Change the value of ImagePath to contain –install_owner [new install owner].
11. Change security settings on each of the following Registry keys.
• For each key under HKEY_LOCAL_MACHINE\SOFTWARE\Wind6432Node\Documentum\DOCBASES
• Right-click the repository name and choose Permissions….
• Click the Add button and add [new install owner] to the list of users.
• Select [new install owner] and give it Full Control.
• Click the Apply button, and then OK.
• For key HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\Server\6.6
• Right-click the repository name and choose Permissions….
• Click the Add button and add [new install owner] to the list of users.
• Select [new install owner] and give it Full Control.
• Click the Apply button, and then OK.
• For key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\Documentum
• Right-click the repository name and choose Permissions….
• Click the Add button and add [new install owner] to the list of users.
• Select [new install owner] and give it Full Control.
• Click the Apply button, and then OK.
12. Open database management tool and login as the database administrator.
13. Run the following SQL query to update the install owner attributes of the server config objects.
• UPDATE [repository name].[dbo].dm_server_config_s SET r_install_owner = '[new install owner]'
• UPDATE [global repository repo].[dbo].dm_server_config_s SET r_install_owner = '[new install owner]'
14. Restart the Documentum services stopped in step 4.
15. Log into DA as the [new install owner].
• Ensure the [new install owner] account privileges are identical to [old install owner] account.
• Select [old install owner] and choose Tools – Reassign User.
• Select the [new install owner]
• Configure the job to run Now, to Unlock All objects, and to Save changes and report results.
• Click OK. This could take a while.
• Note that this process will remove the [old install owner] account from the Docbase.
• To monitor the progress of the reassignments, enter the following query in the DQL Editor, and re-run it often. When the result is zero (0), the reassignment is complete.

                        select count(*)from dm_sysobject where owner_name = '[old install owner]'

16. Run the State of the Docbase report and review for anomalies and/or errors.
17. Run the Consistency Checker and review for anomalies and/or errors. You may have to compare it with a previous report to determine if any reported inconsistencies are due to the changes you made, or were pre-existing.
18. Publish the Data Dictionary and check for errors.
19. From DA, checkout/checkin files.