OSD Drive Letter gotcha to look out for after upgrading to SCCM 2012 SP1

After upgrading to SCCM 2012 SP1 our OSD process was failing due to Windows coming up after mini setup still using the D: drive versus the expected C: drive.

After some digging I found the culprite in the Task Sequence.  There is a Task called “Set Variable for Drive Letter” which sets the OSD Variable “OSDPreserveDriveLetter=False”

This is new functionality in SP1 that allows you to override the drive letter (using variable OSDisk) versus the old method that would always use the drive letter from the WIM file (the drive it was captured on).

After disabling this step, all was right with the world again as I do want to always use the C: drive from my WIM image.  😉

Hope this helps someone else!

More info about this variable can be found here:




5 thoughts on “OSD Drive Letter gotcha to look out for after upgrading to SCCM 2012 SP1

  1. You are my hero!! Thank you!

    Fought with this all last week.

  2. Always glad to help!

  3. Thanks, this was exactly my issue.
    All was well until SP1 update then new builds had group policy and other weird errors all the issues seemed unrelated, but in fact all were due to C: turning into D: on new builds.

    Thanks again for the clear answer and the technet link to read more about it.



  4. I tried changing the variable for OSDPreserveDriveLetter to TRUE and that fixed the problem for me.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s