H
Holger Keil
Hi,
I'm diggin into an issue with those two events on a newly installed Dell server. Directly after installation, it keeps logging event 10149:
The WinRM service is not listening for WS-Management requests.
User Action
If you did not intentionally stop the service, use the following command to see the WinRM configuration:
winrm enumerate winrm/config/listener
The listener is configured and the service appears to be up and running. Nevertheless, the event is logged on every reboot. After installing the AD roles and promoting it to a DC (new forest, single server, AD&DNS) event 10154 showed up as well.
I'd followed and tried dozens of solutions which - in general - all should lead to the same result: Granting the network service the right to create the SPNs by himself... Nothing helped. Finally, I've added the requested SPNs manually which succeeded in that way, that they became listed when querying setspn /l, however event 10154 stayed, as well as 10149 on every reboot.
I'm running out of ideas. Any clues or solutions for this?
Best Regards
Holger
Continue reading...
I'm diggin into an issue with those two events on a newly installed Dell server. Directly after installation, it keeps logging event 10149:
The WinRM service is not listening for WS-Management requests.
User Action
If you did not intentionally stop the service, use the following command to see the WinRM configuration:
winrm enumerate winrm/config/listener
The listener is configured and the service appears to be up and running. Nevertheless, the event is logged on every reboot. After installing the AD roles and promoting it to a DC (new forest, single server, AD&DNS) event 10154 showed up as well.
I'd followed and tried dozens of solutions which - in general - all should lead to the same result: Granting the network service the right to create the SPNs by himself... Nothing helped. Finally, I've added the requested SPNs manually which succeeded in that way, that they became listed when querying setspn /l, however event 10154 stayed, as well as 10149 on every reboot.
I'm running out of ideas. Any clues or solutions for this?
Best Regards
Holger
Continue reading...
