@-red- wrote: You should be able to modify your existing policy. I ended up creating a new check to look for the msseces.exe, added it to my existing ESAP based AV policy, then changed the require option to either "Any of the above rules" or if you have additional rules you may want to apply, then use Custom and do something along these lines "allow=MSE-v4 OR Preferred-AntiVirus "....... This did the trick for me. I do wish Juniper would have proactively sent out an alert on this when the calls started pouring in. Thank -red- Also this is the latest from my Juniper contact on this. We currently have a ticket open for MS Security Essential 4.0. We expect to release support for it in the IVE sometime in June or July. Here is a KB for a workaround: http://kb.pulsesecure.net/KB22348 The KB is a general one for un-supported product. Please use the below mentioned process name instead of the one in the KB, and that should be it. Provide the workaround to do a check for the process "msseces.exe"
... View more