When staging a client using SCCM OS deployment, there may be different issues preventing the deployment to complete successfully. The list below shows the solutions for some of the frequently occurring issues:
Error Message: No error message, Windows PE is just rebooting automatically.
Error occurrence: Stop directly after PE-load, before password authentication.
Possible Cause: The NIC driver of the respective hardware may be missing in the boot image.
Solution: Add the respective NIC driver to the boot image.
Error Message: Failed To Download Policy (Code 0x80004005)
Error occurrence: Stop in Windows PE, after password authentication but before the task sequence selection.
Possible Cause: The PXE certificate stored in the SCCM site database may have been expired or may be missing at all. Time settings of the computer (BIOS) may be incorrect.
Solution: Add a new or renew the existing PXE certificate assigned to the respective distribution point in the SCCM site settings. Verify that the BIOS time matches the current time.
Error Message: Failed with the error code 0x80070002
Error occurrence: 1. Stop at “Auto Apply Drivers”, network connection is lost (ipconfig in F8-console of PE shows no IP address)
or 2. Stop at “Apply Operating System Image”.
Possible Cause: 1. A non PE compatible NIC driver has been applied by the “Auto Apply Drivers” action, which causes a network disconnection or 2. Package sources cannot be downloaded from a distribution point, e.g. due to authentication issues.
Solution: 1. As a workaround, the “Auto Apply Drivers” section in the task sequence can be disabled for the affected HW model, e.g. by using a condition. Please refer to this blog post for more details about this issue and proposals for a solution or 2. Verify the credentials of the network access account. In case of SCCM 2012, check the virtual IIS directory “SMS_DP_SMSPKG$”, if it is enabled for Windows Authentication.
Error Message: Failed with the error code 0x80004005. Windows setup failed code 31
Error occurrence: Stop during “Setup ConfigMgr Client” action, after the “Auto Apply Drivers” action.
Possible Cause: This issue may occur after adding new drivers to SCCM, while one of the drivers may cause issues with Windows setup after being auto applied.
Solution: Identify the incompatible driver in the SCCM driver store and disable it. In the most cases such a driver can only be installed via a separate package instead of using “Auto Apply Drivers”.
Error Message: Failed with the error code 0x00000001
Error occurrence: Stop after unattended setup part of Windows (Windows base OS installation has already been completed), directly after the reboot when the “Setup ConfigMgr Client” action has re-run. Network connection is lost (ipconfig in F8-console of PE shows no IP address).
Possible Cause: NIC driver of the respective hardware may not be available for the installation in Windows, or the “Auto Apply drivers” action has not run at all in the task sequence.
Solution: Add the respective NIC driver to the SCCM driver store and include it in a package. Make sure that “Auto Apply Drivers” in the task sequence will run for the respective hardware.
Error Message: 1. There are no task sequences available for this computer
or 2. No error message, but the Computer gets a name conflicting with another SCCM record.
Error occurence: 1. Stop directly after the PXE password dialogue or 2. OS deployment completes successfully, but the computer has a wrong computer name which conflicts with the name of another SCCM record.
Possible Cause: There may be duplicate SMBIOS GUIDs (System UUIDs) for a record in the SCCM database, which conflicts with the SMBIOS GUID of the system being currently set up. Although this GUID should always be unique, there are obviously possible cases where it isn’t maintained correctly.
Solution: As a workaround, you can create a registry value named “BannedGuids” on the PXE service point, containing a list of known duplicate GUIDs. This instructs the PXE service to skip the SMBIOS GUID lookup during the PXE boot and to fall back to MAC only lookup, when a known duplicate GUID is presented to the PXE service:
To identify the SMBIOS GUID locally on a running system, the following command can be used:
wmic csproduct get uuid
When the registry value is set, the smspxe.log reports the following (note that “GUID=” has no value and “GuidCount=” has a vlaue of “0”)
MAC=<MACADDRESS> SMBIOS GUID= > Device found in the database.
See also this Microsoft KB for more detailed information about this issue.
Please note, that this solution does indeed work to ignore the SMBIOS GUID during PXE boot via WDS, but later when SCCM runs a second lookup to determine all available task sequences for the affected computer, the SMBIOS GUID is used again, uncared of the “BannedGuids” registry value. In this case, the smsts.log file reports the following:
Setting wizard error: There are no task sequences available for
As a conclusion, from my point of view there is no alternative solution available as solving the problem on the hardware itself.
Error Message: No error message, PXE boot loops when downloading the boot loader or PXE boot is not starting at all.
Error occurence: PXE is trying to TFTP download “pxeboot.com” in a loop:
The log file “smspxe.log” logs “Device has been accepted” several times without any further progress or error message (PXE loop) or it stops after logging “Device found in the database” (PXE not starting). The folder “D:\RemoteInstall\SMSBoot” is missing or the x64 resp. x86 sub folders are empty or incomplete with missing files. As a result, “C:\Windows\Temp\PXEBootFiles” is also missing or contains no (PXE loop) boot loader files.
Possible Cause: The standard x86 and x64 boot images may not have been replicated to the PXE point.
Solution: Replicate the standard boot images, restart the WDS service on the affected PXE server and check if the files in the mentioned folders do appear.