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

Defaul policy being used when it isn't supposed to be.

I have a couple machines where the 'Default' policy is being used when it isn't supposed to be.  How do I fix this, and how can I identify other machines doing this?  The console says 'same as policy' in the Policy compliance column, which I guess means it is using a valid policy ... just not the right one!

using Sophos Antivirus 9.0.5, and Enterprise console  4.0.0.2362

:4410


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

    which Default policy and how did you find out?  Computers are in groups and to the groups certain policies are assigned (which could also be the Default policies). So - which type of policy (updating, AV, ...) isn't correct? Same as policy means that the client reported the policy it's using is identical to the one received from SEC.

    Christian

    :4419
Reply
  • Hello nealbscott,

    which Default policy and how did you find out?  Computers are in groups and to the groups certain policies are assigned (which could also be the Default policies). So - which type of policy (updating, AV, ...) isn't correct? Same as policy means that the client reported the policy it's using is identical to the one received from SEC.

    Christian

    :4419
Children
No Data