How to fix windows server 2022 WDS stop working after installed hyper-V role

Question

Hi all,

we have a signl server 2022 installed AD DS, DHCP, DNS and WDS for computer development test, we use this server test our projects with shippong/test OS and applications. we encountered HLK test issues recently, we want to duplicate these HLK test issue and find out solutions, so we installed hyper-V role and prepare to use virtual HLK server vhdx to setup our test environment. we found the WDS always stop working while it looks it works well in server manager after installed hyper-V role. to make WDS service resume from stopping work, we try to restart it. but failed. the only solution is restart windows server 2022 again. is there any potential conflict between WDS and hyper-V？ and how can we make WDS and hyper-V co-exist in the same system?

Answer 1

Hello DaMingA Wu,

Thank you for posting in Q&A forum.

There can be conflicts between Windows Deployment Services (WDS) and Hyper-V on the same server. These conflicts often arise due to network configuration issues, as both services can interfere with each other's network settings.

Here are some steps to help WDS and Hyper-V work together on the same server:

1. Separate Network Adapters:

• Use separate physical network adapters for WDS and Hyper-V. This can help avoid conflicts between the services.

2. Configure DHCP Options:

• Ensure that DHCP options are correctly configured to support both services. For example, configure DHCP to not listen on port 67 and set option 60 to indicate the presence of a PXE client.

3. Adjust Virtual Switch Settings:

• In Hyper-V, configure the virtual switches to avoid conflicts with WDS. Ensure that the virtual switches are properly set up and do not interfere with the network traffic required by WDS.

4. Service Order and Dependencies:

• Ensure that the WDS service starts after the Hyper-V services. You can adjust the service dependencies in the Services console (services.msc).

5. Check Event Logs:

• Regularly check the Event Viewer for any errors or warnings related to WDS and Hyper-V. This can help identify specific issues that need to be addressed.

6. Consider Role Separation:

• If possible, consider running WDS and Hyper-V on separate servers to avoid conflicts altogether.

Port for WDS:

UDP Port 67: Used by DHCP and PXE boot services. WDS listens on this port to respond to PXE boot requests.

UDP Port 69: Used for TFTP (Trivial File Transfer Protocol) to transfer boot files to the client.

TCP Port 135: Used for RPC (Remote Procedure Call) communication.

UDP Port 4011: Used by WDS to listen for PXE boot requests when the DHCP server is on a different server than WDS.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.