Exchange Updates–June 2017

The Exchange Team have released the June 2017 quarterly updates for Exchange 2013 and 2016. These Cumulative Updates will require .NET Framework 4.6.2 installed prior to upgrade; .NET Framework 4.7 is still being validated by the Exchange Team and should not be installed until validation is completed.

Updated functionality in Exchange 2016 Cumulative Update 6:

• Sent Items Behaviour Control, This feature enables mailbox delegates who have Send As or Send on behalf of permissions of a mailbox to save a copy of the item in the delegators Sent Items
  
  Note:  This feature is targeted to Exchange Server 2016 only and will not be included in Exchange Server 2013. Exchange Server 2013 already has its own implementation of Sent Items Behaviour Control which is different to the version released in this Cumulative Update.
  
  
• Original Folder Item Recovery, This feature enables deleted items to be restored to their original folder; This feature does require LAPEID MAPI property on the deleted item, which has been stamping items since Exchange 2016 CU1, this means that as soon as CU6 is installed this feature will work.
  
  Note: This feature is targeted to Exchange Server 2016 only and will not be included in Exchange Server 2013.

Release Details:

KB articles that describe the fixes in each release are available as follows:

• Exchange Server 2016 Cumulative Update 6 (KB4012108), Download, UM Lang Packs
• Exchange Server 2013 Cumulative Update 17 (KB4012114), Download, UM Lang Packs

Exchange Server 2016 Cumulative Update 6 does include new updates to Active Directory Schema. If upgrading from an older Exchange version or installing a new server, Active Directory updates may still be required. These updates will apply automatically during setup if the logged on user has the required permissions. If the Exchange Administrator lacks permissions to update Active Directory Schema, a Schema Admin must execute SETUP /PrepareSchema prior to the first Exchange Server installation or upgrade. The Exchange Administrator should execute SETUP /PrepareAD to ensure RBAC roles are current.

Exchange Server 2013 Cumulative Update 17 does not include updates to Active Directory, but may add additional RBAC definitions to your existing configuration. PrepareAD should be executed prior to upgrading any servers to Cumulative Update 16. PrepareAD will run automatically during the first server upgrade if Exchange Setup detects this is required and the logged on user has sufficient permission.

Exchange Online Hybrid Customers:

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU17, 2016 CU6) or the prior (e.g., 2013 CU16, 2016 CU5) Cumulative Update release.

Exchange 2013 Cumulative Update

The latest Exchange 2013 Cumulative Update (CU) 10 was released on 15th September 2015. There was no schema changes compared to CU9 , in fact the last schema change was in CU7.

Download the CU10 Download Link, and extract the setup files to local on the Exchange Server. To upgrade the Schema, Configuration and Domain this can be done from a 64-Bit Domain Controller or from an Exchange Server with the Remote Tools Administration Pack feature installed. To install this feature:

1. Open Windows PowerShell (Run as Administrator)
2. Install the Remote Tools Administration Pack using the following command
   
   Install-WindowsFeature RSAT-ADDS

To upgrade the Schema, Configuration and Domain(s) open a command window (Run as Administrator) and run the following commands:

1. Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
2. Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
3. Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms

If you you have multiple domains to in the Active Directory Forest you can use the /PrepareAllDomains.

Note: To prepare The Schema the service account used must be a member of Schema Admins and Enterprise Admins, To update the Configuration and Domain(s) the service account used must be a member of Enterprise Admins.

Reference: TechNet Prepare Active Directory and Domains

PrepareSchema, PrepareAD, PrepareDomain

Unattended Installation

Once the Schema, Configuration and Domain has been updated, allow time for this to replicate to all Domain Controllers in the forest, The easiest way to upgrade a Exchange 2013 server is with an Unattended Installation. Open a command window (Run as Administrator) and run the following command:

1. Setup.com /Mode:Upgrade /IAcceptExchangeServerLicenseTerms

The setup will check the environment to ensure that it’s ready to install, any warnings will be displayed, for instance my installation warned that I didn’t have a send connector for ‘*’, this is because my lab sits behind a dynamic IP address and I can’t send external SMTP.

Note: This upgrade was on a standalone Exchange server that was not a member of a Database Availability Group(DAG), If a server is a member of a DAG it needs to removed/suspended from the load balanced environment and put into maintenance mode, I’ll get this posted on another day.

Disclaimer: All scripts and other PowerShell references on this blog are offered "as is" with no warranty.  While these scripts are tested and working in my test environment, it is recommended that you test these scripts in your own test environment before using in any production environment.

Exchange 2013/2010/2007 Updates…

This is delayed post as I've been offline due to operation on my knee. On the 26^th August 2014 The Exchange Team announced updated to Exchange 2013, 2010 and 2007.

• Exchange 2013 CU6 - Article Knowledge Base
• Exchange 2010 SP3 RU7 - Article Knowledge Base
• Exchange 2007 SP3 RU14 - Article Knowledge Base

Exchange 2007 SP3 RU14:

This update includes new daylight saving time (DST) updates for Exchange Server 2007 SP3.

Exchange 2010 SP3 RU7:

Update Rollup 7 for Exchange Server 2010 SP3 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2983261 "HTTP 400 - Bad Request" error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment
• 2982873 Outlook Web App logon times out in an Exchange Server 2010 environment
• 2980300 Event 4999 is logged when the World Wide Web publishing service crashes after you install Exchange Server 2010 SP3
• 2979253 Email messages that contain invalid control characters cannot be retrieved by an EWS-based application
• 2978645 S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment
• 2977410 Email attachments are not visible in Outlook or other MAPI clients in an Exchange Server 2010 environment
• 2976887 eDiscovery search fails if an on-premises Exchange Server 2010 mailbox has an Exchange Online archive mailbox
• 2976322 Assistant stops processing new requests when Events in Queue value exceeds 500 in Exchange Server 2010
• 2975988 S/MIME certificates with EKU Any Purpose (2.5.29.37.0) are not included in OAB in Exchange Server 2010
• 2966923 Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010

Exchange 2013 CU6:

This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2991934 Duplicate mailbox folders after migration to Exchange Server 2013
• 2988229 Hybrid Configuration wizard error "Subtask CheckPrereqs execution failed" for Exchange Server 2013
• 2986779 EMS takes a long time to execute the first command in an Exchange Server 2013 Cumulative Update 5 environment
• 2983512 RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
• 2983426 AutodiscoverSelfTestProbe fails when external URL is not set for EWS virtual directory in Exchange Server 2013
• 2983423 AutodiscoverSelfTestProbe fails when external URL is not set for ECP virtual directory in Exchange Server 2013
• 2983422 The ServerWideOffline component is set to Inactive after Exchange Server 2013 prerequisite check fails
• 2983207 "532 5.3.2" NDR when you send an email message to a hidden mailbox in an Exchange Server 2013 environment
• 2983066 Removed Default or Anonymous permission for Outlook folders cannot be restored in an Exchange Server 2013 environment
• 2982769 "Topology service cannot find the OWA service" when you perform an eDiscovery search in Exchange Server 2013
• 2982763 Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
• 2982762 OAB generation arbitration mailbox can be removed or disabled in an Exchange Server 2013 environment
• 2982760 The Enter key submits duplicate sign-in forms to Outlook Web App in an Exchange Server 2013 environment
• 2982759 You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
• 2982017 Incorrect voice mail message duration in an Exchange Server 2013 environment
• 2981835 You cannot add attachments, delete or move many email messages in bulk in Outlook Web App
• 2981466 MAPI/CDO client cannot connect to Exchange Server 2013
• 2977279 You cannot disable journaling for protected voice mail in an Exchange Server 2013 environment
• 2975599 Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
• 2975003 Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment
• 2974339 OAB generation fails if FIPS is used in an Exchange Server 2013 environment
• 2971270 Blank page after you sign in to Exchange Server 2013 EAC (formerly ECP)
• 2970040 Folder Assistant rule does not work correctly in an Exchange Server 2013 environment
• 2965689 EAS device cannot sync free/busy status if an item is created by EWS in an Exchange Server 2013 environment
• 2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
• 2961715 "Something went wrong" error in Outlook Web App may show an incorrect date

• 2958434 Users cannot access mailboxes in OWA or EAS when mailbox database is removed

Important Note:

The Exchange Team have discovered an issue with the latest Exchange 2013 Cumulative Update 6, a knowledge base article has been posted with information KB2997209, also another knowledge base article with a script to fix issue KB2997355

Also see Michael de Rooji's blog post about an alternative to the knowledge base script Blog Post

Now it's time to go test in my home lab…

Exchange 2013 & 2010 Updates

The Exchange Team have announced Exchange 2013 CU5 and Exchange 2010 SP3 RU6 is now available for download.

Exchange 2013 CU5 – KB2936880

Issues that the cumulative update resolves

This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
• 2963566 Outlook Web App accessibility improvement for UI appearance in Exchange Server 2013
• 2962439 You cannot sync contacts or tasks in Microsoft CRM client for Outlook in an Exchange Server 2013 environment
• 2962435 CRM synchronization fails if the time zone name of a meeting is not set in an Exchange Server 2013 environment
• 2962434 Slow performance in Outlook Web App when Lync is integrated with Exchange Server 2013
• 2958430 "Some or all Identity references could not be translated" error when you manage DAG in Exchange Server 2013 SP1 in a disjoint namespace domain
• 2957592 IME is disabled in Outlook Web App when you press Tab to move the focus in an email message in Exchange Server 2013
• 2942609 Exchange ActiveSync proxy does not work from Exchange Server 2013 to Exchange Server 2007
• 2941221 EWS integration for Lync works incorrectly in an Exchange Server 2013 and 2007 coexistence environment
• 2926742 Plain-text message body is cleared when writing in Outlook Web App by using Internet Explorer 8 in Exchange Server 2013
• 2926308 Sender's email address is broken after importing a PST file into an Exchange Server 2013 mailbox
• 2925559 Users always get the FBA page when they access OWA or ECP in Exchange Server 2013
• 2924519 "SyncHealth\Hub" folder is created unexpectedly after installing Cumulative Update 2 for Exchange Server 2013
• 2916113 Cannot open .tif files from email messages by using Windows-based applications in an Exchange Server 2013 environment
• 2592398 Email messages in the Sent Items folder have the same PR_INTERNET_MESSAGE_ID property in an Exchange Server 2010 environment

Exchange 2010 SP3 RU6 – KB2936871

Issues that the rollup update resolves

Update Rollup 6 for Exchange Server 2010 SP3 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2960652 Organizer name and meeting status field can be changed by EAS clients in an Exchange Server 2010 environment
• 2957762 "A folder with same name already exists" error when you rename an Outlook folder in an Exchange Server 2010 environment
• 2952799 Event ID 2084 occurs and Exchange server loses connection to the domain controllers in an Exchange Server 2010 environment
• 2934091 Event ID 1000 and 7031 when users cannot connect to mailboxes in an Exchange Server 2010 environment
• 2932402 Cannot move a mailbox after you install Exchange Server 2010 SP3 RU3 (KB2891587)
• 2931842 EWS cannot identify the attachment in an Exchange Server 2010 environment
• 2928703 Retention policy is applied unexpectedly to a folder when Outlook rule moves a copy in Exchange Server 2010
• 2927265 Get-Message cmdlet does not respect the defined write scope in Exchange Server 2010
• 2925273 Folder views are not updated when you arrange by categories in Outlook after you apply Exchange Server 2010 Service Pack 3 Update Rollup 3 or Update Rollup 4
• 2924592 Exchange RPC Client Access service freezes when you open an attached file in Outlook Online mode in Exchange Server 2010
• 2923865 Cannot connect to Exchange Server 2010 when the RPC Client Access service crashes

Exchange Server 2013 Cumulative Update 3

With the Exchange Team announcement last week that Exchange 2013 Service Pack 1 will be coming in early 2014, this is essentially CU4, you knew CU3 announcement was due at any point.
That point was Monday, this cumulative update brings a number of fixes found KB2892464.

This CU can be applied directly to RTM version of 2013, however the Cumulative Update 3 includes Exchange related updates to Active Directory schema and configuration changes.

It is also recommended to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.

To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded, remember to reset once the update has been applied.

The Exchange Team Blog – Source
Description of Cumulative Update 3 for Exchange Server 2013 – KB2892464
Cumulative Update 3 for Exchange Server 2013 (KB2892464) – Download