One or more clients report their status to the Sophos Enterprise Console as "differs from policy", under the "Updating Details" tab | "Updating policy" column.
First seen in
There are a variety of reasons for this. To locate the cause work through the What To Do section below in order.
What To Do
Confirm the client has recently reported to the console
Initially it is important to confirm the client has sent a message to the Sophos management server recently. If the client has not reported to the console recently then the warning message may not be accurate.
- Right-click the computer in the console.
- Select "View Computer Details".
- In the computer details windows locate the line "Last message received from computer".
- If the client is switched on and connected to the network ensure the date and time is within the last 30 minutes. If the date and/ or time is outside of this period you should look to troubleshoot why the client is not reporting to the console.
Force the client to comply
If the server has received a recent message from the client then you should attempt to force a comply to the client. This will undo any local changes an administrator may have made to the client's configuration.
- Ensure that the client(s) are shown as connected in the console. To do this: From the 'View:' drop down box select 'Connected computers'.
- Right-click the client and select 'Comply with' | 'Group Anti-Virus and HIPS Policy'.
Warning: Forcing a comply for disconnected clients will generate message build-up in the management server's envelopes folder as these messages cannot be sent to offline endpoints. It is recommended you only force a comply for a small number of online endpoints first and see if the alert disappears and does not come back (see below).
Important: You may initially see the warning disappear from computers that you force to comply only to see it return after a short while (having initially complied). This happens while the policy is being sent to the endpoint and the endpoint is attempting to implement the policy. However if there is an underlying problem forcing a comply will not resolve the issue - you should work through the rest of this article to identify the issue. Forcing a policy compliance at this stage is an important step as you must rule out if the policy simply needs re-sending to the endpoint and/or a local administrator has/is altering the policy from that configured centrally.
Check the updating policy does not contain white space characters
There is a known issue whereby introducing an extra space (white character) into the username field of the updating policy can cause the policy to differ.
- Open the updating policy associated with the group of computers that are reporting as differing.
- On the "Primary Server" tab re-enter the account used for updating in the "Username" field and ensure there are no white spaces at the beginning or end of the string.
- Repeat step two for the "Secondary Server" tab.
- Click OK to save the policy change.
- Force a comply - see section above.
Reboot the client
Occasionally the client may have trouble complying the current configuration until it has been rebooted. If you have not already done so, reboot a client and wait for the client to report (see Confirm the client has recently reported to the console above).
Check the distribution point for a custom configuration file
- Browse to the 'SAU' sub-folder in the distribution point the client is currently updating from (i.e. \\servername\SophosUpdate\Sxxx\SAVSCFXP\sau\).
- Check if there is a 'sauconf.xml' file present. If the file is present, and the custom configuration it contains is no longer required, you should delete this file and use ConfigCID.exe to update the share. For more information on using the ConfigCID.exe tool see: Enterprise Console: using ConfigCID.exe to implement XML configuration file changes