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

    so I ended up running the command PurgeDB.exe -action=purge -category=computers -HistoryLengthInDays=90

    Result: 1941 rows affected- It seems though some duplicates were cleaned out by this.

    I tried to track down commonality factors today and it seems that 75% of the machines with duplicates are laptops, which tells me that ip address changes and network adapter changes are being translated incorrectly by the console, resulting in duplicate entries. Our laptops have wireless capability, ethernet capability, and VPN capability...each of which has an associated physical or virtual adapter.

    About 25% of the duplciates are desktops, but all of the duplicate desktops I saw had different computer descriptions. This tells me that the desktops were rebuilds...yet again, the console is confused.

    Is there any chance for some sort of feature implementation either in PurgeDB, or the consonle itself that would allow for specifically finding duplicate entries, comparing them, and throwing out whatever duplicate has been offline the longest (perhaps based on a threshold like history in days) If this were an option I would set up a scheduled task and hopefully rid myself of this duplicate issue!

    :57664
Reply
  • 0

    so I ended up running the command PurgeDB.exe -action=purge -category=computers -HistoryLengthInDays=90

    Result: 1941 rows affected- It seems though some duplicates were cleaned out by this.

    I tried to track down commonality factors today and it seems that 75% of the machines with duplicates are laptops, which tells me that ip address changes and network adapter changes are being translated incorrectly by the console, resulting in duplicate entries. Our laptops have wireless capability, ethernet capability, and VPN capability...each of which has an associated physical or virtual adapter.

    About 25% of the duplciates are desktops, but all of the duplicate desktops I saw had different computer descriptions. This tells me that the desktops were rebuilds...yet again, the console is confused.

    Is there any chance for some sort of feature implementation either in PurgeDB, or the consonle itself that would allow for specifically finding duplicate entries, comparing them, and throwing out whatever duplicate has been offline the longest (perhaps based on a threshold like history in days) If this were an option I would set up a scheduled task and hopefully rid myself of this duplicate issue!

    :57664
Children
No Data
Unfiltered HTML