I have a case right now where the agent is not detecting a certain build correctly (ie: detects 11.0.2010.7 incorrectly, but when you update the app itself it detects 11.0.3001.2224 fine).

Looking into it now, so not sure the cause, but just to make you aware of it.

Nate

Hennessey, Sean wrote:

Hi all –

Sorry if this has already come up on list – has anyone had to deal with this product? It’s not falling under my rules for Symantec Corporate but it is, apparently, the update for it. It’s failing the checks I have for SCAV and I’d like to catch this one **before** computer support roles it out for a change… J

- Sean

----

Sean Hennessey

Networking and Information Security Systems Administrator

The University of Portland

Reply via email to