Exchange Broke, and the Exchange Update Wasn't the Culprit

Patch Tuesday landed on October 13, and on some on-premises deployments the fallout still hasn't stopped: Outlook on the web refusing sign-ins, mail sitting unsent in the Outbox, delivery queues swelling through the day. The Application log fills with a brutal-sounding error, MapiExceptionMdbOffline, logged as event ID 1006, which reads like a mailbox database coming apart. Except Microsoft's own Exchange Team took pains to point out that this month's breakage is not caused by the Exchange security update released the same week. It's caused by the Windows Server updates underneath Exchange.

The affected combination is specific: Exchange Server 2016, 2019, or Subscription Edition running on Windows Server 2019 or later, with instability surfacing some time after certain October servicing KBs go in. The symptoms aren't one clean failure mode you can unit-test against. Some shops see OWA errors, some see mail crawling toward a full stall, and some report DAG members struggling to reach quorum — a cluster quietly drifting toward degraded availability rather than throwing a flag you'd catch in a staging window. A server reboot buys temporary relief; Microsoft has published a workaround and a note in its Windows release health dashboard. The operational lesson stings a bit: most Exchange admins gate their change window around the Exchange update itself, read its known-issues list, test in a lab, then roll out. The thing that actually broke mail was the OS layer below the product everyone tested. Release health for Windows Server is now part of the Exchange change review, not somebody else's problem — which matters doubly for on-prem mail in a place like the Philippines, where a queue that stalls during business hours is indistinguishable from a company that stopped functioning.

Source article image
Source image 1

The uncomfortable part is how quietly this kind of failure arrives. A queue growing a little each hour, a DAG member one vote shy of quorum — by the time anyone notices, the patch window is closed and remediation happens live, in front of users. My own leaning: treat an OS patch on a mail server host as an application change event, and watch queue depth and DAG health for a day or two after Windows Server servicing, not just the morning after the Exchange update. How strict is your change window, honestly — when you patch a server, do you treat the operating system update and the application running on it as one change, or two?

Source article image
Source image 2

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more