Video Screencast Help

ClientSideClonePrepTool for SEP 11.X

Created: 28 Dec 2012 • Updated: 29 Dec 2012 | 2 comments


Does anyone know how i can download the correct version of "ClientSideClonePrepTool" for Symantec EndPoint Protection 11.X?

The version of the "ClientSideClonePrepTool" that I have is "Version" which does not work on Symantec EndPoint Protection 11.X. Also, when I run this utility I get an error that reads "Failed: Incorrect version, SEP 12.1 or higher is required"

Can anyone please help me as I'm trying to create an Image of Windows 7 with SEP 11.X, and LANDesk installed on it prior to running sysprep.

Your help is greatly appreciated in advance. Thanks

Comments 2 CommentsJump to latest comment

Ashish-Sharma's picture

ClientSideClonePrepTool for SEP 11.X is not available .you can manually repair the client.

Configuring Symantec Endpoint Protection 11.x client for deployment as part of a drive image
Article:TECH102815  |  Created: 2007-01-05  |  Updated: 2012-06-08  |  Article URL

Thanks In Advance

Ashish Sharma

ᗺrian's picture

This tool only works for 12.1, it is not for use with 11.x

For 11.x release earlier than RU5:

Ensure that the Symantec Endpoint Protection (SEP) client does not communicate with the Symantec Endpoint Protection Manager (SEPM) prior to and while creating the image.

If the SEP client has checked in and registered with the SEPM, the following registry values must be deleted prior to creating the image.

HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\HardwareID.

NOTE: The registry value HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\SySoftk must also need to be deleted if present.

Once the image is applied to a new system, the client will generate a unique id value, check in with its SEPM, and register. During the registration process, the SEPM will register all necessary client information into the database.

This value will regenerate the next time the client loads.

For 11.x release RU5 and later:

With this new design, the Hardware Key is now stored in %ProgramFiles%\Common Files\Symantec Shared\HWID\sephwid.xml. This allows for easier remediation in the following situations:

1) A client is generating new Hardware Keys on startup which could potentially conflict with another SEP client or for preparing a machine
a. Move, rename, or remove the Hardware Key config XML file found in the Symantec common area.
b. Remove the “HardwareID” registry value located in HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\Sylink\Sylink\
c. Restart the client.. New Hardware Key information will be generated in this case.

2) When SEP is installed the client on a clean VM or Ghost image using the same hardware, the Hardware Key is different.
a. Since the new algorithm generates random IDs, any install on a clean machine will result in a new ID being generated.
However, if the client is uninstalled and reinstalled, the ID should not change, since it is persisted in an XML file located in the Symantec Common area. i.e. "%ProgramFiles%\Common Files\Symantec Shared".

In order to maintain the same ID when an image is restored, the customer should install SEP first before creating the image. 

Alternatively, a saved sephwid.xml file and force that Hardware Key to be used by setting 

HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\Sylink\Sylink\ForceHardwareKey in the registry to 1 (true).

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

The following steps must be performed on each client which has a duplicate hardware ID.

  1. Stop the Symantec Management Client (SMC) service. This can by accomplished by clicking Start > Run and entering the command: smc -stop
  2. Delete %ProgramFiles%\Common Files\Symantec Shared\HWID\sephwid.xml
  3. Open the registry and navigate to HKLM\Software\Symantec\Symantec Endpoint Protection\SMC\Sylink\Sylink
  4. Edit the HardwareID value data to be blank
  5. Start the Symantec Management Client (SMC).  This can by accomplished by clicking Start > Run and entering the command: smc -start

 When the client next communicates with the SEPM, it will generate unique HardwareID's and sephwid.xml's.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.