Avast 7.0 Home (Host checker Failed)

[haas_]

FYI,

Created a new JTAX case for this. Will let you know what shakes out. Real time protection error here with Win7.

[zanyterp_]

---

@meh wrote:
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

[meh_]

Thanks zanyterp. I've just PM'd you the JTAC number. Unfortunately the call is now closed. I gave up trying to get a resolution.

[haas_]

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.

[haas_]

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.



Software Download:

https://download.juniper.net/software/ive/releases/esap/2.1.7/j-esap-2.1.7.pkg

Checksum: 34D3F2121029B81300C27C17F6B10BD7 *j-esap-2.1.7.pkg



Release Notes:

https://download.juniper.net/software/ive/releases/esap/2.1.7/j-esap-2.1.7-releasenotes.pdf

[zanyterp_]

Thanks, haas, for confirming it is working for you!

[wuchang69_]

It is the middle of June. They still have not fixed this problem. Very frustrating situation.

[evcard_]

I updated to 2.1.7 and it is working for myself and other users with Avast 7 Free and Windows 7 without having to provide the Host Checker Admin Rights.

[PaddleFace_]

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/gears-integration/integrate-juniper-ssl-vpn-opswat-...

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.