hello well in my production environement i want to configure pxe in my platform to do OS deployment i have wds and SCCM on the same server and DHCP in a differente server i see in diffirents post i should configure the option 66 and 67: 066 IP Address of WDS Server 067 smsboot\x86\wdsnbp.com my questions are (i wante to be sure): 1\ the "smsboot\x86\wdsnbp.com" is the wdsnbp.com in the remote install folder ??? when i saw my remote install folder the wdsnbp.com is in boot\x86 not in smsboot\X86 2\ should i change the port 67 to boot\x86\wdsnbp.com 3\ i should configure just this two options ??? thanks

Hi, There is no need to configure any DHCP scope options. In the case of SCCM PXE Service Point, we want the SCCM 2007 site server containing the PXE Service Point, and not the DHCP server, to answer the PXE requests and provide the information for the NBP . Since we do not want the DHCP server to answer the PXE requests and provide theinformation for the NBP, DHCP Scope Options 60, 66, and 67 should NOT be set. When crossing subnets and vlans, IP Helpers in routers/switches should be used to route PXE requests to the SCCM 2007 site server hosting the PXE Service Point role. DHCP Scope Options 60, 66, and 67 should NOT be used to route the PXE requests. The IP Helpers that need to be setup and configured on routers/switches to properly support PXE in SCCM 2007 are as follows: 1) All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server/SCCM 2007 site server hosting the PXE Service Point role. 2) All traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server/SCCM2007 site server hosting the PXE Service Point role is routed appropriately (these requests direct traffic to the server, not broadcasts). -Ankur

i think we can use the two way but it recomended to us ip helper

Yes, you can use both ways.

I experiance problem with running WDS and DHCP server on different servers and the reason for that is IP DHCP SNOOPING on the Cisco enviroment. If you configure your route to send the DHCP broadcast to both the DHCP and WDS server, both of them replies, and the Cisco IP dhcp snooping will then dropping the DHCP request. If you disable the DHCP snooping on the switch port then it works So, anyone got a good working setup for split role setup of the WDS and DHCP services on a Cisco network enviroment which is running ip dhcp snooping? Turning off IP dhcp snooping is not an options!