Showing results for 
Show  only  | Search instead for 
Did you mean: 
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 11 of 12

Re: Duplicate entries

Essentially the order of operations will turn out like this - when a machine sends up a property package to ePO, ePO will first check the GUID attached to the property package. If there is a match, we're done. If there is no match, it'll check MAC address - same deal as before and if it matches, the inbound properties will be associated with the matching MAC address node.

If neither of these can match, we'll check for machines matching the computer name - however, in this case, that is only for "unmanaged" nodes matching the system name in the tree. For example:
System name: EXAMPLE

When EXAMPLE communicates to ePO, with a new GUID and unique MAC address it will be unable to match to any existing system in your database based on those two criteria - then, it will check for any unmanaged entries (for example, added manually or via an AD sync) also named EXAMPLE. If it finds one, it'll match up with that unmanaged EXAMPLE system, essentially turning that previously unmanaged node into a managed node as far as ePO is concerned.

Now, if instead of finding an unmanaged system named EXAMPLE it finds a managed system named EXAMPLE (with a different GUID and MAC address associated off course) it would not match to this system and instead create a new entry, also named EXAMPLE, but with the new GUID/MAC address. This is designed as such to help out a bit in case the environment has machines with the same name throughout the environment (which isn't as uncommon as you'd think).

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 12 of 12

Re: Duplicate entries

Hi vnaidu,

An example of what ‘msmiley’ mentions would look something like the below.

I'd ask that you simply look, at one of the clients that are seen to be 'duplicated'
Access the Registry and look for entries similar to the below (The below an example, your version detail etc would different):

  • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\ENDP_AM_1020

Includes the key: "Version - REG_SZ -" - is the unwanted version and not installed.

  • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\ENDP_AM_1060

Includes the key: "Version - REG_SZ -" - is the active install and the wanted detail

If this is true and you have more than one, that is an issue.

Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see:

Only remove/delete the unwanted entry. (the older version not installed version).
From the above registry hives that would be

Was my reply helpful?

If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community