I am setting up a Distribution Role only Site System. Installation works fine, PXE also comes online as well. All components are ready and in the green.

Problem is once I activate the MultiCast function, WDS entirely dives and will not come back online.

I've removed everything four times and restarted between each step. I have also tried doing the wdsutil /uninitialize-server and then wdsutil /initialize-server /reminst:"C:\RemoteInstall" but then I get a 0x41D error code.

This server was previously running SCCM07 without any problems and is also a DHCP Server. The UseDHCPPorts registry entry has been set to 0 (I'm surprised this still needs to be done manually. I would think with all the hype SCCM2012 got, at least this one little trap would have been taken care of)

I get the following errors in WDS:

Log Name:      Application
Source:        WDSMC
Date:          15/06/2012 12:09:07 PM
Event ID:      594
Task Category: WDS Multicast Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KELOWNA.is.cu
Description:
The Content Provider SMSProvider loaded from C:\SMS_CCM\smswdstp.dll failed to initialize.
 
 Error Information: 0x2

Log Name:      Application
Source:        WDSMC
Date:          15/06/2012 12:09:07 PM
Event ID:      603
Task Category: WDS Multicast Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KELOWNA.is.cu
Description:
The Content Provider SMSProvider failed to initialize. The provider is marked as critical. WDS Multicast server will fail to start.
 
 Error Information: 0x2

Log Name:      Application
Source:        WDSServer
Date:          15/06/2012 12:09:07 PM
Event ID:      513
Task Category: WDSServer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KELOWNA.is.cu
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: 0x2

• Edited by Vorsprung Friday, June 15, 2012 7:43 PM

On what OS does your wds runs on?

Have you moved it to another OU since you have been used it with sccm2012? 

Windows 2008R2 x64 SP1, I haven't moved the server at all, same OU as before.

I ended up getting it going, but only because I added a proxy Management Point role. I still need to know why this didn't work because I was under the impression with CM12 that I could install a site system and only have a distribution point (with PXE, MultiCast) role installed provided it was Windows Server.

• Edited by Vorsprung Tuesday, June 19, 2012 9:07 PM

Does this help? http://social.technet.microsoft.com/forums/en-US/winserversetup/thread/49127bde-3b0f-4f41-a265-5786d06be9a8/

Sounds like a WDS/DHCP issue, did you let SCCM install and configure WDS? Might need to check the DHCP ports setting again.

I did see a similar post and did specify the DC/GC server in WDS, had no effect.

I did pre-install all of the necessary roles according to the http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReq

I did not do anything with WDS after I installed the WDS role, already remembering that with SCCM 2007 it would go funny if you touched WDS in any way. I did however do the registry entry in WDS to not use DHCP ports before installing PXE and checked afterwards as well. After installing PXE, I rebooted several times and all services came up just fine.

Then I turned on MultiCast in the Distribution Point role, and it went downhill from there. :(

Actually i will recommend you to configure wds before adding it as a distributionpoint/pxe. Also in sccm2007 you have most success if you configured wds before adding it as a pxe-point.

I will try that but I'm not sure how that would be relevant to the MultiCast service not starting when WDS/PXE started up just fine to before turning on MultiCast option.

Actually i will recommend you to configure wds before adding it as a distributionpoint/pxe. Also in sccm2007 you have most success if you configured wds before adding it as a pxe-point.

That's not needed at all. distmgr will install and configure WDS automatically.

I'm having the exact same issue.

Remote distribution point is server 2012. SCCM is 2012. SCCM primary site server is 2008 r2.

The only issue is when i enable multicast smswdstp.dll will not initialize.

I'm running out of ideas and will wipe it and rebuild to 2008 next if i have to.

shikikami24 - did you get a solution to this? We are having the same issue too. Setting up PXE is fine, but after enabling Multicast WDS will not start. I believe the error is the same. There are a few logged but the first is event 594 (WDS Multicast Server) "The content provider SMSProvider loaded from D:\SMS_CCM\smswdstp.dll failed to initialize". When trying to the start the service the message ends "refer to service-specific error code 2".

In fact, it was only one of two build servers we have that had the issue. Then I accidently un-checked Multicast on the working server, which of course removed Multicast. When I re-checked Multicast on that server and waited for the config to re-apply, the WDS service failed to start - same as the first server (which I've no idea how it got to that state in the first place.

Any help apprecitated.

By the way - if you remove "Multicast" of that DP and allow for the removal config, you can then start the WDS service fine.

• Edited by PHmusicman Monday, January 07, 2013 6:49 PM

Hi shikikami24

I have the exact same error as you. Evereything was fine and running along nicely, then after a reboot I now get this exact same error. Did you ever fix yours?

Thanks... Jim

Which version of ConfigMgr? Which OS is the DP running on? What errors are listed in the logs/eventlog?

Torsten,

Thanks for the reply. Sorry for not thinking about putting all that info up front.

ConfigMgr 2012 R2 with CU2 (5.00.7958.1303 if that helps define it?)

Primary server runs on Server 2008 R2 Enterprise with SP1

The DP is running on a Server 2012 R2 Standard

The Multicast Service fails to start with a WDSMC 594 error, then a 603. WDSServer then gets a 513 error.

594 Error: The Content Provider SMSProvider loaded from C:\Windows\CCM\smswdstp.dll failed to initialize. Error Information: 0x2

603 Error: The Content Provider SMSProvider failed to initialize. The provider is marked as critical. WDS Multicast server will fail to start. Error Information: 0x2

513 Error: An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shutdown. Error Information: 0x2

I have turned off Multicast for the DP and the WDS Server service starts okay now.

• Edited by englishj Thursday, August 07, 2014 2:44 PM

I don't know if this has any bearing on this issue or not, but...

With Multicast removed/turned off I noticed that there was a Windows Server 2012 R2 Cummulative Update of like 900MB or something sitting out there, so I loaded it and rebooted. Multicast was then enabled/turned on/installed from the DP properties and it installed and was running fine. I rebooted the DP and it all came up okay... I don't want to Jinx it by typing that WDS is still running, but it is... I am even able to stop and start the WDS service and it responds properly....

In case this helps anyone...

Resolved for me:
I was seeing this in the Application Log on the server:

-

System

- Provider [ Name] WDSMC

- EventID 603 [ Qualifiers] 49441

Level 2

Task 1

Keywords 0x80000000000000

- TimeCreated [ SystemTime] 2015-08-19T15:54:38.000000000Z

EventRecordID 13533

Channel Application

Computer blah.blah.blah

Security

-

EventData

SMSProvider

0x7E

The Content Provider SMSProvider failed to initialize. The provider is marked as critical. WDS Multicast server will fail to start.

 Error Information: 0x7E


I didn't have multicast enabled on the Distribution point properties and figured I'd find out what happened if I tried to enable it since it was looking to initialize the provider.  It freaked out and performed a client repair on the server.  All is well and WDS is now running.  Worked for me, probably won't for you.  I disabled the multicast at this point since I didn't want to use it.