Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1348 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

Solid state drives on the endpoint

the_Doctor

I have noticed that when the Sophos Anti-Virus service and the Sophos Client Firewall service are both set to Automatic, that the logon time increases from about 30 seconds to 3 minutes on computers with solid state drives.   These services do not seem to support delayed start, so I have had to create a new service that sets the Sophos services to Manual and starts them after a 90 second delay.    

Has anyone else experienced this?    Can someone from Sophos chime in with a better fix?

Thanks!

EDIT:   We are using 10.3, but noticed this with 10.0 as well.   

:45095


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

    ...create a new service that sets the Sophos services to Manual and starts them after a 90 second delay.    

    Sounds like a new knowledgebase article to me - prefectly acceptable. :smileywink:

    I can't find any specific case history with SAV + SCF causing a delayed logon time.  There are a few cases about just SAV causing startup to increase, but we're talking about just the logon time right?  Have you tried to recreate the problem with just SAV installed to rule out the SCF?  If you can remove the SCF from the equation that would be good.

    You don't say what OS and SPs are involved.  However we have a variety of test machines and we probably would have picked up on this issue if it was a plain problem with the two components.  Therefore it sounds like there may be something else interacting with the logon process.

    Initial questions are: is it every computer?  Just computer with SSD drives (as the subject of this post hints at)?  Different OSes/SPs?  All on the LAN?  Wireless/wired?  Do all the computer have the same AV policy?  What other programs are installed and may try to activate during the period of delay?  Any event log errors?  If you put a non-SSD into a computer is the problem resolved?  What make/model of SSD is installed?

    If only some computers on your network have the problem it's a case of spotting the difference between them.  If all of your computers have the problem it's a case of spotting the difference between your setup and a working computer - one of our test machines for example.  GPOs, DNS, can all affect what the computer does and how it routes data.

    :45111
Reply
  • 0
    the_Doctor wrote:

    ...create a new service that sets the Sophos services to Manual and starts them after a 90 second delay.    

    Sounds like a new knowledgebase article to me - prefectly acceptable. :smileywink:

    I can't find any specific case history with SAV + SCF causing a delayed logon time.  There are a few cases about just SAV causing startup to increase, but we're talking about just the logon time right?  Have you tried to recreate the problem with just SAV installed to rule out the SCF?  If you can remove the SCF from the equation that would be good.

    You don't say what OS and SPs are involved.  However we have a variety of test machines and we probably would have picked up on this issue if it was a plain problem with the two components.  Therefore it sounds like there may be something else interacting with the logon process.

    Initial questions are: is it every computer?  Just computer with SSD drives (as the subject of this post hints at)?  Different OSes/SPs?  All on the LAN?  Wireless/wired?  Do all the computer have the same AV policy?  What other programs are installed and may try to activate during the period of delay?  Any event log errors?  If you put a non-SSD into a computer is the problem resolved?  What make/model of SSD is installed?

    If only some computers on your network have the problem it's a case of spotting the difference between them.  If all of your computers have the problem it's a case of spotting the difference between your setup and a working computer - one of our test machines for example.  GPOs, DNS, can all affect what the computer does and how it routes data.

    :45111
Children
No Data