Ian usingSCCM Sp2 Beta for OSD.I used windows 2008 default image that came with the installation source.For some reason after executing the OS seuqence my image is getting deployed on the single drive and assigning it drive letter D instead of C.Need assitance in fixing this issue.I want the OS drive to assigned as C instead of D

create a build and capture task sequence for windows 2008 and create a new task sequence to deploy the captured WIM image to your servers, that way it will end up being C: instead of D:my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Using the install.wim directly form the media, while supported, results in this side effect. The only way around this is to follow Niall's advice.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

As Niall said you need to capture your own install.wim file. As the one that is provided with SCCM is a captured with D:. The easiest way to do this, imo, is to sysprep a 2008 server, boot it into WinPE and run a capture task sequence.

I have done this using MDT build and capture and still get a D drive instead of C. Any ideas?

can you explain the process you followed please ? My step by step SCCM Guides windows-noob on Twitter

Sure. Created MDT client TS using the install.wim from my w7 iso. Allowed MDT to create all packages etc, etc. Captured resulting reference image. Created a second MDT client TS using reference image and configured unattended.xml with all required changes. Deployed to workstation, swore at d drive.

that was the problem, you used install.wim instead of using an Operating System Install Package (ie: the entire SOURCE of the Windows 7 DVD, everything !) once you create a build and capture of windows 7 (try this guide for pointers ) you'll be fine cheers niall My step by step SCCM Guides windows-noob on Twitter

Thanks Niall, that solved the problem.

I have been told that build and capture will save me time but I am unclear as to how this will save me time if I have to build and capture for every model and make of system that is deployed in our organization. I would love to hear why Microsoft chose to have it install to the D: drive and who do I need to talk to about addressing this issue directly and having the install.wim install to the C: drive

You don't have to do a build & capture for every model; images created by ConfigMgr or MDT are hardware agnostic and both process have the built-in default capability to inject drivers and hardware specific support applications into the deployment of the image dynamically. The goal and desired end-state for all customer deployments that I have done is having a single image which I have achieved in most of those cases. There are reasons to have multiple images -- like OS version or edition -- but these do not include any hardware dependancies when Vista or later is the OS being deployed (even with XP and 2003 this is achievable btw).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys