04-21-2012 01:07 PM
I was hopefully that Avast 7 would be functioning correctly when I saw the release notes for 2.1.3. I tested it after updating to the latest ESAP, it seems to detect the product just fails to detect real time protection even though all the real time shields for Avast 7 are enabled. Hadn't thought to test it on an XP box to see if it could detect correctly. I had no issues at all with the same Windows 7 box and Avast 6.
04-21-2012 06:25 PM - edited 04-21-2012 06:26 PM
There's a workaround to make this work with Avast 7. I'm not happy with this workaround so I still have the call open with Juniper. Not sure what has changed from Avast 6 to 7.
"The Current implementation of OPSWAT needs UAC elevation and administrator's privilege.
The workaround is to turn run as administrator on for dsHostChecker.exe, which is
present in the HC installed folder (C:\User\<username>\AppData\Roaming\Juniper
04-22-2012 06:22 AM
Glad that there is a temp workaround to resolve the issue, but with having so many remote users as well as contractors connecting into my SSL VPN with varing AV Products, I hate having to offer this as a fix for it failing the Host Checker. Especially seeing Avast 6 Free worked without an issue. Certainly will open a JTAC on Monday regarding this.
04-22-2012 01:15 PM - edited 04-22-2012 01:16 PM
04-24-2012 07:50 AM
Created a new JTAX case for this. Will let you know what shakes out. Real time protection error here with Win7.
05-03-2012 09:44 PM
Can you believe I've been told by Juniper I now have to log an enhancement request through my reseller. Although this used to work fine in Avast 6 they have no intention to rectify it in Avast 7 and are regarding such a change as an 'enhancement.' I expressed my dissatisfaction to the juniper tech as that is an impractical workaround in my situation, but it got me no where. I'm finding more and more reasons to replace this product with something else.
you should not have been told that; is the case still open? can you send me the number via PM so I can track this internally to try and make sure this does not happen further?
new products are added by us working with OPSWAT and letting them know what is needed; the newest ESAP shows it _should_ be supported:http://www.juniper.net/support/products/esap/
i am sorry you have not had a good experience with the appliance; is there anything i can assist with (please feel free to PM me).
unfortunately, there can be unexpected failures in the real world that are missed in the lab and work with JTAC must be done to work through these
05-15-2012 12:04 PM
Here is the latest from my JTAC case.
05/10/12 09:39:53 Hi Jason,
Another update. There appears to be a problem with the method that Avast has provided for Opswat to run the check. Opswat is working with Avast to resolve the issue. I will update you as soon as there is more to share.
06-07-2012 08:17 AM
I have tested this and it appears to be resolved. See below.
The latest ESAP version just released should contain the fix for the Avast AV 7
products. Here are the relevant links.
Checksum: 34D3F2121029B81300C27C17F6B10BD7 *j-esap-2.1.7.pkg
04-08-2014 06:30 PM
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.
The 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 Hostchecker-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.