Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 149072 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,

    as said, the logic in SEC tries "to do it right" while not imposing (too m)any restrictions. From an administrator's POV a duplicate is simply an unwanted entry in the database. At the same time you want that all your endpoints have their individual and easily recognizable entries (see changing the description of virtual machines and Computers in Enterprise Console appear to update the same record). 

    From the former article it's clear that using arbitrary descriptions when rebuilding will result in duplicates (indeed having the same name, description, OS version and domain/workgroup the endpoint should be matched to the existing entry) whereas the latter shows that cloning a computer which already has an identity in terms of SEC might result in "overlapping".

    ip address changes and network adapter changes

    shouldn't cause duplicates otherwise the same record problem wouldn't exist. Furthermore using DHCP without reservation would cause chaos. If this really were the cause I should have already more than a few duplicates.

    The question is are there new duplicates (apart from the unwanted but per application correct entries) or appears more than one entry of set to be active (i.e. the Last Message Time changes)? 

    Note BTW that -action=purge affects only entries with no associated alerts, events or errors.       

    Christian

    :57681
Reply
  • 0

    Hello LoXodonte,

    as said, the logic in SEC tries "to do it right" while not imposing (too m)any restrictions. From an administrator's POV a duplicate is simply an unwanted entry in the database. At the same time you want that all your endpoints have their individual and easily recognizable entries (see changing the description of virtual machines and Computers in Enterprise Console appear to update the same record). 

    From the former article it's clear that using arbitrary descriptions when rebuilding will result in duplicates (indeed having the same name, description, OS version and domain/workgroup the endpoint should be matched to the existing entry) whereas the latter shows that cloning a computer which already has an identity in terms of SEC might result in "overlapping".

    ip address changes and network adapter changes

    shouldn't cause duplicates otherwise the same record problem wouldn't exist. Furthermore using DHCP without reservation would cause chaos. If this really were the cause I should have already more than a few duplicates.

    The question is are there new duplicates (apart from the unwanted but per application correct entries) or appears more than one entry of set to be active (i.e. the Last Message Time changes)? 

    Note BTW that -action=purge affects only entries with no associated alerts, events or errors.       

    Christian

    :57681
Children
No Data
Unfiltered HTML