Event ID 768 — Auto-Add Devices Database

  • Article

Applies To: Windows Server 2008 R2

The Auto-Add Devices database enables you to add computer accounts to Active Directory Domain Services automatically. You will find this database in the \RemoteInstall\Mgmt folder (by default, the RemoteInstall folder is located on drive C). The database is created by the Pre-Boot Execution Environment (PXE) provider the first time you enable the Auto-Add functionality (using either the MMC snap-in or the /AutoAddPolicy command-line option). All computers in the pending queue are represented as an entry in the database on the Windows Deployment Services server.

Event Details

Product: Windows Operating System
ID: 768
Source: BINLSVC
Version: 6.1
Symbolic Name: E_BINL_AUTOADD_INIT_FAILED
Message: An error occurred while trying to initialize the Auto Add Policy.

Error Information: %1

Resolve

Ensure that the registry data and permissions are correct

The Pre-Boot Execution Environment (PXE) provider provides client boot services over the network. This provider must be able to create and modify the Auto-Add Devices database and the tables and indexes contained in the database so that it can create and manage pending devices.

To resolve this issue, first ensure that there is enough memory on the server. If there is enough memory, then do the following in the specified order until the issue is resolved:

To resolve this issue, do the following:

  • Ensure that the WDSServer service has permissions to the RemoteInstall folder
  • Ensure that the WDServer service has access to the registry.
  • Ensure that the configuration data in the registry is correct.
  • Recreate the database.

Ensure that the WDSServer service has permissions to the RemoteInstall folder

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To ensure that the WDSServer service has the necessary permissions:

  1. Right-click the RemoteInstall folder (by default, this folder is located on drive C).
  2. On the Security tab, make sure that WDSServer is set to Full control.

If the Full Control check box is already selected, use the procedure in the following section to ensure that the WDServer service has access to the registry.

Ensure that the WDServer service has access to the registry

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To ensure that WDSServer has the necessary permissions:

  1. Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER).)
  2. Locate the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\
  3. Right-click the WDSServer node, click Permissions, click SYSTEM, and then make sure that Full Control is selected.

If WDSServer has access to the registry and the problem persists, perform the procedure in the following section to make sure that the configuration data in the registry is correct.

Ensure that the configuration data in the registry is correct

To perform this procedure, you must either be a member of the local Domain Admins group or have been delegated the appropriate authority.

To ensure that the configuration data is correct, use the following steps to restart the WDSServer service:

  1. Open the Command Prompt window.
  2. At the command prompt, run net stop wdsserver.
  3. At the command prompt, run net start wdsserver.

If you continue to encounter this error, use the procedure in the following section to recreate the Auto-Add Devices database.

Recreate the database

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To recreate the database:

  1. Delete the contents of the RemoteInstall\Mgmt folder. By default, the RemoteInstall folder is located on drive C.

  2. Open the Command Prompt window.

  3. At the command prompt, run net stop wdsserver.

  4. At the command prompt, run net start wdsserver.

Verify

To perform this procedure, you must either be a member of the local Domain Admins group or have been delegated the appropriate authority.

To verify that the Auto-Add policy is active:

  1. Restart the WDSServer service. To do this, open the Command Prompt window, run net stop wdsserver, and then run net start wdsserver.
  2. Open Event Viewer. (Click Start, type Event Viewer in the Start Search box, and then press ENTER).
  3. In the left pane, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  4. Click the Date and Time column heading to sort the events based on date and time.
  5. Look for BINLSVC event 769. The presence of this event indicates that the Auto-Add settings were applied correctly.

Auto-Add Devices Database

Windows Deployment Services