WDS is broken
WDS stopped working over the weekend for no apparent reason. Came in Monday to find that we can't PXE boot to image our machines from SCCM2007. All machines we attempt to image simply report "no boot image available". I've seen this enough that I thought I knew what to do. I removed the PXE distribution points from SCCM, removed the PXE service point, un-installed WDS, renamed the RemoteInstall folder, rebooted a couple times, re-installed WDS, re-installed the PXE service point, re-created the PXE distribution points... And it's still broken. WDS starts up OK... I'm not getting the usual 1067 error. Instead, WDS starts up and I get one error (ID 258) and one warning (ID 512) logged. I've un-installed and re-installed WDS (as well as the PXE service point) at least a dozen times now. I've re-created boot images, task sequences, and everything. I've tweaked the registry to disable multi-threading, I've double-checked with our network guys to make sure they didn't change anything interesting. Frankly, at this point, I'm stumped. The error text from the WDSIMGSRV/258 error makes me think that some component isn't installing correctly... But I'm not entirely sure what to do about that. Maybe REGSRVR some DLL? Absolutely any assistance in resolving this issue would be greatly appreciated. Log Name: Application Source: WDSServer Date: 5/14/2012 3:58:43 PM Event ID: 512 Task Category: WDSServer Level: Warning Keywords: Classic User: N/A Computer: REDACTED Description: An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue. Error Information: 0xC1030104 Log Name: Application Source: WDSIMGSRV Date: 5/14/2012 3:58:43 PM Event ID: 258 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: REDACTED Description: The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 0xC1030104
May 15th, 2012 10:32am

have you reviewed this yet ? Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007 - The Out Of Band Management Support Team blog - Site Home - TechNet Blogs Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 12:54pm

Yes Niall, I have reviewed that document. We used that guide to get PXE up and running during the initial deployment, and that's my go-to guide for re-installing WDS when it fails. I've been through those troubleshooting steps more than once. I re-installed WDS, following those directions, at least a dozen times yesterday. I also forwarded that information along to my network guys and they assure me that nothing has changed with any of those settings.
May 15th, 2012 1:00pm

There are multiple PSP hotfixes for ConfigMgr 2007 Post SP2: http://social.technet.microsoft.com/wiki/contents/articles/4505.list-of-public-kb-articles-and-hotfixes-for-configuration-manager-2007-sp2-en-us.aspx (search for PXE).Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 2:21pm

Jason - We're running SCCM 2007 R3. I'd assume most of those have been included in R3 already? Or is that not true?
May 15th, 2012 2:46pm

Not true. R3 only adds some extra features and no hotfixes.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 3:36pm

As Peter said, that is incorrect. Unfortunately R3 is not a true version of ConfigMgr at all, it is simply an add-on pack that contains no hotfixes or updates. Unless you've installed them separately, then the hotfixes are applicable.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 15th, 2012 3:55pm

Huh. Well, that's what I get for assuming. Looks like I'll be installing hotfixes today... Hopefully one of them resolves my issues. Thanks!
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2012 7:32am

Ran through the document that Jason linked to... Found 5 items that referenced PXE. 3 of them were KB articles that I'd already found while troubleshooting this issue on Monday. 2 of them were hotfixes, but only one of those actually applied to the version of SCCM I've got installed. And it didn't help. I'm still seeing the same problem. The text of the 258 error I'm getting makes me think the issue is less with SCCM than with WDS. Usually that "The description cannot be found" message means something isn't installed or registered properly. Unfortunately, the only suggestion I can find for troubleshooting/fixing WDS is to simply un-install and re-install... Which I've already done repeatedly. Log Name: Application Source: WDSIMGSRV Date: 5/16/2012 8:40:52 AM Event ID: 258 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: REDACTED Description: The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 0xC1030104
May 18th, 2012 8:50am

OK, let's take a step back then. Have you reviewed smspxe.log?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 9:56am

I think reviewed is probably too strong a word. I have looked at the smspxe.log, but I don't know what I'm looking at. There isn't anything that strikes me as obviously wrong in there... But I don't know what it should look like, either.
May 18th, 2012 10:48am

I would create a boot cd with your boot image and check that that even works for your task sequence... just to eliminate any issues there.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 11:03am

I created a stack of bootdiscs on Tuesday morning, when it was apparent that I wouldn't have PXE working again any time soon and we needed to get some new machines imaged. The bootdiscs have been working fine. Machines boot with no issues, contact the SCCM server just fine, download all the appropriate packages, and run the task sequence just fine. ...and, frankly, the more time I put in to fixing PXE the less relevant it seems to be. We've been up and running and imaging machines for a couple days now, and none of the helpdesk techs are complaining about having to use bootdiscs. There's a certain cleanliness and elegance to booting directly off of the network... But I'm starting to wonder if I'm the only one who actually cares about that.
May 18th, 2012 11:08am

When uninstalling WDS, are you also removing the PSP, rebooting, and deleting the WDS registry keys? Are you manaully configuring WDS in any way?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 12:08pm

I'm following the guide that Niall linked earlier. Generally it looks something like this... Remove PXE distribution points for boot images... Wait 'til they're really removed.Remove the PXE Service Point... Wait 'til it's really removed.Un-install WDS through the Roles GUI.Reboot.Re-name the RemoteInstall directory. Check the registry. Check file shares. Make sure everything is gone.Reboot.Re-install WDS. Don't configure anything.Reboot.Re-install PXE Service Point.Re-create PXE distribution points for boot images.Reboot.Curse because WDS is still broken.
May 18th, 2012 12:54pm

Make sure you added a boot image to both x86 and x64 and that you added your boot images to the pxe distribution point ex. \\SCCMServer\\SMSPXEIMAGES$
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 1:33pm

Yes, I'm adding both 32-bit and 64-bit boot images. And I've double-checked to make sure they've been added to the PXE distribution point. No dice.
May 18th, 2012 1:48pm

I would def say it is worth using the PXE boot as you will need to create new boot disks anytime a new NIC or Storage driver is added but great backup plan for now.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 2:31pm

Chris, I ran into exact Same issue once and I ran this command wdsutil /initialize-server /REMINST:"D:\remoteinstall" More info is available in this link http://blogs.technet.com/b/stufox/archive/2008/07/31/configuration-manager-pxe-service-point-errors.aspx May not take a long time to try this.Thanks, Vamsi
May 18th, 2012 4:43pm

Hi Chris, I think add boot images to pxe DP have nothing to do with WDS status failed to start issue. Is your PXE service point enabled on a server that also hosts DHCP? Once I have met this problem with WDS failed to start and finally found DHCP using the port WDS tried to use, this caused WDS failed to start with WDS on the DHCP host. Hope this will help. Thanks
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2012 4:39am

No, my PXE/WDS/SCCM server does not host DHCP. However, no changes have been made to DHCP in the last couple of months, and PXE has been working fine until Monday. Additionally - WDS is starting. The service is running. It just isn't working.
May 19th, 2012 7:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics