Thought I’d do a quick post on this as there is precious little to be found in forums about this task sequence ‘bug’. I say bug, really it’s probably just lazy programming (I haven’t checked the specifics but the evidence leads me to believe this is the case).
Anyway…the scenario is this:
ENVIRONMENT:
SCCM R2 SP1
MDT 2013 U1
MDT-infused Client Task Sequence goes all the way through until it hits the Gather step under the State Restore phase. At this point you are hit with:
In this case the Set Variable For Drive Letter step under the Install section had set the OSDPreserveDriveLetter task sequence variable to TRUE which caused my OS disk to be set to X: for some reason! I suspect the same may happen if the OS had been installed on another drive other than C: but I haven’t tested this so can’t say for sure. Equally it appears to happen only with Gather Only Local Data. In any case the fix is to ensure you are installing to C:
What is the fix for this issue?
Hi Jose
You don’t say what version of ConfigMgr you’re running but there are are a couple of things to try. Firstly, try changing OSDPreserveDriveLetter variable to false (ensure this is set before OS installation step).
Note that this TS var is depracated from ConfigMgr 1606 onwards and should no longer be required.
Failing that, please take a look at the following articles:
https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence/
and this one which appears to discuss the above issue perfectly (and in more detail):
https://www.niallbrady.com/2015/11/17/why-does-windows-end-up-on-x-when-deploying-windows-10-x64-1511-build-10586-with-system-center-configuration-manager/
Thanks
Simon