EPO 4.0 incorrectly listing clients as compliant

[Former Member]

Looking at the log, it appears as though there is no record of the DAT's in the catalog.z. I would also check which branch of the repository the DAT's are in (Current, Evaluation, or Previous) and the machines are updating from the proper branch. This can be altered in the agent policy.

Again, I suspect the machines that are updating are simply failing over to the McAfeeHTTP or McAfeeFTP sites.

Ultimately, you can also try deleting all the DAT's and Engines from the master repository (through the UI) and re-pulling everything into the Current branch.

[Former Member]

Is there a way to see if the Package.zip on the EPO server is not working?
What other reasons could prevent the Package.zip from getting to the clients.

Today the EPO repository is at 5796 DAT. My workstation is STILL at 5381.

I only pull into the Current branch, so there no other agets pulling from any other branch.

[Former Member]

Unfortunately you can't view the contents of the .zip file as it in encrypted.

I'm not sure why you agent's isn't updating. You can follow KB53736 to rebuild the master repository, but that's a bit extreme.

[Former Member]

OK I found the problem, When I looked in the registry, there was a key for Network Associates Vissusscan. Once I deleted that key it would update properly.

If this is whats wrong with the other 70 clients that won't update,  is there a way to do them all at once, without having to touch each PC?

[Former Member]

Unfortunately no. You cannot automate this change through ePO.