I started getting this with out newly imaged machines. They are Windows 7 and we are using the built in sysprep utilties for Win7. I am guessing for me, that is where the problem is. I am going to test deleting that registry key to see if they come back clean, however that solution is a hassle to have to do on every machine we have.
What we did is not install the agent on the "image". we did a post install of the Mcafee agent after the image deployed. then it can elimiate the chance of duplicate AgentGUID.Message was edited by: KelvinCheng on 7/28/11 10:54:13 AM GMT+08:00
I had a similar problem with servers being deployed with the same Agent number.
I now have a server task to run the report indicated earlier for machines with high sequence errors and it will blacklist these ID's. Then the task will reset all these sequence error counts.
When the ID is blacklisted the next time the agent checks in, it will be asked to generate a new ID. If two machines have the same ID they will then start reporting in OK as they will now have separate ID's. Solved my problem straight away! now just let it run once a week to keep on top of it.
hope this helps!
Have you tried checking your workstations' "Sequence Errors" ?
1) there's a query report showing "Systems with High Sequence Errors"
this is often an indication that some systems are using the same GUID (should be called pseudo-Unique ID)
With that report, check that you don't have many systems with the same GUID - this happens especially when using imaged machines.
Check columns such as "Last Communication (date)" vs. "Last Sequence Error" and decide whether you want to
This is something that ought to be checked every once in a while. I haven't gotten to letting the system decide automatically what to do.
hope it helps