If you've recently updated your enterprise-client.config file to include any changes and the changes were not picked up by an end user after restarting Atakama, the likely cause is that the original enterprise-client.config file was created by another administrator.
- Administrator A creates the original enterprise-client.config file.
- The enterprise-client.config file was used to onboard user 1.
- Administrator B updates (i.e., makes changes to) the enterprise-client.config file.
- User 1 restarts Atakama to read the updated enterprise-client.config but the changes made by Administrator B were not picked up.
Because every enterprise-client.config is digitally signed by an administrator, signatures need to match in order for the end user to accept the updated enterprise-client.config file. In the example above, the end user will only accept the enterprise-client.config file from Administrator A. The quickest solution is to have Administrator A open the enterprise-client.config file and save it so that the file updates with his signature (as per below).
To allow Administrator B to create or update enterprise-client.config files that will be picked up by all users, Administrator A will need to do the following:
- Open the enterprise-client.config file by right clicking on the Atakama icon in the system tray and click "Open Configuration File" and navigate to the location of the enterprise-client.config file.
- Administrator A clicks on the "Show More" button within the Administrators section and adds Administrator B (Administrator B must have joined and have been granted access to a Secure Folder that Administrator A had previously created). Administrator A saves the updated enterprise-client.config file.
- The impacted end user needs to restart Atakama (assuming the user uses a centralized distribution process of the enterprise-client.config file) to read the updated enterprise-client.config file. This will add Administrator B as a trusted administrator.
After completing the steps above, Administrator B can create and update the enterprise-client.config file without issue. This concept applies when multiple administrators are responsible for the enterprise-client.config file.