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.
The WinRM service is not listening for WS-Management requests.
If you did not intentionally stop the service use the following command to see the WinRM configuration:
winrm enumerate winrm/config/listener
For more information see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|English: Request a translation of the event description in plain English.|
According to TD363600, to fix this problem, create a listener for the WinRM service (type winrm quickconfig to create a listener for the WinRM service).
From a discussion group:
The problem was caused by a Supermicro server management software that was running and using the port 80 of the server. WinRM apparently needs to have port 80 exclusive by itself in order to SCVMM to run properly. So I had to hunt down the services that is conflicting and killed it.
After server reboot, SCVMM client installed just fine.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated