PXE booting WIN10 UEFI VmWare Workstation.
-
Hi
All machines (FOG (Ubuntu) Windows 2016 server and WIN10 client) are all on VmWare Workstation.
Have windows 2016 server setup as DHCP server.
Try to PXE booting UEFI WIN10 PC in VMWare, but no luck.
Change WIN10 to BIOS instead of UEFI, then everything is working.How to get UEFI working ??
BR
OFH -
@ofh said in PXE booting WIN10 UEFI VmWare Workstation.:
Try to PXE booting UEFI WIN10 PC in VMWare, but no luck.
Please give us more information on what you mean by “no luck”? Take a picture of the error and post here!
Probably this is caused by the DHCP server not sending the right iPXE binary to the UEFI client. What is serving DHCP in your network? Is it the FOG server or some other service?
-
If the problem is similar to the one I’ve been experiencing, you get the normal screen that presents the option to deploy image, register host etc etc, then when you chose the option to register a host, the white background disappears and the continues a normal boot from the virtual disk.
The guide I was following to set it up mentioned that FOG wouldn’t capture from UEFI.
After building my Win10 image (tried with 1903 and 1910) and getting the same problem I found took a different approach. Build the Windows system, sysprep it. Before booting again, change the system type from UEFI to BIOS (as we’re not booting Windows it won’t matter). Then registered the host and reboot to capture the image.
Only thing I found was that when I restored to another VM it had to be set with the virtual disk attached as SATA not SAS.
The guide I followed which mentioned the issue about UEFI capture is below.
https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/Running Fog 1.5.7 from a Centos 7 host, ESXI is 6.7u3
-
@marc49ca Thanks for your input on this. Though I feel like it’s not related to the OP’s question on VMware Workstation.
The guide I was following to set it up mentioned that FOG wouldn’t capture from UEFI.
This statement is no true in general (as you post it here)! What’s mentioned in that guide is:
One more thing, make sure that Legacy Boot (not UEFI) is enabled on whatever computer you want to capture or deploy. I think FOG supports UEFI already but I haven’t looked into it yet.
This is specific to VirtualBox being used in that tutorial and not caused by FOG but simply an issue within VirtualBox that doesn’t properly PXE boot UEFI VMs. I am not exactly sure if this is still true for the latest version. I don’t think so but maybe. ESXi is not like VMware Workstation is not like VirtualBox.
After building my Win10 image (tried with 1903 and 1910) and getting the same problem I found took a different approach. Build the Windows system, sysprep it. Before booting again, change the system type from UEFI to BIOS (as we’re not booting Windows it won’t matter). Then registered the host and reboot to capture the image.
This hint on using legacy BIOS mode just for capturing might be helpful in the OP’s situation as well! Good point.