Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 3897 views
  • Users 0 members are here
Options
Suggested
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 9.7 updates slow on Windows 7 32 bit machine

Sophos_User

Hello,

I know that there were problem with the way Sophos updated the clients with Sophos 9.5.

We have upgraded to 9.7 and still get reports from users that whenever Sophos applies an update their machines become noticeably slower.

These machines are at least Dual Core Processors with 4 GB of ram and plently of HDD space. 

Has anybody run into the same issue and if so how have you resolved it?

Thanks!

:15641


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    In that case, consider this, when a machine starts up, the Sophos AutoUpdate service starts (alsvc.exe), this then kicks off Alupdate.exe which performs the update a short while later.

    So for these machines you could add the registry key:

    32-bit machines

    [HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\AutoUpdate]

    "StartupDelay"=dword:0000000a

    64bit machines

    [HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\Sophos\AutoUpdate]

    "StartupDelay"=dword:0000000a

    Where in this case, the Alupdate Process would kick off 10 seconds after the service starts.

    Maybe if you add in a 5 minute delay (DWORD decimal "300") and increase in the updating policy the update interval to something like 30 minutes that might help these machines.  This way the client would be up and running fully, before SAV updated.

    Also, I've noticed on my machine, which I think is a Windows bug, that although I might schedule a SAV scan for 9pm at night, I've found that it sometimes starts in the morning when I log on,  Looking at the history of the task confirms this behaviour even though none of the properties of the task are set to do this.  So checking that these machines aren't running scheduled scans at startup/resume might also be worth doing.

    Hope that helps.

    Regards,

    Jak 

    :15653
Reply
  • 0

    Hi,

    In that case, consider this, when a machine starts up, the Sophos AutoUpdate service starts (alsvc.exe), this then kicks off Alupdate.exe which performs the update a short while later.

    So for these machines you could add the registry key:

    32-bit machines

    [HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\AutoUpdate]

    "StartupDelay"=dword:0000000a

    64bit machines

    [HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\Sophos\AutoUpdate]

    "StartupDelay"=dword:0000000a

    Where in this case, the Alupdate Process would kick off 10 seconds after the service starts.

    Maybe if you add in a 5 minute delay (DWORD decimal "300") and increase in the updating policy the update interval to something like 30 minutes that might help these machines.  This way the client would be up and running fully, before SAV updated.

    Also, I've noticed on my machine, which I think is a Windows bug, that although I might schedule a SAV scan for 9pm at night, I've found that it sometimes starts in the morning when I log on,  Looking at the history of the task confirms this behaviour even though none of the properties of the task are set to do this.  So checking that these machines aren't running scheduled scans at startup/resume might also be worth doing.

    Hope that helps.

    Regards,

    Jak 

    :15653
Children
No Data