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

The antivirus 'default' policy is the one I speak of.  We started getting false positives on an app that we were scratching our heads on since we knew we had approved it.  Then we noticed one person was getting email aletrs about the false virus that wasn't supposed to.  Turns out the default policy did not list the 'approved' exe, and default also included the email address that was not in the other policy we created.   To confirm our theory, we added my email address to the default policy and reapplied.  Near as we can tell we have *nothing* using the default policy.  So if I start getting antivirus alerts in my email today, it will confirm what is going on.  Will know more in a few days.  Maybe making a change to the default policy is enough to cause everything to synch up again.  Cross fingers!

This false positive, which not everybody has, is really the only clue about the use of the wrong policy, which is why I can't tell what other machines are using.

The antivirus 'default' policy is the one I speak of.  We started getting false positives on an app that we were scratching our heads on since we knew we had approved it.  Then we noticed one person was getting email aletrs about the false virus that wasn't supposed to.  Turns out the default policy did not list the 'approved' exe, and default also included the email address that was not in the other policy we created.   To confirm our theory, we added my email address to the default policy and reapplied.  Near as we can tell we have *nothing* using the default policy.  So if I start getting antivirus alerts in my email today, it will confirm what is going on.  Will know more in a few days.  Maybe making a change to the default policy is enough to cause everything to synch up again.  Cross fingers!

This false positive, which not everybody has, is really the only clue about the use of the wrong policy, which is why I can't tell what other machines are using.