Help! My OS is Installing to D!
Those of you doing OSD with ConfigMgr 2012 SP1 may have noticed something strange happening when running your task sequences, this is that the operating system installs to the D: drive and not the C: drive. Why is this?
This behaviour is actually expected. The reason for this is that the when you use ConfigMgr 2012 SP1 you can no longer run the setup.exe to install the operating system from within the task sequence setup wizard, you can change this later on by editing the task sequence though.
If you are using the default install.wim downloaded from your MVLS or MSDN login then ConfigMgr applies the image to the default letter specified in the WIM. You can use a build and capture to force the image to apply to the C: drive or you can use a new variable available since ConfigMgr 2012 SP1 called OSDPreserveDriveLetter.
This variable should be set to false and set before the Apply Operating System task sequence step in your task sequence. This will ignore the drive letter in the WIM and apply it to the one specified in the step (varies depending on your configuration but usually applies to the OSDisk variable).