In case anyone else sees newly protected clients that won't comply with policy:
I noticed earlier today (19/11/2013) that when I protected clients from the console, they wouldn’’’’t accept any group policies, and the primary update server stayed as the install UNC path instead of changing to HTTP addresses. This also happened if I reprotected existing good clients.
The RMS Agent logs showed errors:
19.11.2013 13:38:00 04CC E Services::GetAdapterData(), data item name SAUPolicy is unknown
19.11.2013 13:38:03 04CC E Services::GetAdapterData(), data item name SAVAdapterConfig is unknown
19.11.2013 13:38:03 04CC E Services::GetAdapterData(), data item name APPCAdapterConfig is unknown
19.11.2013 13:38:03 04CC E Services::GetAdapterData(), data item name TPAdapterConfig is unknown
19.11.2013 13:38:03 04CC E Services::GetAdapterData(), data item name DATCAdapterConfig is unknown
19.11.2013 13:38:03 04CC E Services::GetAdapterData(), data item name DEVCAdapterConfig is unknown
From the Windows event logs, our SEC (v5.2.1) updated SUM to v1.5 at ~16:15 yesterday (18/11/2013) – there was a problem with the Sophos Management Service during the SUM install, so maybe that had something to do with it….
Anyway, I’’’’ve rebooted the SEC server and the clients will now accept policies.
This thread was automatically locked due to age.