Shulou(Shulou.com)06/03 Report--

Conditions for installing SCCM:

Https://blog.51cto.com/bennychen/1885868

Https://blog.51cto.com/2984407/1868409

Https://blog.csdn.net/ansna_yxy/article/details/82872020

The following is a collection of all errors encountered

Error one:

PXE-E51: No DHCP or proxyDHCP offers were received.

-No DHCP server was found. Check your DHCP server configuration.

Error 2:

You can get the IP address, but prompt:

PXE-E55: ProxyDHCP service did not reply to request on port 4011

-the DHCP server needs to be authorized in the AD domain. If the DHCP is configured first, then adding DHCP to the domain will result in authorization failure.

-No restart after DHCP authorization

-the server started by PXE does not have deployment services set up.

Error 3:

The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved.

Message from Administrator: Configuration Manager lookingfor policy

But there is no F12 startup item

-under a variety of circumstances:

1. DHCP and SCCM servers are on different machines in the same network segment:

-on the DHCP management scope option, right-click, configure option, add 066067

-066: the computer fully qualified domain name FQDN (use ping-a's own ip to check the name with the domain)

-067:SMSBoot\ x86wdsnbp.com, this path is under C:\ RemoteInstall\.

2. DHCP and SCCM servers are on the same machine:

-remove 066 and 067 and keep 060

Error 4:

PXE starts, and after the client starts PE, it restarts in the prepraing connecting network interface of the system center interface.

SMSTS.Log: winpe fails after configuring network settings PxeGetPxeData failed with 0x80070005

-first determine if the network is working properly

-then check whether there is no network card driver in PE. If you are a brand machine or virtual machine, skip this step and don't waste your time here.

-if the network is normal, the reason is that TS client attempts to initialize the Windows firewall service and requires permissions to start, stop and modify, while the new Windows (including PE) does not allow permission to stop the firewall when it is started, so Windows is terminated when the TS client request is made.

-problems with SCCM version and ADK, upgrade the latest version of SCCM, or change to an earlier version of ADK. Microsoft SCCM manual has corresponding tables for ADK and SCCM versions. This error disturbed me for a long time. Obviously, I downloaded SCCM1806 and actually installed SCCM1606. However, I didn't notice that the version was so low.

Error five:

UEFI PXE could not get the IP address.

60 policy is enabled on DHCP server, add optiondef 60 PXEClient STRING 0 PXEClient

Copy wdsmgfw.efi from C:\ Windows\ System32\ RemInst\ boot\ x64 to the SCCM installation drive letter:\ RemoteInstall\ Boot\ x64

Then create a policy group with the method https://blog.51cto.com/yimiyinei/2061280

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.