I decided I could try living without this service, so I found the “Windows Remote Management” service disabled it and stopped it. This service is detailed here, Windows Remote Management (Windows) – MSDN If you did not intentionally stop the service, use the following command to see the WinRM configuration: The WinRM service is not listening for WS-Management requests. I noted that during the shut down there was a heap of “service x has shut down” messages, but then there was a 6 minute gap followed by a Warning message from the “Windows Remote Management” service, WinRM. It would take about 8 minutes before the packets were being dropped.Īfter one of these reboots, I opened event viewer and looked at the “System” logs. I tested this a few times, by pinging the server during a reboot and (ping -t), and waiting for lost packets. I applied some patches and needed to reboot the guest and had to wait 10 minutes. The issue of slow logins was also compounded recently with really slow shutdowns. I have changed nothing on the hyper-v host. I have left the sum total of the trouble shooting that I have done, in the previous solutions further down, but this latest solution seems to be the one. Ok, this problem has been driving me crazy, and each time I apply a “fix” I find a week later that I am back to having problems. I have now also noticed it is taking approx 10 minutes to shut down when performing a reboot. It got to the point where it was taking 4 or 5 attempts to login and costing about 15 minutes every morning.
Using AWS Systems Manager to Tag and Patch On-Premises Servers.
0 kommentar(er)
