Just a wild guess, but maybe resetting some environment variables might help?
Sent from my iPhone > On Dec 31, 2015, at 5:14 PM, Miller, Todd <[email protected]> wrote: > > > I am trying to take a machine that is Legacy BIOS and switch it to UEFI > during a bare metal install. So take a machine out of the box and end up > with a UEFI enabled, GPT partitioned, bitlockered, Windows 7sp1 x64 > deployment (fully automated) > > > So the system boots in Legacy bios to a USB Stick with the WinPE 5.1 64bit > boot image. Then I am using Dell tools to switch the Firmware to UEFI mode. > Then I repartition the disk in the GPT format. Then I want to reboot the > task sequence to boot into UEFI mode from the newly GPT partitioned disk. My > problem is that “Restart Computer” task step refuses to stage the WinPE image > on that GPT partitioned disk. > > The error says that disk C: is on a GPT disk, but the system is MBR. It is > unable to see that I have just switched the Firmware to UEFI and so it is > refusing to stage WinPE on that GPT partition. I would have sworn I had > this working, but now it is broken. Can TSCore.dll be made to reevaluate the > Firmware state so it can see that the Firmware has been switched to UEFI? > > Any ideas on how to trick “Restart Computer” step into staging the WinPE > image to the boot drive – even though it thinks the partitioning scheme is > wrong? It isn’t realty wrong… if it would just stage it and reboot, it would > boot OK. > > > > SCCM 2012R2Cu4, OSD+MDT2013, deploying Windows 7sp1 x64, boot image is WinPE > 5.1 based. > > > My other solution would be to force the desktop support staff to go in an > manually set the BIOS to UEFI mode and then restart the process, but that is > unreliable since it is not automated. > > > 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.
