Running BCDBoot.exe after applying the image to the target machine is the correct process.
Wim files are captured on a per-volume basis, so if this is a UEFI machine (which I hope it is), then it won't capture the boot files on the UEFI (FAT32) System partition, so running BCDBoot is necessary. -k From: [email protected] [mailto:[email protected]] On Behalf Of Fast, David D. Sent: Wednesday, March 30, 2016 5:58 AM To: [email protected] Subject: [MDT-OSD] MDT build & capture image not bootable as stand-alone image? 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.
