Hello
Recently at our company we decided to finally switch our OSD from standalone WDS server with MDT to our SCCM server. For some time alraedy I was getting ready for that, so I have my MDT2013 integration, boot images, OS images and TS ready (and tested via media boot). Last piece was to enable PXE on our distribution point. And this is where it got ugly.
What I did: I enabled PXE in properties TAB of our DP, enabled unknown computer support, provided password and turned on User-Device affinity for auto aproval. After that WDS server role was installed on the SCCM server (I left all the settings of WDS unchanged, besides that, my literature research showed that they are not used anyway.).
Our network guys configured options 66, 67 on DHCP server.
Then, I enabled "Deploy this boot image from the PXE-enabled distribution point" on Data Source tab of both my MDT based images and both default SCCM boot images. Then I redistributed them to the DP.
According to the books, this should be pretty much everything.
Now I went and tried to boot my test PC. It obtained IP address from DHCP (good). Then id downloaded WDSNBP from SCCM server (good). Then there were those lines: "Contacting Server: XXX (Gateway: XXX)..." and "No response from Windows Deployment Services server" (this I assume happens because options for the WDS server are basicaly unconfigured).
Last thing I see is "Press F12 for network service boot". If I don't hit it, whole process ends with "PXE-M0F: Exiting PXE ROM" message. If I hit f12 I recieve a blue screen.
File:\boot\bcd
Error code: 0xc0000000f
What is strange is that I get almost no information from SMSPXE log, only 3 lines:
For unknown computers:
Prioritizing local MP XXXXXXXXXX. SMSPXE 2016-02-16 11:46:11 7704 (0x1E18)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 2016-02-16 11:46:11 7704 (0x1E18)
10:60:4B:7C:51:D3, B1896A80-64B4-11E2-B1B0-10604B7C51D3: device is not in the database. SMSPXE 2016-02-16 11:46:11 7704 (0x1E18)
And for known computer, with OS deployed onto collection:
Prioritizing local MP XXXXXXXXXXXX. SMSPXE 2016-02-16 12:39:16 7704 (0x1E18)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16784247" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 2016-02-16 12:39:17 7704 (0x1E18)
A4:1F:72:79:97:F3, 4C4C4544-0054-4410-8034-B9C04F4B5931: device is in the database. SMSPXE 2016-02-16 12:39:17 7704 (0x1E18)
On the serverside, in eventviewer regarding WDS i see that the client downloaded first wdsnbp.com, then pxeboot.com, then bootmgr.exe and lastly some fonts. No errors, nothing I would think is relevant.
Now I'm stuck, because I don't really know WHERE the problem lies. I scratched out network connectivity, since it downloads files via TFTP from the SCCM server. I would blame it on the boot image drivers, but the very same images worked perfectly via usb boot. And logs seem to be almost empty in that matter, so rather than having an error, I think something is not happening at all, only I don't know what exactly.
What I tried as resolution:
-Disabled PXE on DP, that removed WDS server. Later I restarted SCCM and reenabled the option, to recreate whole thing. (Removed remoteinstall folder in the meantime, to get rid of any old stuff)
-Stopped the WDS service, removed mgmt folder, started the service (as described here: https://social.technet.microsoft.com/Forums/windows/en-US/0efa6c4c-d10b-4bea-b5f6-66fe95c7e11b/no-response-from-windows-deployment-services-server?forum=itprovistadeployment )
-Redistributed boot images to the DP.
I would gladly appreciate any hint to what I should look for, as I am pretty confused right now.
Best regards
Jakub Drobiński