Fix SCCM PXE Related WDS Service is not getting started on Server? I wanted to try OSD (Windows 10/Windows 11 deployment) with SCCM /ConfigMgr.
SCCM vNext TP3 Primary server is installed on Windows Server 2012 R2 and enabled PXE role, part of the SCCM DP site system role.
Once the PXE role is enabled, SCCM will automatically take care of the prerequisite of the PXE (Preboot Execution Environment) role called Windows Deployment Service (WDS).
Windows Deployment Services is a server technology from Microsoft for the network-based installation of Windows operating systems. WDS role has been installed on Windows 2012 R2. However, the WDS service was not getting started.
Fix SCCM PXE Related WDS Service is not getting started
There is no log file called PXESETUP.log in SCCM 2012 and SCCM vNext version as PXE point is part of the DP role. DistMgr.log will give you the details about PXE and WDS installation on the site server.
If you are enabling PXE on a remote site system server, then you can refer to smsdpprov.log.
Troubleshooting Fix SCCM PXE Related WDS Service is not getting started
PXE role was installed successfully, but the WDS service was not getting started. I checked the event logs, and the following are some errors related to WDS services…
An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shut down.
Error Information: 0x906 An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x906
Tips – Fix SCCM PXE Related WDS Service is not getting started
I removed /uninstalled WDS from the server manager, removed the RemoteInstall folder, and installed it again. I even tried running the following command
wdsutil /initialize-server /reminst:C:\RemoteInstall with no luck.
WDSUTIL command didn’t work, pointing towards domain controller connectivity.
However, the SET l command provides the correct domain server name and logon server name 🙁
C:\Windows\system32>wdsutil /initialize-server /reminst:C:\RemoteInstall
Windows Deployment Services Management Utility [Version 6.3.9600.16384]
© 2013 Microsoft Corporation. All rights reserved.
An error occurred while trying to execute the command.
Error Code: 0x54B
Error Description: The specified domain either does not exist or could not be contacted.
The issue was related to domain control network connectivity. I’ve deleted the Virtual Switch, which I created in the Hyper-V console, and recreated the Virtual switch with an internal option.
Removed the PXE and WDS, restarted the server, and enabled the PXE point again. This time it started working.
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.