Thanks. That make sense. I am using Hyper-V currently, but am thinking of switching back to Virtual Box for greater flexibility. No drivers needed in either one that I've found. I was hoping that HyperV would improve in Server 2016, but as far as I can tell it is still missing USB pass through and 802.1x authentication. Virtual Box, I am pretty sure does both of those things.
While I am not loading any drivers , I am trying to inject 5-10 updates and it was their failing in DISM that led me to start examining the task sequence more closely. Anyway, thanks for the information on the order of things. ________________________________ From: [email protected] [[email protected]] on behalf of Brian Klish [[email protected]] Sent: Monday, November 14, 2016 6:43 PM To: [email protected] Subject: Re: [MDT-OSD] MDT Reference Image Build question By the way, if it's a reference image then you should be building it on VM's and in my experience you don't need any drivers if it's a Hyper-V VM anyways. Not sure about other virtualization platforms. Might need boot or network drivers potentially, but unlikely. On Mon, Nov 14, 2016 at 7:37 PM, Brian Klish <[email protected]<mailto:[email protected]>> wrote: Someone may correct me if I'm wrong, but I believe the drivers are staged for setup.exe to consume during installation. Apply patches would be if you had imported packages in to MDT that needed to be applied. MDT will do it via DISM offline servicing before it boots the OS. On Mon, Nov 14, 2016 at 7:02 PM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: This question refers to MDT 2013 U2 stand alone being used to build a Reference Image. I have maybe a stupid question, but I cant figure this out… In the Standard Task Sequence, why do the task sequence items “Inject Drivers” and “Apply Patches” occur in preinstall --- before the “Install Operating System” step? How does that work? Isn’t it the OS image that was just applied the thing we are patching and injecting drivers into? How does it work to have those steps before the image is deployed? I am just trying to track down some DISM errors in applying patches and noticed this and I can’t figure out why these appear to be in the wrong order – patch before OS is installed… ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________
