Make sure you use a 32 bit boot image for deployment of a 32 bit OS and 64bit boot image for deployment of a 64bit.
From: Keith Garner [mailto:[email protected]] Sent: 15 April 2014 07:01 To: [email protected] Subject: RE: [MDT-OSD] EFI based deployments There is not nothing special you have to do *capture* a machine to make it uEFI ready, except for the ubiquitous sysprep command. Remember, wim files will only capture a single partition, and MDT+OSD only understands how to use a single partition. However... you do need to *prep* the target machine with the correct partitions, and lay down the Windows Image to the correct partition, *and* set the correct system files for booting in the correct place. BootSys.exe is the correct tool to ensure that a machine that has been given a OS install image has been prepared correctly. That being said, you have excluded a lot of information in your question. Are you using MDT, OSD, or did you roll your own deployment method? Are you mixing CSM mode with uEFI firmware deployments? Check ZTIGather --> isUEFI = TRUE? Did you run bootsys.exe or did you attempt to lay down the correct boot files by hand? Is there a common denominator with the machines that fail? Are they uEFI 2.3.1 secure boot machines? Etc... MDT and OSD should handle this automatically, not sure why you are having problems. :( -k From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Monday, April 14, 2014 11:11 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] EFI based deployments Do you have to do anything special when you capture an image if you are going to deploy it to a UEFI based system? I haven't ready anything specifically that said yes except for one blog article that said the image needs to be captured from a VM that is in EFI mode. However, I have not done that and have deployed it successfully to some machines. On some models however, I keep getting the same error. It fails to boot with the following message: Location: EFI\Microsoft\Boot\BCS Status: 0xc000000d Info: An error occurred while attempting to read the boot configuration data Thanks! Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State _____________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of Leeds College of Building. For more information please visit http://www.symanteccloud.com _____________________________________________________________________ _____________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of Leeds College of Building. For more information please visit http://www.symanteccloud.com _____________________________________________________________________
