One of the things I took away from MMS last month was a desire for getting machines on UEFI - even Windows 7 machines so that we would be able to in-place-upgrade them to Windows 10 in the future. I am beginning to test flipping machines to UEFI during the OSD bare metal process for Windows 7 64bit.
My current environment is SCCM 2012R2CU4 + MDT 2013. For this testing process, I am interested only in deploying Windows 7 64bit to reasonably recent dell Optiplex models (9010 9020 9030). And in the first test case specifically an Optiplex 9010 running the current A24 firmware. I have a lot of the process worked out and functioning correctly, but I am running into a problem that I hope someone here will know about. I am able to switch the system to UEFI and disable legacy BIOS. I can partition the drive and boot WinPE back onto the staged WinPE boot image on the Hard Disk. I am able to lay down the Windows 7 64bit image. When it comes time to reboot into the full OS, I get an error. So it boots and reboots OK into the staged WinPE 5 x64 boot image, but will not boot into the Win7 x64 WIM that is deployed by SCCM. The error looks like this... Windows Boot Manager -Windows Failed to start-File EFI\Micrtosoft\Boot\BCD Status 0xc000000d An error occurred while attempting to read the boot configuration data. I booted back into WinPE and then ran diskpart to look at the partitions. I can only see three partitions instead of 4 The WinRE tools is part0, EFI is part1, and OSDisk is part2 - there is no MSR partition listed in between EFI and OSDisk. Not sure if there should be visible in diskpart or not - but it IS listed in the Format and Partition (UEFI) that runs on the client during the task sequence. If I enable legacy ROM when the computer is in this state, the computer will boot correctly. Do I need to do something myself to populate that EFI partition with an EFI bootloader or does the OSD process take care of that? My Windows 7 x64 machine is built on HyperV VM that is almost certainly emulating a BIOS with MBR partition machine. Is that the reason? When I look up the problem people suggest enabling Legacy ROM in the BIOS - but doesn't that defeat the who idea of UEFI? This web page makes me think I need to deploy both a Windows WIM to the OSDisk AND a EFI.wim to the EFI partition.... Where would I get that EFI.WIM from. https://technet.microsoft.com/en-us/library/cc765951(v=ws.10).aspx Here is the first bit of my task sequence where I am setting UEFI and formatting the disk to prepare for the Windows 7 image and the details of the UEFI partition step in the Preinstall phase. Help me Obi-Wan Kanobi. [cid:[email protected]]. [cid:[email protected]][cid:[email protected]] ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
