There is one or more invalid / unwanted InTrust server listed in under Servers in InTrust Manager even after the unwanted servers have been uninstalled manually (via Add/Remove programs). Also some jobs are failing to run while referencing the old server name and/or a GUID. This may also be used to speed up the manual move process of sites and all jobs from one InTrust server (which is being decommissioned) to a new one.
This can be caused by incorrectly rebuilding an InTrust Server after a crash and/or moving to a new InTrust server.The old server remains in the config db with a separate GUID even if it has the same Netbios name as the new server. The InTrust 10.x/11.x User Guide.pdf does reference a tool, adcserverremove.exe, which can be used if and only if the InTrust server has no sites, tasks or jobs associated with it but that adcserverremove.exe can cause issues if the InTrust server had been used.
If you see duplicate names within InTrust Manager (using after an OS or InTrust in place rebuild) you can determine by using the SQL query below which server is the invalid one from the InTrust config db.
Important: You should always make a backup of the InTrust Config database, normally "InTrust_Cfg_DB", before editing it and/or running any scripts.
select GUID,Name,LastServerPing,RollbackInfo from dbo.adcserver
Typically the invalid server will have an older ping time (LastServerPing entry)
If needed rename the duplicate server
update adcserver set name=invalidserver where guid=
Make sure that the old server has been shutdown/uninstalled or at bare minimum the InTrust 10.x "Quest InTrust Server" service or the InTrust 11.x "Dell InTrust Server" service is set to disabled and stopped on the old server.
Execute the attached script against the InTrust Config DB after updating the correct entries for OLD-SERVER-NAME-HERE and NEW-SERVER-NAME-HERE
If the script completes the old/invalid server should be removed.
Go back and refresh InTrust Manager to confirm that old/invalid server is removed.
The script will has been tested on 11.x up to and including 11.3. Before running any scripts or making any changes you should make a manual backup of InTrust_CFG_DB. Also it is best to stop the "Quest InTrust Server" service (and dependencies) on all InTrust servers in the org to prevent any tasks from running. After the script has been run you can start the "Quest InTrust Real-Time Monitoring Server" on the new / remaining InTrust servers.