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
  • Have you possibly used cloning to deploy computers?

    There are at least two potential problems:

    1.) It's best to install SAV after the duplication, as every client has a unique ID which is stored locally. Cloning this ID will result in inconsistent behaviour of objects in the Console. There is a documented way to re-issue new IDs after cloning, but it is less work to just install SAV individually directly after the domain-join.

    2.) Based on the tool you use for deduplication (Sysprep, Newsid or the like) we have seen cases where the TCP/IP-hostname in the registry was not correctly updated when the new name was issued to the PC.

    Best regards,

    Detlev

    :4243
Reply
  • Have you possibly used cloning to deploy computers?

    There are at least two potential problems:

    1.) It's best to install SAV after the duplication, as every client has a unique ID which is stored locally. Cloning this ID will result in inconsistent behaviour of objects in the Console. There is a documented way to re-issue new IDs after cloning, but it is less work to just install SAV individually directly after the domain-join.

    2.) Based on the tool you use for deduplication (Sysprep, Newsid or the like) we have seen cases where the TCP/IP-hostname in the registry was not correctly updated when the new name was issued to the PC.

    Best regards,

    Detlev

    :4243
Children
No Data