I would probably do a search for the two machines with the same name, then look at the last contact time on them, delete the one with the oldest contact time...
If they are both the same, then I would go for what you are thinking, delete them both and wait for it to come back in again.
The PC has returned!!!
As before showing duplicate in non-compliant list.
Did a search on computer name, which returns only 1 PC!
Any other ideas?
It could be a "type 24" machine. This issue occurs when you delete a machine from the EPO system tree and select the "remove agent" option. When this is done the machine's entry is left in the DB waiting for that machine to report back so it can send an uninstall command. If the machine never reports back to that entry then it is never completely removed from the database. See KB52112 for instructions on how to correct this:
Cheers, already tried that one. The PC is listed once in the sql database and once when I do a search for it, it only shows 2 in the 'non-compliant' report, strange thing is if I click on the tick box next to one of the duplicate names it will highlight both if you know what I mean. It's shame as it's the only PC that is non-compliant in our organisation at the moment. I think it may have something to do with upgrading the agent and VSE on the PC.
Out of curiosity what is is showing non-compliant for? Do both entries show the same item as being "out of compliance" (dat, engine, vse version, etc)? Are you using HIPS?
You could try deleting the machine from EPO completely (both entries) and allow it to re-populate. If its a corrupt entry in the DB that should clear it up.
It's because the dat won't update on that PC, the log file states that the update starts then it never completes, so subsequent tasks can't be run. Not using HIPS. Have already tried deleting, only need to select it once and duplicate gets selected too, but comes back with 2 entries again. I once managed to get the PC compliant, and it only listed itself once in the compliant list. May contact McAfee about it.
If you drill down to this machines properties (or look at them in the compliance report) does it list two different version of VSE as being installed (even though the client only has 1 version installed)? I've seen that cause this issue in the past.
Interesting, yes it does show 2 instances of VSE, but both the same version!
Is there a fix available do you know?
Have a look at the 'HKLM\Software\Network Associates\ePolicy Orchestrator\Application Plugins' reg key on the offending machine... have you got two VirusScan subkeys under it (that start VIRUSCAN)?
If so, try this:
1) Uninstall VirusScan from the machine
2) Check that reg key again: one of the subkeys should have disappeared
3) Delete the remaining VIRUSCAN subkey
4) Reinstall VirusScan
You should now only have one VIRUSCAN subkey - that should hopefully fix it.