Exchange Center

ENow Software's Exchange blog built by Microsoft MVPs for IT/Sys Admins.

Posts by

Thomas Stensitzki

activated online archive mailboxes

Floating Mailbox Databases in Exchange 2019: Pros & Cons

Image of Thomas Stensitzki
Thomas Stensitzki

Since the early days of Exchange Server, the limits of user mailboxes were strictly regulated. In many Exchange organizations, these quota limits were configured on a mailbox database level and were therefore consistent for all mailboxes stored in the same database. This approach was selected because the existing hard disk space was scarce and expensive in the past.

The following example shows two databases (DB-USER-1 / -2) for standard users and one database with larger mailboxes for executives (DB-C level).

The approach to configuring quotas at a database level was never questioned when transitioning to modern versions of Exchange Server. The old operating patterns were merely taken over.


With modern Exchange Server versions and the Preferred Architecture recommendations this type of servicing of mailboxes no longer makes sense. One of the essential non-technical recommendations is to standardize and simplify the daily operation of the entire Exchange Server platform. Especially with a hybrid setup, which is the parallel operation of a local Exchange organization a and Exchange Online, it is recommended to simplify the service model.

You can standardize and simplify Exchange Server operations by configuring mailbox quotas at the mailbox level. This standardization eliminates the need for dedicated mailbox databases for different user groups. You can move mailboxes between any database, allowing you to respond to on-premises IT infrastructure challenges more flexible.

The following example illustrates this standardization with three mailbox databases (DB-1 / -2 / -3) which store a different number of mailboxes with varying quotas of mailbox.

The simplification becomes even more apparent when we look at the distribution of varying user mailboxes (MBX, blue/yellow) and activated online archive mailboxes (ARC, green).

In addition to user mailboxes and online archive mailboxes, there are other types of mailboxes:

  • Room and resource mailboxes (RES, gray)
  • Public folder mailboxes (PF, orange)

For simplified and standardized operation, these additional mailbox types provide the following example with mailboxes distributed across five mailbox databases.

With a modern implementation of Exchange Server utilizing a Database Availability Group (DAG), you do not need a traditional backup solution. All required functions to protect mailboxes and mailbox content are integrated into the Exchange Server product. Therefore, it does not matter in which database a particular mailbox is stored. This type of operation is the same as the operating model in Exchange Online. In Exchange Online a user mailbox is stored in "a" mailbox database on “some” Exchange Servers.


Are there any disadvantages for such a simplified and standardized operation of mailbox databases in an on-premises Exchange organization?

There is one disadvantage to a standardized operation in an on-premises Exchange organization, at least if you continue to rely on traditional backup methodology and regularly restore mailbox content from a classic (or legacy) backup. In this case, you need to know in which database a mailbox was stored at the time of backup to restore exactly that single database explicitly. The Active Directory object of a mailbox owner has no history of the previous locations of a mailbox. The object stores the current mailbox database location only.

There are no restrictions regarding security for the service operation and administration of Exchange mailboxes. With Exchange Server Role Based Access Control (RBAC) you have all the options to allow management of dedicated mailboxes, e.g., executive mailboxes, to only specific support personnel.  You should refrain from restricting the access to Active Directory objects by adjusting object permissions directly. Modifying the object security settings is much more insecure compared to controlling access using RBAC.


Modern operation of an Exchange organization with database-independent control of mailbox quotas provides flexibility and standardization. In a hybrid setup with Exchange Online, you operate mailboxes in the local Exchange organization in the same way as in Exchange Online. Therefore, you have a consistent mode of operation. The only differences are the different mailbox quotas compared to Exchange Online. Ideally, you also adjust the mailbox quotas in the on-premises Exchange organization to match those in Exchange Online.

If your on-premises IT infrastructure does not provide the necessary operational parameters for secure and stable operation of Exchange Server, but mailbox availability is essential to your business, then Exchange Online is the better alternative.


Enjoy Exchange Server.

Read More

Prepare your On-Premises Public Folders for migration

Image of Thomas Stensitzki
Thomas Stensitzki

Many companies use old-style public folders, known as legacy public folders, on Exchange Server 2010. Often, the public folder hierarchical structures have grown uncontrollably for years. And not only in terms of data volume but also in the number of folders and the folder depth in the public folder hierarchy. For these reasons, many companies fear legacy public folder migration to modern public folders.

Read More

What can we expect from Exchange Server 2019?

Image of Thomas Stensitzki
Thomas Stensitzki

On July 24, 2018, the Exchange Product Group released the preview version of Exchange Server 2019. This version is the third version of modern Exchange Server. Like the previous versions, Exchange Server 2019 benefits from the product developments tested and implemented in Exchange Online. But not all features available in Exchange Online are available in the on-premises version of Exchange Server. Additionally, not all features that are announced for the new release will be available when the RTM build is released. That is something that we have learned with previous releases of the product.

Read More

Secure Mobile Device Access with MobileIron Sentry and Kemp LoadMaster ESP

Image of Thomas Stensitzki
Thomas Stensitzki

Securing mobile devices access to an on-premises Exchange Server infrastructure without a hybrid setup is not complicated when using a single-vendor strategy. You simply implement a Mobile Device Management Solution and you are done. Enterprises doing business in the high security industry tend to follow a multi-vendor strategy to reduce the risks due to security flaws in third-party devices.

Read More
Solutions Engine blog

Creating an Exchange 2010 Transport Agent

Image of Thomas Stensitzki
Thomas Stensitzki

Writing your own transport agent for Exchange Server 2010 is not complicated or an unsolvable task to do.

This transport agent example is the outcome of a requirement to modify email attachments with a GUID based filename. Those filenames were not really usable for the recipients. Interestingly, the email subject contained the information of the content of the attachments. The emails were automatically generated by a SAP reporting application.

The automatically generated email contains two attachments (two different file types just for the sake of demonstration). 
The email subject contains the report date in dd.MM.yyyy format.

The transport agent should perform the following actions:

Read More