We could use this as well, one of our contractors use this on their laptops and they updated over the weekend.. If there is a ticket open, can we add ourselves to it or do we need to open another ticket?
Yes, you would need to open a new ticket so the impact can be tracked based on the number of tickets received
This will be fixed in ESAP2.1.5, which will be released tentaively on May 18th.
The date may vary a day or two.
Hope the above helps.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
Just updated ESAP. Looks like ESAP 2.1.5 fixes the issue. And we didn't have to wait months. Yay Juniper / Opswat!
We at OPSWAT are aware that consumption of OESIS Framework updates by Juniper (and other partners) for inclusion in Hostchecker features released to end customers can be painful for Juniper and for its customers.
We are committed to releasing OESIS more frequently (currently weekly, with a goal of daily updates by end of 2014) and to make it easier for Juniper to validate OESIS releases and incorporate into their packages.
In addition, OPSWAT recently released a configurable client, GEARS, which auto-updates OESIS and stores endpoint device compliance status in the Windows Registry or Mac OS p-list.
Host Checker can access and use this information through implementing either a (1) the default Antivirus Rule or (2) a custom process / registry checks.
A Host Checker-GEARS configuration guide is posted at http://files.cdn.opswat.com/www.opswat.com/files/g
Using GEARS together with Hostchecker should reduce the number of issues you encounter with your end users being blocked due to their running an unrecognized endpoint security application.