Return
-
Title
How to re-install InTrust and connect back to an existing InTrust configuration database. -
Description
How to re-install InTrust and connect back to an existing InTrust configuration database.
-
Cause
Some customers may wish to re-install InTrust and the pre-existing InTrust server and configuration database still exist.
-
Resolution
Please Note: Backup the InTrust Server machine before taking any action. Ensure the Ogranization Password is on hand. Also, backup the InTrust Configuration database (InTrust_Cfg_Db).
- Important: on the InTrust Server machine, save the setting (GUID) defined by this registry value: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Aelita\ADC\Server\LocalServerID.
- Install .Net 4.5.2 or above
- Install InTrust Server from scratch into a new (different) InTrust organization. That is, when prompted, specify a new (empty) configuration database.
- Stop the Quest InTrust Server service (adcrpcs.exe).
- Edit the HKEY_LOCAL_MACHINE\Software\Wow6432Node\Aelita\ADC\Server\LocalServerID value in the registry to replace the GUID of the new InTrust Server installation with the GUID you saved on step 1 above.
- Use the AdcCfgDb.exe command line utility ((\InTrust\Server\ADC\SupportTools\) to switch your InTrust Server to the old configuration database.
For further instruction how switch the intrust server to old configuration database, please refer to Quest Solution article SOL15300 - "How to Point the InTrust Config Database to a New Configuration Database"
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL15300&category=Solutions&SKB=1 - 6. Start the Quest InTrust Server service (adcrpcs.exe).
Notes: Installing the .Net 4.5.2 or above prevents issues with Deployment Manager and Repository Viewer.
Using AdcCfgDb.exe you will need to use both server and database switches as you will be going back to the original config database.