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.
|Source: OnePoint Operations|
The Agent Manager experienced an error attempting to contact computer <computer> while resolving the Managed Computer rules. The service account may lack necessary privileges, the computer may be offline, or the computer may be running something other than Windows NT or Windows 2000.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "Network problems that prevent communication are often the reason why computers cannot be accessed. This is true especially when computers are added to the list of managed computers manually, instead of relying on pattern matching. Using pattern matching and wildcards only includes computers that exist in the domain browse list. These computers are probably on the network and running. If a computer name has been entered manually, the Agent Manager will continue attempting to contact it, regardless of whether it exists or not". See "Microsoft Operations Manager 2000 Chapter 8 - MOM Agent Management" for more details on this issue.
|Private comment: Subscribers only. See example of private comment|
|Links: Microsoft Operations Manager 2000 Chapter 8 - MOM Agent Management|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated