![]() ![]() When no boot file is configured, the WDS will decide what boot file to use: legacy boot or UEFI boot. Its a very basic network setup that i have created just to test the fundamentals of WDS, which is list below: Both servers are domain joined and are VM's on Workstation 14.1. The best way to solve this is to delete the DHCP scope options 66 and 67, configure IP Helpers on the switches, and add the IP address of the deployment server so that the clients are able to find the WDS. And as mentioned above i load the win10 "cd" to its local "cd drive" and it still couldnt boot UEFI. I have read numerous forum posts, one said you need to add DHCP options 66 & 67 which i did but had not effect. WDS will hear the dhcp/pxe boot request and supply the pxe booting client computer with the proper boot file name. I also tried loading the win10 iso into the vm's virtual cd drive and tried to boot with UEFI and i have the same problem. It then just returns me to the boot menu to select hdd, cd or network. Ensured its on the right network but when it trys to PXE boot it just says: ![]() In the create a new VM wizard on Workstation i have selected windows 10 and UEFI boot. My WDS server also a workstation vm on the same host, which works perfectly deploying to BIOS based vm's. I'm trying to get a VM to spin up on VMworkstation 14.1.2 using UEFI boot and install Windows 10, via WDS. If your environment is like mine and you are getting new equipment. Been banging my head a against this problem for a couple days now. However, some NBPs can only deploy to traditional BIOSs and others can deploy to EFI/UEFI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |