F12 network boot

[DBRSE]

I have been trying to get OSD to work on diffrent subnet.

Got it working on 1 laptop but having imported computer info into SCCM ready for more OSD get the following message on both new laptops.

 

Architecture: x64 WDSNBP

started using DHCP referral

Contacting server (myIP) (Gateway: 0.0.0.0)

no response from windows deployment services server

Launching pxeboot.com..

Press f12 for network service boot

 

I then press f12 and get the following:

 

connects to sccm and then goes into the Windows Boot Manager screen with the following error:

 

File: \Boot\BCD

Status 0x000000f

info: An Error occurred while attempting to read the boot configuration data

 

Any suggestions please??

[anyweb]

no response from windows deployment services server

 

have you configured Ip helpers for your switch/router that sits between your computer and the configuration manager server that is on the other lan ?

[DBRSE]

Thanks for the swift reply. Yes the network guys have. Its worked on one laptop that I connected yesterday.

[boyjaew2]

Geez, man!

 

I don't get it. Nobody has been on the SCCM server for two weeks. I know this because I'm the only admin. But here it is ONCE AGAIN pxe boot FAIL. It was working absolutely flawlessly for weeks and now ...nothing. This is a bit from my last attempt.

 

From smspxe.log

 

 

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

Begin validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

Completed validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4)

Set media certificate in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set media certificate in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18)

Set media certificate in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18)

Set authenticator in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4)

PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CNotifyTimer::Init SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500)

 

 

 

What the hell does this say? I get the same message as above.

 

Please help me out. I've already checked the everything is deployed to the DP. The only thing that has changed since I first discovered PXE broken (again) is that I deleted the adverts for the task sequence that pushes the image and re-deployed it. It says 0% compliant. I don't think this is a problem because pxe wasn't working before this, but just thought I'd throw it out there. What does that 0% compliant even mean?

[Rocket Man]

Can I ask why you import data into SCCM for these laptops??

If they are new then they are already unknown to SCCM......just deploy the TS to the unknown computer collection and f12 boot the laptops.....(once the DP is configured for unknown Computer Support of course)

 

I have seen this error

File: \Boot\BCD

Status 0x000000f

info: An Error occurred while attempting to read the boot configuration data

before with my old WDS and most of the time the fix was to re-seat the RAM modules in the system...

[boyjaew2]

I think in the beginning I was having some issues with PXE and not enabling support for unknown computers was part of what I did to fix. I would certainly enable it if it will work. I don't enjoy importing them all one by one or with a file, but it is what fixed it in the beginning. So, it just kind of got left that way.

 

When you say re-seat RAM in the system are you talking about the client I'm trying to image or the SCCM server? Sccm is running in a VM. So, I can't really re-seat that. I'll try both of the above suggestions and see how it goes.

 

Thanks for the suggestions!

[boyjaew2]

So, check this out.

 

After I:

 

- disabled PXE and Multicast on the DP

- Stopped WDS

- Rebooted the SCCM server

- Enabled PXE (before I did this the WDS was not showing up - I was in a state of WTF)

- Eventually after I enabled PXE again WDS started

- I updated the boot images to the DP

 

PXE is now working properly again. In the smspxe.log it looks to my untrained eyes as if it had to re-find all the boot images. I can post the log if anyone wants to see.

.

Anyway, I was receiving the exact same error message as the OP and this is what fixed it for me.

 

The thing that is so frustrating, like I said, is that NOTHING had been changed since the last time I imaged a batch of PCs. At least I didn't change it and I am the only one with access to this server. So, I'm stumped and await the next time it bugs out for no apparent reason.

 

RocketMan, thanks for the advice. I had been avoiding unknown pc support for some reason. Thanks for reminding me. I'm going to enable it, seems like it would save me some time.....if it doesn't break something.

 

 

Thanks again! I hope this helps somebody. This forum is pretty much the only place on the net that I have ever found pertinent information and I hope I can contribute if even in a very small way. If this site wasn't here I don't know where I could look.

[Rocket Man]

Unknown computer support is a major component of SCCM....without it you would have to fully configure all Out of the box PCs..join to domain etc.... get the client installed before you can do anything with them with regards to SCCM(bar importing system info of course...which can be time consuming).....with unknown computer support all you have to do is physically connect the new PCs tp the LAN and F12 them for PXE boot...simple as that......if you boot a known PC it will not take a PXE advertisement...this is the total security of Unknown Computers..

 

EDIT: it will always be the client you try and re-seat the RAM in....do not know why this is the case but it has worked for me before on lots of occassions!!

[boyjaew2]

Thanks, man

 

Yeah, that all makes perfect sense. I have enabled this since and it HAS made things much easier (obviously). Thanks again for the feedback on both counts.

[bdazle]

Just a word of advice, if you have enabled unknown computer support, make sure you enable pxe flags, last thing you want is an end user pressing f12 and blowing away their device without a backup