Jump to content






Recommended Posts

Hi all,

 

I have looked all over the Internet and found people with the exact same problem, but I can't seem to fix this issue with the suggested solutions.

 

Suddenly PXE boot stopped working.

It worked for a couple of months.

No changes have been made on SCCM, Firewall or DHCP but PXE suddenly stopped working.

 

Error message (also see attached file):

Your PC needs to be repaired

The Boot Configuration Data for your PC is missing or contains errors.

File: \boot\bcd
Error code: 0x000000f

You'll need to use the recovery tools on your installation media. If you...

Our situation:

SCCM 2012 R2

9 Distribution Points on different sites. PXE is failing on all remote locations.

DHCP Options are all set and are not changed since we've set it up.

Option 67 is: \smsboot\x64\wdsnbp.com

In the Boot Image Properties > Dara Source the option "Deploy this boot image from the PXE-enabed distribution point" is checked.

Both x86 and x64 Boot Images are deployed on the DP.

We do have a custom Boot image though, only x64 as we don't deploy x86 systems. We only deploy x64 Windows 8.1.

 

in the SMSPXE.log file I don't see any errors.

There is, however, one part that keeps coming back (change MAC address):

00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: device is not in the database.
00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced.
00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced.
00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced.
00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced.

So the SMSPXE.log file is full of these.

My guess is that this has something to do with the problem.

 

 

Any more suggestions?

Thank you.

 

 

 

post-31237-0-69308000-1441952826.png

Share this post


Link to post
Share on other sites


Hi,

Is it the same computer model you are trying to image? Are you using unknown computer support?

DHCP Options should not be used, when PXE booting a device that runs UEFI instead of Leagcy BIOS it will fail as the boot file name is different from the one you are pointing on..

Regards,
Jörgen

Share this post


Link to post
Share on other sites

Hi Jorgen, We have different computer models:

A couple of Dell laptops (Latitude E5520, E5540, Precision, etc...) and Microsoft Surface Pro 3

 

On all the laptops Legacy Boot is enabled.

PXE worked for a couple of months on all these models btw.

The MS Surface is being deployed with a bootable USB because we don't have that many of them.

 

Gr

Share this post


Link to post
Share on other sites

When you say you don't use an x86 boot image, do you at least still have one?

WDS PXE doesn't work unless both boot images are present even if you're not using one. The x86 doesn't need drivers in or anything if you're not using it but it does need to be enabled for PXE and distributed.

 

Edit: just noticed you did say the x86 is distributed, but is it enabled for PXE?

 

Also regardless of the bit level of boot image your DHCP option points to SCCM will actually load the WinPE image that was associated with the last task sequence that was deployed to any collection, so if you've deployed a TS that uses anything other than your usual x64 image it could be that.

I recently discovered that this still happens even if the last deployed TS uses a boot image that isn't PXE enabled, resulting in completely broken PXE.

Share this post


Link to post
Share on other sites

Hi phil,

 

Yes, the x86 boot image is also enabled for PXE.

Now that you've mentioned it... We have created a new custom Task Sequence with a new Boot Image but didn't use it yet.

Share this post


Link to post
Share on other sites

Hi,

The screenshot you posted above looks very much like a UEFI based computer trying to boot using the "old" .com file you specified in the option 67. Have you verified that the computers not are configured to used UEFI as Surface Pro 3?

/Jörgen

Share this post


Link to post
Share on other sites

Try this.

 

Create a new device collection, don't bother adding any members or rules just leave it empty.

 

Deploy the task sequence for your legacy machines that uses your normal PXE boot image to the new collection.

 

Now see if your PXE is working again.

Share this post


Link to post
Share on other sites

Hi,

The screenshot you posted above looks very much like a UEFI based computer trying to boot using the "old" .com file you specified in the option 67. Have you verified that the computers not are configured to used UEFI as Surface Pro 3?

/Jörgen

 

Yes, I am sure that UEFI is not enabled.

As I've said before it worked for a couple of months.

 

Only the MS Surface is is using UEFI and we are booting there with a USB stick.

Share this post


Link to post
Share on other sites

Try this.

 

Create a new device collection, don't bother adding any members or rules just leave it empty.

 

Deploy the task sequence for your legacy machines that uses your normal PXE boot image to the new collection.

 

Now see if your PXE is working again.

 

I will try this today.

Thanks for the tip.

Share this post


Link to post
Share on other sites

I have a small update for this issue...

 

As our problem is not yet solved, we know where to look now.

The DP, PXE settings and DHCP Options are all OK.

I have created a new DP with PXE and changed the DHCP options to point to this DP and placed the DP in the client VLAN rather than the server VLAN (which is behind a firewall).

Tested PXE -> All works fine

Then we moved the server to the server VLAN where our actual DP resides without changing any settings -> Same problem as before

So it's a network problem.

 

I don't know yet what exactly the problem is because our firewall doesn't block or drop anything to the MP and DP servers.

I created explicit rules allowing all access just for testing purposes and the log files are showing that all traffic is allowed.

 

So basically what happens during the PXE boot: wdsnbp.com file is downloaded succesfuly.

We also see this traffic in our log files. then pxeboot.com also succesfuly.

After this, we get the error.

The bcd cannot be downloaded but this we don't see in our firewall logs.

 

in Wireshark I can see that \boot\bcd cannot be found... whatever that means.

 

 

 

Anybody an idea?

post-31237-0-91888100-1444049241.png

Share this post


Link to post
Share on other sites

Hi...., any  updates?
I have a one-on-one problem ....

Reinstall DP did not help

 

 

Edited by uni

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×