Exchange News

Today was a big day for Exchange updates. Not only did we get Cumulative Update 14 for Exchange 2013, but we also got our third update for Exchange 2016.

As always, test these updates in a lab first! I recommend checking out this 7-part guide on configuring Exchange in your lab. It doesn’t take much to get one going.

The updates are as follows:

Exchange Server 2016 Cumulative Update 3 | KB3152589 | UM Language Pack

Exchange Server 2013 Cumulative Update 14 | KB3177670 | UM Language Pack

Exchange Server 2010 SP3 Update Rollup 15 | KB3184728

Exchange Server 2007 SP3 Update Rollup 21 | KB3184711

So what’s new in these Cumulative Updates?

Quite a lot actually. Namely Exchange 2016 can now be deployed on Windows Server 2016. Keep in mind that you must deploy Cumulative Update 3 to Windows Server 2016. Older Cumulative Updates will not work. Exchange 2013 is not supported on Windows Server 2016. It is unlikely support will ever be added.

Exchange will also work with Server 2016 domain controllers. However, this will require raising the domain and forest functional levels to a minimum of Server 2008 R2.

Another amazing addition to Cumulative Update 3 is the ability for search indexes to read from their local database copies. In prior versions, search indexes would reach across the network to read from the active database copy. With search indexes using their local copies network utilization can drop by a staggering 40%.

Windows Server 2016 ships with .NET Framework 4.6.2. That said Exchange Server 2016 CU3 on Windows Server 2016 will be the only supported scenario for .NET Framework 4.6.2. The Exchange Team plans to support .NET 4.6.2 for older releases in the December update. Until then keep .NET 4.6.2 blocked from your 2012 servers.

The Exchange Team has also changed how servers are placed into a server-wide offline mode during upgrades. In previous versions, when applying a cumulative update, Exchange 2013 and 2016 would be placed into an offline mode during pre-requisite analysis. If a server were to fail analysis it could remain offline despite no changes being made. Starting with the September releases server-wide offline is not set until after analysis completes and the installation is ready to make changes.

UPDATE: .NET 4.6.1 is now supported beginning with Exchange 2013 CU13 and Exchange 2016 CU2 (.NET 4.6.2 Preview is not currently supported).

The Exchange Team posted a quick note yesterday addressing a compatibility issue between .NET framework 4.6.1 and Exchange. As of right now (Feb 2016) .NET 4.6.1 is not supported.  Framework 4.6 is also unsupported.

The currently supported version for Exchange 2013 and 2016 is 4.5.2. Framework 4.5 can also be installed on Exchange 2010–although 2010 will only use the OS installed 3.5.

The urgency of this statement is that 4.6.1 is now being pushed as a recommended update in Windows Update.

As with any series of patching it is always critical to review all updates against the Exchange Supportability Matrix. If you want support from Microsoft you must be within the boundaries of that matrix

If you are using WSUS it is always a good idea to put Exchange in its own update group. If you don’t have a patch management system then keep your servers on notify and download. Whichever update method you use, be sure to not blanket accept all updates.

Microsoft has identified one possible compatibility issue with 4.6.1, where a mailbox may be accidentally quarantined, its databases dismount, or, an unnecessary failover to another DAG member. More info can be found in this KB article.

If you have already installed 4.6.1 (or 4.6) Microsoft recommends you uninstall the update.

Below is the note from Microsoft on the supportability of 4.6.1.

Join the conversation on Twitter @SuperTekBoy.

On January 8th Microsoft announced the first Exchange 2016 beta exam. The exam titled ‘Designing and Deploying Microsoft Exchange Server 2016′ (Exam # 70-345) is currently in beta and is proctored by Pearson VUE.

It’s currently uncertain what exams will be required to achieve MCSE Messaging in Exchange 2016. In 2013 there were two paths. One could first either achieve an MCSA in Server 2012 or Office 365. Then you had the two core Exchange 2013 exams to complete your MCSE. At the time of writing beta exam 70-345 is the only announced Exchange 2016 exam. I suspect it won’t be long until we learn more.

Beta exams differ from live exams in that they offer no score at the end. In fact, candidates often have to wait as much as twelve weeks after the conclusion of the beta period before they are notified of their score. You may wonder, why take a beta exam only to wait months on end? Simply put–to demonstrate early competency. Being one of the first to certify on a product can certainly aide career growth. Especially if you are a consultant.

The challenge of sitting a beta exam is the sheer lack of certification books and study material available. However, with the striking resemblance to its predecessor, a strong and well-rounded understanding of Exchange 2013 will provide a great head start. But it’s only a head start. Being an early adopter of Exchange 2016 is critical. It doesn’t have to be early adoption in your work environment, or, at your customer’s sites. The early adoption could be your own lab. A sandbox where you can build and break and play. It doesn’t cost must to get a lab going. My current lab costs a few hundred dollars on a popular auction site. Exchange MVP Jeff Guillet recently posted his specs for a few different lab servers depending on budget. Hosting a lab in Azure is also possible but may come at a bit of a steep price tag. Whatever you decide a lab is a brilliant way to learn and gain exposure to Exchange 2016.