Exchange 2016: Release notes
Microsoft Exchange Server 2016 introduces a refined set of technologies, features, functions, and services to Exchange Server. Objectively support people and organizations evolving from a communication focus to a collaboration focus. Exchange 2016 reduces the total cost of ownership whether you opt to deploy Exchange 2016 on-premises or opt for provisioning your mailboxes over to the cloud.
This topic covers important information which is needed for successful deployment of Exchange 2016. This primary information is going to help before commencing deployment. This tutorial covers the following sections:
- Windows Server 2012 R2 : Slow installation
Computers executing Windows Server 2012 R2 with Windows update KB3097966 installed, might take up to 50% longer time , comparatively, for Setup to finish.
To work around for resolving this issue, perform the following on each respective server where you are planning to install Exchange 2016, prior from running Setup. You need to perform this once on each respective server.
- First, open an elevated command prompt.
- Execute the command given below
“Note: This command might produce several warnings / errors. As it is expected, hence doesn’t mean the command has failed.
- Execute the following command. In case the number returned is 0, then ngen.exe command successfully completed.
- Installing or Configuring Exchange using Delegate Admin permissions lead Setup to fail
In case a user is a member of the ONLY delegated setup role group tries to install exchange on a pre-provisioned server, then setup might get fail. This occurs as the Delegated Setup group lacks the permissions needed to build and configured certain objects in Active Directory.
To work around on such issue, take one of the following measures:
o Add the user installing Exchange via running setup to the Domain Admins Active Directory security section.
o Install Exchange using a user who is a member of the Organization Management role group.
- Mailbox servers running variant versions of Exchange may be added on the same database availability group
The Add-Database Availability Group Server cmdlet and the Exchange Admin Center incorrectly permit an Exchange 2013 server require to be added to an Exchange 2016-based database availability group (DAG), and vice versa. Exchange supports adding only Mailbox servers executing the same version (Exchange 2013 versus Exchange 2016, for instance) to a DAG. Moreover, the Exchange Admin Center shows both Exchange 2013 and Exchange 2016 servers in the list of servers present for adding to a DAG. This might permit an administrator to unintentionally add a server running an incompatible version of Exchange to a DAG (for instance, adding an Exchange 2013 server to an Exchange 2016-based DAG).
There is presently no workaround for this challenging issue. Administrators should be diligent while adding a Mailbox server to a DAG. Add only required Exchange 2013 servers to Exchange 2013-based DAGs, and only Exchange 2016 servers to Exchange 2016-based DAGs. You can distinguish each version of Exchange by glancing at the Version column in the list of servers in the Exchange Admin Center. The list of the server versions of Exchange 2013 and Exchange 2016 are :
- Exchange 2013 15.0 (Build xxx.xx)
- Exchange 2016 15.1 (Build xxx.xx)
2. While using MAPI over HTTP , Could not connect to archive mailbox In Exchange 2016, MAPI over HTTP can be enabled per-mailbox. An issue come into existence that prohibits users from accessing their archive mailbox, in case one is configured, when the given below commands are said to be in true state:
- MAPI over HTTP is enabled on the user’s mailbox.
- MAPI over HTTP is disabled at the organization level.
When above conditions are found to be true, the user will not be able to open their archive mailbox and they’ll observe the error:
The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.
To work around in resolving the issue, perform one of the following:
- Open the archive mailbox via using Outlook on the web.
- Disable MAPI over HTTP on the mailbox by executing the following command.
- Set-CasMailbox <email address> -MapiHttpEnabled $False
3. After 30 seconds , notifications Broker service stops
When you begin your Exchange server, you may notice the Notifications Broker service commence and then stops after approximately by 30 seconds. In case you attempt to start the service manually, it will successfully begin and then stop, again after approximately 30 seconds. No errors or warnings are included in the Event log.
Such behaviour is expected in on-premises deployments of Exchange 2016. The Notifications Broker service conducts a configuration check at each time the server starts. In case there is nothing for the Notifications Broker service to do, it halts automatically until the next time the server is restarted or re-booted.
- Edge Transport servers may reject mail sent to validly authorized recipients
Exchange 2016 Edge Transport servers might reject messages issued to valid internal recipients when the following are true:
- Exchange 2016 Cumulative Update 1 (CU1) is installed on the server.
- Recipient validation is enabled and activated on the server.
When an Edge Transport rejects /refuse or dismiss a message because of this issue, the sender will receive a non-delivery report (NDR) status, along with the status code 5.1.10, and the error Recipient not found by SMTP address lookup. The recipient will not receive the message.
To work around this issue, perform one of the following:
- Disable recipient validation/authorization on the affected Edge Transport server(s) by executing the following command.
Set-RecipientFilterConfig -RecipientValidationEnabled $False
- Disable the recipient /authorize validation cache on the affected Edge Transport server(s) by executing the following command.
Disabling the recipient authorize validation cache causes Exchange to verify to examine that recipients on inbound messages are valid or authorized by querying the local instance of Active Directory Lightweight Directory Services. This may significantly increase and elevate the resources Exchange needs to process messages. Before you disable the recipient validation cache, examine and verify that your server has sufficient capacity to handle the additional demand.
- Install setup & configure your firewall or external mail exchanger (MX) DNS record to send mail to an Edge Transport server which doesn’t have Exchange 2016 Cumulative Update 1 installed. You may need to configure your firewall to permit TCP port 25 to connect to the new Internet-facing server.
- Install setup & configure your firewall or external MX DNS record to send mail to an Exchange 2016 Mailbox server. You may need to configure and setup your firewall to allow TCP port 25 to connect to the new Internet-facing server.