Another Solution for the 9/19/2012 fiasco

I am providing a bat file for 32bit and 64bit computers.

1. If some machines are no longer "managed" by Sophos and you are unable to push new clients to them you will need to stop all of the services, and copy the Autoupdate folder from a working computer. The scripts (.bat Files) below will help with multiple networked computers. Use PSEX to deploy.

2. From a working computer copy the Autoupdate folder. One for 32bit and one for 64 bit. I copied them to a server share and named them Autoupdate64 and Autoupdate32.

3. The .bat files are rough and dirty. I really didn't have time to make nice vb scripts. I was able to fix 90% - 95% of our provblem computers. Push the clients back out to the computers having issues.

32Bit Computers

ECHO "Stopping Sophos Services"

sc stop "Sophos Agent"

sc stop "SAVService"

sc stop "SAVAdminService"

sc stop "Sophos AutoUpdate Service"

sc stop "Sophos Message router"

sc stop "Sophos Web Control Service"

sc stop "swi_service" sc stop "Sophos Web Intelligence Update"

ECHO "Overwriting Sophos AutoUpdate Folder"

xcopy /E /Y /C /H /Q \\server\share\AutoUpdate32 "c:\program files\Sophos\AutoUpdate"

64Bit Computers

ECHO "Stopping Sophos Services"

sc stop "Sophos Agent"

sc stop "SAVService"

sc stop "SAVAdminService"

sc stop "Sophos AutoUpdate Service"

sc stop "Sophos Message router"

sc stop "Sophos Web Control Service"

sc stop "swi_service" sc stop "Sophos Web Intelligence Update"

ECHO "Overwriting Sophos AutoUpdate Folder"

xcopy /E /Y /C /H /Q \\server\share\AutoUpdate64 "C:\Program Files (x86)\Sophos\AutoUpdate"