This message was deleted.

We have not but may be considering the same thing (currently using cylance). I did briefly test in our app layering)/user layer environment and seemed to work pretty well without much extra work. I didn't get too much into the fine tuning but the scheduled scans SAID they completed in 5-6 minutes but actually took about 25-30 so that was a weird anomoly

Did you have to run the scanner to process the entire image before sealing it up?

I'm not sure if it's needed not I did make sure to do a full scan on my published image before sealing/deploring just to make sure it didn't trigger a full small on the vda's and seemed to work on our limited tests

The physical desktop team is moving there. However. It's not vetted for vdi yet. But I suspect it's coming my way. We had trend and also had to run a tool before sealing the master image.

Yeah, I'm used to the TCacheGen tool for Trend. I used to love them, but my last 3 upgrades have been flaky as hell, including the most recent one today, which is still down.

Oh yea that's what is it. I ditched it after it killed my logins.

We haven't had a single issue with the client, mind you. That part has been great. The server piece, though...

Have you seen this? https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-antivirus/deployment-vdi-microsoft-defender-antivirus

@Cory Zaner just started implementing the doc above

I have seen that, but as is this case with everything else Microsoft, I'm 100% positive that they've left items out of the documentation, allowing places like this to fill in the gaps. 🙂

I had to add the exclusion for fslogix and the container location. That fixed my ost issue