Where are we now? Microsoft 363? 362? We've lost count because Exchange Online isn't playing nicely this morning Microsoft's Exchange Online service fell over in the early hours of this morning. The company's status orifice initially figured that the problem mainly affected users in India as its engineers noted the wobbling at around 0700 BST. Just under an hour later Microsoft had to admit it was another global outage. It is the latest …
I can tell you don't use Office 365, because you didn't use the word "we". The fact this article's title uses the word "we" is offensive. If you can no longer use the words "Master" and "Slave" in general computing context, surely you can't use the word "we" in Microsoft context.
What is "we" in Microsoft context anyways? "We feel ignored", "We feel impatient", "We feel trapped"?
"If you can no longer use the words "Master" and "Slave" in general computing context"
Ah, but you can. But only if you want to be understood by virtually everybody involved with technology on the entire planet.
"What is "we" in Microsoft context anyways?"
That's when they piss all over you.
Cheaper right?
Imagine the money spent on a room full of engineers not ever creating anything new, to draw in yet more of that lovely cash, but instead, fixing things. Can you imagine it, the shareholders would be horrified to see such wasted time.
Nah, better to chuck it out to the masses and let them test it, And if they don’t fucking like it we can just refer them to our license agreements, which basically say “fuck you” in legalese
Glad to know, in some sense, that when it all fails, won’t be my responsibility, its the cloud owners responsibility, and the cloud owners will just point to the T’s & C’s, which nobody in legal has bothered to read, and understand, it’s kinda hilarious and stupid
Our new overloads pushed Office365 through our throats to replace our old Exchange on premise. The later was not fantastic but at least was working 364,9 days per year. Teams are really delighted not being able to use mail, a critical service for us as this is the main tool used by customers to place orders.
I *love* when accountants take IT decisions.
Note to the Author: you owe me author's rights for your 'first stone' remark
But just think of all the money they have saved by not purchasing software and the machines to run it on! What's a few missed orders here & there? And of course we save money by not fielding complaints! Maybe we should do away with the "support@" email address, it's a money-sink ...
Your Accountants listening to Their Marketing is running down the economy. Seriously, think about it ... How many Billions of dollars has Microsoft-induced downtime cost corporations world-wide in the last year? The last five years? The last decade? Two decades?
And how much would your company have saved in downtime alone (after re-training costs & etc.) had you switched to BSD & Linux twenty years ago?
What is this to do with Linux or BSD and why would it have saved anything?
Corporations are looking for fully supported products that have defined SLAs, Support frameworks and updates etc. That you have to pay for and the likelihood is that you would then be using have a commercial Linux distribution with commercial applications running on top.
The only truly viable enterprise alternatives for Exchange were Groupwise or Lotus Notes, both hanging on by a thread.
I've used Groupwise and Notes. Heavyweight maybe, but a hammer to crack an egg in cases I've seen. cc:Mail seemed more responsive. My Email Server of choice is undoubtedly Mdaemon. Not sure how far up the Enterprise scale Mdaemon will go, but they have standard pricing up to 2500 users. Biggest installation I've carried out was 50 users, which replaced Exchange.
Disclosure: I am an Mdaemon reseller.
(DV was not me!)
No Service as a Service
Just another thought-experiment.
Imagine a world in which we pay for micros~1 362 only the (362/365)-th fraction of the subscription. Or, if we recieved some sort of compensation if the outage lasts longer than say 3 hours, as it is the case with airline flights.
I know the way out.
If you outsource your personal or corporate key services and tools, you have outsourced your own destiny. While it may look really good on paper, in the long term that kind of decision making tends to backfire. Just ask the guys at IBM who thought outsourcing OS/2 development to Microsoft was a good idea.
* Micros~1 Upgrades - highly overrated
* The Cloud - highly overrated
* Universal Desktop - highly overrated
* RDP workstations - highly overrated
Micros~1 "Solutions" (in general) - HIGHLY OVERRATED
I recommend Libre Office instead. And if you MUST do the cloudy thing, google has something (google docs) that _ALMOST_ works.
Our org just went full tilt 365 with huge restrictions for most users.
When the outage occurred, not one announcement mentioned the global outage, but simply that users were having difficulty signing on and they were investigating. I had already figured out where the outage was.
I certainly heartily agree with
In the meantime, folk were left twiddling their thumbs and pondering the wisdom of a leap cloudwards versus an on-premises service, staffed by engineers that could be yelled at face to face.
I was one of them!
Oh yeah, we had just gone through a seemingly pointless email address change.
Do we actually do any work other than grappling with IT issues? Boss of mine once said, "We never had these problems with typewriters!"
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
