Worked, after hours from home, on a Windows Server and fixed and issue with the Database on there. After doing so i thought I'd go to bed and shut down the machine... only I hadn't yet left the RDP connection and shut the server down by Accident. Had to drive to work and start the server up again.
Accidentally shutting down a Windows server is impressive. They have that "why are you shutting down?" dialogue to prevent this scenario.
And there are ways of having that entry removed from the list of options entirely, and not just shifted to the drop-down menu. Makes it harder to physically shut down, but its absence can be a WTF big enough for you to realize which machine you are working on.
I don’t bother doing that to VMs, which can be trivially restarted, but their Hyper-V hosts? You betchya I do it to those.
Oh I was totally on autopilot and selected "Maintenance (Software)" because that is what I did... and I discovered the brainfart two seconds too late.
Worked, after hours from home, on a Windows Server and fixed and issue with the Database on there. After doing so i thought I'd go to bed and shut down the machine... only I hadn't yet left the RDP connection and shut the server down by Accident. Had to drive to work and start the server up again.
Accidentally shutting down a Windows server is impressive. They have that "why are you shutting down?" dialogue to prevent this scenario.
And there are ways of having that entry removed from the list of options entirely, and not just shifted to the drop-down menu. Makes it harder to physically shut down, but its absence can be a WTF big enough for you to realize which machine you are working on.
I don’t bother doing that to VMs, which can be trivially restarted, but their Hyper-V hosts? You betchya I do it to those.
Oh I was totally on autopilot and selected "Maintenance (Software)" because that is what I did... and I discovered the brainfart two seconds too late.