After OSD by sccm with PXE, there is only a local disk D in reference computer
server: win2008R2 standard sccm sp2 r2 reference computer: a new VM in Hyper-V document SCCM_EvalGuide7b_OSDeployment_PXE.xps get from Microsoft Website. After OSD by sccm with PXE, there is only a local disk D in reference computer. didn't edit the task sequence, everything is default. I check the disk partition in TS, the default setting is that use 100% of the left space(My sccm isn't English edition, those words was translated myself). but after OSD, there is only a D: in the computer with correct volume. where is the disk C:? I need to install the OS into C:. what's with the OSD?
November 22nd, 2010 5:02am

this is a known problem when you are deploying the os using the install.wim from the DVD, instead of doing this, create a build and capture ts and and use that captured wim as your install.wim file. see below for more info Why does Vista end up on the D: drive? Several people have tried to use the install.wim from the Windows Vista installation media in an Install an existing image package task sequence. They are surprised to discover that, upon completion, the operating system is on the D: drive instead of the C: drive. The short explanation for why this happens is that the operating system volume for the images in install.wim is D:. In other words, when the image was captured, the reference machine had the operating system on volume D:. Why this is the case for the install.wim that ships on the Windows Vista installation media is beyond the scope of this blog. OSD preserves the drive letter of the operating system volume in the image when it applies the image to the target computer. If OSD let the operating system assign itself the first available volume letter (typically C , and this letter did not match the operating system volume letter in the image, then Windows setup would fail due to invalid volume references. I leave it as an exercise for the reader to verify this at home: 1. boot to Windows PE 2. format your drive 3. using imagex.exe, apply an image from the install.wim in the Windows Vista installation media 4. reboot to the hard drive Windows Setup does a lot of work to "fix up" drive letter references in the registry and elsewhere, so that this is not the case for Setup-based installations. Duplicating this work in OSD was beyond the scope of ConfigMgr 07. In addition, the images applied by OSD may contain arbitrary third-party applications, which may contain hard-coded drive references in the registry, which OSD may not be able to determine how to handle correctly when the operating system's drive letter changes. The supported method for generating an image which can be used in an Install an existing image package task sequence is to capture an image of a reference machine, which can be built manually or using the Build and capture a reference operating system image task sequence. My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 5:26am

This sounds like a pretty big bug. Deploying Windows 7 to the D drive is obviously not acceptable for most enterprises. The beauty of WIM is you are supposed to be able to copy install.wim from the DVD. This means when SP1 comes out this week, we can’t just drop and replace. This damages the credibility of the whole WIM spirit. Here you and I can discuss WinPE limitations, but customers are going to hear "you can't use the wim from the DVD because its broken" Mike Crowley Check out My Blog!
February 14th, 2011 6:10pm

I don't know if this is a bug, but this is known since Windows Vista days: http://blogs.technet.com/b/inside_osd/archive/2007/08/08/why-does-vista-end-up-on-the-d-drive.aspx (that's just the link to the statement that Niall already posted). So it's nothing new and it has been discussed quite a few times here in the forums. The workaround (also mentioned by Niall already) is to create a custom image (using ConfigMgr's automated way). Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 6:27am

The task sequence has an option to define the drive letter the OS is installed on. This setting being ignored equates to a bug to me. I acknowledge it’s been a problem for a while, but that doesn’t change the fact. Workarounds are always frustrating because by definition it means we have to fix a finished product. It seems there was ample time to get this right in the many versions and service packs of SCCM. I've had some trouble with OSD this week, so this is just me venting!
February 15th, 2011 5:07pm

I ran into this recently and I discovered the reason behind it and an easy way to fix it. The reason the drive letter is D is due to the fact that we installed an image based off the dvd install.wim, and since the image on a dvd is generally defaulted to D thats where our problem comes in. The easiest way to fix this is to go into your Task sequence and right click on it and choose Edit. Now click on the Apply operating system and on the right side if you had the same problem I did it is currently set to Apply operating system from a captured image. Change this to Apply operating system from an original installation source browse for the base package (it should be the same as the one you had set for the captured image settings above it) after the correct package is selected click the apply button and the ok button. There you have it the next machine you deploy from this task will go through the windows 7 install instead of just copying the image file from the DVD and this will cause your drive letter to default to C.
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2012 3:04pm

Thanks CO. You just need create build and capture TS one time and use this image in future. Using of Source media is not best solution, because you can't deploy x64 images with WinPe x32, but with .wim image you can.
September 13th, 2012 6:29am

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

Other recent topics Other recent topics