Client upgrading from DocsOpen 4 to DM 5. Since we are migrating users slowly to new system need to be able to run DM and DocsOpen at the same time. OpenText recommended we go to DM 5.1.0.5 first and after all users upgraded to DM, move to DM 5.2.1.
Creating Testbed for the upgrade from DM 5.1.0.5 to DM 5.2.1
Existing SQL server not being used. Using SQL backup file from production SQL server, restored DOCS database to this SQL server.
Confirmed DEP was set for only essential Windows Services Under Performance.
Copied document storage location to another folder. Used the following command:
robocopy s:shareddms s:sharesdms2 *.* /E /ZB /R:2 /NP >s:sharedcopydms.log
Connect to System parameters and added the new document storage path.. Ran queries to update all profiles to point to new path and all people to point to new path
update profile set DOCSERVER_LOC = 'servernamesharesdms2' where DOCSERVER_LOC = 'servernamesharesdms'
update people set TARGET_DOCSRVR = '334222' WHERE TARGET_DOCSRVR = '223570'
You have to lookup the system_ID’s for the document server locations for the second query. They are in the DOCSERVERS table.
Installed DM 5.1.0.5 Server and DM Extensions Server.
Installed Service Release 6 (SR6) Maintenance Release 5 (MR5) for both (DM Server and DM Extensions Server)
Had to go into DCOMCNFG and change the permissions as described in OpenText’s best practices because the client could not find the server. I wonder why they don’t just have the install configure this? It seems if I run the DM server configuration wizard, I have to go into DCOMCNFG again and fix the permissions. Restarted DM service and viola I was able to get the client to use this server.
