After successfully upgrading InTrust to version 11.5.x or later, the application may not behave as usual or may become unstable. Showing several errors and warnings across the consoles and logs.
This happens because after the InTrustFIPSMigrator Tool runs, it automatically disassociates this from your repositories, sites, and collections due to re-encryption, requiring the user to manually set this again
These are the places you should be looking for to make sure the appropriate InTrust server name is set there and not a GUID entry (you can always select it again just to be sure):
InTrust Manager Console (make sure to commit the changes after finishing):
Each of your custom and used Sites:
Configuration > Data Stores > Each of your Repositories (Properties > Indexing):
InTrust Deployment Manager Console:
Each of your Collections > Edit Collection:
Note: In some rare circumstances, the collections may need to be recreated from scratch, so take screenshots of their current settings before doing so.
Storage > Security (on each repository used):
Note: You should also check here for the Forwarding options if you are using this feature. If you do, it may require you to disable it, restart the InTrust services before you can re-enable it.
