When opening the SafeGuard Management Center the following warning message is displayed:
We have found inconsistencies in your database, which should be corrected quickly. Please contact Sophos Support for further assistance.
In addition to this, one or more users are not getting a new keyring after login at the Operating System.
The above message implies one or more failed attempts to provide a client with a new keyring.
Please Note: Apart from the fact that affected users don´t get a keyring, we do not anticipate other limitations or an operational impact. If you are using SafeGuard Device Encryption only, users will probably not notice anything unusual.
First seen in
SafeGuard Management Center / Local Policy Editor 6.0
With SafeGuard Enterprise 6.0 an additional consistency check has been implemented for the SafeGuard database. Inconsistencies such as the above usually stem from failed Active Directory synchronizations performed with previous versions of SafeGuard Enterprise.
If a SafeGuard Client is requesting an object that cannot be provided by the SafeGuard Server due to database inconsistencies, a flag is set in the database that triggers the information message at every Management Center start. The requesting user, who logs on at the SafeGuard Client, will only be able to receive a new keyring after the issue has been resolved in the database.
What To Do
Please contact Sophos Support (email@example.com) and provide the complete build version of the SafeGuard Management Center. We'll gladly assist you in checking your database, finding the affected objects, and solving the inconsistency.
We recommend that you resolve the issue as soon as possible. This will ensure correct operation of the file-based encryption modules of SafeGuard Enterprise that rely on the availability of the user keyring (e.g. SafeGuard Data Exchange, File Share or Cloud Storage).