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

    Not really sure where that leaves me on bulk cleaning these up. At this point I've received the best results from deleting both entriest when a duplicate is present, re-syncing the OU with Auto-deploy disabled, either waiting, or reploying the client to the re-detected machines.

    From what you've described this leads me to believe that a new IdentityTag is being prematurely created during an active directory sync. Perhaps the install has already initiated and created the new identifier, but then aborts when an existing client is discovered? I really have no idea...if active directory syncs could operate indepdently from auto deployments it might be easier to narrow this down.

    :57420
Reply
  • 0

    Not really sure where that leaves me on bulk cleaning these up. At this point I've received the best results from deleting both entriest when a duplicate is present, re-syncing the OU with Auto-deploy disabled, either waiting, or reploying the client to the re-detected machines.

    From what you've described this leads me to believe that a new IdentityTag is being prematurely created during an active directory sync. Perhaps the install has already initiated and created the new identifier, but then aborts when an existing client is discovered? I really have no idea...if active directory syncs could operate indepdently from auto deployments it might be easier to narrow this down.

    :57420
Children
No Data
Unfiltered HTML