This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Safeguard Policies Updates

Our organization is going purchasing new PCs for all of our users.

I have already purcahsed 18 PCs and have deployed all but 3 of them so far.  The current PC I am getting setup and another PC I setup (a PC before this past one) has an issue after installing the Sophos SafeGuard Enterprise version 6.00.0.155.

The PCs will do the initial SafeGuard client install then reboots.  It then goes through the process of contacting and synchronizing with the server.  It will receive the certificate, key and policy.

But 2 out of the last 3 PCs have not received all the complete settings in the policy.  They both show they have received the policy.  It is date and time stamped.  But there are policy settings in the current policy the PC does not have.  It is like they still need to receive yet another updated policy or something.

In fact - looking at the status of the SafeGuard client on the PC - everything is date and time stamped.  The status also shows the user as SGN User.  It also has all Data Packets Prepared for Transmission completely sent and shows 0 to transfer.

It will show in the status the Local Self Help is enabled but not active.  I can activate Local Self Help.  When I reboot the PC to use Local Self Help Recovery - it is not an option I can take.  I can only do a Challenge/Response Recovery.

One of the policy settings is I do not display the computer name in the title bar of the SafeGuard POA screen.  So on these 2 PCs - because it does not have the current, latest policy for whatever reason still shows the computer name in the title bar.  So when I reboot a PC I can easily tell by the POA authentication screen if the policy on the PC is correct or not.

Any ideas or suggestions to try and/or check?

And like I said - the current PC did this.  The PC previous to this one worked perfectly.  The one before it is doing the same thing as this one.

:39957


This thread was automatically locked due to age.
  • It is possible that these new PCs are assigned to .AutoRegistered OU, or some different OU, where different set of policies is configured.

    Check also RSOP for policy name that is set for this PC. Based on this you can find on which OUs is this policy applied.

    :40823