Endpoint Protection

 View Only
  • 1.  Running ClientSideClonePrepTool.exe silently

    Posted Oct 07, 2015 04:38 AM

    Symantec! Why are you not able to develop a ClientSideClonePrepTool that can run unattended?

    https://support.symantec.com/en_US/article.HOWTO54706.html

    Selveral customers have been waiting for years now!

     



  • 2.  RE: Running ClientSideClonePrepTool.exe silently

    Trusted Advisor
    Posted Oct 07, 2015 05:23 AM

    Might be worth submitting your request to the ideas forums if it gets enough votes symantec will look into the viability of implmening it.

    https://www-secure.symantec.com/connect/security/ideas



  • 3.  RE: Running ClientSideClonePrepTool.exe silently

    Posted Oct 07, 2015 11:01 AM

    The function of the ClientSideClonePrepTool is to clear the SEP Hardware ID on a machine and leave the machine without a hardware ID so that a template or a base image can be created out of that machine. Templates or base images created in such way will not have the Hardware ID and hence every new machines made out of this template will generate a unique hardware ID for itself.

    Just to confirm, this tool is NOT to be executed on cloned computers, after being cloned with a SEP hardware ID already present in the template or the base image.

    Symantec provides a seperate tool (RepairClonedImage.exe) for clearing Hardware ID from computers on which the hardware ID is already duplicated. This tool can be run silently. Please check the following link for more details on this tool.

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



  • 4.  RE: Running ClientSideClonePrepTool.exe silently

    Posted Oct 08, 2015 09:07 AM

    I am using ClientSideClonePrepTool on a PVS image for our Citrix XenApp environment. When the image are done this is being streamed to several XenApp servers. So I still believe ClientSideClonetool is the right tool. 

    This PVS image is created by MDT, where everything has to be unattended.

    Right now I am using the workaround to delete sephwid.xml files and delete registry keys.