We are creating Windows7 Images and once the image is complete Sysprep is performed, here is where the problem lies... I have run the solution
-
Empty the Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\HardwareID=""
-
Delete the file: C:\Program Files\Common Files\Symantec Shared\HWID\sephwid.xml
-
If present, delete: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\SySoftk
-
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)
The problem here is once this is all done Sysprep is run and the imaged PC IS connected to the network during the Sysprep, and even though the above steps WERE performed, the client can STILL communicate with the SEPM server, thus bringing me back to square 1. I performed the steps above and the SMC service WAS stopped, but once the Sysprep was run, the SMC service MUST have reinitiated and connected to the SEPM server. Once we received an order of 50 PC's. 50 showed up, but then 20 mins later, ONLY one was left. I was thinking the BEST thing for me to do is to switch the SMC service from Automatic to Manual and ask the people who are rolling it out to the clients to switch it back to Automatic, and turn the service back on.
Not even a reinstall will correct this issue after the fact, which is something I really do not like in SEP, with SAV, once you removed it, it was GONE. With this, it continues to KEE P the same HWID information even WITH an uninstall and reinstall.
Basically, the question is, HOW IS THIS DONE when doing a sysprep, and how to I prevent communication from the client to the server during Sysprep so that HWID's are NOT generated. The above solution is a good solution, but it really does not apply in this case.
Thank you.