Im having serious problem after R2 upgrade and Im in a hurry to fix this, because OSD in production is interrupted.

So, before R2 upgrade, OSD with W7 x64 was working fine. Image had 2 indexes and it was captured with MDT based task, with 2 partitions (which is wrong, I know).

After I performed R2 upgrade, we noticed that Windows started go to D: drive. PreserveDrive letter variable has no effect, since image was captured previously in the wrong way. After I forced the image to go to C: By modifying Apply Image step (I changed from  OSDisk to Logical C:), I got W7 go to C: but now I can see BDEDrive letter in Windows Explorer. Enabling or disabling "do not assign drive letter to this partition" at BDEDrive partition has also no effect.

In WinPE and OSPhase, I can see drive letters with diskpart and BDEDrive has always come up with letter.

Capturing new image will take longer time to test everything else, so thats why Im trying to make this work with old image. CM 2012 R2 non-CU is with MDT 2013 and were using UDI based MDT tasks.

Any help or sightview is good, share you thoughts please :)

• Edited by yannara Monday, February 23, 2015 8:39 PM

Delete the MDT task sequence and create a new one. Edit the new TS and  edit the  format 6.1 and tick the bde partition not to assign drive letter.  Leave the preserve drive letter to false. Let us know t

Also Im thinking, should I update CU4 to my current non-CU R2 site?

I would recommend it, we experienced a couple of OSD related issues before we put CU4 on (the fixes were from CU1 or CU2 i believe).

Also, make sure you read this excellent post. It goes over the inconsitencies around drive letter assignment in task sequences, and how you can work around it.

We now use method 3 and we get the same behaviour every time.

http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx

Or this one: http://blogs.technet.com/b/configurationmgr/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx

• Edited by MikhailCompo 22 hours 9 minutes ago

Damn it, no way. I updated to CU4 and re-do my MDT+UDI TS only with one modification - I ticked on "do not assign drive letter to BDE".

My image is 1-indexed.

I still see D drive (BDE).