Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 770 Source: BINLSVC

An error occurred while updating the Auto Add Policy settings. The Windows  Deployment Services server will not process incoming client requests.

Error Information: 0x3A
The ME960489 article provides a workaround and a hotfix. Apparently, the Windows Deployment Services (WDS) server in Windows Server 2008 stops working after the authenticating domain controller becomes unavailable.
T726520 suggests that this might be related to a permissions issue and is providing a list of things to check:
- Ensure that the registry data and permissions are correct
- 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

If all these look fine, the article provides information on how to recreate the Auto-Add Devices database.

Error 0x3A is Error code 58 in decimal system.
In my case, this error followed event ids 266 from WDSIMGSRV and 513 from BINLSVC.  Happened while upgrading a DC (it was offline) but other DCs in the same site were available.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.