Skip to main content

Failed to Start Windows Deployment Services Server.

Symptoms of the Issue :

Getting the below errors after clicking on WDS server.
ERROR 1: Failed to Start Windows Deployment Services Error, the service changed to an unexpexted state.
ERROR 2: The service did not respond to the start or control in a timely fashion.

Reason for Issue:
This issue will occur if we configure WDS and DHCP on the same server, in this situation WDS service tries to use the port 67. However, the DHCP server already uses this Port.
Solution :
Try below steps to check the issue
Method 1
At the command prompt, type the following command, and then press ENTER:
wdsutil /set-Server /UseDhcpPorts:No
Method 2
1.Click Start, click Run, type wdsmgmt.msc, and then press OK.
2.In the Windows Deployment Services window, expand Servers, right-click the WDS server name, and then click Properties.
3.In the Server Properties dialog box, click the DHCP tab.
4.Click to select the Do not listen on port 67 check box, and then click Apply.
Once done check the issue.
Please comment if this post helpful.
Labels:

Comments

  1. UnknownJune 12, 2015 at 12:44 PM

    Hello Mahadev this kind of issues very useful us because whenever issues will come that time help to us ..thanks for your valuable time ..

    ReplyDelete
  2. MahadevNittureJune 12, 2015 at 1:22 PM

    You are welcome Siddu :)
    Thank you for the kind comment on my post :)

    ReplyDelete

Post a Comment

Popular posts from this blog

WMI Error - Windows Management files may be moved or missing.

WMI ERRORs: Symptoms: >>Unable to open System Information. >>WMI Error - Windows Management files may be moved or missing. Resolution : Navigate to Start >> All programs >> accessories >> right click on CMD >> run as administrator, and run the below commands one by one. 1)     sc config winmgmt start= disabled 2)     net stop winmgmt /y 3)     %systemdrive% 4)     cd %windir%\system32\wbem 5)     for /f %s in ('dir /b *.dll') do regsvr32 /s %s     6)     regsvr32 %windir%\system32\tscfgwmi.dll           7)     wmiprvse /regserver                                 ...
10 comments
Read more

Unable to transfer Schema master role from Primary Domain Controller to Additional domain controller (backup server) In Windows Server

Issue: Unable to transfer Schema master role from PDC to ADC. Symptoms: You will get below error while transferring Schema master using NTDSUTIL fsmo maintenance: seize schema master Attempting safe transfer of schema FSMO before seizure. ldap_modify_sW error 0x32(50 (Insufficient Rights). Ldap extended error message is 00002098: SecErr: DSID-0315137D, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 Resolution: Add your user to Enterprise admin  group in Active directory to resolve this issue.
Post a Comment
Read more

Installing Reporting Services Point role in SCCM Current Branch 1702

In Today’s tutorial, we will learn about the Configuration of Reporting Services Point role in SCCM CB 1702. Before moving ahead, we will throw some lights on to understand the Reporting Services Point Role in SCCM. What is Reporting Services Point Role? A reporting services point integrates with SQL Server Reporting Services to create and manage reports for Configuration Manager. The reporting services point copies report folders and reports to SQL Server Reporting Services, applies the security policy for the reports and folders, and sets configuration settings in Reporting Services. The reporting services point is a site system role that must be configured on a server with Microsoft SQL Server reporting services installed and running. To install and configure follow the below steps. In the Configuration Manager console, Click on Administration, Site Configuration, right click on Sites and click on Add Site System roles. Provide the required details and Click next to continue. ...
Post a Comment
Read more