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

    your (surprisingly small and therefore lacking some important details) screenshots don't prove that your installation suffers from the duplication blight. 

    this problem has already been patched

    Not only has it been patched for 4.5.0 and the code updated in later releases, the logic has been completely revamped for later versions. There are many details which might not apply to your suspected issue so I'll try to present it in digestible bites.

    1. The problem you're referring to was that computers "popped up" twice (or even more often) even if you deleted (note that this only makes the objects invisible) all instances, (all but) one appearing managed and connected,  one in the "correct" place and one in the Unassigned group.
    2. The current code is rather rigorous when "folding" computers (please see Computers with the same name, domain and user name are considered to be the same computer, while written for the Cloud product it applies to SEC as well (except for the User name attribute which doesn't exist there).
    3. 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?
    4. If you think you don't need the duplicates for further investigation use PurgeDB to get rid of them (caution: Depending on the parameters this might also take managed ones with it).
    5. Check for duplicates to recur. The following statement lists the n-plicate names together with the number of instances
      sqlcmd -E -S .\SOPHOS -d SOPHOS51 -Y 20 -Q "SELECT Name,COUNT(Name) FROM ComputersandDeletedComputers WHERE Deleted=0 GROUP BY Name HAVING COUNT(Name)>1"

    Please follow up here  

    Christian

    :48558
Reply
  • 0

    Hello AppliedMedical,

    your (surprisingly small and therefore lacking some important details) screenshots don't prove that your installation suffers from the duplication blight. 

    this problem has already been patched

    Not only has it been patched for 4.5.0 and the code updated in later releases, the logic has been completely revamped for later versions. There are many details which might not apply to your suspected issue so I'll try to present it in digestible bites.

    1. The problem you're referring to was that computers "popped up" twice (or even more often) even if you deleted (note that this only makes the objects invisible) all instances, (all but) one appearing managed and connected,  one in the "correct" place and one in the Unassigned group.
    2. The current code is rather rigorous when "folding" computers (please see Computers with the same name, domain and user name are considered to be the same computer, while written for the Cloud product it applies to SEC as well (except for the User name attribute which doesn't exist there).
    3. 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?
    4. If you think you don't need the duplicates for further investigation use PurgeDB to get rid of them (caution: Depending on the parameters this might also take managed ones with it).
    5. Check for duplicates to recur. The following statement lists the n-plicate names together with the number of instances
      sqlcmd -E -S .\SOPHOS -d SOPHOS51 -Y 20 -Q "SELECT Name,COUNT(Name) FROM ComputersandDeletedComputers WHERE Deleted=0 GROUP BY Name HAVING COUNT(Name)>1"

    Please follow up here  

    Christian

    :48558
Children
No Data
Unfiltered HTML