Can you please confirm me that the last ESAP 2-3-4 doesnt support the avast! Free Antivirus 8.x but only 7.x ?
Can you please give me the roadmap to include this version into an ESAP?
Thank you in advance
I've checked the release notes for 2.3.4 and avast! free antivirus 8.x is not supported yet. However, it should be included in the next release 2.3.5 which is released in a few days. When available, I will review the release notes and update the forum post accordingly.
Same concern here, release 2.3.5 ASAP please for support of avast! Free Antivirus 8.x
Avast! Free AV 8.x is listed in the supported platforms for ESAP 2.3.5: http://www.juniper.net/techpubs/software/ive/esap/releasenotes/j-esap-2.3.5-supportedproducts.pdf
The package can be downloaded at : https://download.juniper.net/software/ive/releases/esap/2.3.5/j-esap-2.3.5.pkg
Updated to ESAP 2.3.5 and Avast 8 does get detected but with Windows 7 it requires you to set the Host Checker to run as Administrator other wise it fails to detect that the Real Time Protection is Enabled.
I know this was an issue with Avast 7 on Windows 7 when it was first released and they stated that a workaround was to disable and re-enable the real time protection and it would then detect it correctly but that didn't work when the issue existed on Avast 7 and didn't do the trick either on Avast 8.
Will there be a fix for this at somepoint?
Yes, ESAP 2.3.5 doesn't work with avast 8. Is there any workaround solutions?
ESAP 2.3.5 does not work with avast! Free Antivirus 8 despite the fact that it is in the list of supported antivirus for ESAP 2.3.5
Juniper, you guys gotta wake up now...
Has anyone made any progress regarding this? My client is running avast! Pro 8.x and the error message is that RTS isn't enabled, but in fact it is. ESAP version used now is 2.3.6.
This issue should be resolved in ESAP 2.3.8 which is tentative for Mid-May.
That is good news to hear that an official fix is coming to correct the issue of detecting the status of the Real Time Protection.
For now I have just been defining the Host Checker to Run as Administrator as that seems to be the only work around to get it to correctly detect the status of it and allow any remote PCs that choose to use that product as their Anti-Virus.