Released: December 2015 Quarterly Exchange Updates

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

Cumulative Update 11 for Exchange Server 2013 and UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 11 contains the latest set of fixes and builds upon Exchange Server 2013 Cumulative Update 10. 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 KB3099522. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 11. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 11 directly.

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

We are also releasing Update Rollup 12 for Exchange Server 2010 Service Pack 3 (KB3096066). The Exchange Server 2010 update includes a DST update as well as a collection of important fixes. Update Rollup 18 for Exchange Server 2007 Service Pack 3 (KB3078672) is also being released. Update Rollup 18 is primarily a DST fix with an additional opportunistic fix.

We would like to call attention to two particularly important changes included in these updates:

  • Cumulative Update 11 and Update Rollup 12 each contain a time zone calculation fix to resolve the issue reported in KB3048372 – Exchange Calendar Items are shifted incorrectly when some Windows DST updates are applied. Customers in impacted time zones are encouraged to deploy these updates to address the issue identified after the release of the OS time zone changes in KB3039024.
  • Cumulative Update 11 also includes a change in behavior when deploying/administering Exchange Server 2013 in a co-existent manner with Exchange Server 2010 or 2016. These changes are outlined in the following blog article: Exchange Management Shell and Mailbox Anchoring.

For our customers running Exchange Server 2016, Exchange Server 2016 Cumulative Update 1 will be added to our next set of quarterly updates for Exchange Server.

Microsoft recommends all customers test the deployment of any 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., CU11) or the prior (e.g., CU10) Cumulative Update release.

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 (13)
  1. "Cumulative Update 11 does not include updates to Active Directory Schema, but may add additional RBAC definitions to your existing configuration. PrepareAD should be executed prior to upgrading any servers to CU11."

    I have already installed Exchange 2016 Mailbox server, AD Schema and domain have been prepared for Exchange 2016 (objectVersion on Configuration Naming context = 16210).

    TechNet: Exchange 2013 CU11 objectVersion on Configuration Naming context = 16130.

    Exchange 2013 CU11 Prepare AD: setup /PrepareAD /IAcceptExchangeServerLicenseTerms

    Setup encountered a problem while validating the state of Active Directory: The Active Directory organization configuration version (16210) is higher than Setup’s version(16130). Therefore, PrepareAD can’t be executed. See the Exchange setup log for more information
    on this error. For more information, visit:

    Can this be safely ignored because of Exchange 2013 – 2016 coexistence?

  2. sime3000 says:

    Does Microsoft plan on ever releasing another Help file for Exchange 2013 ? The last one is more than a year and several CU’s old ( )

  3. ansari786 says:

    i want to install patched on exchange server 2013 .please tell me process and precation

  4. Jesse Reppin says:


    First prepare your AD with : "\pathtosetup" /PrepareAD /IAcceptExchangeServerLicenseTerms
    Than "\pathtosetup" /m:upgrade /IAcceptExchangeServerLicenseTerm

  5. Phillip Lyle says:

    If Exchange 2016 CU1 is released with the next set of quarterly patches, then that's nearly 6 months since RTM without an update…quite a stretch.

  6. Chris Clark says:

    I am installing the first Exchange 2013 CU11 server into an Exchange 2010 environment. The install just finishes and disappears from the screen. No indication that the install is done or if a reboot is needed. Is this by design?

  7. alan.debaene says:

    @Chris Clark

    The install should not have just closed the GUI. If I were you, I would check the Setup Logs. They should be located here. "C:ExchangeSetupLogsExchangeSetup.log"

    You can look here to see if there was a successful install. I had this problem when upgrading an older CU install to CU10. The GUI kept crashing but it was actually a known problem.
    I got around this by following the above instructions and performing a silent install from command prompt.
    "\pathtosetup" /m:upgrade /IAcceptExchangeServerLicenseTerm

    I only perform this install now. I realize this command is designed for an upgrade, but if you search you can find the silent command.

  8. RobK-SSHA says:

    What about Exchange 2013 and Exchange 2016 ‘verbosity’. When running on Windows2012R2 the -verbose switch does nothing. This has been an on going since windows 2012r2 came out. Is there an appetite to correct this?

  9. Satyajit321 says:

    Hi RobK-SSHA ,

    This should give you the verbosity you are looking for, no more waiting for the switch to work.

    Open a PS Session on the server:

    Get-Content "C:ExchangeSetupLogsExchangeSetup.log" -Tail 1 -Wait

    Use Ctrl+C to break stop tailing.

  10. RobK-SSHA says:

    what i meant was that when running Exchange 2013 or Exchange 2016 on windows 2012r2 server exchange powershell commands do not honor -verbose switch at all. a simple command like -get-mailbox -verbose does not produce extended yellow verbose details. i
    was hoping maybe this time aorund with the new CU thing will work better

  11. S. Rodriguez says:


    It seems that for Exchange 2010 SP3, the KB3106421 fix in Rollup 12 actually broke some redirections for us. I’m seeing a few 403 errors on link redirections (/owa/redir.aspx) since applying the patch. Can be reproduced in any browser in premium mode (IE11
    / FF 43.0.4) on specific links (which are otherwise perfectly reachable).

  12. S. Rodriguez says:

    Edit : it results in an error 403 if clicked from OWA, but if the link is clicked from Outlook 2013 it results in an error 400

  13. S. Rodriguez says:

    2nd addition : it seems that the faulty links actually work and keep working for the 1st person to open them in the organization, but subsequent access requests from different accounts will result in the 400/403 errors

Comments are closed.