Lets see if I can answer all the questions:
We upgraded to ESAP 2.1.3 (which is now released) at the request of JTAC for this issue.
We've tested this with Trend Micro Officescan 10.6 on WIndows 7, Avast 6 on Windows 7, various flavors of McAfee and Microsoft Security Essentials (contractors) and Trend Micro AV 1.5 for OS X 10.7. All fail the AV Check.
We've tested a single AV policy (checking trend), a larger policy with lots of products and a policy with all the products in the ESAP. All failed.
Trend was not upgraded at all, except for the normal signatures.
We are working with JTAC, although it's taking a bit longer than we expected to resolve. Hopefully ghuber can join in on the caes and help solve the problem.
I will pm tbehrens to test against his lab system too. Thanks!
Thank you, ghuber & jspanitz.
ghuber: if you test with a specific AV, do you see failure as well? I am aware of an issue with using the "all AV" components from an upgraded system; however, we have not seen this happen in our labs yet (that I can tell). Also, are you able to work with JTAC on this or have you already rolled back to the working system?
I was able to hook up with tbehrens and tested against his lab. Everything worked as expected and our system passed the host checker AV check. So the problem is definitely on our box.
We may revert this weekend if JTAC doesn't have an answer by then.
Many thanks to tbehrens for his assistance!
Have the same problem with 7.2R1 esap 2.1.3 or 2.1.2 on win7 (x32 and x64).
Done the test with Mcafee (numerous version)
All fail the antivirus check....
I am sorry to hear that you are experiencing an issue with this. There is an issue with 7.2 and Host Checker and downloading updates that we are currently investigating and working toward a solution; it is possible that you are experiencing this-please see KB23478 for more information.
If you are not meeting this requirement, please open a case with JTAC for further investigation and work to determine why the checks are failing.
Thanks for the quick response, the problem seems to be exactly was is describe in KB23478.. Will wait for the fix today or tomorrow.
You are welcome; glad to be of assistance.
Due to a last minute failure found after this KB was initially published, the fix will not be available this week; the new date on that should be for next week (the week of 16 April 12).