WDS PXE Uefi not working in AD integrated mode, TFTP to slow
dear all
1 physical host: w2k12r2, 1 hyper-v virtual switch.
1 hyper-v vm w2k12r2 dc dns, dhcp, wds.
1 empty hyper-v vm generation 2 uefi booting network.
problem: error "pxe-e16: no offer received" on empty hyper-v vm when trying uefi boot wds in ad integrated mode.
i verified works when wds set-up standalone mode. see also: https://social.technet.microsoft.com/forums/windowsserver/en-us/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode
ps: switch standalone mode: on wds server: wdsutil /verbose /uninitialize-server /server:<servername>; wdsutil /verbose /progress /initialize-server /server:<servername> /reminst:c:\rminst
cause (found netmon ip traffic monitoring):
the client asks tftp server on udp port 4011.
the tftp server takes more 8 seconds reply on port 4011.
seems due nbtns (netbios name search) broadcast queries searching 1c domain controllers.
solution: ???????
any appreciated.
dominique, zürich, switzerland.
hi dominique, zürich, switzerland.,
you can create virtual machine act client machine when building , testing deployment images. useful building custom images. note, however, performance degraded, particularly during trivial file transfer protocol (tftp) download phase. phase resource-intensive , may fail if insufficient resources available on server running hyper-v, use physical computer configure same settings monitor issue again.
the related kb:
windows deployment services overview
https://technet.microsoft.com/en-us/library/hh831764.aspx
i’m glad of you!
please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com
Windows Server > Setup Deployment
Comments
Post a Comment