Wally, I read your post that SCCM should be able to reassign a GUID after a PC is syspreped without having to do anything but I've also read about removing any machine certs, stopping services, and uninstalling the client. I'm not clear how to properly ensure that the SMS client will work with a syspreped PC and would like some direction. Is it simple enough to sysprep the PC?

Hello - I think, if you are planning to include client installation as a part of OSD Task sequence then there is no need to do anything like "machine cert, stopping services, etc..." If you want to include SCCM client as part of your base image as best option you should be doing "Machine cert, stopping services...etc.,..Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I finally found the official MS response below. I think we are pushing the client via logon scripts in AD so I might be ok with just removing the client off the master: Or is this documentation irrelevant (do I just image the PC with sysprep and SCCM will detect a new GUID)? I'm removing the PC from the domain & restarting 1 more time prior to syspreping it, if that helps. Update: I've just verified that on 2 of my PCs, I do have unique ConfigMgr UID's. Upon changing from a workgroup to a Domain and changing the PC name to a unique name, the GUID changes. Is there something I might be missing? http://technet.microsoft.com/en-us/library/bb694095.aspx To prepare the client computer for imaging Manually install the Configuration Manager 2007 client software on the master image computer. For more information, seeHow to Install Configuration Manager Clients Manually. Important Do not specify a Configuration Manager 2007 site code for the client in the CCMSetup.exe command-line properties. Typenet stop ccmexecfrom a command prompt to ensure that theSMS Agent Hostservice (Ccmexec.exe) is not running on the master image computer. Remove any certificates stored in the local computer store on the master image computer. Additionally, remove any native-mode client certificates if applicable. For more information, refer to your public key infrastructure (PKI) documentation. If the clients will be installed in different Configuration Manager 2007 hierarchies than the master image computer, remove the Trusted Root Key from the master image computer. For more information, seeHow to Remove the Trusted Root Key. Use your imaging software to capture the image of the master computer. Deploy the image to destination computers.

I would suggest to use or create master image without any client installed on it. If the client is already the image and u r planning to uninstal then ensure that there is no trace of client including cert etcAnoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If you are using MDT or OSD they will handle this for you. If not follow the instructions you posted. Better yet, never install the client in your reference machine. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I am using MDT 2010. Thanks!

If you are using MDT to both build and capture and SCCM to deploy the image it should handle everything for you. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|