OSD Task Sequence Failed with Error 0x80072EE7 | SCCM | ConfigMgr

During SCCM Operating System Deployment (OSD), you may encounter the error 0x80072EE7 when the machine reboots into full OS mode. This error indicates that the client cannot resolve the SCCM server name or address, often due to missing or incorrect network drivers. In this guide, we’ll walk through the root cause analysis using smsts.log, explain why the Ethernet adapter fails to initialize, and provide step‑by‑step remediation strategies to ensure a successful deployment.

Issue

In Configuration Manager (SCCM), Windows 10 and Windows 11 Operating System Deployment may fail with error code 0x80072EE7 after the machine reboots into full OS mode. The issue is captured in the smsts.log file, where the following errors are recorded.

unknown host (gethostbyname failed)

Sending with winhttp failed; 0x80072ee7

failed to send the request

Failed to send status message (80072ee7)

Note: This article focuses on the error 0x80072ee7 when it occurs in full OS mode. If you get the same error code during the Windows PE phase, then the issue may be related to DHCP, DNS, or drivers in the Windows PE boot image.

Cause:

The error code 0x80072EE7 translates to “The server name or address could not be resolved.” In SCCM/ConfigMgr, this error often occurs due to incorrect TCP/IPv4 settings and typically points to a network driver issue during the Task Sequence. When the machine reboots into full OS mode, it cannot communicate with the SCCM server, causing the OSD to fail with error 0x80072EE7.

Log analysis confirms that the Windows PE phase completed successfully, but the failure occurred after the system transitioned into Windows full OS mode, where the network adapter was unable to initialize properly.

Further analysis of the smsts.log file shows that the Ethernet adapter was not detected during the Task Sequence. Instead, only the wireless adapter was identified, but no IP address was assigned to the Wi‑Fi adapter. As a result, the machine failed to establish network connectivity, preventing communication with the SCCM/ConfigMgr server and causing the OSD to fail with error 0x80072EE7.

The Task Sequence failed because the Ethernet adapter was not detected, leaving the client unable to communicate with the SCCM/ConfigMgr Management Point. Without a valid network connection, the Operating System Deployment (OSD) process could not continue, resulting in error 0x80072EE7.

Solution:

Since the Ethernet adapter was not detected, the issue is most likely related to network drivers. To fix error 0x80072EE7 during SCCM OSD on Windows 10 or Windows 11 machines, follow these steps:

Confirm that the Apply Drivers / Apply Driver Package step was executed during Task Sequence execution.

Check network connectivity

Verify that there was no network outage at the time of deployment.

If the OSD succeeds on a retry, the failure may have been caused by a temporary network interruption.

Validate network drivers

Add the latest drivers for the specific hardware model in ConfigMgr.

Include an Apply Drivers or Apply Driver Package step in the Task Sequence.

Re‑validate product name

• Even if drivers are already added, confirm the product name matches the hardware. Hardware models may have different product names due to specification changes.

Use the following PowerShell command to get the product name:

Get-WmiObject -Class win32_computersystemproduct Example output:CodeIdentifyingNumber : PFXXXXXX Name : 20XXXXXX Vendor : LENOVO Version : ThinkPad X390 Caption : Computer System Product

Check Task Sequence execution

Review the smsts.log or Task Sequence status messages in Configuration Manager.

Related Posts:

• SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
• PXE-E99: Unexpected network error – SCCM OSD
• Location of smsts.log file during SCCM OSD
• ConfigMgr OSD – PXE Troubleshooting
• OSD Task Sequence Failed with Error 0x80072EE7