Ho hum, another day another Sophos problem....
Installed on Windows laptops. Installs ok, updates and is fine. Reboot and the shield icon is missing. Open up Sophos and the Updating/Update log options have disappeared.
I'm gettting soooooo tired of ringing Sophos, and them 'escalating' the problem (i.e forgetting about it) so has anyone else seen this problem?
Clients are installed from EC by the way, running on Server 2008 R2. XP Clients are working ok (generally speaking) this just seems particular to Windows 7
Are you installing on a clean Windows Install? If not I'd remsav the machine and then try it again. The latest version of Sophos that we have here doesn't always liketo remove the old version and then it just fails.
Yup these are all clean (fresh images anyway!) installs. Never had sophos on the image either.
In the console they're all showing Comparison Failure, and all show the error 'buffer overflow detection is disabled because of a configuration error'
Did Sophos actually test this with Windows 7? I've never had one client keep it running for more than a couple of reboots!
We had MAJOR problems with Sophos last year, it just went on for months, not specifically Windows 7 but something that has fixed all the issues we had was installing Sophos as a web service through IIS. The machines get their updates via this website.
Sophos themselves remoted in and did everything configuration wise and it has been working perfectly on all machines including Win 7 since then.
Once thing I will say is I tend to install from the machine as I’ve never really trusted doing it from EC, I just prefer to install, reboot and confirm it's on and working correctly.
Hope this helps.
Sorry, I worded that wrong. When I say I installed from the EC, I meant we ran the install package on the EC from the client.
Sophos has been 100% unreliable on Windows 7. All installations have failed so far in one form or another. The XP ones occasionally fall over but not to this extent.
Sophos sent me a document containing a list of steps that needed to be carried out before you deployed Sophos to a Win 7. Certain things to turn on/off, adjust, etc. I can't actually find the document anymore but it may be it should be easy enough to find from their knowledge base or give them a call.
Personally, I've never done anything other than run the installer but like I said, we did have some huge problems last year which started after we upgraded EC to version 4.00.
Since using web to do the updating, don't recall having a it fail on a single machine. Maybe you should give it a go? I thin the 2 can run side by side. Ask them to set it up for you.
If you're not getting far with tech support, contact your Account Manager. That's what I did and the next day I had a specialist call me back who stuck with me on a daily basis until we got the problem resolved.
One thing that has sprung into my mind is that on my Windows 7 machine in the office I had to enable the remore registry service. Sophos requires this for install and I believe on Vista and 7 it's disabled by default.
I ran through the checklist on the first batch - all of the services and firewall settings are in a group policy. Sophos usually ask for a ton of diagnostics files and then sit on them.
Updating seems to work - when the actual update service is running. Its just that it fails to start on reboot.
For a long time i've done it this way now, its a set and forget no need to remember if you reimage the machien :-)
Deploying Endpoint Security and Control through Active Directory group policy
We tried to use Sophos for 3 years. We finally just ditched them in favor of Microsoft Forefront. We have been much happier with Forefront, also, we only had to pay $15 for the management console (our campus agreement covered all the client licenses)!
All of our Windows 7 clients now show an error in the console - 'a050000d Buffer overflow detection is disabled because of a configuration error'.
Needless to say Sophos have no knowledge of this error code, has anyone see this on their W7 clients?
Got the same issue here. @Sheridan did you ever get a fix from Sophos?
Originally Posted by Sheridan
I seem to remember that we had to change the permissions on the ProgramData\Sophos folder to allow write access for System and Local Service accounts. Then run an update and it worked. This was something we worked out ourselves by seeing what files were modified on a working machine and comparing. I think its a file called config.bop in that folder that needs to be writable by the system.
I'll have another look tomorrow and see if that's all we did!