Exchange 2013 CU9 Released


Exchange 2013 CU9 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 CU9 is the fifth post SP1 release.

Exchange 2013 CU9 Download

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

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.

Updates Of Particular Note

 

Issues Resolved

 

Some Items For Consideration

As with previous CUs, CU9 follows the new servicing paradigm which was previously discussed on the blog.  The CU9 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU9.  You do not need to install Cumulative Update 1 or 2 for Exchange Server 2013 when you are installing CU9.  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!
  • CU9 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 (13)

  1. MarcoR84 says:

    As CU9 is released now, it seem there is no new paramter for the set-Mailbox command as described here:

    http://blogs.technet.com/b/exchange/archive/2015/03/03/want-more-control-over-sent-items-when-using-shared-mailboxes.aspx

  2. Marco – Please check back tomorrow – have a new post coming to address this.

    Cheers,
    Rhoderick

  3. MarcoR84 says:

    Thanks.
    Works in my test environment.

  4. Ken says:

    Hi Rhoderick,

    The link "KB3049849" doesn’t work at this point of time.

    "Try searching for what you need

    This page doesn’t exist."

    Regards

    Ken

  5. Thanks Ken!

    Updated to make the link location agnostic.

    Cheers,
    Rhoderick

  6. TheN4cer says:

    There seems to be an issue with this update. I have a receive connector enabled for Integrated Windows Authentication which Xerox printers use to send emails, and it broke after this CU. I had to remove Integrated Windows as an authentication method and
    use Basic only. The issue is similar to this post:

    https://social.technet.microsoft.com/Forums/office/en-US/f2dc6351-b43f-40fc-b4a4-779433fbd8db/after-upgrade-to-cu9-is-impossible-to-allow-authenticated-email-from-fsrm-and-wsus?forum=exchangesvrsecuremessaging

    And in the protocol logging for the receive connector I get these type of errors for some accounts, but not all.

    Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user

    This was working fine before CU9.

  7. TheN4cer says:

    There seems to be an issue with this update. I have a receive connector enabled for Integrated Windows Authentication which Xerox printers use to send emails, and it broke after this CU. I had to remove Integrated Windows as an authentication method and
    use Basic only. The issue is similar to this post:

    https://social.technet.microsoft.com/Forums/office/en-US/f2dc6351-b43f-40fc-b4a4-779433fbd8db/after-upgrade-to-cu9-is-impossible-to-allow-authenticated-email-from-fsrm-and-wsus?forum=exchangesvrsecuremessaging

    And in the protocol logging for the receive connector I get these type of errors for some accounts, but not all.

    Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user

    This was working fine before CU9.

  8. Anthony I/. says:

    Great post. Thanks for taking the time to write it.

    Quick question: When CU IU6 was released, MS support informed me that CU IU6 needed be removed before the install of CU7 (At that time). Does this same apply if jumping from CU IU6 to CU9?

  9. happy diwali greetings says:

    Nice article thanks for sharing this useful information.
     

  10. Stefan says:

    Hi, we fixed the "535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user" error by assigning a UPN to the affected User Accounts.

    1. Tyler Berens says:

      Can you explain how you did this?
      Thanks!

Skip to main content