Deploy an existing (thick) image
Hi there, hoping someone can help. I have an existing Win7 Enterprise reference computer that I want to (possibly) capture and then deploy, using SCCM 2007. Our organization is moving away from Ghost-type imaging to SCCM, which I'm still learning.... I've been reading all over the forums and I know full well that the recommended method for SCCM OSD is the build and capture method with MDT. I'm working on that, but our reference image has tons of software packages, a lot of them have tweaked settings just so, so it's taking a lot of time creating unattended installers for everything that we have, as well as testing everything to ensure it works as expected. Meanwhile I have an existing image/reference PC that is ready to go, as I've deployed it with Ghost for almost two years now with no problems. The problem I'm having is, somewhere along the line during deployment, the image gets stripped of drivers and they're not reinstalled. This *doesn't* happen when I deploy the same image using Ghost. The reference image has never been on a domain, has all relevant drivers included, and already has an unattend.xml that does everything I want it to. It's ready to be sysprepped & saved. So in this scenario all I would really want SCCM to do is copy the image to the PC, rename the PC and join it to a domain. Or is that only possible when doing a build and capture setup? Or at the very least copy over the image with the drivers maintained, as is the case when I use Ghost. So I mentioned above that I want to *possibly* capture the image, as I've already managed to get the PC to boot up with PXE & WDS and save a WIM file. I just don't know if there's something during that capture process that is stripping out drivers, or if it would be something in the deploy task sequence. As it is right now, during deployment, the laptop PXEboots into WinPE, SCCM installs the image but without the drivers that should be there. It then installs the ConfigMgr Client and reboots to the desktop. The computer even gets the correct name. But since the computer is missing the Intel chipset INF, NIC drivers, etc, it can't continue at that point. So do the task sequences in SCCM override the Sysprep/unattend.xml settings on the reference computer in regards to drivers? How do I get SCCM to install an image without stripping them out? Hope that makes sense. And yes, I'm still working on a build & capture setup using MDT as well. But it's frustrating when I already have something that's all ready to go and just needs to be deployed. Thanks in advance.
July 6th, 2012 4:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics