WDS’s Service Control Point
January 22nd, 2009 Posted in WDSToday I was alerted to an issue in Operations Manager on one of my WDS servers:
Log Name: System/Application
Source: BINLSVC
Date: Date
Time: Time
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.
Research ensued, and a quick Googling (sorry Google) revealed the following:
When the computer starts, BINLSVC queries for the information that is contained in the Service Control Point (SCP), this operation is performed before the creation of the SCP, and then BINLSVC logs an error message in the Application log or the System log. This error message states that the server’s SCP is missing. This is expected behavior on new WDS servers and in other instances where the SCP has not yet been created for the server. In this case, you can safely ignore the error that is logged in the Application log or the System log.
However, the problem here is that this is not a new WDS server. So, I came across this from another Google result. It doesn’t really apply to my situation (as I was not moving the Computer object to a different OU), but it fixed the error and restored the SCP.
For posterity:
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:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
- Move the WDS account to Active Directory in the new organizational unit.
- To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.