Endpoint Protection

So if I'm going to take an image of a pc that will be redeployed to a number of machines and I want to have SEP RU5 pre-installed.  Do I need only to delete this file: %programfiles%\Common Files\Symantec Shared\HWID\sephwid.xml   before taking the image?

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/d84071c5137d6d318825738a00663b8d?OpenDocument

Thanks

https://www-secure.symantec.com/connect/forums/question-about-deploying-sep-11-mr5-client-virtual-desktops-within-vmware-view-master-image 

Yep, I read through that.  I'm just wondering... before I take the image, do I need only to delete the file, or do I also need to delete the HardwareID value in the sylink key in the registry?

Title: 'Configuring Symantec Endpoint Protection client for deployment as part of a drive image'
Document ID: 2007110510364248
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2007110510364248?Open&seg=ent

That's the link I initially posted.  I'm just trying to get a final answer specifically on RU5.  I can't seem to see at what point I need only to delete the file vs (the hardwareid value in th registry + the file).  Thanks

 I would suggest delete both as doc says to delete the Reg key.So you should delete it however since this new file is an addition to hardware ID so delete that aswell.

AS even in the above discussion Ghent says "If you are cloning a machine, either physical or virtual, it's best to delete the hardware key before you clone the machine..."

OK Thanks.  Do I delete the entire hardwareID string or just the actual value data (actual HardwareID)?

 Delete the whole HardwareId string.

The registry key HKLM\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\SySoftk may also need to be deleted if present. 

I'd delete that "new file" (new to RU5) and delete computer and hardware id in the registry. On the right side of "regedit", I click and delete.

I have NEVER EVER EVER had an issue with ANY images, ever.
In the past, I simply deleted both computer and hardware keys
Now it's that file, too.
Otherwise, it's been consistant.
Both keys get regenerated, so I figured in my testing with 0 failures ever on any images at any time on any computer, it's good enough.
The Symantec document otherwise should be viewed as "king" - do what it says and life will be good.