Remember, images are nothing more than CAB files - they are file based and have zero hardware specific information. So, for the image itself, no there's absolutely nothing you need to do. As for prepping the hardware, that's a bit different. In general you need to have the appropriate partitions of course (the EFI, the MSR, and the System) and these must be formatted correctly - the default TS in 2012 R2 will take care of this. There are other possible factors though well beyond the control of ConfigMgr like enabling UEFI in the BIOS.
J From: [email protected] [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Monday, April 14, 2014 1:11 PM To: [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
