Why are the Client Security Policies not applied on the client?

The Client Security Policies defined in the Server Manager under Manage → CE Client Policies are transferred by the Enterprise Server to the clients of the Corporate Edition as soon as the user logs on to the server successfully. If the settings do not arrive on a client, check the following points in this order:

1. Is the Corporate Edition actually installed? The Standard Edition of the Windows client does not apply the policies. You can recognize the Corporate Edition by the suffix "Corporate Edition" in the client's window title. If the Standard Edition is installed, install the Corporate Edition (installer pdepot19CE.exe from the server download page).

2. Do the versions match? The Windows client and the Enterprise Server must have the same main version (e.g. client 19 with server 19). After a server migration, therefore, also update all Corporate Edition clients – updating outdated clients first is the most common solution step in support cases.

3. Has there already been a successful server logon? The policies are only transferred with the user's first successful logon to the Enterprise Server. Before that, numerous functions are disabled by default in the Corporate Edition (including printing, exporting, synchronizing, encrypting external files) – this is not an error but the delivery state. If the connection itself already fails, work through the connection checklist first (see "Related topics").

4. Are the policies enabled on the server side? Open Manage → CE Client Policies and make sure the toggle switch at the top of the dialog is switched on – only then does the server enforce the policies. Confirm changes with OK.

5. Reset the local policy file. The client stores the received policy in the file C:\Users\<USERNAME>\AppData\Roaming\AceBIT\Password Depot 19\Data\default.localpolicy. You can delete this file – it will be recreated at the next logon to the server. The file is bound to the respective Windows user account; a file copied from another profile is not accepted.

Note: The CE Client Policies always apply server-wide to all users. A deviating set of rules for individual users, groups, or databases is not supported – if only a single user behaves differently, this points to items 1–3.

Note: In offline mode, the most recently received policy remains in effect. Server-side changes only reach the client at the next logon to the Enterprise Server.

Related topics:

• Corporate Edition: Managing Client Security Policies Centrally

• Connection to the Enterprise Server fails (Socket Error 10060/10061/11001) – checklist

• How do I migrate the Enterprise Server to version 19?

• Deploying license keys to the Windows clients automatically