<

Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x

How the Windows Deployment Service not starting was solved

Published on
18,279 Points
12,279 Views
Last Modified:
The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box.

This is what Event viewer showed after trying to start the WDS service:

 An error occurred while trying to start the Windows Deployment Services server.
 
 Error Information: 0xC1030104  
After this failure, the PXE Service point was removed then the WDS server role was also removed. The PXE point was then added again and the WDS server role was also again added. The service was then restarted but failed with the same error. Based on the information in the following link to tech net, the problem was solved.
http://technet.microsoft.com/en-us/library/cc726654%28WS.10%29.aspx
These are the step by step directions that were used to solve the issue.

SCCM
1)   Remove the PXE Service Point
      I removed the server but this may not be applicable if the SCCM server also serves as the PSP
2)   On the PXE server (if it exists) remove the WDS role
3)   Reboot
4)   Add the WDS role but do not set it up, just add it
     a.  If it fails to start (Error: The description for Event ID 258 from source WDSIMGSRV cannot be
          found.)  Use the article I attached.
     b.  Step 4 in the article.  Run wdsutil /uninitialize-server will run but it will error out, keep going
          on with the next command.  It is erroring out because we do not configure WDS, SCCM does.
     c.  Once you’ve finished the wdsutil /initialize-server verify that the service has started.  It did for
           me so hopefully that’s all you need to do.
5)   Add the PXE Service Point role again within SCCM
6)   Wait about 10 minutes for SCCM to update to show that you have a new distribution point for
       your boot images
7)   In your boot images, re-add the distribution point and make sure it updates.

After these steps were completed, the WDS service started and imaging through SCCM could resume in this enterprise. I hope this helps others fix this problem as I have seen users in many tech forums with the same error code when trying to use PXE and WDS.
0
Comment
Author:efosnaught
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
 

Administrative Comment

by:Eric AKA Netminder
efosnaught,

Congratulations! Your article has been published.

ericpete
Page Editor
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Join & Write a Comment

In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month