App Control Server: 8.7+
The agent-to-server communication key (keychain.json) auto-updates periodically due to scheduled task
which may cause multiple agents to become Out-of-Date or disconnected in the console.
These steps can be used to reset the communication key file (keychain.json) back to the previous version if the agents aren't able to pull the newest one from the server.
- Connect to one of the Out-of-Date or disconnected agent systems and open CMD and run:
cd "C:\Program Files (x86)\Bit9\Parity Agent"
- Take note of the Communication Key value (for example):
Communication Key: 6601155A-C399-4B15-A8DF-1234567890
- Login to the App Control Server System
- If there is an agent on the system please disable Tamper Protection
- Open Services (services.msc) and Stop the CB App Control Server service
- Move Out or Delete the existing "keychain.json" file here:
\Program Files (x86)\Bit9\Parity Server\hostpkg\keychain.json
- Open SQL Mgmt Studio with account that has permissions to make change to the DAS database (e.g. CB service account)
- Execute the following queries:
use das; update dbo.communication_keys set key_state = 0 where key_state = 1
use das; update dbo.communication_keys set key_state = 1 where key_id like '6601155A-C399-4B15-A8DF-1234567890' --this is an example value, pls replace it with the one from Step 1
- Start the App Control Server service
- Verify that a new "keychain.json" file has been generated:
- check here: "\Program Files (x86)\Bit9\Parity Server\hostpkg\"
- open the "keychain.json" file in Notepad and check that the "keyRevision" value matches the value from the Sql query
- Disable the auto-generation of a new communication key file (keychain.json) again, please follow the steps in this KB
- Verify that the agents are connected and Up-to-Date in the console
To manually manage the agents-to-server communication key (keychain.json) in the console > System Configuration page > Security tab > Scroll to the bottom > Communication Key > "Regenerate" button