Released: June 2015 Exchange Cumulative Update and Update Rollups


The Exchange team is announcing today the availability of our latest quarterly updates for Exchange Server 2013 as well as updates for Exchange Server 2010 Service Pack 3 and Exchange Server 2007 Service Pack 3.

Cumulative Update 9 for Exchange Server 2013 and UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 9 contains the latest set of fixes and builds upon Exchange Server 2013 Cumulative Update 8. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved can be found in Knowledge Base Article KB3049849. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 9 today. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 9 directly.

For the latest information and product announcements please read What’s New in Exchange Server 2013, Release Notes and product documentation available on TechNet.

Cumulative Update 9 may include Exchange related updates to the Active Directory schema and Exchange configuration when compared with the version of Exchange 2013 you have currently deployed. Microsoft recommends all customers test the deployment of a cumulative update in their lab environment to determine the proper installation process for your production environment. For information on extending the schema and configuring Active Directory, please review the appropriate TechNet documentation.

Also, 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. If the policies are NOT set to Unrestricted you should use the resolution steps in KB981474 to adjust the settings.

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., CU9) or the prior (e.g., CU8) Cumulative Update release.

Also being released today are, Exchange Server 2010 Service Pack 3 Update Rollup 10 (KB3049853) and Exchange Server 2007 Service Pack 3 Update Rollup 17 (KB3056710). These releases provide minor improvements and fixes for customer reported issues. Update Rollup 10 is the last scheduled release for Exchange Server 2010. Both Exchange Server 2010 and Exchange Server 2007 are in extended support and will receive security and time zone fixes on-demand on a go-forward basis.

Note: If you do not see the new CMDlet parameters available in Exchange 2013 CU9, please perform /PrepareAD manually.

The Exchange Team

Comments (17)
  1. Thanks team!

    "Cumulative Update 9 may include Exchange related updates to the Active Directory schema and Exchange configuration when compared with the version of Exchange 2013 you have currently deployed."

    So does CU9 contain schema updates when you upgrade from CU8 or was CU7 the latest version with a schema update?

  2. Ofir Doron says:

    schema number stays the same as in CU7 and CU8. 15312.

  3. Hopefully the storing of sent messages in shared mailboxes "Sent Items" folder has been implemented :-)

  4. Jan Aarts says:

    Thomas I’m hoping for the same

  5. dirkverhagen123 says:

    @Nino, to confirm, the send items config only works for shared mailboxes right? and not user mailboxes right?

  6. Bakerm00 says:

    Is there a chance that we can see the ability to assign publicfolder databases for load balancing by policy instead of random global selection?

  7. I installed Exchange 2013 CU9 in my lab env (2x Exchange 2013 multi-role DAG members; upgrade from CU7)

    Remarks:

    * Reboot required after CU9 installation?
    Exchange 2013 CU9 Setup Wizard mentions to restart the computer after Exchange 2013 has completed
    Exchange 2013 CU9 Unattended Setup does NOT mention to restart the computer after Exchange 2013 has completed

    Unattended setup (https://technet.microsoft.com/en-us/library/aa997281(v=exchg.150).aspx): Restart the computer after Exchange 2013 has completed.

    * KB3049849 refers to KB3050877: Emails that are sent as a secondary mailbox are not saved in the delegate’s Sent Items folder in Exchange Server 2013

    KB3050877:
    This issue occurs even if you configure the MailboxSentItemsConfiguration settings for a secondary mailbox. When you send email messages as or on behalf of the mailbox, the messages are only saved in your Sent Items folder in a Microsoft Exchange Server 2013
    environment.

    MailboxSentItemsConfiguration links to Set-MailboxSentItemsConfiguration (https://technet.microsoft.com/en-us/library/jj884078(v=exchg.141).aspx)

    However, Set-MailboxSentItemsConfiguration is only available with Exchange 2010 SP3 (and some specific UR).

    Sent items configuration has been implemented with Exchange 2013 CU9 as described at

    http://blogs.technet.com/b/exchange/archive/2015/03/03/want-more-control-over-sent-items-when-using-shared-mailboxes.aspx with set-mailbox -MessageCopyForSentAsEnabled & -MessageCopySendOnBehalfAsEnabled parameters.

    * Testing shared mailbox with parameter -MessageCopyForSentAsEnabled

    Configured shared mailbox Info: Set-Mailbox info -MessageCopyForSentAsEnabled $True

    When testing sent as functionality, a message copy is not saved in the Sent Items folder of Info but appears in Info Inbox folder:

    The attached message was sent by a member of this shared mailbox. Usually, it would appear in Sent Items, but your service is currently being upgraded. Things will be back to normal after the upgrade.

    This seems to be an Office 365 notice? See als
    https://community.office365.com/en-us/f/158/t/318175

  8. jackal2001 says:

    Per the note above:
    "Update Rollup 10 is the last scheduled release for Exchange Server 2010."
    So I thought the MS documentation for upgrading to Exchange 2016 was that you needed 2010 SP3 RU11?

  9. @jackal2001 – Sorry for the confusion. We are trying to convey that RU10 is the last release which satisfies our mainstream support requirements for Exchange Server 2010. We will continue to ship security and time zone updates for Exchange Server 2010
    on an on-demand basis during extended support phase. As part of our product planning, we expect to ship Time Zone Updates later this year which will be delivered in RU11 as part of our on-demand servicing. We expect RU11 to be the most current update when
    Exchange Server 2016 releases and anticipate that this will be the co-existence supported version. As Exchange Server 2016 has not yet released, this requirement is subject to change.

  10. @ Brent
    So Exchange 2010 users who want to migrate to Exchange 2016 will need a special "extended support"-contract to get that CU11?

  11. [Chris] says:

    Any information about some issues with Outlook 2007 and/or Outlook 2011 for Mac with CU9 ?
    Some of our clients cannot connect to our CAS servers anymore (a few because those are old clients and the one with Outlook 2011 should be an old version as well).

    But is there any update about this wiki since CU9 :
    http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx#Exchange_Server_TwentyThirteen

    For Exchange 2013 :
    Outlook 2007 SP3 with November 2012 Cumulative Update (it seems that this old version does not work anymore)
    Outlook for Mac 2011 (but with which update ?)

  12. ablanken says:

    Thanks guys – we’ve had no issues with the latest 2013 update.

    There is one very minor annoyance that has been around for a while: When the MyTextMessaging user role assignment setting is unchecked, users get a 500 error when attempting to open the Voicemail tab under their OWA settings

  13. I have upgraded Exchange 2013 CU7 to CU9 at a customer without setup /PrepareSchema & /PrepareAD. No problems :-)

    However, the new cmdlet parameters were not available after upgrade. It seems /PrepareAD is still required.

  14. I have D:MonitoringDiagnosticLogs after installing Exchange 2013 CU9 binaries on D:Program FilesMicrosoftExchange ServerV15

    See also:
    http://jaapwesselius.com/2014/01/30/strange-directories-in-exchange-2013-on-d-drive/

Comments are closed.