Please note: VMware is not Microsoft’s product, we have no condition to test them, you’d better consult VMware support directly for some ideas.
About Q2: Yes, but it is not the main problem, slow down performance should not obvious.
Let’s see the following two scenarios:
- If WDS and DHCP are running on different servers but on the same subnet so broadcasts are not a problem: As long as the client deploying an image from the WDS server and the WDS server are on the same subnet and different servers, everything works fine with no DHCP options configured.
- If WDS and DHCP are installed on the same server: You must tell WDS not to listen on port UDP 67, leaving it available for DHCP traffic only. But then how does the client find the WDS server? You set option 60 in DHCP.
If you install WDS on a server that's already running DHCP, during the configuration of WDS the DHCP Option 60 page will appear, and you can select both Do not listen on port 67 and Configure DHCP option 60 to “PXEClient”. If you install DHCP on a machine that already has WDS installed, you must manually enable option 60 in DHCP.
If fact, it is kind of strange that configure a physical WDS server and virtual clients on the same physical server for WDS experiment, why not just use the Hyper-V on your physical WinServer 2016, create multiple Virtual machines, one VM is WDS server and others are clients, make all of them on the same subnet then do your experiment…
-------------------------------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.