Exchange 2013 CU7 Released


Exchange 2013 CU7 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 CU7 is the third post SP1 release.  CU7 contains AD DS schema changes so please test and plan accordingly!

One aspect to note is that CU7 does contain the security fix for the issues described in security bulletin MS14-075.  To address these security issues in pre CU7 builds of Exchange 2013, there are separate updates available.  While not directly applicable to CU7, it is worth noting should you wish to implement the security fix prior to upgrading to CU7.

 

Update 10-12-2014: Corrected CU7 security update wording.

 

CU7 provides support for Public Folder Hierarchies in Exchange Server 2013 which contain 250,000 public folders.  Yay!!!!  CU7 also resolves backup and restore issues.  The Exchange product group recommend upgrading to Exchange 2013 CU7 and then taking a full backup.

Please take the time to review these additional posts:

 

For those co-existing with Exchange 2007 there were some issues with CU6, that should all be resolved in CU7.  For example if you are deploying into a mixed environment with Exchange 2007, you need to review KB2997209 Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007.  Customer with Exchange 2007 and 2013 also had to review KB 2997847 You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6.  There were some issues with the post CU6 IU that was released to correct these issues as it did not always copy all the OWA files.   CU6 also had an issue which affected Hybrid mailboxes.

Exchange 2013 CU7 Download

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

 

Updates Of Particular Note

  • CU7 addresses the security issues described in MS14-065.  To address these issues in pre CU7 builds of Exchange 2013 there are separate updates available for:

 

  • 2999031 A cross-forest mailbox move from Exchange Server 2007 to Exchange Server 2013 finishes with CompletedWithWarnings status
  • 3008438 User who is trying to Log on to Exchange Admin Console is logged in to OWA instead

  • 3006672 Move request fails if the IsExcludedFromProvisioning option is true in Exchange Server 2013

  • 3005391 Exchange Server 2013 Cumulative Update 5 breaks free/busy lookup from Exchange Online to Exchange Server 2007

  • 3001217 TLS 1.0 is hardcoded for SMTP traffic encryption in Exchange Server 2013

  • 3003580 Event ID 4999 and 4401 when the Microsoft Exchange Replication service crashes in Exchange Server 2013

  • 3000944 Subfolders under the Deleted Items folder are not visible in Outlook in an Exchange Server 2013 environment
  • 2997847 You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6
  • 2997355 Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6
  • 2997209 Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007

 

Issues Resolved

 

  • 3004235 Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

  • 3012655 New-MailboxImportRequest causes unreadable characters when you import an ANSI format .pst file of Russian language

  • 3012652 CalendarProcessing cmdlet does not generate delegate permissions to universal security groups in Exchange Server 2013

  • 3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013

  • 3009612 Outlook Web App shows organization details on the contact card beyond the scope of user ABP in Exchange Server 2013

  • 3009291 Shared mailbox cannot be opened in Outlook in an Exchange Server 2013 environment that has multiple domains

  • 3008453 Cannot edit or delete forms from the organizational forms library in Exchange Server 2013

  • 3008438 User who is trying to Log on to Exchange Admin Console is logged in to OWA instead

  • 3006672 Move request fails if the IsExcludedFromProvisioning option is true in Exchange Server 2013

  • 3005391 Exchange Server 2013 Cumulative Update 5 breaks free/busy lookup from Exchange Online to Exchange Server 2007

  • 3003986 RejectMessageReasonText in transport rule appears in the user section of a DSN in Exchange Server 2013

  • 3001217 TLS 1.0 is hardcoded for SMTP traffic encryption in Exchange Server 2013

  • 3001037 Distribution group cannot send email messages to a mail enabled public folder in an Exchange Server 2013 environment

  • 2999031 A cross-forest mailbox move from Exchange Server 2007 to Exchange Server 2013 finishes with CompletedWithWarnings status

  • 2998144 New-MoveRequest cmdlet with RemoteLegacy parameter cannot perform a cross-forest mailbox move

  • 2988553 Add-ADPermission and Remove-ADPermission can be run outside the management scope in Exchange Server 2013

  • 2981538 Exchange Control Panel crashes when you proxy from Exchange 2013 to Exchange 2010

  • 3014051 Cannot migrate mailboxes in a multiple domains environment in Exchange Server 2013

  • 3012986 ContentIndexRetryQueueSize value for a passive node never drops to zero in Exchange Server 2013 Cumulative Update 6

  • 3004011 Sound alerts do not work in Outlook Web App when new email or calendar notification is received in Exchange Server 2013

  • 3003580 Event ID 4999 and 4401 when the Microsoft Exchange Replication service crashes in Exchange Server 2013

  • 3003518 "550 5.7.1" NDR when you send messages to external recipients in an Exchange Server 2013 hybrid environment

  • 3003068 Cannot see online archive mailbox after you upgrade to Exchange Server 2013 Cumulative Update 6

  • 3000944 Subfolders under the Deleted Items folder are not visible in Outlook in an Exchange Server 2013 environment

  • 2997847 You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6

  • 2997355 Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6

  • 2997209 Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007

  • 2995263 OAB cannot be rebuilt if the .flt file is larger than two GB in Exchange Server 2013

  • 2994216 PublicFolderMoveRequest deletes all read or unread state in target mailbox for each user in Exchange Server 2013

  • 2993871 Resource Booking Assistant crashes after you upgrade to Exchange Server 2013 Cumulative Update 5

  • 2983216 Category setting on an item in Outlook jumps the selection to the top of the list in an Exchange Server 2013 environment

  • 2931223 MAPI virtual directory is missing from Default Web Site node

 

Some Items For Consideration

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

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

CU7 contains AD Schema updates – please test and plan accordingly!

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 (28)

  1. anonymouscommenter says:

    Has anyone tested this in coexistence with 2007 yet? We are in the middle of a 2007-2013 migration but cu6 databases fail over so frequently that it has got to the point where we can’t move any mailboxes in or out of 2013 databases as they failover before
    the move has completed and users are starting to complain about the disconnections in outlook. So we might have to bit the bullet and install. We tried the interim update from Microsoft but had loads of missing files in OWA so reverted back to cu6.

  2. Hi David, were you not able to copy the files over after installing the IU to get OWA working again?

    I’ll be updating my labs with this build in the next couple of days, and I’d also suggest monitoring Twitter and the TechNet forums.

    Cheers,
    Rhoderick

  3. anonymouscommenter says:

    "The Exchange product group recommend upgrading to Exchange 2013 CU7 and then taking a full backup."

    Its wrong! Please update post. (Ask Brett Shirley)

  4. Hi Iiya,

    This is listed on the EHLO post here:
    http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx#comments

    Which part of it is wrong please?

    Feel free to use the mail me link to the right hand side of the blog post.

    Cheers,
    Rhoderick

  5. anonymouscommenter says:

    I can’t find anywhere that sais for sure and clearly. Can you just installed cu7 as a New exchange server? Or do you need to still installed exchange 2013 then cu5 cu6 then cu7.. .As I understand it. They are all full installs.

  6. anonymouscommenter says:

    The CU’s are full installs so it’s not necessary to install all old CU’s !!

  7. anonymouscommenter says:

    It could be that this article was later updated after your post but I’m not sure which part of "CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one." is not easy to understand?

  8. When I edit posts I add the Updated: section with a comment. Unless it was a minor typo.

    Cheers,
    Rhoderick

  9. anonymouscommenter says:

    I am using CU 7 with an Exchange 2007 and the Activesync is not proxying as it is supposed to be working again in CU7. Can someone confirm if the issue is actually resolved with CU7?
    Thank you
    Brian

  10. anonymouscommenter says:

    Is it necessary to uninstall IU’s to CU6 before installing CU7? Will those rebuilt config files be OK?

  11. anonymouscommenter says:

    Exchange Server 2013 CU7 is unable to provide public folders access to Windows XP clients. Would you explain it officially?

    If it is out of support, should we expect that MAPI mailbox access for XP will be broken in CU8?

  12. Hi Michael,

    I’m afraid I cannot comment on products that have exited their extended suupport lifecycle.

    Sorry!

    Cheers,
    Rhoderick

  13. Hi Steve,

    We are instructed that removing IUs should not be needed with Exchange 2013.

    Cheers,
    Rhoderick

  14. anonymouscommenter says:

    Hi Rhoderick!

    I’ve examined Exchange Server Supportability Matrix, it is clearly stated that Outlook 2010 is supported with Exchange Server 2013 SP1 and later (regardless of client operating system).

    Customers had made decision to migrate to Exchange Server 2013 when it was fully compatible with the customer’s environment (including XP OS). Microsoft once again has broken (was it accidental?) the compatibility with Exchange Server update.

  15. anonymouscommenter says:

    Hi Rhoderick !
    Is it possible to uninstall Exchange server 2013 CU7 and reinstall only Exchange 2013 no CU ?
    Thanks
    Florin

  16. anonymouscommenter says:

    It seems I too have a 2007 to 2013 setup. CU7 completely broke ECP/OWA, everything…!! I have MSExchange AppPools in IIS that are pointed to folders with nothing in them but the web.config.bak files. I have App Errors in event viewer with .NET 4.0 Application
    crashes. This is a nightmare. Luckily I was able to move my mailbox from the now broken exchange back to 2007, but 2013 is completely down. I waited because CU6 broke my hybrid config and I am trying to get to Office365. Can anyone out there help????? Please…..I
    don’t want to have to build another server. The Exchange Dev team does not seem to be doing a very good job with these updates…..

  17. anonymouscommenter says:

    Hi I’m having the same issue as Mike. I have Ex2010 coexisting with Ex2013 and when I went from Exch2013 RTM to CU7, it broke my ECP/OWA. When logon to ECP it actually logs me on to OWA. Any help please.

  18. CorneliusTF says:

    Hi All,

    I would like to ask the following question. I’ve got exchange 2010 SP3 RU5 in Coexistence with Exchange 2013 SP1.

    Is it possible to update the Exchange 2010 to SP3 RU8 and then Exchange 2013 SP1 to CU7?

    If so what will the procedure be for doing that? We are not going to migrate to Exchange 2013 fully very soon.

    Thanking You

    Tobias

  19. anonymouscommenter says:

    Help, getting this error at end of CU7 upgrade. No other CU’s applied, just a vanilla install of Exch2k13 with SP1.

    If I do anything post this, it says Exchange is in an inconsistent state and to run with /m:RecoverServer but this just fails also with little info in the ExchangeSetup.log

    Error:
    The following error was generated when "$error.Clear();
    upgrade-ExchangeServer -Identity $RoleFqdnOrName -DomainController $RoleDomainController

    " was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn’t be performed because object ‘dc.domain.com’ couldn’t be found on ‘dc.domain.com’.
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory
    errorCategory)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError)
    at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.UpgradeExchangeServer.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

  20. anonymouscommenter says:

    …and I’m going around in circles here, running with the Recover server option, I get this:

    C:Temp>setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

    Welcome to Microsoft Exchange Server 2013 Cumulative Update 7 Unattended Setup
    Copying Files…
    File copy complete. Setup will now collect additional information needed for
    installation.
    Client Access role: Front End Transport service
    Management tools
    Client Access role: Client Access Front End service
    The Exchange Server is in an inconsistent state. Only disaster recovery mode is
    available. Please use Setup /m:RecoverServer to recover this Exchange server.

    The Exchange Server setup operation didn’t complete. More details can be found
    in ExchangeSetup.log located in the :ExchangeSetupLogs folder.

  21. Hi Cornelius,

    You can update the existing Exchange 2010 server to RU8V2 today.

    Then deploy new Exchange 2013 CU* at a later date, and then move the mailboxes over etc.

    Look at the Exchange Deployment Assistant for some details on the process.
    There are no more inplace upgrades.

    Cheers,
    Rhoderick

  22. Jimmy, check that you are not seeing any of the issues here
    http://blogs.technet.com/b/rmilne/archive/2013/12/05/6-mistakes-to-avoid-with-exchange-2013-cu-command-line-installations-.aspx

    the RecoverServer option expects that you have just built a new server with the same name, taken over the existing computer object 9without deleting it), then installed the pre-requs and are now recovering the Exchange install based on the metadata in AD.

    If this is a production issue, I’d recommend to call into support. Forums and blog posts are probably not going to respond quickly enough for you.

    Cheers,
    Rhoderick

  23. anonymouscommenter says:

    Just installed Exch 2013 CU7 and now my imap connection doesn’t work. This previously worked with the base version of Exch 2013.

    I was using the imap cmd "login domain/username/alias {password}" method to login. Now this doesn’t work

    Where do i report this to get it fixed.

  24. anonymouscommenter says:

    For – Mark Sandler : Run again – Set-IMAPSettings -LoginType PlainTextLogin. Restart IMAP (restart-service -service msExchangeIMAP4) and test. And Test IMAP for port 993.

  25. anonymouscommenter says:

    Hi Rhoderick,
    I have 2 Exchange 2013 server CU2 (both CAS + Mailbox role) EX01 & EX02 in DAG01 . I upgrade EX01 to CU7 successfully , when I try to upgrade CU7 on EX02 by command
    setup.exe /mode:upgrade /IAcceptExchangeServerLicenseTerms
    I get error :
    The Exchange Server setup operation didn’t complete. More details can be found
    in ExchangeSetup.log located in the :ExchangeSetupLogs folder.
    Here content of ExchangeSetupLogsExchangeSetup.log
    [ERROR] An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may
    be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See
    http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

  26. anonymouscommenter says:

    I fixed it, because of lock exe or something, I just have to extract cu7 and run on local server

  27. Question – what version of .NET do you have on those machines Jack?

    Cheers,
    Rhoderick

  28. anonymouscommenter says:

    After updating to CU8, some users are unable to connect to Public Folders on Exchange 2013. These users are using Outlook 2007 and are getting the following error: Your profile is not configured. (/o=First Organization/ou=Exchange Administrative Group
    (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers)…

    It worked fine when it was just on Exchange 2013 SP1.

Skip to main content