Exchange Server SE Enterprise Review: More Databases, Same Subscription

Fix it now

Exchange Server SE Enterprise runs the same binaries as Standard, offers the same features and is administered identically. What it changes is the number of mailbox databases a server may mount: up to a hundred rather than five. If your design does not need more than five, including passive copies, Enterprise gives you nothing at all.

1. Buy it if the mounted database count on any server exceeds five once you have counted passive copies as well as active databases.
2. Buy it if smaller databases are a deliberate choice, because restore time and failure domain matter more than a tidy file count.
3. Buy it if you are consolidating several sites onto fewer, larger servers, where the copy map alone will push you past five.
4. Skip it if one or two servers with a handful of databases meet the design, because the software is identical.
5. Skip it if the organisation is moving to Exchange Online within the term. Buy the smaller licence and spend the difference on the migration.
6. Work the copy map before you choose the edition. The edition falls out of the design; it is not an input to it.

Standard can be upgraded to Enterprise by product key. Going back is not a key change: it requires uninstalling Exchange, reinstalling it and entering the correct key, so treat the move as one-way.

If your copy map keeps every server at five mounted databases or fewer, buy Standard. The next section is about doing that arithmetic properly.

Why it happens

Standard supports five mounted mailbox databases on a server; Enterprise supports up to a hundred. Copies count, and this is the sentence to read twice. Microsoft defines a mounted database as one in use, and that explicitly includes a passive mailbox database mounted in recovery for log replication and replay. So a resilient design consumes the Standard allowance far faster than administrators expect.

The arithmetic is worth doing explicitly rather than by feel. Take eight mailbox databases with three copies each: twenty-four copies in total. Spread evenly across four database availability group members, that is six copies on every server, and Standard tops out at five. The organisation does not need a hundred databases and it is nowhere near a hundred, but it does need more than five on a server, and that alone decides the edition.

The reason to want more databases in the first place is restore time and blast radius. A single very large database takes a long time to restore or reseed and takes every mailbox in it down when something goes wrong. Several smaller databases restore faster, fail over independently, and let you place noisy or sensitive groups of users on their own storage. That is a design preference with real operational value, and the edition is what permits it.

A database availability group can hold up to sixteen Mailbox servers, and each member is bound by its own edition limit. Design the copy map first and read the edition requirement off it rather than the other way round, because copy layout, activation preference and witness placement matter more to real-world availability than the edition ever will.

Lagged copies deserve a mention because they are regularly confused with backups. A lagged copy replays logs on a delay, which protects against logical corruption propagating instantly, and it is a genuinely useful tool. Exchange Native Data Protection, where multiple copies plus a lagged copy replace traditional backups entirely, is a legitimate design that many organisations should still not adopt. If you cannot describe how you would recover a mailbox deleted six weeks ago, you are not ready to give up backups.

More databases means more log streams, more memory used for database cache and more I/O to schedule, so Enterprise servers are usually specified with more memory and faster storage rather than more processor. Microsoft’s sizing calculator is the tool for that; guessing produces servers that are simultaneously too expensive and too slow.

Full reference

Which edition your design needs

Counting mounted databases correctly

1. List every mailbox database in the organisation.
2. For each one, list how many copies exist and which server holds each copy.
3. For each server, add up active databases and passive copies together. That total is what counts against the limit.
4. Any server whose total exceeds five needs Enterprise, regardless of how small the organisation is.
5. Recount whenever you add a copy or change activation preference, because a resilience improvement can quietly become a licensing change.

Virtualising Exchange without creating problems

Virtualising Exchange is supported and common, and two rules are not negotiable. Microsoft states that making virtual machine snapshots of an Exchange guest is not supported, because snapshots are not application aware and Exchange maintains state data. Microsoft also states that using dynamic memory or memory overcommit for Exchange is not supported. Give the machine fixed memory, and take your backups with an Exchange-aware method rather than at the hypervisor.

The host-based clustering condition is the one that bites in production. Configure the virtual machines so they do not save and restore state on disk when moved or taken offline; failover at the hypervisor level must produce a cold boot on the target node. Planned moves must be a shutdown or a live migration, never a resume from saved state.

Where the licences actually sit

• The server edition governs how many mailbox databases a server may mount. It has nothing to do with which CALs your users hold.
• Standard and Enterprise CALs are chosen per user according to which features that user needs, independently of the server edition.
• Every server still needs a Windows Server licence, and your users still need Windows Server CALs on top of the Exchange CALs.
• The entitlement behind Exchange Server SE is active Software Assurance on Exchange Server licences or a qualifying Microsoft 365 subscription with Extended Use Rights, and it is what entitles you to cumulative updates as well.
• A server kept purely for recipient management with no on-premises mailboxes is licensed at no cost through the Microsoft 365 Hybrid Configuration wizard.

Questions people ask about this