Exchange 2016 Cumulative Update 1 Installation

Cumulative Update 1 for Exchange 2016 has been out since 03/15 but I didn’t get a chance to write about it. Below you will find some step how to roll it out in your environment. Of course it has a number of fixes and  that’s the reason you need to update you server. The server patching process is different on a single exchange server 2016 and in a environment where you have more than one server and running DAG and CAS behind the load balancer. For a HA environment , you will need to plan accordingly.

This is one of the example when you run this cmdlet on Exchange 2016 prior to CU 1
Screen Shot 2016-04-24 at 10.35.30 PM

Below is the screen capture of Exchange 2016 RTM version (before CU 1)

 

Here is the installation process
Screen Shot 2016-04-22 at 10.23.54 AM Screen Shot 2016-04-22 at 10.22.44 AMScreen Shot 2016-04-22 at 10.22.07 AM Screen Shot 2016-04-22 at 10.21.29 AM Screen Shot 2016-04-22 at 5.16.37 PM

 

Here is the Server build of Exchange 2016 CU 1 with a new schema

Screen Shot 2016-04-26 at 9.21.56 PM

Screen Shot 2016-04-26 at 9.22.09 PM

List of issues fixed by CU 1

Here is the list of all issues fixed in this Cumulative Update CU 1

Updated OWA S/MIME control
New distribution package for Exchange Server 2016 update
Change to Mailbox Anchoring for Remote PowerShell
Additional languages for Outlook on the Web
.Net 4.6.1 Support
Slow installations on Windows Server 2012 R2
Support for Standalone Hybrid Configuration Wizard in Exchange Server 2010

.Net 4.6.1 Support

Make sure you are not running this version of DotNet Framework. This version is nut supported yet.

For the latest information on Exchange Server and product announcements please see What’s New in Exchange Server 2016 and Exchange Server 2016 Release Notes. You can also find updated information on Exchange Server 2013 in What’s New in Exchange Server 2013Release Notes and product documentation available on TechNet.

Now if you run Test-ExchangeSearch , you will get this cmdlet working

Screen Shot 2016-04-26 at 9.15.16 PM

Now you have successfully installed the CU 1

Cheers:)

 

Are you still behind on Cumulative Update 11 For Exchange 2013

This is not very common these days but still some organizations are other three months behind or six months behind the Exchange 2013 Cumulative Updates. or you may have setup a new Exchange 2013 you may want to bring it up to the updated CU.

So if you are even no onto the CU11 , below are the some important (depending on the scenario) updates it covers, not all are very important but some of them are very critical .

Here is the list of important updates in my opinion I’d consider upgrading to CU11.

To get the full list of al the update here is the TechNet url

https://support.microsoft.com/en-us/kb/3099522

 

New-AddressBookPolicy – Name ‘New ABP’ ***Exchange 2013 Address Book Policy – Step by Step ***

This will explain how to create a new Address Book Policy, it is not just the New-AddresBookPolicy  cmdlet.

In this scenario we will setup a new address book policy for RD (Research & Development) Department. Below is the list of cmdlets you need to type in order to create ABP for HR Department

Things you need to setup before creating a new Address Book Policy – Pre Reqs

1- Global Address List for RD
********************************

New-GlobalAddressList -Name “GAL RD” -IncludedRecipients MailboxUsers -ConditionalDepartment RD

2- New Address list for RD
****************************
New-AddressList -Name “RD” -RecipientFilter {((RecipientType -eq ‘UserMailbox’))} -RecipientContainer RD

 

3- New Offline Address Book for RD
***************************************
New-OfflineAddressBook -Name “RD OAB” -AddressLists “RD” -VirtualDirectories “Ex2013-mbx1OAB (Default Web Site)”

4 – New Room list  — for room list you will need to setup a room mailbox and distribution group
******************************************************************************************************

New-Mailbox -Database “MBX2DB1” -Name RD_Confroom -OrganizationalUnit “RD” -DisplayName “RD_ConfRoom” -Room
***********                                                        *************************
New-DistributionGroup -Name “RD_ConfRoomList” -OrganizationalUnit “WindowsITAdmin.net/RD” -RoomList
Add-DistributionGroupMember -Identity “RD_ConfRoomList” -Member RD_Confroom@WINDOWSITADMIN.NET

Use shell to convert the Distro to Room List
********************************************
set-DistributionGroup -Identity “RD_ConfRoomList” -RoomList

get the list of room list
Get-DistributionGroup -RecipientTypeDetails ‘roomlist’

Create a new Address Book Policy based on above details for R&D Department
New-AddressBookPolicy -Name “RD ABP” -AddressLists “RD” -OfflineAddressBook “RD OAB” -GlobalAddressList “GAL RD” -RoomList “RD_confRoomList”

Now apply the policy to a mailbox in R&D department
Set-Mailbox RD1 -AddressBookPolicy  ‘RD ABP’

This is how ABP can lock down a user mailbox to specific to their department.