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.
On December 17, 2019 Microsoft released Exchange 2019 CU4 and Exchange 2016 CU15 as part of their quarterly release cycle. As expected, no new features in these Cumulative Updates. According to the Microsoft vision, if you want the latest and greatest you need Exchange Online, if you’re satisfied with a rock solid on-premises deployment you’re good with these versions. And since Exchange 2013 is out of support, no Cumulative Update for Exchange 2013 is released.
On September 17, 2019 Microsoft released its quarterly updates for Exchange. This time, the updates contain Exchange 2019 Cumulative Update 3 and Exchange 2016 Cumulative Update 14. No updates are released for Exchange 2013 or Exchange 2010.
Over the past 20 years we’ve seen some dramatic changes in Microsoft Exchange Server. Exchange server 2000 was the first version that was using Active Directory, after switching from its own directory that was in Exchange server version 4.0 until version 5.5.
In an earlier blog post I wrote about Autodiscover changes, especially when using Outlook 2016 Click-to-Run.
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.
The Exchange Team provides you the Exchange Role Requirements Calculator now for a long time. This tool is still maintained and the preferred one for correct sizing. You can find information on how to use it on this EHLO blog post.
Everybody receives spam and phishing email. Most of the time they are easy to recognize and just annoying, but sometimes there’s phishing email that’s harder to detect by eye. Imagine you’re the CFO of a company and you receive an email from your CEO where he asks to transfer $ 50,000 to an account. And you cannot talk about it, because it is for an unannounced acquisition.
SSL Certificates in Exchange are widely used, both for encryption of traffic as well as server authentication. Despite the fact they are widely used, a lot of admins still think certificate management is difficult (and expensive). But it is not, let me explain.
The current version of Exchange can, and in most cases should, be installed on Windows Server Core. Windows Server Core is a version of the Windows Server operating system that does not have a Graphical User Interface (GUI). Since “windows” are well ingrained into the administrative habits of most of us Windows Server administrators, it’s reasonable to expect that most Exchange administrators are going to be a bit hesitant to go down this route.