[sccm 2012] PXE build now booting into WDS

[clareq]

Having successfully built machines via SCCM for the last 18 months, today PXE booting a machine starts the WDS interface. How do I troubleshoot this? We applied the latest Windows updates last night - could that be the issue?

[clareq]

Bump I'm starting to run out of ideas. I've tried uninstalling and reinstalling WDS, but it hasn't helped.

[DJ-1701]

Unfortunately I myself am not familiar with SCCM, just WDS and MDT.

Does SCCM make a separate boot image on the network boot option? If so selecting a default boot wim in WDS or renaming of the bootable wim file may reorder it.

[clareq]

No, I don't think it does.

[free780]

Basically you shouldn't touch the WDS mmc use the sccm console. Remove the pxe role by unticking the box in the DP properties wait 30 mins. Then tick it and add it. Distmgr.log should show you when it's done.

[clareq]

Yes, I tried that - when I said I uninstalled WDS that is how I did it.

[clareq]

I tried removing and reinstalling WDS once more, monitoring the log @free780 referenced. Now I have a different error message - The Windows Boot Configuration Data file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. Error code 0xc0000098

[clareq]

SMSPXE log gives the following error:

Prioritizing local MP http://DAN-SC-001.int.danum.org.	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
RequestMPKeyInformation: Send() failed.	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
Failed to get information for MP: http://DAN-SC-001.int.danum.org. 80004005.	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
reply has no message header marker	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
Failed to send status message (80004005)	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
Failed to send the status message	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
PXE::MP_ReportStatus failed; 0x80004005	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)
PXE Provider failed to process message. 
Unspecified error (Error: 80004005; Source: Windows)	SMSPXE	17/02/2016 09:10:18	3968 (0x0F80)

[free780]

You need to distribute both x86 and x64 boot images from the console.

[clareq]

I have. Triple checked that one. It's looking like it's the Management Point role that's at fault (from the log entries posted above), but removing and reinstalling that hasn't helped. I am now restoring an older version of the server from before the updates in order to try that. if that doesn't work it's a new SCCM server and transferring the MP and DP roles.

[clareq]

Restore has run, and The Windows Boot Configuration Data file error has gone, but I'm still booting into WDS not SCCM. I'm open to any suggestions...

[Norphy]

Is it possible that there's another server on the network somewhere which has WDS installed on it and is responding before your DP?

 

What happens if you power off your DP entirely and attempt to netboot?

[clareq]

There shouldn't be, but I'm getting desperate😀 I'll give that a go first thing.

[clareq]

@Norphy - good news - there isn't a rouge WDS server on our network. Bad news, I'm no nearer PXE building.

[clareq]

Fixed it. I had moved WSUS to another Server, as it never really worked properly via SCCM. Uninstalling the WSUS role from the SCCM server broke PXE. I reinstalled WSUS, but didn't configure it. Once I had reboot, building via PXE started working again.