Solved

SCCM 2012 - WDS responding to PXE requests, not SCCM

Posted on 2013-10-30
11
2,472 Views
Last Modified: 2014-01-03
Hi Guys,

I am stumped on an SCCM / WDS issue where when a client PXE boots, they are hitting WDS rather than SCCM. Since WDS isnt configured / initialized it has no boot images and as such you are presented with a message that says as much (not the no pxe boot found error).

If I add a boot image to WDS, it will load this image however this doesnt load the SCCM bits and ultimately the task sequence that has been advertised.

I have uninstalled and reinstalled WDS in a number of ways. The only thing I havent tried is removing the dist point as this is the only SCCM server and I am worried about losing any packages ect that have been created.

Not sure where to go from here as I cant find anything on Google for this.

Thanks
Chris
0
Comment
Question by:Chris--W
  • 6
  • 5
11 Comments
 
LVL 8

Expert Comment

by:Leon Taljaard
ID: 39626361
Hi

Have you checked your DHCP settings, specifically option 66 as well as maybe looking at if option 67 is set and pointing to the correct file location.

Hope this helps a bit

Thanks
0
 
LVL 1

Author Comment

by:Chris--W
ID: 39641357
Neither option is set as this is all in the same subnet.
0
 
LVL 1

Author Comment

by:Chris--W
ID: 39692589
This issue is still ongoing. I have configured both option 66 and option 67 in DHCP, removed and reinstalled WDS in multiple ways to try and get this to work properly but no joy.

I have removed and re-installed SCCM but issue still exists.

When PXE boots it trys to use: boot\x64\pxeboot.com
Rather than: SMSboot\...
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 8

Expert Comment

by:Leon Taljaard
ID: 39692696
Hi

The only other thing I can think of right now is that there might be some corruption in your .wim files, I would remove the boot images and re add them again and also maybe check that your AV is not to blame and stopping something somewhere on the server.

Is your option 67 something like this \smsboot\x64\pxeboot.com ?

Thanks
0
 
LVL 1

Author Comment

by:Chris--W
ID: 39692752
I uninstalled AV on the server to make sure that it wasn't the cause.
Option 67 is set to: SMSBoot\x86\wdsnbp.com

My understanding is that when SCCM installs WDS it should only have a few folders in RemoteInstall, and if "boot" exists it wont work. I cant delete this as it just gets recreated.

This all went wrong when someone thought that WDS wasnt configured and went and configured it (20+ installs ago)
0
 
LVL 8

Expert Comment

by:Leon Taljaard
ID: 39692873
Ok have you also maybe looked to see if there are any "unknown" computers in your "All Systems" collection ? if there are any delete them then maybe try again ?

My PXE boot server has the boot folder in it and all works perfectly.

What error are you getting ?

Thanks
0
 
LVL 1

Author Comment

by:Chris--W
ID: 39694926
There are what looks like 2 devices in All systems, but they cant be deleted:
"x64 Unknown Computer (x64 Unknown Computer" and "x86 Unknown Computer (x86 Unknown Computer".

Attached is the error I get on the PXE client.
error.png
0
 
LVL 8

Expert Comment

by:Leon Taljaard
ID: 39694941
That's not good :)

Maybe try go to PXE options on the DP and untick enable, wait a while for WDS to uninstall then go back and tick it again, once WDS is installed again then try boot again.

Also do you have both boot images distributed, x86 and x64 ?

thanks
0
 
LVL 8

Accepted Solution

by:
Leon Taljaard earned 500 total points
ID: 39694951
Also maybe delete the "RemoteInstall" folder after un-ticking and removal if it doesn't remove it on its own
0
 
LVL 1

Author Comment

by:Chris--W
ID: 39754093
Resulted in a fresh install of Server 2012 and SCCM. I suspect that there is something in the registry that remembers that WDS was configured before and everytime SCCM installs it, it reverts to that state.
0
 
LVL 8

Expert Comment

by:Leon Taljaard
ID: 39754118
I am glad you eventually sorted it out.

Well done
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we have discussed the manual scenarios to recover data from Windows 10 through some backup and recovery tools which are offered by it.
I use more than 1 computer in my office for various reasons. Multiple keyboards and mice take up more than just extra space, they make working a little more complicated. Using one mouse and keyboard for all of my computers makes life easier. This co…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now