Moved to ePO for better handling - Moderator
We had the same scenario and we are dealing with that with 2 automated task.
From 6am to 6pm we have the following task running every hour.
Delete duplicates machines from system tree at hours o'clock
Synchronizing from AD at half past hours
With that we make sure we can have duplicates for less than 30 minutes..
That was what i was thinking of doing, but as some are away from the office and potentially offline until the next day, with no way to wake up the agent I'm just concerned that this could lead to undesireable behaviour of the Encryption system.
Thank you for the response. i will chat with support as well and maybe this needs to be a product improvement for the next patch release of the agent.
Tasking to the McAfee presales guy here in NZ and he emailed this to me
'New GUID’s are created based on a unique combination of elements per machine – under Server Settings – Detected System Matching – you can define the list of elements. Might pay to look for a different combination to identify unique machines.'
I'll check this out tomorrow as it may help solve your duplicates too.
Hi jose , please follow :
Clients communicating with ePO via VPN disappear from ePO tree
Technical Articles ID: KB52949
By adding the first six characters to the ePOVirtualMacVendor table, you're telling ePO to skip the MAC address check for any machines whose MAC address starts with those six characters:
this means that each machine will get its own entry in ePO, as it shoud
after performing this KB article, are there any other possibilities for having duplicates? If I am syncing with Active Directory with the option (Move systems from their current System Tree location to the synchronized group). Shouldn't the duplicate stay in Lost and Found?
Let say the Mac Address for the virtual nic is something static (ex. XXXXXXXXXXXX). What becomes the new unique value? Computer name? Agent GUID?
I don't see Detected System Matching under ePO 5.1 server settings
Unfortunately the comment about how the GUID is created is incorrect. The detected systems matching criteria are a function of RSD, and are not relevant in the situation we're describing here.
This is a complex area of ePO that seems to create a lot of confusion. I'm in the process of writing an explanation which will hopefully clarify things - bear with me.