This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You are running a Windows Server 2008-based computer that has the Windows Deployment Services (WDS) server role installed.
You configure the WDS settings.
In this scenario, an event that resembles the following may be logged in the System log or in the Application log:
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.
Error Information: 0x2
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.
Although the 1803 event is logged, there is no real harm to the system in this scenario. This is because WDS queries for the SCP before the creation of the SCP. For more information about WDS and the SCP, see the Deploying and Managing the Windows Deployment Services Update on Windows Server 2003 white paper. To do this, visit the following Microsoft Web site: