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

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
  • Hi Christian, I'm looking for some clarity on your reply. I too have several duplicates. I have tried deleting both instances...when they come back they are automatically redeployed to. At this stage I only notice 1 entry.  Somepoint after the synchronized deployment the machine shows a duplicate again. One in unassigned, and another in the correct AD location.

    As you have apparently unmanaged duplicates - did they appear out of the blue or were they added by one of the find/import/discover methods? If so, which of the "main attributes" (ComputerName, DomainName/Workgroup and OS) are set for them? Have the "live" ones been protected from the console or by other means?

    I'm not following your comment regarding main attributes. I'm also a tad confused on PurgeDB. Does that command find duplicates automatically and delete? Do you have to specify the name of individual duplicates? I've never tried PurgeDB...I remember attempting to use it once but it apparently only likes 32bit OS's, and the server running the database is 64

    :57398
Reply
  • Hi Christian, I'm looking for some clarity on your reply. I too have several duplicates. I have tried deleting both instances...when they come back they are automatically redeployed to. At this stage I only notice 1 entry.  Somepoint after the synchronized deployment the machine shows a duplicate again. One in unassigned, and another in the correct AD location.

    As you have apparently unmanaged duplicates - did they appear out of the blue or were they added by one of the find/import/discover methods? If so, which of the "main attributes" (ComputerName, DomainName/Workgroup and OS) are set for them? Have the "live" ones been protected from the console or by other means?

    I'm not following your comment regarding main attributes. I'm also a tad confused on PurgeDB. Does that command find duplicates automatically and delete? Do you have to specify the name of individual duplicates? I've never tried PurgeDB...I remember attempting to use it once but it apparently only likes 32bit OS's, and the server running the database is 64

    :57398
Children
No Data