Epo agent not updating

22 Feb

servers in a new Vscan 8.5i group just weren't being updated and e PO wasn't communicating with the agent on lots of computers.

Turns out that there was duplication of computer names. the log looks oktry what prak saysit is obviously getting to the server as is displayedthe other log tells you more if you save the previous - it is more diagnostici assume you are still at default policy that it is 5 mins and i assume you have checked the obvious - of can it resolve back etc Thanks Prak, Terry I have searched the directory listing for this machine name and nothing is returned I don't think there are duplicate machines.

Obviously one or two have agent issues, but, for the majority seem to be communicating properly.

They register that tags have been applied for install, but after the install completes it does not reflect the installed software on the server side.

Which of the other logs should I try I have the following debug logs Frame Svc current/previous and Na Prd Mgr current/previous? Becasue the agent was included in the image all machines subsequently inherited the same agent GUID.I have remoted into these machines manually and checked the version numbers for these Products (VSE, Policy Auditor, HIPS, DLP, etc.) and they all list the most up-to-date information for those products, (example, HIPS then open up the Mc Afee Agent Status Monitor Console and select "Collect and Send Props", "Send Events", "Check New Policies" and "Enforce Policies" to ensure that the agent is able to communicate with the e PO server without throwing out any error messages. When I log back into e PO and check the computer name in System Tree, the computer still shows an outdated version of that product number (HIPS, for example).I deleted the key from the registry and restarted the framework service which automatically generated a new agent GUID.I found the resolution at the following link Hi Lawn Boy, That's great it took me ages to realise what was wrong something so simple..