I'll have to try Michael's suggestion. Trevor, I too am worried about over complicating the process. The MDT integrated task sequence deployed the factory WIM to drive D and my custom WIM (generated using MDT) to drive E. So, this has me very worried as we get ready to move from SCCM 2007 to 2012.
I look at the simplicity of the native task sequence and the complexity of the MDT task sequence and I have to wonder if it's time for me to make a break from the tradition of using MDT integrated sequences and take this opportunity to start with a clean slate. I'll try Michael's suggestion and see where it leads. Thanks Mike From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, November 26, 2013 3:43 PM To: [email protected] Subject: RE: [MDT-OSD] OS Installed to Drive D using MDT+SCCM Maik, How about this reason: "So as not to overcomplicate an already complicated process." It's a matter of opinion, but I find that there are enough challenges with ConfigMgr OSD, and integrated concepts (Application management, Software Updates, custom scripts, etc.) to not need to introduce even more variables / issues. I don't want to get too off-topic concerning this thread, though. Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Koster, Maik Sent: Tuesday, November 26, 2013 1:54 PM To: [email protected] Subject: RE: [MDT-OSD] OS Installed to Drive D using MDT+SCCM The question is rather, why would someone not :P Maik From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Dienstag, 26. November 2013 19:07 To: [email protected] Subject: RE: [MDT-OSD] OS Installed to Drive D using MDT+SCCM 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]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, November 26, 2013 12:03 PM To: [email protected]<mailto:[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 [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/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 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: win7logoTiny] UMHS Windows 7 Everywhere by December 2013<https://processmgt.mcit.med.umich.edu/sites/mcit/customer/applicationsoftware/Pages/Windows7.aspx> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information of Cameron and its Operating Divisions. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message inclusive of any attachments. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
<<inline: image001.png>>
