Posts about:
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.
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 February 12, 2019, Microsoft released its quarterly updates for Exchange server, and in this case Microsoft has released Exchange 2019 CU1, Exchange 2016 CU12, Exchange 2013 CU22 and Exchange 2010 SP3 Update Rollup 26 (although the latter is not really a quarterly update).
In October of last year Microsoft released a new version of on-premises Exchange server. Here at the ENow's Solution Engine blog, we realized we had a lot we could cover. Normally I focus mostly on writing about Office 365 and Azure features and updates, but I think there is still room in the blog-o-sphere for a post about on-premises software too.
Autodiscover was first introduced in Exchange 2007 and Outlook 2007 to quickly configure Outlook profiles, based on only the username and password. Outlook connects to the Exchange server, you enter your email address and password, and the Exchange server returns an XML package that Outlook uses to create or change its profile. The first implementation of Autodiscover was in Exchange 2007, but it is still used in Exchange 2019. Of course, there have been some improvements over the years, both in Exchange server as well as in Outlook, but overall the mechanism is the same.
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.
Outbound messages to the Internet are routed from the Exchange Online organization through your on-premises organization. With the exception of messages sent to other recipients in the same Exchange Online organization, all messages sent from recipients in the Exchange Online organization are sent through the on-premises organization.