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

Scanning Exclusions problems

I set up some scanning exclusions in the global settings in the Sophos Cloud control panel, but they do not seem to be passing down to the clients.  Should these global exclusions show up in the list of scanning exclusions on the client side?

I also set up some on-access scanning exclusions on some of the clients locally.  A few days later, these exclusions seemed to have disappeared and are no longer in the list of on-access scanning exclusions.  Am I doing something wrong?

:56514


This thread was automatically locked due to age.
  • Hello,

    The exclusions being lost on the client is as expected.  After 2 hours the "Cloud" will send the policy down if it reported as differs which it would have done adding local exclusions.

    You should see on the client the exclusions under:

    "Configure" - "Anti-Virus" - "On-access scanning..." - "Exclusions" tab

    If they were realtime scanning exclusions.

    If you add an additional global exclusion are they seen? Adding a new item should cause a new policy to be rendered.

    If you add exclusions in a specific policy rather than the global exlcusion list do they appear?

    Are these realtime/on-access scanning exclusions, just to check your checking in the right place.

    The exclusions you add should end up in the file:

    C:\ProgramData\Sophos\Sophos Anti-Virus\Config\machine.xml

    if you just want to search for the exclusions.

    The only other thing to check is that there aren't any errors in the MCSClient log file but if it's getting the auto-comply I assume MCS is working.

    Regards,

    Jak

    :56515
  • These are real-time and scheduled scanning exclusions set in the global exclusions list, but they are not showing up on the client where you specified.  I have just added these same exclusions to the base policy.  I will wait to see if they are sent down to the clients. Thanks.

    :56574
  • So after I added the on-access scanning exclusions to the base policy and then forced the clients to update, the exclusions in both the global settings and the base policy started showing up in the exclusion list on the clients.

    :56575