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

Windows permissons prevent Sophos install have others seen this?

VCU

I feel Sophos is a good product, which provides high protection. I’’’’m pleased with the product over all.

The following item I’’’’m posting to get feed back from other Sophos users, have you seen this in your environments? Sophos is the only anti-virus product I’’’’ve come across that is so interlaced with the Windows security that Windows permission failures will prevent Sophos from installing. I’’’’ve seen many cases over the past 6 years where Sophos would not install because of Windows permission issues while other anti-virus vendors products could install without errors on the same Windows system that would not allow Sophos. The common error I get is 1920 in cases like this. I’’’’ve folloed the suggestions provided by Sophos under article 32249 to resolve a few of the cases.
http://www.sophos.com/en-us/support/knowledgebase/32249.aspx

Thanks

:28013


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

    Hi,

    From my experience, the main cause for such issues is that the SAVService runs as "Local Service".  On Windows 2000 it ran as local system and you'd never see a problem.

    If SAVService ran as local system 99% of the service not starting permission issues wouldn't exist.  That being said, Sophos has chosen a more linited user as it's more secure and best practice, if something took control of the service in some way, it would only be running as local service.

    Often permission problems are related to the "users" group no longer having access to a key/file/directory as this would give local service the access it requires.

    Maybe all the vendors run their services/main components as local system?  Ultimately the client computers are at fault as the system as designed works.  it's likely to be custom settings or other applications doing "bad things" to the permissions.

    Regards,

    Jak

    :28019
Reply
  • 0

    Hi,

    From my experience, the main cause for such issues is that the SAVService runs as "Local Service".  On Windows 2000 it ran as local system and you'd never see a problem.

    If SAVService ran as local system 99% of the service not starting permission issues wouldn't exist.  That being said, Sophos has chosen a more linited user as it's more secure and best practice, if something took control of the service in some way, it would only be running as local service.

    Often permission problems are related to the "users" group no longer having access to a key/file/directory as this would give local service the access it requires.

    Maybe all the vendors run their services/main components as local system?  Ultimately the client computers are at fault as the system as designed works.  it's likely to be custom settings or other applications doing "bad things" to the permissions.

    Regards,

    Jak

    :28019
Children
No Data