OSD installing on wrong drive letter
Hello. Is there a known issue where SCCM is installing the operating system on the wrong drive letter on computers with 2 partitions (c: and d:)? We are using the following: Windows Server 2003 SP2 SCCM 2007 R2 SP2 When we recently upgraded to SP2, we started deploying Windows 7 but it was installing on the D: drive instead of C:. The task sequence, under "Apply Operating System", has the Destination of the OS as "Specific logical drive letter" and the Drive Letter is set to C:, however, the OS gets installed on D:. We've also tried using "Specific disk and partition" for the Destination, Disk 0 and Partion 1; same results. The server was missing some updates so we installed them and it started working fine (i.e. the OS started to get installed on the C: with no issues). However, again this week it started to install on the D: drive. No changes have been made to the task sequence and the server is not missing any more updates. Any ideas? Thanks
December 17th, 2009 10:15pm
it will probably install on D if you use the install.wim file directly from the DVD, which is why you should do a build and capture of Windows 7 (and vista, and server 2008) to create the install.wim file which you can deploy with another task sequence. you could try deploying Windows 7 like so My step by step SCCM Guides Follow me on Twitter
December 17th, 2009 10:18pm
Are you using the default install.wim from Windows 7? Because the default install.wim from Windows 7 (and Vista and Server 2008) all install by default on D. If that's not wat you want, then you have to create your own WIM image.My Blog: http://www.petervanderwoude.nl/
December 17th, 2009 10:19pm
Yes, I am using the default install.wim. I'll try doing a build and capture to create a new install.wim.Thanks for your fast replies.
December 17th, 2009 10:32pm
Are you using the default install.wim from Windows 7? Because the default install.wim from Windows 7 (and Vista and Server 2008) all install by default on D. If that's not wat you want, then you have to create your own WIM image. My Blog: http://www.petervanderwoude.nl/ I have the same problem also.. I only have it with the x64 version and not with the x32 version. i created an image with MDT 2010 and made sure that it would install on c: so no other partition is used. In the past that would be enough to make sure that in a later stadium the default partition would be c: for the OS. because we use bitlocker we need to add a primary bootable partition of 500mb but even when i do an installation without it it still installs on d: i captured it on a dell optiplex 780 with MDT 2010 2 times already. rolled out with an MDT rollout, without. so i am looking for a solution also.
December 18th, 2009 7:52pm
how was the image installed on the Dell Optiplex 780 ? My step by step SCCM Guides Follow me on Twitter
December 18th, 2009 9:29pm
I would just like to ask one question that doesn't seem to be getting asked here and that is,"Why does the Install.wim assign the operating system to the D: drive instead of the C:drive?" This does seem to me like something that could be quite easily fixed by Microsoft by simply reissuing the install.wim. I mean thats why we were sold on the wim format wasnt it? That Microsoft would issue install.wim files we could load and customize for our environments without having to go through a build and capture in the first place.
January 8th, 2011 12:07am
Isnt there any way by which you can define a specific drive letter C: using the task sequence if we actually have things running that way. Regards, Amim Muhammad KhanAMIM MUHAMMAD KHAN | CTTCNET USER GROUP LEAD | EVENT SPEAKER, MCT, MCTS, MCITP-ENTERPRISE, MCSA http://amimkhan.wordpress.com
April 27th, 2012 6:32am