D: drive issue driving me to madness

Question

I typically use MDT Lite Touch to build and capture so this is really the first time I am running up against this..
Trying to use SCCM 2012 R2 with MDT 2013 to build and capture and subsequently deploy a Windows 7 x86 Enterprise image.  I am aware of the issue with Windows 7 being defaulted to the D: drive on the install.wim as well as the OSDPreserveDriveLetter variable.  The only
way I have successfully got Windows 7 to come up on the C: drive is by not assigning a driver letter to the BDE partition during deployment, however this results in a client install failure during the task sequence.
The things I have tried:
Build and Capture: Setting the OSDPreserveDriveLetter to False, and allowing it create the BDE partition prior to applying the Install.wim.
Deployment:  Setting OSDPreserveDriveLetter to False, creating both BDE and OS partition, assigning drive letter to both.
Result: D:\
Build and Capture: Setting the OSDPreserveDriveLetter to False, and NOT creating the BDE partition prior to applying the Install.wim.
Deployment:  Setting OSDPreserveDriveLetter to False, creating both BDE and OS partition, assigning driver letter to both.
Result: D:\
Build and Capture: Setting the OSDPreserveDriveLetter to False, and NOT creating the BDE partition prior to applying the Install.wim.
Deployment:  Setting OSDPreserveDriveLetter to False, creating both BDE and OS partition, Only assigning drive letter to OS partition.
Result: C:\ but ccmsetup fails during deployment.
Build and Capture: Setting the OSDPreserveDriveLetter to False, and NOT creating the BDE partition prior to applying the Install.wim.
Deployment:  Setting OSDPreserveDriveLetter to Blank (per the MDT 2013 release notes), creating both BDE and OS partition, assigning driver letter to both.
Result: D:\
Build and Capture: Setting the OSDPreserveDriveLetter to False, and NOT creating the BDE partition prior to applying the Install.wim.
Deployment:  Setting OSDPreserveDriveLetter to False, adding "whack.wsf" ( with some needed modification to allow it to run,
http://keithga.wordpress.com/2013/09/17/osdpreservedriveletter/) after applying image, creating both BDE and OS partition, assigning driver letter to both.
Result: C:\, but ccmsetup fails during deployment.
Everything I read says by simply capturing with OSDPreserveDriveLetter to False should be sufficient for enabling C: as the partition during deployment, regardless if you specify the variable again or not.
Can anyone shed some light on what I may be missing here?
Thanks!

Answer 1

OK, so the that worked!  Windows is now installing as C:\ and ccmsetup is executing successfully.
What I used:
Native SCCM Build and Capture task sequence.  Only creating a single partition (i.e. no BDE Drive) and adding the ts variable OSDPreserveDriveLetter = False prior to Apply Image task.
I then deployed it via MDT Task Sequence that created both BDE and OSDisk partition (with drive letters for both).  I did NOT include the ts variable OSDPreserveDriveLetter, and my "Setup Windows and ConfigMgr" properties is simply SMSMP=myserver.mydomain.com.
So, certainly seems related to MDT B&C.  Either way thank you very much for the nudge in the right direction. :-)