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. 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 (not joined to a domain however)?

When you want to make changes to your image, before capturing is taking place, the build and capture TS is not the answer. I should create Capture Media in SCCM for doing this. Look for this on: http://henkhoogendoorn.blogspot.com/2011/03/create-task-sequence-capture-media.html Just install your device, with apps and updates, and all customizations you want. Then capture it with the Capture Media, and add the WIM image in SCCM. For creating this image Windows 7 must be added to a workgroup, otherwise it won't work. Sysprep is not needed, because it's build-in. Re-sysprepping the image doesn't matter, just update your image as often as you like.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

When you want to make changes to your image, before capturing is taking place, the build and capture TS is not the answer. [...] Just install your device, with apps and updates, and all customizations you want. Then capture it with the Capture Media, and add the WIM image in SCCM. Why is the build and capture tasksequence not an option then? Could you please add details? The purpose of it *is* the automation of creating an reference image IMHO. Installing and configuring Windows manually and using the capture media does work of course, but it's not automated then.Torsten Meringer | http://www.mssccmfaq.de

Why is the build and capture tasksequence not an option then? Could you please add details? The purpose of it *is* the automation of creating an reference image IMHO. Installing and configuring Windows manually and using the capture media does work of course, but it's not automated then. Torsten Meringer | http://www.mssccmfaq.de Hi, it depends per situation.. When creating a default image which will be fully automatic use the build and capture TS. When an image must be made, with updates, apps and other customizations it's easier I think to capture it by SCCM capture media. That way not all customizations has to be build-in TS. Most of times I'm using the build and capture TS for creating reference images. Last time the device was already installed, with apps, and customizations, and SCCM capture media was the right answer here. This because no additions has to be created in TS, and capture media is created in a few minutes. This is what this post is all about: 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 my opinion you can use SCCM capture media as snapshots. Just update the image, and create a new image then. All these images can be used in SCCM console for deployment or test, and can be updated later. When using TS only for that it becomes kinda difficult I think. My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Agree with Mr. Henk on this one. Configuring everything to be as automated as possible requires too much effort for a once in a quarter(in most cases) imaging activity (image refresh). Its usually easier(and faster) for me to just boot up a fresh windows 7 install on audit mode and throw everything i need to the installation. Afterwards, I use my handy WinPE usb stick and do imagex myself. Probably just me, but i want my images to be completely under my control. There are also some OS settings which i think (not exactly sure) are unconfigurable on the task sequence, such as security settings, the default user profile, and local group policy settings. Just my two cents. Thanks

Hi, Why prepare an OS with all the drivers and applications. Just create a basic Win7.wim file and do the rest in a tasksequence. That is mutch easyer with a tasksequence. If an application change is needed then you can change it in te tasksequence. Otherwise you have to create a new Win7.wim file to deploy. Cheers

Cmillian, I explained the why already, and I'm happy for those who have the time, resources and patience to put together a thin-image as you suggest, with all apps, settings and patches layered as task sequences. I will get there eventually, just not now. Success! Alas, I have found a simple solution to my problem! At least a partial solution; as I stated originally, I really just wanted to mirror the same imaging methods I was used to in Novell Zenworks; setup a windows box with all the trimmings, snapshot it, upload it, sysprep it, snapshot again for final deployment via pxe/zenworks. I can achieve this functionality, and the solutions were so simple as to be embarrassing to admit. To capture any OS in a non-sysprepped state via pxe OSD task sequence: create a new custom ts first ts: 'Use Toolkit Pakage" - first integrate MDT 2010 into SCCM, then create a package for the MDT Deployment Toolkit second ts: "Set Backup Location" - set a task sequence variable with 'ComputerBackupLocation' and a value that points to your backup share location third ts: "Set Backup File Name" - yet another ts variable called "BackupFile" with a value that will be your image name 'myimage.wim' fourth ts: "Create Image" - here's the magic ts, it is a 'Run Command Line' ts with the command line of cscript "%scriptroot%\ZTIBackup.wsf Advertise this, make it available to pxe boot image and voila! It simply works! Tested it on a Windows 7 x64 and XP machine, no issues. Now to reverse the process, even simpler: 2. To apply a non-sysprepped wim via pxe OSD task sequence: first ts: "Partition Disk 0" - change the format to quick, otherwise left everything default here second ts: "Apply Operating System Image" - point this to your previously captured non-sysprepped image get a cup of coffee Again, tested on W7 and XP, works fine. I understand that this method is only valid if you are capturing and reapplying to the same model due to HAL and Mass Storage driver issues, but this will get me started and I can work on creating my 'thin-image' and custom application deployment ts's at a later date. All this because I just HAD to use pxe/SCCM when I could just as easily stuck with MDT and a custom boot disk. On that same note, I could forgo pxe booting and still use SCCM by creating a custom task sequence media disk, which I imagine works much the same way as a custom MDT WinPE disk. Thanks all, Sincerely, T

Thank you Henk, I will employ that method as well, I didn't realize until I read your post, that creating media would allow me to capture and deploy non-sysprepped images.