A Windows Deployment Services server that is running Windows Server 2003 may not start after you move the server to a different organizational unit


Symptoms


A Windows Deployment Services (WDS) server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or Microsoft Windows Server 2003 with Service Pack 2 (SP2). If you move the WDS server to a different organizational unit, the WDS server may not start. Additionally, one of the following error messages may be logged in the System log on the WDS server:

Error message 1
Type: Error

Event ID: 7024

Source: Service Control Manager

Description: The Windows Deployment Services Server service terminated with service-specific error 9 (0x 3).
Error message 2
Type: Error

Event ID: 7024

Source: Service Control Manager

Description: The Windows Deployment Services Server service terminated with service-specific error 19 (0x13)
One of the following groups of error messages may also be logged in the Application log:

Error message group 1
Type: Error

Event ID: 261

Source: WDSPXE

Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x 3



Type: Error

Event ID: 1800

Source: BINLSVC

Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x 3



Type: Error

Event ID: 1803

Source: BINLSVC

Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2
Error message group 2

Event Type:Error

Event Source:BINLSVC

Event ID:1803

Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2



Event Type:Error

Event Source:BINLSVC

Event ID:1800

Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x13



Event Type:Error

Event Source:WDSPXE

Event ID:261

Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x13



Event Type:Error

Event Source:WDSPXE

Event ID:265

Description: An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x13



Event Type:Error

Event Source:WDSServer

Event ID:513

Description: An error occurred while trying to initialize provider WDSPXE from C:\WINDOWS\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x13



Event Type:Error

Event Source:WDSServer

Event ID:522 Description: An error occurred while trying to shutdown provider WDSPXE. Error Information: 0x6

Cause


This problem occurs because the location of the computer object that is running WDS has changed in the Active Directory directory service.

Resolution


To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:

  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
  3. Move the WDS account to Active Directory in the new organizational unit.
  4. To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

More Information


During startup, WDS uses the computer account in Active Directory to create an object. If the location of the computer object has changed, you may experience the problem that is described in the “Symptoms” section.