Posts by
Exchange Server has two core components. First, there is the mailbox component, with all the required client access protocols and well-known mailbox functions. The second major component is the message flow, with receiving, processing, and sending email messages.
Before we talk about Exchange Server's Managed Availability features, let's first remember the architecture of Exchange Server.
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 virtualized operation of Exchange Server has been a hot topic for discussion ever since the introduction of hypervisor platforms. Often these discussions are very emotional, and the valid arguments rarely heard.
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.
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.
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.
Exchange Server is a very tolerant software product and allows for installation in different IT infrastructure environments. Some of the possible infrastructure environments are well suited for running Exchange Server, others are less good.
This post is about a recent migration of legacy public folders hosted on Exchange Server 2007 to modern public folders hosted on Exchange Server 2013.
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.