The fix was to open WDS on our servers with DHCP, and ensure these two boxes are checked. After doing so, restart the WDS service, and you're good to go!
On Mon, Oct 12, 2015 at 2:04 PM, Nick <[email protected]> wrote: > Have you seen this? > > > http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/ADS/en-us/nbs_configure_dhcp_pxe_collocation.mspx?mfr=true > > Configurations that implement DHCP and PXE services on the same system > must make the following DHCP option effective to cause the client to return > the same system for PXE discovery. You must turn off the binding to port 67 > by using the PXEUseDHCPPort registry setting or by using the ADS Management > snap-in > > > > We don’t run DHCP on the same servers, so I couldn’t validate anything for > you. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Owen > *Sent:* Monday, October 12, 2015 1:46 PM > *To:* [email protected] > *Subject:* [mssms] SCCM 2012 R2 Sp1 - deploying PXE-enabled DP on a DHCP > server?? > > > > Hi guys, > > > > Hitting a serious snare in this configmgr deployment. I found some WDS > issues around the environment after migrating DPs yesterday and have found > today that a handful of the DPs in my environment are also running DHCP. > > > > I'm finding no real results in my googling. How should the DHCP options > be set if my DP is running on a DHCP server? I found the checkbox on WDS > to specify SCCM not to listen on port 67 anymore, so now DHCP and WDS will > both start, however I'm not getting any more PXE boot requests logged on > this machine. > > > > Thanks guys, > > > >
