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

Disabling Web Content Scanner.

Hi,

We are running endpoint security Version 4 and version 9 of sophos on the machines.

I need to globally disable the plugin within ie "sophos web content scanner"

When looking through endpoint security you would assume "web content scanning is:" option within antivirus and hips policy would disable that plugin.

So i selected it to "off"

and the ie plugin is still enabled.

I also found this article on the Sophos knowledge base but it is refering to a older version of sophos and i can not find the savconf.xml file it is refering to on this installation of endpoint.

sophos article

Has anyone got any ideas how i can disable this plugin centrally? Our machines are not logging onto a domain so a gpo will not work. Is it possible to amend a file like in the above article or anything else i can try?

Thanks,

:1570


This thread was automatically locked due to age.
  • Why do you want to disable the plugin? Is it causing troubles? Performance?

    I think the "articles for older versions" still apply (if I follow the links in Sophos Anti-Virus for Windows 2000+: overview of web content scanning the most recent version mentioned is and above :smileywink:). Funny (well, if you are easily amused) that neither SEC nor the client UI show you whether web scanning is active or not - at least I don't know how I could see it. All I found is the how to check article.

    I think add-ons can be disabled using the registry (or local security policy)

    Christian

    :1587
  • We are needing to disable the plugin because it IS causing problems for us.  When IE launches we see a "page cannot be displayed" error and then when we hit f5 or go to another site, the browser works.  But for our end users, it is too much.  If we disable it, IE works fine.

    It can be disabled using the registry, but this is not a simple solution.
    Looking forward to a better solution while working with Sophos tech for a better fix to the issues.
    :1620
  • The add-on doesn't cause any troubles at our site (guess I would have heard). We still had IE6 when the add-on was introduced and now it's IE8. I know this won't help you though.

    I'm not an IE expert but AFAIK the settings are stored in the registry. if you want to disable an add-on "globally" then in an AD environment it's done with a policy. In a workgroup environment it's using either the registry or a local policy (registry.pol in %SystemRoot%\system32\GroupPolicy\Machine).

    But of course the issues should be identified an fixed.

    Christian

    :1629
  • I did some testing on this following on QC suggestion and using the fake virus download.

    Within Enterprise Console and within the anti virus and hips policy.

    "Web scanner is:" if selected to off disables the plugin in IE.

    However do not be fooled as the plugin within IE is still saying enabled which is a big lie as it is disabled.

    You can test this by QC post, using the dummy file, turning the content scanner off within enterprise console. You need to give it some time for the machines to update the policy though.

    :1631
  • Oh and replying to QC question the reason we needed to turn off this feature is because it caused us problems on websites. Some things not loading stopping pops ups which are needed on some sites. The problems got better with the newer updates.

    We now have the Sophos WS1000 unit in place so we no longer needed this plugin running as the WS1000 unit does the same tasks at the gateway.

    :1632
  • Sheesh, these posts are from March 2010 and there are still issues with this. We too get pages not fully loading as well as multi-page printouts only printing the first page. Only in IE8 though, but we only tested in IE8.

    Disabling the Sophos Web Content Sanner add-on in IE8 fixes all of it. We went though each add-on to check if it was any of them and that is how we found it to be the Sophos one.

    Thanks for the thread! We will be disabling ours too.

    :9513