Article ID: 928645
Article Last Modified on 5/31/2007
APPLIES TO
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise x64 Edition
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
When you try to configure the Windows Deployment Services server (WDSServer) service on a Microsoft Windows Server 2003-based computer, the WDSServer service does not start. Additionally, the following error message is logged in the Application log:
CAUSE
This problem may occur if the WDSServer service cannot bind to a domain controller that is running the Active Directory directory service. The WDSServer service cannot bind to this domain controller if one of the following conditions is true:
- The wrong domain controller or global catalog server was specified by using the following command:
WDSutil /set-server [ /PreferredGC:
name of global catalog server| /PreferredDC:name of domain controller] - The wrong domain controller or global catalog server was specified on the Advanced tab of the server properties in the Windows Deployment Services Microsoft Management Console (MMC).
- The Domain Name System (DNS) service cannot access the domain controller or the global catalog server from the Windows Deployment Services server.
- An error has caused the Windows Deployment Services server to switch the authentication protocol from Kerberos to NTLM.
- A Lightweight Directory Access Protocol (LDAP) Service Principal Name (SPN) registration error has occurred.
- The Windows Deployment Services server is a member of a domain that has a disjointed namespace.
RESOLUTION
To troubleshoot this problem, follow these steps.
Verify that the correct domain controller or global catalog server is specified
- Click Start, point to Administrative Tools, and then click Windows Deployment Services.
- Expand Servers, right-click the server that is running Windows Deployment Services, and then click Properties.
- On the Advanced tab, verify that the correct domain controller is specified in the Domain Controller box.
- Verify that the correct global catalog server is specified in the Global Catalog box, and then click OK.
Use the Network Diagnostics tool to troubleshoot DNS service issues
The Network Diagnostics tool (Netdiag.exe) is included in Windows Support Tools on the Windows Server 2003 installation disc. For more information about how to install Windows Support Tools, visit the following Microsoft Web site:
To determine whether a DNS service issue has caused the domain controller or the global catalog server to become inaccessible to Windows Deployment Services, follow these steps:
- At a command prompt on the Windows Deployment Services server, type the following command, and then press ENTER:
netdiag /v
- Examine the output to determine whether an error has occurred in the DNS service.
- At a command prompt on the domain controller or on the global catalog server, type the following command, and then press ENTER:
netdiag /v
- Examine the output to determine whether an error has occurred in the DNS service.
Use the Network Diagnostics tool to troubleshoot Kerberos authentication issues
- At a command prompt on the Windows Deployment Services server, type the following command, and then press ENTER:
netdiag /v
- Examine the output to determine whether an error has occurred in Kerberos authentication.
- Examine the System log to determine whether an error has occurred in Kerberos authentication.
Use the Network Diagnostics tool and the Domain Controller Diagnostic tool to troubleshoot LDAP SPN registration issues
- At a command prompt on the Windows Deployment Services server, type the following command, and then press ENTER:
netdiag /v
- Examine the output to determine whether an error has occurred in the LDAP SPN registration.
- On the domain controller, type the following command, and then press ENTER:
dcdiag
- Examine the output to determine whether an error has occurred in the LDAP SPN registration.
Change the DNS suffix order if the Windows Deployment Services server is a member of a domain that has a disjointed namespace
- On the Windows Deployment Services server, click Start, point to All Programs, point to Control Panel, point to Network Connections, right-click Local Area Connection, and then click Properties.
- Click Internet Protocol (TCP/IP), and then click Properties.
- On the General tab, click Advanced.
- On the DNS tab, click the DNS name of the Active Directory domain in the Append these DNS suffixes (in order) list, and then click the up arrow to move the DNS name of the Active Directory domain to the top of the list.
Add the name and IP address of the domain controller to the Hosts file on the Windows Deployment Services server
- At a command prompt, type the following commands. Press ENTER after each command.
cd %windir%\system32\drivers\etc\hosts
notepad hosts
- Add the IP address and the name of the domain controller to the bottom of the text in the Hosts file.
- On the File menu, click Save.
- On the File menu, click Exit.
Enable tracing on the Windows Deployment Services server and on management components
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To enable tracing on the Windows Deployment Services server and on management components, you must modify the registry. After you enable tracing, verify that the WDSServer service is binding to the correct domain controller or global catalog server.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Tracing\WDSServer
- Right-click EnableFileTracing, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Tracing\WDSMGMT
- Right-click EnableFileTracing, and then click Modify.
- In the Value data box, type 1, and then click OK.
- View the trace log for the WDSServer component in the following location:
%windir%\tracing\wdsserver.log
- View the trace log for the Wdsmgmt.log component in the following location:
%windir%\tracing\wdsmgmt.log
MORE INFORMATION
In Windows Server 2003, Remote Installation Services (RIS) can be updated to Windows Deployment Services. To install Windows Deployment Services in Windows Server 2003, obtain the Windows Automated Installation Kit. For more information about how to obtain this kit, visit the following Microsoft Web site:
Additional query words: win2003 wds
Keywords: kbtshoot kbprb KB928645
