Netshield 4.5 client refuses to believe it is out of date

[Windexx]

Yes, I know that NetShield will soon no longer be supported by McAfee and I must upgrade. This is in the works but I have to get ePO out there first. Mostly we are running VS7 but still have a bunch of NS left.

On a couple servers running NS4.5 I did a superDAT rollback to force engine/DAT to a lower version (this is working in our lab environment before deployment). Communications to master is fine but the machine believes itself to be up-to-date. All repositories have newer files (with legacy enabled) and the SDAT does not even exist in the repository anymore. I've been back and forth with tech support and we still haven't figured out what is causing the NS clients to be so stubborn. All logs show that it checks and then sees itself as up-to-date. Even added the extra logging value to the registry but doesn't give any clues. If this was one machine then I would say an anamoly but both NS boxes I tested. It was first thought a corrupted task but that is now ruled out. Both boxes been rebooted. Repositories resynched. Oh, and btw the VS boxes updated fine.



Any ideas?

 

[jfp23]

I have had this happen with both Netshield and VS, what has worked for me on some machines is to manually run a forced superdat update on the machine. Than it would start working properly on the next update cycle.

 

[Windexx]

I'll give that a shot...thanks.

 

[Windexx]

Just let anyone who is still archaic like me with the NS4.5 product. I forgot to post my own solution.

Rollbacks are not possible with NS4.5 for DATs or for engines. ePO manages the update using the update task for NetShield. I originally customized a domain startup script for the installation of the ePO and disabled the current upgrade and scan task. This was due to custom install scripts to set up tasks way before ePO. I also deleted the update task which was my big mistake. In our environment prior to ePO NS4.5 was updated by using SDATs and therefore was an upgrade task. I now leave the update task alone in the registry and just disable the registry key for the schedule to be enabled. All works okay now.