Endpoint Protection

 View Only

  • 1.  Avoid problem of duplicate Hardware IDs

    Posted Oct 12, 2012 01:09 AM

    Hello,

         We are facing the problem of duplicate Hardware IDs in some PCs.I have already got the solution of this problem.

        I want to know the reason of this problem? Why this problem occurs after using Image OS? Also, can anybody please suggest any method by which this problem can be avoided in further PCs installation?



  • 2.  RE: Avoid problem of duplicate Hardware IDs

    Posted Oct 12, 2012 01:14 AM

    Why this problem occurs after using Image OS? Also, can anybody please suggest any method by which this problem can be avoided in further PCs installation?

    This problem occure because same hardware id are available in another system.

    If you prepare Image os you can follow this steps

    How to prepare a Symantec Endpoint Protection 12.1 client for cloning

    http://www.symantec.com/business/support/index?page=content&id=HOWTO54706

     

    How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 clients

    http://www.symantec.com/business/support/index?page=content&id=TECH163349



  • 3.  RE: Avoid problem of duplicate Hardware IDs

    Broadcom Employee
    Posted Oct 12, 2012 03:31 AM

    Hi,

    Q. Why this problem occurs after using Image OS? Also, can anybody please suggest any method by which this problem can be avoided in further PCs installation?

    --> Each SEP client will have unique hardware id, if SEP is a part of clone image then same hardware id will be copied on each machine and result in duplication of records.

    Duplicate Hardware IDs result in only one client showing up in the Symantec Endpoint Protection Manager for multiple systems

    http://www.symantec.com/docs/TECH97626

    In some cases duplicate entries in the embedded database (DB) exist for a computer even after formatting.

    http://www.symantec.com/docs/TECH95625

    To overcome this problem Symantec has given guidelines to follow:

    SEP 11.x: Configuring Symantec Endpoint Protection 11.x client for deployment as part of a drive image

    http://www.symantec.com/docs/TECH102815

    SEP 12: How to prepare a Symantec Endpoint Protection 12.1 client for cloning

    http://www.symantec.com/docs/HOWTO54706

    http://www.symantec.com/docs/TECH163349

    I hope it helps.

     



  • 4.  RE: Avoid problem of duplicate Hardware IDs

    Posted Oct 12, 2012 03:47 AM
      |   view attached

    want to know the reason of this problem? Why this problem occurs after using Image OS?

    This issue is occured because of using the Cloning/ Image disk which has been created after installed all the application included symantec.

    Reason of this issue is that when you can install the image on different system avail hardware Id is getting mismatch and Communication b/w client and server is getting stop.

    can anybody please suggest any method by which this problem can be avoided in further PCs installation?

    I have created one file for my office use which is use while creating the image and it really helpfull in my Branches. Find the attach file "Image Disk Creation.docx"

     

    Attachment(s)

    docx
    Image Disk Creation.docx   255 KB 1 version


  • 5.  RE: Avoid problem of duplicate Hardware IDs

    Posted Oct 12, 2012 04:44 AM

    Hi

    Mainly this happens due to imaged systems.

    Regards

     



  • 6.  RE: Avoid problem of duplicate Hardware IDs
    Best Answer

    Trusted Advisor
    Posted Oct 12, 2012 11:18 AM

    Hello,

    Cause: There are two causes for this issue:

    Current Theory: The first possible cause for this is when an Endpoint has been re-imaged (whether in a virtual machine or on a physical system).

    Things we know: Each installation of Symantec Endpoint Protection (SEP) randomly creates a "Unique Identifier" for the client. So if this changes and the re-imaged system checks in, it is recognized as a new client.

    Example: The IP and computer name are the same, yet the database still shows a different Unique ID.

    The second cause for this is related to an issue with moving clients to a different OU in Active Directory.

    Duplicate Endpoint Protection client IDs occur if the base image was not prepared for cloning. For more information, read the article How to prepare a Symantec Endpoint Protection 12.1 client for cloning.

    However to Resolve this issue, check these Articles for SEP 12.1: -

    How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 clients

    http://www.symantec.com/docs/TECH163349

    Duplicate SEP clients appear in the Symantec Endpoint Protection Manager console

    https://www-secure.symantec.com/connect/articles/duplicate-sep-clients-appear-symantec-endpoint-protection-manager-console

     

    To prevent this from happening, I would recommend you to prepare your clients before cloning /image, check this article:

    How to prepare a Symantec Endpoint Protection 12.1 client for cloning (image)

    http://www.symantec.com/docs/HOWTO54706

    Hope that helps!!