I called it yesterday!
Re: Windows Update: http://forums.theregister.co.uk/forum/1/2013/08/14/microsoft_cloud_problems/
Do I get a cookie?
Microsoft has pulled a security update for Exchange 2013 after problems emerged with the latest patch to the email server software just hours after its release. The critical MS13-061 security update for Exchange Server 2013 broke the message index service, preventing Exchange 2013 email users from searching their mailboxes. …
This post has been deleted by its author
"I think Vista could be argued to be the beginning of the end as the first major product that went Pete Tong."
Erm, Microsoft Bob. Windows ME both come to mind.
But, they're still in business churning out shitty patches.
Remember NT4 SP6? The lawyers were howling over their broken Lotus Notes.
You'd have thought the Microsoft would've learned from that debacle!
"Q: You have told us time and time again that you were going to improve your testing procedures, and yet each time you have to tell us that you missed something. When will it end?"
Good that they're asking the questions, bad that this isn't the first time it has happened.
from the blog linked in the article:
"Q: How was this issue not detected in Exchange Online if Exchange Online is always receiving fixes before on-premises customers?
A: Exchange Online does not deploy .msp patches into the environment; instead, Exchange Online deploys new full builds of the product (cumulative updates, if you will) on a regular release cadence. As a result, Exchange Online was not impacted by this issue."
Someone has to be first!
The problem that occurred in this case is one that you might easily have missed if you relied on testing patches yourself on a test server, but luckily, if you are taking that approach, you're probably not planning to get all your testing finished within the first 24 hours of patches being released, so you'll still benefit from the reports trickling in of other people encountering problems.
"The problem that occurred in this case is one that you might easily have missed if you relied on testing patches yourself on a test server,..."
Except when the patch works on the test server, but fails for obscure reasons when it hits the production environment.
Had that a few times in the past.
Annoying as hell.
So... Another Oracle failure which manages to take a MS product with it.
Guys: STOP USING ORACLE SHIT!!! We know everything that comes out of them is full of holes.
While at it, roll these patches out to your OWN servers FIRST. When you have the kinks worked out then put it out for general usage.
Biting the hand that feeds IT © 1998–2020