The guys at Microsoft definitely dropped the ball this time. This is going to have serious consequences, and make people start contemplating other options.

They're not. They don't want to. They are being told they don't need to. It's the Cash Register Syndrome at work.Text from my new alma mater:
View attachment 373169
You know, back in my day, the Computer Science department hosted all of the University's own services on its own servers, managed by CS profs, grad students, and Information Systems work-study undergrads (I was one!).
How are the kids supposed to learn anything if MS is managing their IT?
I had to ask Google AI about this one:Cash Register Syndrome...
You are correct. My bad….
Follow the link.NSAspook; I looked at the definition of “Cash Register Syndrome” but I cannot figure out how this relates to the topic.
Ah. Except that, there are no more cashiers!
How about just reading either one of the links that has been provided?Who knows what is the Cash Register Syndrome or is this something that @WBahn made up?
I can only surmise that he is making reference to the situation where something adds up to $9.20 and you give the cashier a $10 bill and a 25-cent coin which confuses the heck out of the cashier. The usual response is, "Sir, you gave me too much money!".
Easy fix, tell Copilot not to make any mistakes.Microsoft blames failed server health checks
On a status page, Microsoft said “we have no evidence of malicious activity associated with this incident” and promised to “share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.”
“We’re aggressively pursuing all pathways to reduce impact,” Microsoft said on X.
But Microsoft’s public statements make clear that the tech giant was blindsided by the outage and struggled for hours to find mitigations that could reliably restore user access.
Shortly after detecting the outage, Microsoft confirmed that the main issue was “a portion of infrastructure” that “is experiencing elevated load across multiple regions.” This was not caused by increased traffic, Microsoft said, but “a problem that’s causing servers to fail automated health checks and become unavailable.”
Once it became clear that the failed health checks were to blame, Microsoft said it took steps to prevent additional server outages while validating alternate health check methods. But four hours later, the company admitted that it was still in the weeds.
This is akin to what a colleague of mine (who, in the 90s, was considered one of the nation's top 100 researchers in AI) told me about how self-driving cars would be programmed by just telling them to take the action that is, overall, in society's overall best interest.https://arstechnica.com/tech-policy...-health-checks-not-hackers-for-global-outage/
Easy fix, tell Copilot not to make any mistakes.
It depends on what you are going to do with it and what level of performance is acceptable. I tend to opt for higher-end machines when I buy one because I only upgrade computers every ten to fifteen years. I've had my current machine for about five years and it's performance is still far beyond what I need. My prior laptop served me well for about 13 years, though is was definitely getting long in the tooth.I am very close to buying a Windows 11 machine to run stuff that demands it. But I honestly have no idea what to buy. I don't need a powerhouse, but I don't want a dog either. It's quite confusing.
An Intel based/Nvidia graphics desktop PC system with reasonable processing speed that can be used for just about anything will cost $4K to $5K whether you build or buy. I recommend Intel Z890 CPU, RTX 5080 graphics for starters. This could be used for video rendering, Gaming, etc.I am very close to buying a Windows 11 machine to run stuff that demands it. But I honestly have no idea what to buy. I don't need a powerhouse, but I don't want a dog either. It's quite confusing.
The nerve! ... all possible malicious activity has already been copyrighted by MicrosoftOn a status page, Microsoft said “we have no evidence of malicious activity associated with this incident”