There are the following types of alerts for issues that affect installation of Sophos agents,updating of Sophos agents, or policy compliance: HighFailed to protect computer or serverA computer has started installation of the agent software but has not become protected forone hour. The installer that has been run on the affected computer may provide moreinformation about the reason of the failure. MediumComputer or server out of dateA computer that has not been updated in the last 24 hours has been communicating withSophos Central in the last 6 hours, and did not update inthe following 2 hours. Normally, a computer will attempt to update about 5 minutes after ithas been started, and then regularly every 60 minutes.
If re-applying the policy failsrepeatedly, it may be due to a more serious problem. In those cases, re-installation maysolve the problem.Reboot requiredThe reboot of a computer is needed to complete an update of the agent software, but thecomputer has not been restarted for 2 weeks.
Sophos Won't Update
Sometimes, after installing/updating the agentsoftware, a restart is needed to fully enable the capabilities of the new/updated version ofthe software. Although an update does not need to be performed immediately, it is advisableto perform it as soon as possible.Policy non-complianceA device may not comply with a policy for various reasons, for example because the settingshave been changed on the device itself. In that case, after two hours of non-compliance, thesystem will raise an alert and will try to re-apply the corresponding policy. When thedevice is back in compliance, the alert will be automatically cleared. If re-applying failsrepeatedly, it may be due to a more serious problem.
In those cases, re-installation maysolve the problem.Peripheral detectedA removable media or peripheral device has been detected on a device monitored by Sophos Central.Duplicate device detectionA duplicate device has been detected. If devices have been cloned from an image they havethe same ID. Duplicate IDs can cause management issues. Duplicate devices are re-registeredwith a new ID.For more information, see.Notes:.
How to install brother 2540d. Windows 7 (64-bit).
Computers running Windows XP/Vista or Server 2003/2008 are not detected as duplicates.However, if they have the same ID as the one running a supported OS (e.g. Windows 10),they are detected as duplicates but not re-registered. Any Windows servers with the server lockdown product installed and locked are notre-registered if they are detected as duplicates. We don't support duplicate device detection on VDI style environments such as VMwareHorizon or Citrix PVS or Citrix MCS.
Hi,Same problem with windows XP Servicepack 2. No matter how many permisions I give to the user, it will not install under XP.At first it did not have enough permissions for a certain registery key. No it cannot find a unique accountname? This is what shows up in event viewer:-Product: Sophos AutoUpdate - Error 3057.There was an unexpected error while attempting to create, repair or delete a user account. Contact your support personnel. Description: When creating a user account, could not find a unique account nameProduct: Sophos AutoUpdate - Error 3057.There was an unexpected error while attempting to create, repair or delete a user account. Contact your support personnel.
Description: Could not open registry key SOFTWARESophosAutoUpdateService A Windows API call returned error 5-They only thing I can think of is that my domain policy prevents security center from running. I will check this now. Good evening people,Hate to dissapoint you but I had to reinstall xp SP2 completely. After that I reinstalled the sophos package on my machine.This time I had different errors, but was solved by calling sophos customer support. People who get these errors shouldrename their sophos directory called SophosEM to Sophos and give everyone full control on the sharingpermissions.
Sophos Protection Updating Failed Password
JAllen wrote: Can you run both Sophos and Endpoint together in an image if you install one or the other, we have MSNDAA, What I have been doing so far, is to set up SCCM 2012 to install Endpoint Protection on selected computers and then when Spiceworks complains about having 2 Anti-Virus programs installed on a computer to go in and remove Sophos. 3 thoughts on “ Sophos Endpoint: How to change the update location if it is greyed out ” Jennifer Coborn 5th September 2015 at 8:12 am. I cant get Sophos to update. Am I protected, I had Windows 8.1 now windows 10 please help asap. To get my protection an Sophos running correctly again.