Exchange 2013 CU10 Released


Exchange 2013 CU10 has been released to the Microsoft download centre!  Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one.  Exchange 2013 SP1 was in effect CU4, and CU10 is the sixth post SP1 release.

Exchange 2013 CU10 Download

This is build 15.00.1130.007 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu10.exe.  Which is a great improvement over the initial CUs that all had the same file name!  Details for the release are contained in KB3078678.

Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post.   CU10 does not contain additional AD Schema changes, but does contain additional RBAC definitions. 

For those looking at deploying Exchange 2016, CU10 will be important.  Cumulative Update 10 is the minimum version of Exchange Server 2013 which will co-exist with Exchange Server 2016.

 

Updates Of Particular Note

  • KB 3087126 MS15-103: Description of the security update for Exchange Server: September 8, 2015
  • KB 3079217 Outlook Web App replies to the wrong email address when an email has more than 12 recipients in Exchange Server 2013
  • KB 3078404 Can't access a shared mailbox after you migrate from Exchange Server 2010 to Exchange Server 2013
  • KB 3069516 Mailbox size and quota information are reported incorrectly in Outlook and Outlook Web App in Exchange Server 2013
  • KB 2999011  Documents are partially indexed by Exchange search when they embed other documents in Exchange Server 2013
  • KB 2983161 Organization unit picker is missing when you create a Remote Mailbox in Exchange Admin Console in Exchange Server 2013

  

Issues Resolved

  • KB 3087126 MS15-103: Description of the security update for Exchange Server: September 8, 2015
  • KB 3094068 Permissions for a linked mailbox are added to an account in the wrong forest in an Exchange Server 2013 environment
  • KB 3093884 The link in a quarantined email shows an empty list for ActiveSync-enabled devices in Exchange Server 2013
  • KB 3088911 Inline attachments are sent as traditional when you smart forward an HTML email in an iOS device in Exchange Server 2013
  • KB 3087571 Can't edit or resend a delayed delivery message when you open the message from the Outbox folder in Exchange Server 2013
  • KB 3087293 "550 5.6.0" NDR and duplicated attachments when an encrypted email is sent in Outlook in Exchange Server 2013
  • KB 3080511  HTML forms aren't available when the DisableFilter parameter is enabled in Outlook Web App in Exchange Server 2013
  • KB 3080221  LegacyExchangeDN attribute is displayed when you use Outlook Web App to view an appointment in Exchange Server 2013
  • KB 3079217 Outlook Web App replies to the wrong email address when an email has more than 12 recipients in Exchange Server 2013
  • KB 3078966 Outlook 2011 for Mac client displays emails as they come from the same senders in Exchange Server 2013
  • KB 3078443 Incorrect results are displayed when you search for an email that has a certain attachment name in Exchange Server 2013
  • KB 3078438 Performance issues occur in an Exchange Server 2013 environment that's running BlackBerry Enterprise Server 5
  • KB 3078404 Can't access a shared mailbox after you migrate from Exchange Server 2010 to Exchange Server 2013
  • KB 3076257 EWS returns a Success response code even if a batch deletion request isn't completed in Exchange Server 2013
  • KB 3074823 No Send As audit events are logged when you use Send As permission in Exchange Server 2013
  • KB 3071776 "A problem occurred" error when you access shared folders in Exchange Server 2013 mailbox by using Outlook Web App
  • KB 3069516 Mailbox size and quota information are reported incorrectly in Outlook and Outlook Web App in Exchange Server 2013
  • KB 3061487  "FailedToGetRootFolders" error when you run an eDiscovery estimate search for archive mailboxes in Exchange Server 2013
  • KB 3058609  Wrong recipient is specified in an inbox rule that has the ForwardTo or RedirectTo option in Exchange Server 2013
  • KB 3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013
  • KB 2999011  Documents are partially indexed by Exchange search when they embed other documents in Exchange Server 2013
  • KB 2983161 Organization unit picker is missing when you create a Remote Mailbox in Exchange Admin Console in Exchange Server 2013
  • KB 3091308 Can't install cumulative updates or service packs when MachinePolicy or UserPolicy is defined in Exchange Server 2013

  

Some Items For Consideration

As with previous CUs, CU10 follows the new servicing paradigm which was previously discussed on the blog.  The CU10 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU10.  You do not need to install Cumulative Update 1 or 2 for Exchange Server 2013 when you are installing CU10.  Cumulative Updates are well, cumulative.  What else can I say…

  • After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2013. If you uninstall this cumulative update package, Exchange 2013 is removed from the server.

  • Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, mobility and management services.

  • Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter. 

  • Disable file system antivirus prior to installing.

  • Once server has been restarted, re-enable file system antivirus.

  • Note that customised configuration files are overwritten on installation.  Make sure you have any changes fully documented!

  • CU10 may contain AD Schema updates for your organisation – please test and plan accordingly!  Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version.  This will dictate if the AD Schema needs to be modified.  Check the values as noted in this post

Please enjoy the update responsibly!

What do I mean by that?  Well, you need to ensure that you are fully informed about the caveats with the CU  and are aware of all of the changes that it will make within your environment.  Additionally you will need to test the CU your lab which is representative of your production environment.

Cheers,

Rhoderick

Comments (47)

  1. Gsilva says:

    Hi, thanks for your information, but M$ is failing on patching process to update the Exchanges. 10 CU´s for probably the most important server in the lab? On year 2015 how many updates are out? 3? So this means i need to update a server 3 times in 6 months?
    Or M$ wants to all move to exchange online? On past month i patch my exchange to CU9, now, i need put the server offline again to another update. Thanks

  2. Thanks for the comment!

    I would note that all software needs maintenance, and the hardware/firmware/management software on the servers themselves is no different. Exchange releases on a predictable schedule, and has done since 2007. Windows updates also come out on a predictable schedule,
    Patch Tuesday.

    I would expect that serves are being patched and rebooted monthly.

    This is part of the OPEX that is required to run any platform/service.

    Do you have WSUS or something similar deployed to help streamline your operations?

    Cheers,
    Rhoderick

  3. turbomcp says:

    Btw, you don't have to update a server 3 times in 6 months but its highly recommended:)

  4. gsilva says:

    Hi, thanks for responses.
    Yes, we have wsus but only for workstations and less important server´s. The critical server´s are patched manually, like exchange.
    But the future is exchange online to avoid this patch processes and other task´s 😀
    Im waiting for server 2016 , exchange 2016 and system center 2016.
    Cheers

  5. Exchange 2016 says:

    Failure trying to upgrade from 2013 CU9 to CU10, with 2016 Preview installed in the environment.

    Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis COMPLETED
    Configuring Microsoft Exchange Server
    Organization Preparation FAILED
    The following error was generated when "$error.Clear();
    if ($RoleDatacenterFfoEnvironment -eq "True")
    {
    Install-CannedRbacRoles -InvocationMode $RoleInstallationMode -Domai
    nController $RoleDomainController -IsFfo
    }
    else
    {
    Install-CannedRbacRoles -InvocationMode $RoleInstallationMode -Domai
    nController $RoleDomainController
    }
    " was run: "System.Collections.Generic.KeyNotFoundException: The given k
    ey was not present in the dictionary.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ExchangeRole.StampIm
    plicitScopes()
    at Microsoft.Exchange.Management.Tasks.RoleUpgrader.PrepareRoleForUpgradeAndG
    etOldSortedEntries(ExchangeRole roleToUpgrade, Boolean isDeprecated)
    at Microsoft.Exchange.Management.Tasks.RoleUpgrader.UpdateCannedRole(Exchange
    Role existingRole, ExchangeRole cannedRole, RoleDefinition roleDefinition)
    at Microsoft.Exchange.Management.Tasks.RoleUpgrader.CreateOrUpdateRole(RoleNa
    meMapping mapping, RoleDefinition definition, List`1 enabledPermissionFeatures,
    String suffix, String mailboxPlanIndex)
    at Microsoft.Exchange.Management.Tasks.RoleUpgrader.CreateOrUpdateRole(RoleNa
    meMapping mapping, RoleDefinition definition, List`1 enabledPermissionFeatures)
    at Microsoft.Exchange.Management.Tasks.NonDeprecatedRoleUpgrader.UpdateRole(R
    oleDefinition definition)
    at Microsoft.Exchange.Management.Tasks.InstallCannedRbacRoles.UpdateRolesInOr
    g(RoleNameMappingCollection mapping, RoleDefinition[] roleDefinitions, ServicePl
    an servicePlan)
    at Microsoft.Exchange.Management.Tasks.InstallCannedRbacRoles.InternalProcess
    Record()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
    cName, Action func, Boolean terminatePipelineIfFailed)
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage tas
    kStage, Action initFunc, Action mainFunc, Action completeFunc)
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    at System.Management.Automation.CommandProcessor.ProcessRecord()".

    No extra info in the setup log. Same error when running setup.exe /prepareAD separately.
    setup.exe /prepareSchema shouldn't be needed. setup.exe /prepareDomain works fine.

    Any ideas?

  6. Exchange 2016 says:

    Some additional info from the logs...

    Setup logs
    [09-29-2015 13:23:22.0528] [2] Used domain controller XYZ to read object CN=My ReadWriteMailbox Apps,CN=Roles,CN=RBAC,CN=XYZ,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XYZ,DC=XYZ.
    [09-29-2015 13:23:22.0559] [2] [ERROR] The given key was not present in the dictionary.
    [09-29-2015 13:23:22.0559] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The given key was not present in the dictionary.

    Event viewer (MSExchange Management)
    Cmdlet failed. Cmdlet Install-CannedRbacRoles, parameters -InvocationMode "BuildToBuildUpgrade" -DomainController "XYZ".
    Cmdlet failed. Cmdlet Install-ExchangeOrganization, parameters -Industry "NotSpecified" -PrepareDomain "True" -DomainController "XYZ" -ActiveDirectorySplitPermissions $null -PrepareOrganization "True" -OrganizationName "XYZ".

  7. That's a known issue with the E16 preview. The minimum CU was later announced to be Exchange 2013 CU10 for Exchange 2016 coexistence.

    Cheers,
    Rhoderick

  8. Exchange 2016 says:

    Rhoderick,
    Thank you for the reply.

    The 2016 preview announcement states that 2013 CU9 is the minimum
    http://blogs.technet.com/b/exchange/archive/2015/07/22/announcing-exchange-server-2016-preview.aspx

    Is there a workaround for upgrading to CU10?
    Any serious known issues running 2013 CU9 with 2016?

  9. No workaround at this time that I've seen. The Exchange 2016 preview is for lab purposes only, so the issues will be addressed with a later build of 2016.

    While your lab should be functional with CU9 and Exchange 2016 preview, the support requirements did change. It will be Exchange 2013 CU10 at a minimum going forward.

    Cheers,
    Rhoderick

  10. Exchange 2016 says:

    I'll give it another try after upgrading from 2016 Preview to RTM (released yesterday).

  11. Interesting that you said yesterday --> due to the time zone differences 🙂

    Cheers,
    Rhoderick

  12. Exch13_CU9 says:

    Setup on Admin-Workstations (Win7 and Win8.1) not working, Exchange Tools / Powershell 2013 CU9 installed, installing from local harddisk

    Event 4999:
    Der Watson-Bericht steht kurz vor dem Versenden für die Prozess-ID: 1308, mit den Parametern: E12IIS, c-RTL-AMD64, 15.00.1130.007, ExSetupUI, ExSetupUI, M.E.S.E.SetupWizard.PopulateWizard, M.E.S.ExSetupUI.AssemblyLoadFileNotFoundException, a60d, 15.00.1130.007.
    ErrorReportingEnabled: False

    Event 1026
    Anwendung: ExSetupUI.exe
    Frameworkversion: v4.0.30319
    Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.
    Ausnahmeinformationen: Microsoft.Exchange.Setup.ExSetupUI.AssemblyLoadFileNotFoundException
    Stapel:
    bei Microsoft.Exchange.Setup.ExSetupUI.SetupWizard.ThrowAssemblyLoadFileNotFoundException(Microsoft.Exchange.Setup.CommonBase.SetupBase, System.String)
    bei Microsoft.Exchange.Setup.ExSetupUI.SetupWizard.PopulateWizard(System.Collections.Generic.IList`1, Microsoft.Exchange.Setup.CommonBase.SetupBase)
    bei Microsoft.Exchange.Setup.ExSetupUI.SetupWizard..ctor(Microsoft.Exchange.Setup.CommonBase.SetupBase, Boolean, Boolean)
    bei Microsoft.Exchange.Setup.ExSetupUI.ExSetupUI.Run()
    bei Microsoft.Exchange.Setup.CommonBase.SetupBase.MainCore[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String[], Microsoft.Exchange.Management.Deployment.ISetupLogger)
    bei Microsoft.Exchange.Setup.ExSetupUI.ExSetupUI.Main(System.String[])

    Event 1000:
    Name der fehlerhaften Anwendung: ExSetupUI.exe, Version: 15.0.1130.7, Zeitstempel: 0x55dfc493
    Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.3.9600.18007, Zeitstempel: 0x55c4c341
    Ausnahmecode: 0xe0434352
    Fehleroffset: 0x000000000000871c
    ID des fehlerhaften Prozesses: 0x51c
    Startzeit der fehlerhaften Anwendung: 0x01d0ff6ef92edd26
    Pfad der fehlerhaften Anwendung: C:WINDOWSTempExchangeSetupExSetupUI.exe
    Pfad des fehlerhaften Moduls: C:WINDOWSsystem32KERNELBASE.dll
    Berichtskennung: 379ff62c-6b62-11e5-8295-0050b67c5c64
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

    Any suggestions what to do?

  13. Oh crap, I ran into that error too: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

    I'll try to find a workaround, I don't want to wipe this lab. If anyone found a way to circumvent this error I really like to know.

  14. Hannel says:

    I am also running into error below when i try to upgrade to Exchange 2013 CU10 on my lab environment.

    [ERROR] The given key was not present in the dictionary.

    Following the information above this is because i have Exchange 2016 Preview in the environment, right?

    If i uninstall Exchange 2016 preview would i be able to upgrade to Exchange 2013 CU10 or just wait for a compatible update?

  15. Exch13_CU9 says:

    There seems to be an error in the GUI....
    Running "Setup /m:upgrade ..." from an elevated command prompt upgrades all admin-Workstations (so, no GUI ;-))
    without any problem

  16. Hannel Hazeley says:

    I actually ran it from the command line.

    I am going to try upgrading the Exchange 2016 preview to RTM then try Upgrading to the Exchange 2013 servers CU10.

  17. Hey Rhoderick, I removed the 2016 Preview from my lab earlier but this error message blocks me from adding a 2016 RTM server in the 2013 environment. Do you know if adding 2016 Preview again and then to a build-to-build upgrade to 2016 RTM would fix this?

  18. Hannel Hazeley says:

    Upgrading Exchange 2016 will not work either, as it seems the requirement for RTM to coexist with 2013 is CU10. I tried it yesterday and got error below.

    All Exchange 2013 servers in the organization must have Exchange 2013 Cumulative Update 10 or later installed. The following servers don't meet this requirement: 001-EV1CAS2-001, 001-EV1MBX2-001, 001-EV1MMR2-001.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.exch.setupreadiness.E16E15CoexistenceMinVersionRequirement.aspx

    see link screenshot.

    https://app.box.com/s/6h47coo6gy2jr6sg3xgw0hwewtll6ovf

  19. Not something that I tried folks - I already paved my preview labs and built fresh for RTM as I never want any legacy bits in them.

    Cheers,
    Rhoderick

  20. Vladislav Dimitrov says:

    Hello, does anyone have an idea what are the changes in the RBAC roles?

  21. Thomas Pedersen says:

    You need to change the “msExchRoleType=132” to 115 in the “CN=My ReadWriteMailbox Apps,CN=Roles,CN=RBAC,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com” from the configuration container in adsiedit.
    Typically, this is from an Exchange 2016 preview installation before Exchange 2013 CU 10 was released.
    https://dk.linkedin.com/pub/thomas-pedersen/a/4b4/814

  22. Tai says:

    When Exchange 2013 CU7 have public folders, Windows XP will have problems with the use of outlook 2007/2010
    Did Cu10 have to fix this problem?

  23. Exchange 2016 says:

    This error (during Organization Preparation) is blocking the upgrade from 2013 CU9 to CU10:
    "[ERROR] The given key was not present in the dictionary."

    And 2016 Preview can't be upgraded to RTM because now 2013 CU10 is a pre-req:
    "All Exchange 2013 servers in the organization must have Exchange 2013 Cumulative Update 10 or later installed."
    Earlier CU9 was the minimum.

    So it's Catch-22 situation...

    Will this be fixed?

  24. Tai - Windows XP Pro has exited out of Mainstream support back in April 2014. Your clients should be upgrading at this point.

    Cheers,
    Rhoderick

  25. Have not seen anything further on the 2016 Preview issue.

    Cheers,
    Rhoderick

  26. Sebastian Loscher says:

    After removing the RBAC role "My ReadWriteMailbox Apps" via ADSIEDIT I managed to install CU10, see

    http://port25guy.com/2015/11/09/cannot-update-exchange-2013-after-installing-exchange-2016-beta/ for further information.

  27. dirk says:

    I have run CU10 over a well running CU9. After that my certificate using mobile clients are not able to connect anymore, outlook and owa are well. Mobile users get a password popup on their devices.
    I have checked exchange certificates but cannot see something wrong.
    Are there known issues about cu10 and active sync?

  28. Sergey says:

    Am I the first one to notice the command line shows "...cumulative update 8" when running "Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms" ?

    1. frank says:

      Its using the wrong install dir cached..

  29. CU 10 Update takes forever to install says:

    We have a 6 server Exchange farm plus 2 Edge servers. The Edge server installation went smooth. However attempts to update our two standalone Mailbox servers as well as members of our DAG took roughly 2-4 hours per server.. I opened a support ticket to
    help troubleshoot. The update would stall on each component config.

    1. Please see the .NET issue noted in this post:
      https://blogs.technet.microsoft.com/rmilne/2016/03/15/exchange-2013-cu12-released/

      That has been slowing down some installs by several hours.

      Cheers,
      Rhoderick

  30. Benedictus says:

    CU 10 turns SSLv3 back on?

    [1] Executing:
    $keyPath = $keyPathRoot + "SSL 3.0Server";
    if (!(Test-Path $keyPath))
    {
    New-Item -path $keyPathRoot"SSL 3.0" -ItemType key -Name "Server" -Force;
    }
    Set-ItemProperty -path $keyPath -name "Enabled" -value 0x1 -Type DWORD -Force;

  31. Benedictus says:

    Actually, looks like all Cumulative Updates do it. Not just CU10.

  32. koorosh says:

    Why not working imap v4 after installed update cu10 on exchange 2013 sp1

  33. Manar says:

    Can we upgrade from CU7 to CU10 directly?

  34. Tlachy says:

    Can we upgrade from 2013 SP1 ( 15.00.0847.032 ) to CU10 directly?

  35. Benedictus - thanks for the feedback. Let me follow up on this.

    Koorosh - what auth scheme are you using for the client?

    Cheers,
    Rhoderick

  36. From the post:

    As with previous CUs, CU10 follows the new servicing paradigm which was previously discussed on the blog. The CU10 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU10. You do not need to install
    Cumulative Update 1 or 2 for Exchange Server 2013 when you are installing CU10. Cumulative Updates are well, cumulative. What else can I say.

    yes you can use CU10 to do a fresh install from scratch, or upgrade an existing install.

    Cheers,
    Rhoderick

  37. Ken says:

    Hi Rhoderick,

    would you please confirm CU10 installation package is still right? https://www.microsoft.com/en-us/download/details.aspx?id=49044

    when I was trying to install, it is showing CU9 and Configuration--objectVersion=15965

    thanks

    Ken

      1. Ken says:

        Hi Rhoderick,

        🙂 it turns out I am just getting #6 mistake. "setup" vs. ".\setup".

        Much appreciated for your help.

        Ken

        1. Good deal - there is a reason I have that post there 🙂

          Cheers,
          Rhoderick

  38. Ken says:

    Hi Rhoderick,

    I am on CU9 currently. When I upgrade to CU10, my thought is NO schema and AD Domain change. But, there is an AD change.
    So, what I have to do is to run
    “Setup /PrepareAD /IAcceptExchangeServerLicenseTerms”
    Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version. This will dictate if the AD Schema needs to be modified. Check the values as noted in this post. CU10 does not contain additional AD Schema changes, but does contain additional RBAC definitions.
    Would you please confirm my thought?

    Cheers

    Ken

    1. That's correct - CU10 does have additional RBAC changes.

      If you manually run each of the AD preparation commands, then you are golden. As mentioned in the CU mistakes blog post, use the full syntax not the shortcut.....

      Exchange actually does this behind the scenes every time setup is run. It checks the current environment, and if there are changes to be made it will make them (assuming the account executing setup has the requisite permissions).

      Cheers,
      Rhoderick

      1. Ken says:

        Golden answer. 🙂 Thanks Rhoderick.

        In my company, My account was restricted to "Organization Management" group only.

        So, I will ask Windows guy who has the "Enterprise Admin" power to help me run "PrepareAD" command.

        Cheers

        Ken

Skip to main content