MSD installing on clients outside of the policy
We have one of our 6 active MSD policies installing on clients outside of the filter applied (about 1k so far). What we do here is create a master filter for each deployment then add sub filters as inclusions. The sub filters are built either by query (name ranges) or CSV so nothing out of the norm. The master filter and each of the sub filters DO NOT contain any of the clients that it incorrectly went to and neither does the policy. One of the clients that got the MSD was mine so I was able to check the logs, and know (since I built the filters) that my client ID is nowhere near the ranges that have been used in the filters. I've also made sure that there are no DNS reated issues and no duplicate GUID's.
We have an open case with Symantec on this, and like I said we have 6 active policies all built the same way and this is the only one going off the reservation. Any thoughts or ideas are greatly appreciated.
SMP 7.1 MP1 SP2