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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
BMSS failed to bind to a network interface card (NIC) because none was specified in the registry. Check the registry to make sure the network bind policy is correct.
|English: Request a translation of the event description in plain English.|
Richard A. Scott
This error occurs because the ADS Administration Services is running on a server for which there is no ADS Server. From Microsoft KB ME910831:
The BMONITOR Subsystem (BMSS) is the underlying transport for the following devices:
- Devices that are running the Deployment Agent.
- Devices that are running an operating system and the Administration Agent.
The BMSS network service binding settings consist of the BindPolicy and BindExcept registry entries. By default, BMSS binds to all network interfaces. BMSS supports the network service binding mechanism that is specified for Microsoft Automated Deployment Services (ADS).
If you have the Administration Service running and you do not have an ADS Server (we retired ours) you are likely to get this error. Stopping and disabling the service seems to resolve the issue. We normally uninstall the agent completely after the build.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated