The Customization Tool available for 5.5.x and later can be downloaded here:
After you upgrade, there is a possibility that the Local.storage file changes the value of “role” from “Primary” to “Secondary” if it detects any existing Service Connection Points in Active Directory.
This issue can happen in these scenarios: One Identity Password Manager
Please keep in mind that if you have multiple Password Manager servers, one of these must be “Primary” and all others “Secondary” for the same domain (realm) instances.
If you fall into either of the aforementioned scenarios, please check the settings in the following file after you finish the overall upgrade process:
C:\ProgramData\One Identity\Password Manager\Local.storage
The setting is located near the top of the file:
<setting name=”role” value=”Secondary” />
Ensure only one Password Manager server has this setting:
<setting name=”role” value=”Primary” />
|NOTE: If no servers are set to "Primary", designate one of your choosing and update it. After the file is updated and saved, restart the Password Manager service on that server only.|
Logging is a valuable resource in troubleshooting issues with Password Manager. When working with One Identity Support, Verbose logging is required as it provides more details for troubleshooting issues.
|Caution: One Identity does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support: .|
Navigate to the PMAdmin site | General Settings | Logging Settings:
The log files created on the Password Manager server are called: