With nothing even running on it and little to no features or roles installed. This is really unacceptable on a production server, especially a Hyper-V 2016 host, as a core Do the restart and then wait for 2 hours for it to restart.
I shutdown all the guest VM's, use the Sconfig tool to Download and Install updates. No status, no percent complete, no idea what it is doing. Don't turn off your computer" and stays there for 2 hours. When I do the restart to install updates it goes to a command window which shows, "Getting Windows ready. Running Hyper-V 2016 as a host on a new HP ProLiant D元80 G9. Hyper-V CPU usage is showing 5 % CPU usage Right this second I'm waiting on an RDS server to simply shut down and it's been sitting at that screen for 40 minutes now. We're also seeing this on servers with little to no services, they're basically lightweight servers that have no activity. Often these are high-end servers with extremely fast I/O. Up? I don't have enough fingers to count the amount of times it's disrupted the schedule of IT/IS folks who are waiting on a server to shut down.īasically Windows Updates' are not installing, either the servers are already up to date or we've configured the servers for manual install of updates yet despite that we regularly experience unacceptable waiting periods while we're restarting servers We've pretty much hit our breaking point with this grossly disruptive shutdown process with Windows Server 2016, similar to what's seen with Windows 10 Does anyone know how to adjust this, maybe disable a shutdown process that's hanging servers
0 kommentar(er)
