Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 149064 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Duplicate PC names in enterprise console

CDC

I've noticed after upgrading the Enterprise Console to version 4.5 and AV to 9.5 that duplicate PC names have started appearing.  This normally happens after a PC's AV has either not upgraded properly or has stopped updating so i've uninstalled and it and then redeployed it down.  One of the PC names will say its connected & managed (although not properly as the 'up to date' colum is blank and you can't deploy any policies down)  whilst the other will be greyed out.

I've tried deleting both entries in the Enterprise Console in an attempt for the AD sync to sort it but they both re-appear again.  Is this a known issue with the 4.5 upgrade?

:4224


This thread was automatically locked due to age.
Parents
  • 0

    Hello LoXodonte,

    let's start with the easier ones.

    PurgeDB

    has no intelligence whatsoever, in particular it has no "holistic" view.

    attributes

    SEC has to identify new endpoints, to distinguish between different ones and to recognize known ones. Furthermore one should be able to match a computer in SEC to a certain (physical or virtual) endpoint. For deployment from the console you need some attribute with which you can find (and contact) a computer on your network. I'm not going into the details here.

    At install time the endpoint creates an IdentityTag which is used to recognize it even if its name changes (that's why certain procedures must be followed if you clone from an image - otherwise all clones are folded into one entry). OTOH an as yet unknown IdentityTag does not necessarily indicate a new endpoint - SESC might have been reinstalled or the computer reimaged. Thus if an endpoint presents an unknown IdentityTag but the combination of Name, Description, OS and Domain/workgroup matches an existing entry no new computer entry is created but the IdentityTag in the existing is replaced.

    So - the duplicate entries differ at least in the IndentityTag, the question is: What else could make them unique?

    Christian

    :57419
Reply
  • 0

    Hello LoXodonte,

    let's start with the easier ones.

    PurgeDB

    has no intelligence whatsoever, in particular it has no "holistic" view.

    attributes

    SEC has to identify new endpoints, to distinguish between different ones and to recognize known ones. Furthermore one should be able to match a computer in SEC to a certain (physical or virtual) endpoint. For deployment from the console you need some attribute with which you can find (and contact) a computer on your network. I'm not going into the details here.

    At install time the endpoint creates an IdentityTag which is used to recognize it even if its name changes (that's why certain procedures must be followed if you clone from an image - otherwise all clones are folded into one entry). OTOH an as yet unknown IdentityTag does not necessarily indicate a new endpoint - SESC might have been reinstalled or the computer reimaged. Thus if an endpoint presents an unknown IdentityTag but the combination of Name, Description, OS and Domain/workgroup matches an existing entry no new computer entry is created but the IdentityTag in the existing is replaced.

    So - the duplicate entries differ at least in the IndentityTag, the question is: What else could make them unique?

    Christian

    :57419
Children
No Data
Unfiltered HTML