jc1875

Hi We've an option with our hardware supplier to provide an image, and they'll image this onto the hard drives of the machines before we get them. At the most basic level, it means we can purchase machines with the lowest (cheapest) windows OS and our SA allows us to upgrade to any version of windows we like ie enterprise. So, we've got our existing internal deployments working fine, captured an image and use it to deploy and refresh existing pcs. My question is, is it as simple as supplying the captured .wim (with the latest OS patches etc applied) importing the machines MAC and name adding machines to a collection apply a copy of the standard new computer TS with the imaging part removed It almost seems too good to be true.....

I added this to the bottom of the OSD win7x64 post, but as its not really for SP1 it probably shouldnt be there. I can find and SP1 thread, so here goes. I had SP1 installed to take advantage of server 2012 client install. However, as I didnt read all the issues, working through the guides on here was all fine until I hit the OSD stage. After hours of head scratching, permissions checking, log verification, reboots etc I read https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/756714/sccm-2012-sp1-ctp2-unable-to-select-os-installer-for-build-capture-task-sequence Not a massive change but when you like to follow the guides diligently, it can be a pain. Addin the 'install.wim' to the OS Images, allows it to show in the OS deployment task sequence, rather than adding the DVD contents to OS installer (which leaves the entry in the task sequence blank - cue much head banging.)

after much head scratching it dawned on me that having SP1 in my test lab might be confusing the issue. Sure enough, the OSD has changed slightly 'by design' https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/756714/sccm-2012-sp1-ctp2-unable-to-select-os-installer-for-build-capture-task-sequence Looking forward to some SP1 guides