SCCM of installation conditions:
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 the errors encountered
Error 1:
PXE-E51: No DHCP or proxyDHCP offers were received.
- DHCP server is not found, check your DHCP server configuration.
Error two:
Able to obtain an IP address, but the tips:
PXE-E55： ProxyDHCP service did not reply to request on port 4011
-DHCP in AD domain requires authorization server, if DHCP is configured first, then the field is added to DHCP failed authorization.
Authorization does not restart after -DHCP
-PXE server is not set to start deploying services.
Error three:
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 no startup item F12
- points a variety of situations:
1, DHCP and SCCM servers on different machines on the same subnet:
- On the DHCP scope options management, right, configuration options, adding 066,067
-066: computer fully qualified domain name the FQDN of the (own use ping -a ip, view the name of the band that is)
-067: SMSBoot \ x86wdsnbp.com, this path is C: \ RemoteInstall \ under.
2, the DHCP and SCCM server on the same machine:
- Remove the 066 and 067, 060 reserved
Error Four:
PXE boot, the client starts PE, the system center interface prepraing connecting network interface restart.
SMSTS.Log : winpe fails after configuring network settings PxeGetPxeData failed with 0x80070005
- first determine whether the network is working properly
- and then see where PE is not no network card driver, if you are brand machine, virtual machine, skip this step now, do not waste time on this.
- If the network properly, because the TS client attempts to initialize the Windows Firewall service, you need to start, stop, change permissions, and the new Windows (including PE) does not allow the firewall to stop operating privileges at startup, so the TS client request when Windows terminates the run.
-SCCM version and ADK problem, upgrade the latest version of SCCM, or change an earlier version of the ADK, Microsoft SCCM SCCM version of the manual has ADK and the corresponding table. The errors due to interference me for a long time, obviously downloaded SCCM1806, the actual installation is SCCM1606, but I did not notice such a low version. . .
Error 5:
UEFI PXE can not obtain an IP address.
60 open policy on the server DHCP, add optiondef 60 PXEClient STRING 0 PXEClient
The wdsmgfw.efi from C: \ Windows \ System32 \ RemInst \ boot \ x64 copied to the SCCM installation drive: \ RemoteInstall \ Boot \ x64
Then create a policy group, the method https://blog.51cto.com/yimiyinei/2061280