Released: September 2015 Quarterly Exchange Updates


The Exchange team is announcing today the availability of our latest quarterly update for Exchange Server 2013 and Exchange Server 2010 Service Pack 3 Update Rollup 11.

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

Cumulative Update 10 does not include updates to Active Directory Schema, but does include additional RBAC definitions requiring PrepareAD to be executed prior to upgrading any servers to CU10. PrepareAD will run automatically during the first server upgrade if Setup detects this is required and the logged on user has sufficient permission.

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

Also being released today is, Exchange Server 2010 Service Pack 3 Update Rollup 11 (KB3078674). This release provides an important fix for an Information Store crash when customers are upgrading their Lync server infrastructure to Skype for Business. Exchange Server 2010 is in extended support and will receive security and time zone fixes on-demand on a go-forward basis.

The updates released today are important pre-requisites for customers with existing Exchange deployments who will deploy Exchange Server 2016. Cumulative Update 10 is the minimum version of Exchange Server 2013 which will co-exist with Exchange Server 2016. Exchange Server 2010 Service Pack 3 Update Rollup 11, is the minimum version of Exchange Server 2010 which will be supported in a coexistence deployment with Exchange Server 2016. No earlier versions of Exchange will be supported co-existing with Exchange Server 2016. Exchange Server 2016 is anticipated to be released later this year. Customers who plan to deploy this new release of Exchange into their environment should be aware of these important prerequisites.

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

Note: Documentation may not be fully available at the time this post was published.

The Exchange Team

Comments (12)
  1. Kotov Dmitry says:

    KB3078678 – cannot open I, getting an error that KB does not exists?

  2. Korbyn says:

    Are there anymore details on this Exchange 2010 store crash when upgrading Lync to Skype? Will seem like a odd prerequisite going forward, but obviously an issue which I do not feel like encountering…

  3. @Korbyn – The crash occurs when the Lync Contacts folder is renamed to Skype for Business Contacts as part of a migration to Skype for Business. It is not a 100% failure, but occurs frequently enough to warrant a fix.

  4. Is a reboot required after installation? Installing CU from Command Prompt does not mention this.

    I think GUI setup says to reboot…

  5. sime3000 says:

    Does Microsoft plan on ever releasing another Help file for Exchange 2013 ? The last one is a year and several CU’s old (
    http://www.microsoft.com/en-us/download/details.aspx?id=35395 )

  6. In our lab environment, update from CU9 to CU10 was only successful on the mailbox role. Updating the cas role leads to a setup crash :(

    Does anybody know a workaround?

    Log Name: Application
    Source: MSExchange Common
    Date: 18.09.2015 14:32:08
    Event ID: 4999
    Task Category: General
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: CAS2.xlabor.local
    Description:
    Watson report about to be sent for process id: 5736, with parameters: 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: True

  7. An unattended setup seems to be a workaround :)
    PS C:cu10> .setup.exe /m:Upgrade /IAcceptExchangeServerLicenseTerms

  8. Barebodkin says:

    Same as GeorgeFromGermany, the GUI setup would not run on CAS servers, on Win 2012R2 hyper-v vm’s. Command line setup worked ok on the CAS servers. GUI setup worked on mailbox servers on Win2012 physical machines but required two hotfixes which had never
    been needed before CU10. Neither GUI setup nor command line setup are working for me on Windows 10 management tools installations.

  9. sime3000 says:

    When installing the Exchange 2013 admin tools using CU10 on a Windows 7 SP1 workstation, (
    https://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx ), the installer halts with the following error:

    Error:
    Exchange Server 2013 can’t be installed on a server that has an Exchange 2007 or Exchange 2010 server role installed.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Exchange2013AnyOnExchange2007Server.aspx

    The Windows 7 SP1 workstation has the Exchange 2010 and Exchange 2007 admin tools installed and is obviously not running the "Exchange 2007 or Exchange 2010 server role".

    Why does this occur ?

  10. TomGM says:

    Hi guys!

    I’ve upgraded 4 freshly installed Exchange 2013 CU9 Servers to CU10 last week. The web.config files all have the entry

    meaning Legacy Logoff is enabled by default. So it is the complete opposite of what is described in an earlier post that states that LegacyLogOff is disabled by default since CU9:

    (http://blogs.technet.com/b/exchange/archive/2015/01/12/owa-forms-based-auth-logoff-changes-in-exchange-2013-cumulative-update-8-and-good-news-for-tmg-customers.aspx).

    Since I never touched these settings I’m just wondering why.

    Kind regards
    Tom

  11. Dude5414 says:

    CU10 does not fix the "KB 3036952 Mailbox quota warning messages are not sent out after you migrate from Exchange Server 2010 to Exchange Server 2013". This was supposed to be fixed in CU8. We upgraded from CU7 to CU10 thinking the fix will be included.
    We just ran the workaround from KB3036952.

Comments are closed.