Fuck Microsoft.How has this thread not gravitationally pulled in @bradstevens yet? I bet his home office has already been redecorated with coffee stains and broken ceramics.
...MicrosoftHow has this thread not gravitationally pulled in @bradstevens yet? I bet his home office has already been redecorated with coffee stains and broken ceramics.
/Jeopardy_Mode_On
What is the pet name for Brad's pecker?
What is the title of Brad's sex tape?
/Jeopardy_Mode_Off
A good friend will bail you out of jail, but your best friend will be sitting next to you in the cell saying "that was f***ing awesome"
Reporting today says the outage was the result of an update that went awry. Hard to believe, I know.
Nationwide ground stop issued by FAA. Any chance it's related to this MSFT fubar?
"Extraordinary circumstances" and "safety" being cited.
Indiana BMV posted last night one can go get their license faster than Microsoft can repair Outlook.
Microsoft says a repair caused a server to stop responding and the remaining servers couldn't handle it. So I guess they didn't expect the first server to go down? Then they didn't have a hot spare ready to go in case a server, any server, went down. My take, having done this is if you must have 2 servers to handle the load you run 3. Now they have many more, but there must be a margin of error.
Except in emergency, I did work like this at 3AM. Now sometimes that went badly and wasn't back up at 8.
I did once have to down a server in the middle of a busy day and the load balancer thought that meant all traffic should go only to one remaining server. But that resulted in a short outage until I rebooted the balancer. That said, my first instinct was to throw the balancer out the window which would have been a longer outage.
Maybe that is what Microsoft did.
Microsoft says a repair caused a server to stop responding and the remaining servers couldn't handle it. So I guess they didn't expect the first server to go down? Then they didn't have a hot spare ready to go in case a server, any server, went down. My take, having done this is if you must have 2 servers to handle the load you run 3. Now they have many more, but there must be a margin of error.
What I heard was that there was a funky "update." I presumed software, but I suppose it could have been a hardware update.
@unclemark if software, even more crazy. Unless it was to update a zero day exploit, why apply it during the workday.
Though having spent a lot of time trying to get Microsoft updates removed so systems would work again, it would be poetic justice.
Teams looks different. Assuming update. why middle of the day? who knows.Microsoft says a repair caused a server to stop responding and the remaining servers couldn't handle it. So I guess they didn't expect the first server to go down? Then they didn't have a hot spare ready to go in case a server, any server, went down. My take, having done this is if you must have 2 servers to handle the load you run 3. Now they have many more, but there must be a margin of error.
What I heard was that there was a funky "update." I presumed software, but I suppose it could have been a hardware update.
@unclemark if software, even more crazy. Unless it was to update a zero day exploit, why apply it during the workday.
Though having spent a lot of time trying to get Microsoft updates removed so systems would work again, it would be poetic justice.
The outage was worldwide. If it was hardware, I'd have to believe they have servers across the globe that are mirrored and that one going down shouldn't cause a worldwide outage. A bad software update would propagate across all their servers.
I thank my lucky stars I don't have to deal with all that shit anymore.