Can't PXE boot a client after upgrade to 1511 and ADK 10

[couillardk]

After upgrading to 1511 and ADK win10 and running the patch kb314370,

F12 a client and get "No boot file name available".

Cannot get F8 to open a cmd prompt for support logs either, yes it is enabled.

Both the new (x86 and x64 from ADK) boot images are distributed and have WinPE 10 drivers.

PXE is enable and advertised by the DT.

SMSPXE.log on the server is not even being populated.

Previous to this upgrade, we could PXE boot, now we can't.

 

Thank you for any help!

KACouillard

[couillardk]

I just found this in Monitoring Componet Status:

Critical SMS_MP_CONTROL_MANAGER

ERROR SMS_MP_CONTROL_MANAGER

MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error.

Possible cause: Management point encountered an error when connecting to SQL Server.

Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Server database.

Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory

Solution: Ensure SQL Server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate.

Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use.

Possible cause: The designated Web Site is disabled in IIS.

Solution: Verify that the designated Web Site is enabled, and functioning properly.

Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges.

Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy.

For more information, refer to Microsoft Knowledge Base article 838891.

And the site server Event Log:

Warning WAS

The description for Event ID 5009 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

SMS Management Point Pool
3824
fffffffe

And this in the Event Log:

Error DistributedCOM

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{4D581488-83B4-46AF-921C-275B583B691C}
and APPID
{AD65A69D-3831-40D7-9629-9B0B50A93843}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

[anyweb]

have you tried reinstalling the Management Point role ?

[couillardk]

I just fixed the MP issue (ERROR SMS_MP_CONTROL_MANAGER) by changing the Management Point Connection Account from use the computer account to domain service account.

 

Still unable to PXE boot.

 

On a client I am trying to PXE boot, F4 to get a command prompt. ipconfig /all results:

Host Name: (blank)

Primary Dns Suffix: (blank)

Node type: Hybrid

IP Routing Enabled: No

WINS Proxy Enabled: No

[couillardk]

• Steps I tried with No success:

  • 1. Disable PXE support on all (old and new) boot images

  • Disable PXE support on DP

• Remove WDS role

Reboot server

Enable PXE support on two new boot images (x64 and x86 winpe ADK Win10)

Enable PXE support on DP

Wait for WDS role to be installed

Redistribute two new boot images to DP

Verify RemoteInstall folder has been populated

F12 a client – no, same error PXE-E53 No boot file name available

[couillardk]

Do you think I should still try reinstalling the Management Point role?

[couillardk]

Also, sorry typo in my first post. I applied this patch to both boot images

https://support.microsoft.com/en-in/kb/3143760

[couillardk]

I removed, and reinstalled the MP. I also added DHCP scope options even though the client and server are on the same subnet.

 

The good news:

a. the MP is healthy online again

b. the smspxe.log is populating again

c. the client gets an IP and downloads the wdsnbp, then errors.

The bad news:

a. errors in the smspxe.log (see below)

b. the client error: The BCD from the PXE server does not contain a valid operating system. Ensure the server has boot images installed for this architecture.

File:\\Tmp x86x64(<numbers>).bcd

Error code: 0x0000098

Severity Type Site code Date / Time System Component Message ID Description

Information Milestone C10 6/22/2016 2:08:52 PM CSD10.CSD.LOCAL SMS_MP_CONTROL_MANAGER 4629 Component Status Summarizer detected that the availability of component "SMS_MP_CONTROL_MANAGER" on computer "CSD10.CSD.LOCAL" has changed to Online.

PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

94:57:A5:01:8C:40, B3B369FF-F4C2-11E4-A609-7070990000FF: Not serviced. SMSPXE 6/22/2016 2:08:30 PM 6936 (0x1B18)

Prioritizing local MP http://CSD10.csd.local. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

RequestMPKeyInformation: Send() failed. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

Failed to get information for MP: http://CSD10.csd.local. 80004005. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

reply has no message header marker SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

Prioritizing local MP http://CSD10.csd.local. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

RequestMPKeyInformation: Send() failed. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

Failed to get information for MP: http://CSD10.csd.local. 80004005. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

reply has no message header marker SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

Failed to send status message (80004005) SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

Failed to send the status message SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

94:57:A5:01:8C:40, B3B369FF-F4C2-11E4-A609-7070990000FF: Not serviced. SMSPXE 6/22/2016 2:08:34 PM 6936 (0x1B18)

[anyweb]

so are both architecture boot images distributed, and enabled for PXE and attached to the task sequence you are testing ?

[couillardk]

both x86 and x64 winpe boot images contain two net drivers (an Intel and a Realtek), distributed and enabled PXE. Only one is attached to the task sequence. In this case I have a win10 OS, so I attached the x64 boot image.