W
williamgault
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 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.
Basically 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 or shutting them down for maintenance.
Often these are high-end servers with extremely fast I/O. We're also seeing this on servers with little to no services, they're basically lightweight servers that have no activity.
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. Hyper-V CPU usage is showing 5 % CPU usage
Continue reading...
Basically 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 or shutting them down for maintenance.
Often these are high-end servers with extremely fast I/O. We're also seeing this on servers with little to no services, they're basically lightweight servers that have no activity.
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. Hyper-V CPU usage is showing 5 % CPU usage
Continue reading...