Question : WDSServer service will not start

I have a Windows 2008 domain. In this domain, I have a Windows 2008 32bit server that is running Windows Deployment Services and Microsoft Deployment Toolkit 2010. Everything has been working just fine for several months.

This last weekend, I pushed out thelatest Microsoft Updates to all of the servers, including the WDS server. Shortly after I completed the updates, the primary UPS popped a breaker and the servers all came down. Everything came back up, encluding my Exchange 2007 server, and I didn't have any apparant data loss.

However, afterwards, the WDSServer service on the WDS server will not start. I get the following messages;

Windows could not start the Windows Deployment Services Server on Local Computer. For more information, review the system event log.

Event ID: 7025
Source: Service Control Manager Event
The Windows deployment Server terminated with a service specific error 2148073483

Event ID: 257
Source: WDSServer
An Error occurred while trying to start the Windows Deployment Service Server. Error in information 0x8009000B

I found one entry on Experts Exchange that talked about this being a DNS issue. From the WDS server, I have the correct DNS suffix attached to the network adapter. I can ping any server by DNS name and get a reply. From any other server, I can ping the WDS server and get a reply.

I tried the following, each with no success;
1. Disabling the Windows Firewall
2. Unjoined and then rejoined the WDS server to the domain
3. Removed and reinstalled the WDS role
4. Took down all servers. Brought up just the domain controllers, one at a time, and then brought up all of the other servers.

I am at a loss. My image deployments are at a complete standstill because I can't PXE boot. I am falling behind schedue and need ot get this resolved asap.

Does anyone have any ideas?

Thanks in advance,

Dave

Answer : WDSServer service will not start

I think this is not a DNS issue
is the  DHCP server and the WDS server are installed on the same computer? and  you selected Do not listen on port 67 option is enabled in the DHCP tab ?

When the DHCP server and the WDS server are installed on the same computer, the WDS Service tries to use the port 67., the DHCP server already uses this port

At the command prompt, enter this
wdsutil /set-Server /UseDhcpPorts:No

or you can  change that via GUI at the DHCP tab

The following registry subkey controls whether the PXE server listens on the DHCP port:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

To enable the PXE server to listen on port 67, set the value of the UseDHCPPorts registry entry to 1

To disable the PXE server from listening on port 67, set the UseDHCPPorts registry value to 0
Use this setting in configurations where the Windows Deployment Services PXE server and the DHCP server are installed on the same computer.