I found the answer so I hope it helps anybody else. There is a bug in the AV check that OPSWAT provides to Juniper OR there is a bug in how Trend is updating 64-bit machines (or it's just us...)
Here is the problem:
the AntiVirus checker is searching the registry for TrendAV information and if it finds this key on a 64bit machine:
HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion
It will stop searching and error out. The problem is that on 64-bit machines, the keys are really in
HKLM\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion
The AV check knows how to find this 64-bit location but it errors out if the previous key already exists. (ie: On first failure, it boots out). What I think is happening is that some Trend update is stuffing a blank registry entry in the 32-bit locationÓ and that is hosing up the OPSWAT AV checker. (Which should hose it up for all OPSWAT users, not just Juniper).
I was able to successfully delete
HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion
Along with its subkey (Misc.) and the AVCheck now passes.
(more research - it looks like only the Misc. key needs to be deleted). These are blank keys anyway, and I've noticed no other problems. Now, some keywords for google: Trend OfficeScan problem 64-bit Juniper OPSWAT host checker
