IT Consultant Everyday Notes

Just some problems/solutions storage

Category Archives: PXE

SCCM: PXE boot fails with “Unsuccessful in getting MP key information. 80004005.”

I recently faced a weird issue with PXE boot.

Nice error in smspxe.log said:

RequestMPKeyInformation: Send() failed.

Unsuccessful in getting MP key information. 80004005.

etc..

image

Internet search suggested reinstallation of PXE DP (including killing WDS and fill clean of RemoteInstall). I tried that but without any success.

MP was in a good health, gladly replied to http tests, but I still tried to reinstall it. Obviously without any success…

Resolution: I tried to remember what I did recently, before I first noted PXE issue. MBAM 2.5 was installed!

So I removed MBAM and PXE immediately start to reply, successfully connect to MP etc…

Who knew!

Advertisements

SCCM:Speed Up boot image download in WinPE

Jorgen Nilsson made a whole research tweaking TFTP parameters for WDS; post is ccmexec.com/2016/09/tweaking-pxe-boot-times-in-configuration-manager-1606/

I used it to optimize a Lab on my laptop – I am using Hyper-V with SCCM infrastructure on Internal network.

The best option for my Hyper-V Based SCCM VM is

image

You can tweak registry settings manually or use a PowerShell script Jorgen kindly provided in his post.

If you goes too aggressive PXE can fail with 0xc0000001

For additional optimization I also use a command line

Powercfg.exe –s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

In my OSD Task Sequences for WinPE and after each reboot to be sure my VM uses High-Performance power plan.

At the end of TS I set it back to Balanced:

powercfg.exe –s 381b4222-f694-41f0-9685-ff5bb260df2e

SCCM: Reusing the same NIC for multiple PXE initiated deployments in System Center Configuration Manger OSD

Microsoft SCCM OSD support published a nice article about the subj: http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2015/08/27/re_2d00_use-the-same-nic-for-multiple-pxe-initiated-deployments.aspx

 

You basically need to add MAC address of a docking station or USB NIC you use for multiple machines to SCCM Discovery exclusion via editing SCCM registry as described:

This can be done by opening Regedit on the site server and navigating to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components \SMS_DISCOVERY_DATA_MANAGER

followed by editing the registry value of:

ExcludeMACAddress

This registry key value is a multi-string value that is the placeholder of the list of MAC addresses to be filtered. The registry key holds one MAC address per line in the following format:

50:1A:C5:FE:AA:8C

 

Note the known computers should be introduced with GUID instead of MAC after that. Please read details in the article.

SCCM 2012: Failed to get client identity (80004005)

Issue: OS Deployment failed:

-  PXE keeps rebooting after “preparing Network connection”. Errors: “reply has no message header marker”, “Failed to get client identity (80004005)”, “Failed to request for client”

image

– OSD Boot media cannot see TS

 

Resolution: Set correct time in BIOS!

I found the hint here. Thanks!

SCCM 2012: PXE boot fails with: PXE-53: No boot filename received

I recently work on a case when we need to configure PXE boot –enabled Distribution Point for SCCM 2012 clients. Server holding DP and clients are in different subnets, so the router should be configured with IP Helpers (aka DHCP relays) to forward BOOTP requests from bare-metal clients to the PXE DP.

Problem: We configured IP helper on the router, but  PXE clients got an error: PXE-E53: No boot filename received. Everything was working if we configured options 66 and 67 (PXE server IP and boot image name) on the Corp DHCP, but this way is not recommended by Microsoft.

Resolution: In addition to IP Helper we needed to configure bootp-gateway option on the router and set it with IP address of the router for desktop VLAN.