Mike,
Just curious: Why are you integrating MDT into ConfigMgr? Is there some specific functionality you need? Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, November 26, 2013 12:03 PM To: [email protected] Subject: [MDT-OSD] OS Installed to Drive D using MDT+SCCM This one has me scratching my head. I have an SCCM 2012 R2 server set up and a "native" (no MDT integration) OS deployment task sequence. I'm deploying the factory install.wim. I use a collection variable to set OSDPreserveDriveLetter to False. This works fine, my OS (Windows 7,8,8.1) install fine and show up on the C drive. So far, so good. I then install MDT2013 and create an MDT integrated task sequence. I deploy it to the same collection as my non-MDT integrated task sequence and I have not touched the "Set Variable for Drive Letter" within the task sequence that sets OSDPreserveDriveLetter to false. But when I deploy Windows 7 using it the OS drive is D:. Is there a trick to get the MDT integrated task sequence to install the OS to the C drive? Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA [ <https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile> Profile] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb UMHS Windows 7 Everywhere by December 2013 <https://processmgt.mcit.med.umich.edu/sites/mcit/customer/applicationsoftwa re/Pages/Windows7.aspx> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
<<image001.png>>
