Well we updated the core infrastructure to run on the latest Windows for windows (2016), and it doesn't seem to allow us to control the reboots for updates like it used to. It just allows a 'not busy hours' time to be set which is of course rather useless in a global business.
We have found a few workarounds to prevent this since it happened just now, but the VMs are all starting up now and will be back ASAP. We will also be voicing our displeasure to our software overlords.
We have found a few workarounds to prevent this since it happened just now, but the VMs are all starting up now and will be back ASAP. We will also be voicing our displeasure to our software overlords.