情形1：If DHCP is installed on a server that is located in a different subnet, you will need to do one of the following:（二选一）
1.Add DHCP options 66 and 67.
Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com. For more information, see Managing Network Boot Programs (http://go.microsoft.com/fwlink/?LinkId=115304).
2.(Recommended) Configure your router to forward broadcast packets.
All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services server should be routed appropriately (these requests direct traffic, not broadcasts, to the server).
情形2：If Windows Deployment Services and DHCP are running on the same computer, configuring Windows Deployment Services to not respond to any client computers will not work. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP option 60 on the DHCP tab
情形3：If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to your DHCP scopes.
In Additional，Internet Protocol version 6 (IPv6) is not supported for Windows Deployment Services in Windows Server 2008. Windows Server 2008 R2 does not support IPv6 for network booting, but does support IPv6 for deploying p_w_picpaths.