Adminoob

Hello, I have a Windows 7 x64 machine that is updated/customized, but NOT domain joined; your method here is fine for a domain joined machine, but as you pointed out, it isn't a good idea to sysprep and re-deploy a previously domain-joined machine because of the various changes that occur. How can I modify your method here to sysprep/capture my W7 image? It simply isn't feasible to do a build and capture ts, while that is fine if I want a vanilla OS with no apps or updates, the fact is, our organization has WAY too many apps and customizations to include as either custom ts software installs or to be somehow delivered via GP/AD. It is much faster to build a gold image (thick image) with everything on it, then prep it and capture an image for later deployment. I am NOT going to make custom ts software installs for things like Adobe CS4 and a dozen other HUGE apps, the imaging time would take hours for the base image and all of the software updates to come down.

Here's what I want to accomplish, and I've been successful with MDT 2010 but we've since added SCCM to our environment: 1. deploy base OS with sccm via pxe (I can do this fine using the build and capture ts, no problem here) 2. I do NOT want to capture the os immediately, so I'm assuming I either have to disable the capture portion of the ts or create a custom ts( any suggestions ??) 3. after deploying the base OS Windows 7 x64, I want to customize it, add apps, drivers, settings and so on. 4. I want to capture a .wim image of this non-sysprepped gold-image, and be able to re-image a machine at some future date, same model of course (so I don't have to go through the hours of customizing later when I need to update the image. (capture via imagex is possible, I'd rather do it via pxe/sccm to keep it all simple and together) 5. finally, I am ready to simply sysprep and capture this image, again, it seems I need to create a custom ts, this one only including the sysprep/capture portions of the build and capture ts? My problem is, I can find TONS of guides on how to deploy a bare-metal os, capture it and redeploy it....doesn't anybody customize their images anymore?!? Why is it so hard to find someone who is using this model of image development and deployment and who can provide a step by step guide that isn't simply a regurgitation of the technet docs on sccm osd? I want to add stuff to my 'gold' image BEFORE I sysprep and capture it, and want to maintain the option to capture the gold image at any stage of its development, i.e. perhaps I want to run windows updates, install office 2010 and a handful of standard apps and plugins, then simply archive this image for updating later in this state (in a non-sysprepped state, non-domain joined). I realize the functionality of sccm in conjunction with AD Group Policy can allow you to deploy apps via the configmanager client or gp, but there are instances where I do not want to spend hours repackaging apps to push via the network, when I can simply include them in the base build. As a side question, what are the implications of re-sysprepping a W7 computer that has already been sysprepped?