Exchange 2013’s new Information Store architecture — where each database runs in its own worker process (Microsoft.Exchange.Store.Worker.exe) — changes what you monitor compared to Exchange 2010. Problems are more isolated, which is good, but your monitoring approach needs to account for per-database process tracking rather than a single monolithic store. The Counters That Actually Matter … Read more
By late 2014, Office 365 had matured to the point where the question wasn’t “should we consider it” but “when do we move.” Organizations that had just completed Exchange 2013 deployments found themselves weighing a cloud migration sooner than expected. Here’s what a realistic transition looked like. The Hybrid Configuration: Necessary Complexity Microsoft’s recommended migration … Read more
Mail flow issues are the highest-urgency Exchange problem category — users notice immediately when email stops working, and everyone assumes it’s the mail server’s fault even when it’s not. A methodical approach saves time and prevents chasing the wrong thing. Start With Scope Before touching any configuration, establish the scope of the problem. Is the … Read more
Exchange 2013 was designed to tolerate slower, cheaper storage better than any previous version. Microsoft optimized it heavily for JBOD (Just a Bunch of Disks) in large enterprise deployments. For mid-size organizations, that changes the calculus around storage architecture — but only if you understand what the optimization actually buys you. Separate OS, Database, and … Read more
Certificate issues are the most consistent source of Exchange 2013 headaches I’ve encountered across different organizations. The platform handles certificates in a specific, opinionated way — and when something goes wrong, the error messages are rarely helpful enough to point you directly to the fix. The Certificate Landscape in Exchange 2013 Every Exchange 2013 server … Read more
Managed Availability is one of Exchange 2013’s most significant operational changes — and one of the least understood. It’s a built-in health monitoring and self-healing framework that watches Exchange components and takes corrective action when it detects problems. In theory, it means Exchange fixes itself. In practice, it can make troubleshooting significantly harder if you … Read more
At some point, you will open the Exchange Admin Center or EMS and find a database in a dismounted state. If you’re lucky, it’s a managed availability-triggered failover that resolved cleanly. If you’re not, you’re staring at a database that won’t mount because it’s in a dirty shutdown state. Here’s how to work through it … Read more
Database Availability Groups in Exchange 2013 are the right answer for most organizations that need mailbox redundancy. But “you should use a DAG” is where most guidance stops, and the actual design decisions — how many members, which witness server, how to handle network configuration — are where people run into trouble. Two Nodes vs. … Read more
Exchange 2013 launched with a significantly revamped architecture, and when the organization I was supporting decided to move off Exchange 2010, I expected a relatively clean migration path. We’d done the 2007-to-2010 move a few years prior without too much drama. Exchange 2013 turned out to be a different beast. The Architecture Shift That Changes … Read more