Windows Deployment Services relies on both DNS and DHCP for its functionality.
DNS is used to help located the WDS server in your network. DHCP is used to hand out IP addresses to your clients and the address of a DNS server so they can locate resources, in this case WDS, and communicate with it.
According to Microsoft’s documentation, you can utilize non Microsoft products to provide DNS and DHCP services to your WDS environment. Something to note is that you must select the following two options during the WDS configuration:
If the non-Microsoft DHCP server is located on the same server as WDS, you will need to configure the server to listen on port 67 and also to add Option 60 to your DHCP scopes.
If the DHCP server is installed on a different subnet, you will need to configure your router to forward broadcast packets to both the DHCP and the WDS server. You will also need to route traffic from UDP port 4011 from the client to the WDS server.
http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx
DNS is used to help located the WDS server in your network. DHCP is used to hand out IP addresses to your clients and the address of a DNS server so they can locate resources, in this case WDS, and communicate with it.
According to Microsoft’s documentation, you can utilize non Microsoft products to provide DNS and DHCP services to your WDS environment. Something to note is that you must select the following two options during the WDS configuration:
If the non-Microsoft DHCP server is located on the same server as WDS, you will need to configure the server to listen on port 67 and also to add Option 60 to your DHCP scopes.
If the DHCP server is installed on a different subnet, you will need to configure your router to forward broadcast packets to both the DHCP and the WDS server. You will also need to route traffic from UDP port 4011 from the client to the WDS server.
http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx
Comments