I ran into an issue where I was unable to start the WDS service on a newly installed SCCM 2012 SP1 server running on Windows Server 2012. The following errors were experienced in the application log on the SCCM 2012 distribution point server.
Log Name: Application
Source: WDSServer
Date: 25/10/2013 12:30:44 PM
Event ID: 257
Task Category: WDSServer
Level: Error
Keywords: Classic
User: N/A
Computer: sccm2012.domain.internal
Description:
An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x906
Log Name: Application
Source: WDSServer
Date: 25/10/2013 12:30:44 PM
Event ID: 257
Task Category: WDSServer
Level: Error
Keywords: Classic
User: N/A
Computer: sccm2012.domain.internal
Description:
An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x906
Source: WDSMC
Date: 25/10/2013 12:30:45 PM
Event ID: 594
Task Category: WDS Multicast Server
Level: Error
Keywords: Classic
User: N/A
Computer: sccm2012.domain.internal
Description:
The Content Provider WDSBOOT loaded from C:\Windows\system32\wdsbcp.dll failed to initialize.
Source: WDSMC
Date: 25/10/2013 12:30:45 PM
Event ID: 603
Task Category: WDS Multicast Server
Level: Error
Keywords: Classic
User: N/A
Computer: sccm2012.domain.internal
Description:
The Content Provider WDSBOOT failed to initialize. The provider is marked as critical. WDS Multicast server will fail to start.
Error Information: 0x906
Log Name: Application
Source: WDSServer
Date: 25/10/2013 12:30:45 PM
Event ID: 513
Task Category: WDSServer
Level: Error
Keywords: Classic
User: N/A
Computer: sccm2012.domain.internal
Description:
An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shutdown.
Error Information: 0x906
This was resolved by initialising the WDS server using the following command. Generally WDS automatically initialises itself however for an unknown reason on this SCCM server it did not initialise as expected.
