Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Is there an issue of Identical Hardware ID on SEP 12 clients from Image?

Created: 15 Oct 2011 | 2 comments

For SEP 11, I understand that if a computer image with SEP 11 is distributed throughout the network and tries to check into SEPM, the SEPM will think all those SEP 11 clients are just one UNLESS we follow instructions in this artlcle http://www.symantec.com/docs/TECH102815

 

Is this the case for SEP 12?

 

Or, can I make as many computer images with SEP 12 as I want, distribute it throughout the network and when it tries to check into SEPM, the SEPM will see that these clients belong to individual computers.

Comments 2 CommentsJump to latest comment

Vivek Jain's picture

It would be the same for SEP 12.1 as well., however the process for cloning or repairing duplicate IDs is slightly different.

How to prepare a Symantec Endpoint Protection 12.1 client for cloning - http://www.symantec.com/docs/HOWTO54706

How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 clients  - http://www.symantec.com/docs/TECH163349

 

Idimple's picture

hello,

 The clients have the same Hardware ID, they appear to be the same system to the SEPM

If clients are exhibiting this behavior please follow these steps on affected systems:

 

  1. Stop SMC on both of the affected client computers by clicking Start Run, type smc -stop then click OK.
  2. On the SEPM console, delete the client entry that the two computers have been sharing. This will prevent the client duplication that would otherwise occur due to the following steps.
  3. On each of the affected computers, go to registry location: 
    • HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\Sylink\Sylink
  4. Clear the value for "HardwareID." (make it blank)
  5. Disable Tamper Protection if you are unable to edit the value.
  6. On each of the affected computers, navigate to the following directory location:
  7. SEP 12.1 Location: 
    • Windows XP/2003: C:/Documents and Settings/All Users/Application Data/Symantec/PersistedData
    • Windows Vista/7/2008: C:/ProgramData/Symantec/Symantec Endpoint Protection/PersistedData
  8. Find file "sephwid.xml". Rename it to "sephwid.xml.bak".
  9. Start SMC on each computer by clicking Start Run, type smc -start then click OK.
  10. Check the SEPM console for the new SEP client 
    • When the clients check in they should have unique hardware IDs
Your satisfaction is very important to us.If you find above information helpful or it has resolved your issue...please mark it accordingly :)