I have searched all though these formus, Technet, and any place Google will send me. Any assistance would be appreciated.
I'm setting up a new distribution point ("newDP") with dedicated hardware to be used for OSD. The DP is setup, but clients continue to hit the IP of the original DP, despite PXE being disabled on the Orig, but enabled on the New DP.
Windows Boot Manager (Server IP: "origDP")
Info: The Windows Boot Configuration Data file does not contain a valid OS Entry
Note that the error indicates the IP of origDP, which is NOT enabled for PXE. The boot files are indeed present (on both DPs).... the problem is wrong IP/server.
We do not need or use DHCP option 66 because client and server on same network segment. The SCCM server simply replies directly to broadcast request for PXE server.
Verified DHCP Option 66 isn't responding with the OrigDP address
Ensured Restarted WDS service on orig and newDP. Also restarted servers.
Ensured boot images (and pxeboot.com) files were present on newDP
Erased hard drive of a client device in case somehow using a cached IP from the hard drive (note: it is all clients, though)
Ensured PXE is enabled on general tab of newDP, boot images, and Task Sequence
If I shut down origDP entirely (instead of just disabling PXE), the error changes to TFTP timeout.
The SMSPXE.log file on newDP is not updated. It's not updated on origDP either (when PXE/WDS is disabled)
I cannot imagine why the IP in the error is for a server not even configured to respond to PXE requests. It's been vexing me for a week and my management is becoming impatient. Any help is GREATLY appreciated. Thanks!