I'm finding conflicting information about whether it is necessary to remove the SCCM client GUID prior to Ghost imaging. Originally (SMS era) we used the NEWUID.exe tool to remove it prior to taking the image. I'm reading that upon deploying the Ghost image to a new machine the SCCM client somehow recognizes the change in hardware and therefore regenerates a new GUID for that machine. Is this the case? Is there any documentation on how this works? I prefer not to remove the CM client entirely, just remove the identifiable configuration or anything that would prevent the imaged machines from correctly communicating. Thanks for the info!

I woudn't put the client in my image but if insist on doing it here's how:http://technet.microsoft.com/en-us/library/bb694095.aspxJohn Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Reading the link you posted makes it seem easier to just uninstall the CM client prior to imaging. I know the standard ccmsetup.exe /uninstall route but are there any other files/folders that I need to remove to ensure the image is ready for duplication? (e.g. ccm or ccmsetup)A little background: Our IT group is distributed so there are a few groups that make their own images and I'm trying to put together some instructions on how to prepare a image for replication.

Honestly I am not sure if just running uninstall will remove everything. Back when I used Ghost I always made sure to not let the client get installed. I think running ccmdelcert will take care of it but I am not sure.John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Given the relatively automatic installation of the client I'm pretty sure some of the images being built will end up with it on there so need to figure out how to remove it "enough" as well. Thanks for your help so far, anyone else know what needs to be removed to make sure the image is clean enough to image?