Endpoint Protection

I am looking for the DOC for, when using GHOST to make a install image. how to make the changes need for SEP client, so that each system does not get the same SID...

I use ghost for all of my machines and i dont change a thing with SEP.  It starts reporting with the new computer name of the ghosted machine.  

Follow this

Configuring Symantec Endpoint Protection client for deployment as part of a drive image

http://www.symantec.com/business/support/index?page=content&id=TECH102815&actp=search&viewlocale=en_US&searchid=1295450917248

Preparing a Symantec Endpoint Protection Release Update 5 and above Client for Image redistribution

http://www.symantec.com/business/support/index?page=content&id=TECH96808&actp=search&viewlocale=en_US&searchid=1295450917248

In order to prepare the client for the image, it is vital that you follow these steps:

1. Empty the Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\HardwareID=""
2. Delete the file: C:\Program Files\Common Files\Symantec Shared\HWID\sephwid.xml
3. If present, delete: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\SySoftk
4. Prevent a restart of the original host before creation of the image (shutdown is OK, but after startup both Key and File will be re-created)

After applying the Image the client will be started and the Registry Key and File newly created.

How to fix RU5 clients that have been misconfigured and already rolled out to production (For each client:)

1. Delete %programfiles%\Common Files\Symantec Shared\HWID\sephwid.xml
2. Open the registry and navigate to HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink
3. Edit the "HardwareID" value data to be blank
4. Restart the Symantec Management Client (SMC) service in the services snap-in.

Clients should now generate unique HardwareID's and sephwid.xml's.