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: OpsMgr Connector|
OpsMgr was unable to set up a communications channel to <IP address> and there are no failover hosts. Communication will resume when <IP address> is both available and allows communication from this computer.
|English: Request a translation of the event description in plain English.|
This is also an issue if you have duplicate SPN's. If you have multiple Management servers there is a possibility that the MSOMHSvc may be duplicated in AD, you can run the following setspn to check for duplicate SPNs:
setspn -T * -T msomhsvc -X
This will give you a list of duplicate SPNs. You will need to delete the duplicated SPNs for the agents to speak to the MS servers.
This can occur if the System Center Operations Manager 2007 Agent is installed on the Gateway Server computer. See ME2004886 for a recommended fix.
This problem usually occurs when the agent cannot establish a security communication channel to the management server because the correct certificates are not available. This problem occurs because agents in the workgroup cannot use the Kerberos protocol for mutual authentication. The certificates must be used in an environment in which the Kerberos protocol is not used. See ME947691 for information on solving this problem.
|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