Thanks for the responses. Inhouse deployments are done with non-MDT media and all of our current systems use legacy BIOS, but we will be transitioning to UEFI shortly for both new hardware and re-image/Win10 upgrades, so might as well just set that expectation now.
David From: [email protected] [mailto:[email protected]] On Behalf Of Joe Krilov Sent: Wednesday, March 30, 2016 10:27 AM To: [email protected] Subject: Re: [MDT-OSD] MDT build & capture image not bootable as stand-alone image? Are you deploying the WIM using offline media created with MDT? If so it should be running BCDBoot for you. Otherwise you'll need to run it manually as you have been. -Joe On Wed, Mar 30, 2016 at 8:58 AM, Fast, David D. <[email protected]<mailto:[email protected]>> wrote: I am trying to run a build & capture in MDT 2013u1 to create a Windows 7 thick image for delivery to our workstation hardware provider. The image will be applied to new PC orders using standalone WinPE. When I apply the image to a blank drive that has been partitioned/formatted using Diskpart, the system will not boot unless I run “BCDBoot c:\windows /s c:” My previous image builds were essentially manual process (install the OS from disc, run a script to install apps, sysprep and capture from WinPE boot disc), and those captured images are bootable by default with no extra steps required. Both the MDT task sequence for the Build steps and the vanilla WinPE Diskpart settings are configured to partition and format as a single partition. On the manual builds, the image was captured with ImageX using default settings for file exclusions, etc. What is different with the MDT-driven image capture, and can it be modified to capture/apply the boot files? Thanks, David ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
