SCCM2012 PXE failing

[idavidson]

Hi All,

I have been reading through this forum quite a bit, including using the guides available to setup a couple of SCCM installs (firstly with 2007, and now with 2012).

 

My current issue is with getting PXE to work.

 

In my SMSPXE.log file when trying to PXE boot a machine, i get the following messages:

 

 

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

Set media certificate in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

Set authenticator in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

In SSL, but with no client cert SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634)

 

 

 

I've replaced the server name with FQDN, but you can see the errors I am having.

 

Some things I have tried are:

removing and re-adding the Distribution Point

changing the date on some of the certificates (to hopefully generate new ones).

removed and re-installed the WDS role.

rebooted.

restarted WDS service.

 

PXE booting has worked once for me, but when it did the task sequence i was trying to run (build and capture) failed, but before I had a chance to look into that, PXE stopped working.

 

I have tried this on a couple of different machines, and at the client end, I get the following message:

 

Status: 0xc000000f

Info: An error occured while attempting to read the boot configuration data.

 

I am at my wits end trying to get this to work, I have searched online, and the only solution it looks to be is to rebuld the server, which I really do not want to do. (if i do though, i will wait for SP1).

 

If I haven't provided enough info, please let me know, and I will be sure to post it.

 

Thanks in advance!

[willisj318]

How far does it actually get in the process? Does it boot and try to load the boot image then fail? Or does it not even get that far? Put the boot image on a memory stick and boot with it. I find this is a good way to get errors and troubleshoot pxe issues. Yes it bypasses PXE, but you can 1. see if it finds its advertisements and 2. you can pull the smsts.log file and look at that for clues.

[alewoodrum]

it happenned to me. it turned out to be that the boot files got lost from some reason from remote install. check this link:

 

http://msitpros.com/?p=55

 

basically all I had to do was to copy the files from RemoteInstallBoot into their respective folders at sccm folders. for x64 and x86.

[Rocket Man]

basically all I had to do was to copy the files from RemoteInstallBoot into their respective folders at sccm folders. for x64 and x86.

 

Bad idea copying.....if and when PXE is configured on DP, then it should automatically populate the SMSBoot x64 & x86 directories with files needed......If it is not then there may be a connectivty issue

 

You could remove the PXE role again......check WDS after 10-15 mins to see that it is an unconfigured state(yellow exclamation mark on server in the WDS console)....remove the WDS role from server manager.....reboot......delete the REMOTEInstall folder if it still exists (more than likely still does).....Manually add the WDS role from server manager but do not configure when finished......restart the server......then on DP re-enable the DP for PXE........then make sure and check that the Remote Install folder that it has populated with SMSBoot x86 and x64 directories.....

 

On the boot.wims specify to deploy from PXE server also...if you do not do this then the SMSBoot directories will not create!

[Peter33]

If you got trouble with PXE it's mostly because of BITS. To fix it, disable the PXE on your distribution point. Make sure that you remove the checkmarks of the 3 checkboxes before you uncheck the "enable PXE" box (there is a bug in SCCM 2012). When being asked if you want to remove WDS too, chose Yes.

After doing this open your server manager and remove the BITS feature. Then reboot the server (you don't need to remove WDS manually through the server manager).

When the server is up again enable BITS in the server manager. Open the SCCM console and anable PXE. Wait a minute and reboot the server again.

That should fix the problem.

[idavidson]

Excellent, Thanks for the replies guys. I will give this a go shortly and report back.

 

It has been doing my head in for quite some time.

 

Cheers,

Ian.

[heineborn]

Excellent, Thanks for the replies guys. I will give this a go shortly and report back.

 

It has been doing my head in for quite some time.

 

Cheers,

Ian.

 

Hey Ian,

 

I've run into a couple of similar issues. Posted the solutions on my site, check out these 2 posts;

 

Troubleshooting: http://heineborn.com/tech/sccm-2012-troubleshooting-pxe/

 

Other PXE issues: http://heineborn.com/tag/pxe/

[Djackson]

Hello

 

Has any had any issues with pxe when working with Datalux devices? Any help would be great

[alim_long]

Which type do you choose communication with client and server, http or https?

 

If you choose https, you need to request Client certification for distribution point.

 

http://technet.microsoft.com/en-us/library/gg682023.aspx