I don't have a huge user base (yet) - we're just gearing up - so I'm not sure if this is a one off type client-side quirk (cl is on Vista so anything is possible) or a juniper side problem recognizing this antivirus product in general.
Anyone else have trouble getting hostchecker to recognize it?
Just curious. thx!
We have had this problem (with other AVs as well as Norton 360) for months but seem to be getting on top of it with OS 5.5R5 and ESAP 1.3.3. Two caveats: we've only just implemented this update, so it'll take a few weeks to verify and our user base is on Windows XP. (We were running 5.5R1 and ESAP 1.3.1 with no luck.)
Hope that helps!
I believe you won't fix this issue with Norton 360. I just had a Client inhouse today with Norton 360 v2.x.
Was my first time to see the Client Side of the effect with Norton 360.
I could see how hostchecker always tried to download but couldn't be installed, IMHO blocked by Norton 360.
The Download of the hostchecker and the AV-detection files kept on an on to download, always again. I stopped it after about 30 minutes. Probably some of those tampering protection features of Norton 360 (and even other Internet-Security-Suites) discard the the installation of hostchecker an the ESAP dll's (I have newest ESAP 1.3.7 installed - which knows even Norton360 v2.x) So - this looks like a dilemma: no hostchecker installed, no detection of norton 360......., but with Norton 360 running, installation of hostchecker fails......
I have not tried to install hostchecker on the target system manually yet - perhaps this will help ....., or the user (or his admin) has to make an checking exception in Norton 360 for the installation directory of Hostchecker (as described in the IVE manual for client-side changes...)
perhaps this can help in some way...