Tag Archives: Exchange 2016

Updated Exchange Server Role Requirements Calculator

The Exchange Server Role Requirements Calculator which you need for designing a proper Exchange 2013 or Exchange 2016 on-premises environment has been updates, currently the calculator is at version 8.4.

Some new functionality is added to this version:

  • Added support for ReplayLagMaxDelay
  • Added support for SafetyNetHoldTime in CreateDAG.ps1

And seven bug fixes in this version:

  • Improved the DAG auto-calculation results display to highlight deployment configuration in both datacenters
  • Fixed an issue that prevented DAG auto-calculation in single site DAG deployments
  • Fixed a SPECInt2006 validation issue with DAG auto-calculation
  • Fixed a bug with the DAG auto-calculation with Active/Passive deployments
  • Fixed conditional formatting issues with the transaction log table
  • Removed data validation from certain unused cells on the Input tab
  • Fixed bug in calcNumActiveDBsSF formula

The requirements calculator can be downloaded here: https://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780

More information:

Exchange 2016 CU4

On Tuesday december 13, 2016 Microsoft has released its quaterly updates:

and Update Rollups:

Looking at Exchange 2016, what does this CU bring us?

There are minor changes to the user interface of Outlook on the Web or Outlook Web App, whatever you may call it. It’s not that dramatically, the formatting controls have been moved to the bottom of the frame containing the editing pane, as can be seen on the following screenshot.


And finally, there’s support for the .NET Framework 4.6.2. Using .NET Framework 4.6.2 is still optional (but recommended), but the upcoming release in March 2017 (Exchange 2016 CU5) will require the use of .NET Framework 4.6.2.

As you might have noticed, Exchange 2016 CU3 (the previous release) introduced support for Windows Server 2016. This was also announced at the Ignite 2016 in Atlanta. Unfortunately there was a major flaw in Windows 2016 clustering that caused issues with Exchange 2016 in a Database Availability Group configuration. This has now been fixed by the Windows team (KB3206632), and Exchange 2016 again fully supports Windows 2016. The hotfix is mentioned is mandatory, and the setup application does a check for this hotfix.

Exchange 2016 does not introduce any new schema changes, but you may execute setup.exe /prepareAD /IAcceptExchangeServerLicenseTerms to make sure any changes in the configuration partition are applied successfully.

As usual, and especially after the latest issues with Exchange 2016 CU3 and Windows 2016 I strongly encourage everybody to thoroughly test Exchange 2016 CU4 (or any other update that’s needed of course) in your lab environment before bringing it into production!

Install Office Online Server 2016

In Exchange 2013 you could use the Office Web Apps server in combination with Exchange server to view attachments online, without having to download these attachments first to the local workstation. Exchange 2016 is the successor of Exchange 2013, Office Online Server (OOS) 2016 is the successor of Office Web Apps 2013.

For an optimal user experience in Outlook on the Web you want an Outlook Online Server to view attachments online. Instead of downloading the attachment to your client workstation (not ideal when working on a non-trusted workstation) you can view it in your browser, and your browser will show something like this:


So how does this work?

Continue reading Install Office Online Server 2016

Export to PST in Exchange 2016

This blogpost is more a note to self. I’ve blogged about this years ago, but this blog seems to be gone, although I found some remnants on msexchange.org 🙂

But, sometimes it can be useful to export Mailboxes to PST files, for example when an employee leaves the company, his account and Mailbox is removed, but you want to archive the contents of the Mailbox.

By default, no user can export or import Mailboxes to or from PST files, so these permissions need to be assigned first. As part of the Role Based Access Control (RBAC) in Exchange 2016 there’s the Mailbox Import Export role, but this role isn’t assigned to any user or Security Group.

To assign this role to a user, you can use the New-ManagementRoleAssignment command:

New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "Administrator"

Beware that you have to logon again to the Exchange server to activate this change. After logging on again, you can go to PowerShell and execute the following command to export the content of a user named John:

New-MailboxExportRequest -Mailbox John -FilePath \\FS01\PSTFiles\john.pst

The export request will be queued, and the MRS (Mailbox Replication Service) will pick up the request and start exporting the Mailbox to a PST file. You can use the Get-MailboxExportRequest and the Get-MailboxExportRequestStatistics to get more information regarding the actual export:


After some time, your PST file is completed and ready for archiving.

Note. These commands are similar in Exchange 2013 and Exchange 2010.

Change SMTP mail flow in hybrid scenario

After building a hybrid Exchange environment as outlined in a couple of previous blog posts we have an Exchange 2013/2016 environment where some Mailboxes exist on-premises and some Mailboxes exist in Exchange Online. Autodiscover is still pointing to the on-premises environment, and so are the MX records. Inbound SMTP mail flow from the Internet is still accessing the on-premises Exchange 2016 Edge Transport servers before being delivered to the intended recipients.


Figure 1. The Exchange hybrid environment with Mailboxes on-premises and in Exchange online.

Continue reading Change SMTP mail flow in hybrid scenario