ePO incorrectly reporting VirusScan not installed

[cottonpants]

I have a group of about 30 computers, all of which were created by the same image containing VirusScan 4.51. All except 3 are showing the software as being installed. I have verified that the 3 'rogue' workstations do in fact have the software installed and running.

Any ideas why they would be reporting no product installed?

The LastUpdate field for the workstations is also current.

Thanks in advance. (running ePO 2.51, workstations are Win2K SP2)

 

[VictorySabre]

I've seen this problem before as well. I don't know the official reason, but in most cases, I was able to resolve it by performing the following steps. (You may want to test this out first)

Try #1:
Uninstall ePO Agent and reinstall. Does it work?

Nope?
Try #2: (Done locally on the problem box)
1. Uninstall VirusScan
2. uninstall ePO Agent
3. Reboot
4. Open REGEDIT
5. Browse to HKEY_LOCAL_MACHINE\Software
6. (Assuming you don't have any other NAI products) Delete the Network Associates key.
7. Reboot
8. Reinstall VirusScan (May require another reboot)
9. Reinstall ePO Agent

I've done this on several PCs and they have resolved nearly every one that acts up. Make sure you have a backup (and best tried on a test PC) before trying the steps above.

 

[JCA74]

I would suggest trying a Wake-Up Call using the Full Properties option. If that doesn't fly delete or rename the fullprops.ini file and try the wake-up call with Full Properties option to generate the new fullprops.ini

 

[AVChap]

BTW, before you can do a Wake-Up Call with Full Properties, you would need to install HotFix 2 for ePO 2.51. This is NOT available without the hotfix. Unless you upgrade to version 3.0.

HTH,

AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation

 

[cottonpants]

Thanks for your suggestions!

I don't have the FullProp option so I guess we don't have the hotfix yet.

I did try rename the fullprop.ini and let the wake up recreate it, which it did, but still no joy.

I am very hesitant to get into all of this uninstalling/reinstalling, because it looks like I've got about a 10% failure rate of detection, and that'll turn into a lot of (re)installing once we continue our roll out. So if I could find a funky reg value or something easier I'd be really happy.

I suppose I might have to resort to throwing myself into the McAfee support black hole...

Thanks again for your help...