I'm experiencing the same problem with one of my colleague's
Sophos says "sophos protection disabled" and a red X is shown in the Sophos shield in the systray. All other users do not have this problem. In the Enterprise console the client is up to date and complies with policy.
I have already reinstalled the client and removed it from the Enterprise Console and reinstalled.
My colleague informed me the red x comes 5 minutes after Windows logon.
I'm experiencing the same problem with one of my colleague's
Sophos says "sophos protection disabled" and a red X is shown in the Sophos shield in the systray. All other users do not have this problem. In the Enterprise console the client is up to date and complies with policy.
I have already reinstalled the client and removed it from the Enterprise Console and reinstalled.
My colleague informed me the red x comes 5 minutes after Windows logon.
IIRC the disabled message commonly signifies a service (SavService.exe) or perhaps internal communication error. Please check the Windows Event logs. I'm not sure about the red x which normally means a failed update attempt, you should also check the updating log.
The 5 minutes after startup would be the first update. For example: If a computer has been shutdown over night. You start it up, the Sophos AutoUpdate service will start and the first update check will be after 5 minutes. As it's been off there is a very good chance it will download and install a new ide.
With this set, the updating process would kick off 10 minutes (600 seconds) after the Sophos AutoUpdate service starts rather than the default of 5.
I wonder if the computer would be more responsive 10 minutes after startup such that the update would happen quick enough that Action Center/Security Center doesn't jump in when it sees the update is happening. Might be worth trying for a few days to see if the behaviour changes.
