[mdt] D partition created despite task sequencer set to 100% primary drive??

[bondbill2k2]

Having some issues with deploying an image having recently implemented MDT however it keeps creating a D: drive after deployment.

 

The capture is taken from a VM which has 100% disk used as the C drive. The Task sequencer was set to partition just a single primary partition, set as the boot partition and use 100% of remaining space (screenshot attached).

 

Any idea why it keeps creating this D drive? The task sequence completed fine with no errors.

 

[ReadTheNetwork]

Is this for Win 7?

 

OSDPreserveDriveLetter=false

[sparkeh]

Is this for Win 7?

 

OSDPreserveDriveLetter=false

For any Win OS that you apply from a .wim really.

 

If you apply it without that then uses the drive letter that was used during the capture of the wim so could end up with anything. To be sure use the above

 

Here's a guide, there is a section on MDT: 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/

Edited June 7, 2017 by sparkeh