Exchange releases: December 2014
Published Dec 09 2014 09:00 AM 137K Views

Editor's Note: Updates added below for important information related to Exchange Server 2010 SP3 Update Rollup 8.

The Exchange team is announcing today a number of releases. Today’s releases include updates for Exchange Server 2013, 2010, and 2007. The following packages are now available on the Microsoft download center.

These releases represent the latest set of fixes available for each of their respective products. The releases include fixes for customer reported issues and minor feature improvements. The cumulative updates and rollup updates for each product version contain important updates for recently introduced Russian time zones, as well as fixes for the security issues identified in MS14-075. Also available for release today are MS14-075 Security Updates for Exchange Server 2013 Service Pack 1 and Exchange Server 2013 Cumulative Update 6.

Exchange Server 2013 Cumulative Update 7 includes updates which make migrating to Exchange Server 2013 easier. These include:

  • Support for Public Folder Hierarchies in Exchange Server 2013 which contain 250,000 public folders
  • Improved support for OAB distribution in large Exchange Server 2013 environments

Customers with Public Folders deployed in an environment where multiple Exchange versions co-exist will want to read Brian Day’s post for additional information.

Cumulative Update 7 includes minor improvements in the area of backup. We encourage all customers who backup their Exchange databases to upgrade to Cumulative Update 7 as soon as possible and complete a full backup once the upgrade has been completed. These improvements remove potential challenges restoring a previously backed up database.

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

Cumulative Update 7 includes Exchange-related updates to Active Directory schema and configuration. For information on extending schema and configuring Active Directory, please review Prepare Active Directory and Domains in Exchange 2013 documentation.

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

Update 12/12/2014:

Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package corrects the issue which impacted users connecting to Exchange from Outlook. The issue was insulated to the MAPI RPC layer and was able to be isolated to quickly deliver the updated RU8 package. The updated RU8 package is version number 14.03.0224.002 if you need to confirm you have the updated package. The updates for Exchange Server 2013 and 2007 were not impacted by this regression and have not been updated.

Update 12/10/2014:

An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.

The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish further updates to this blog post regarding RU8.

This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.

The Exchange Team

98 Comments
Not applicable
Not sure what you're talking about Klaus, not a single issue has occurred here!
Not applicable
wits1 - did you have to uninstall the previous RUs as the article says needs to be done? I thought we didn't have to do that any more after Sp3.
Not applicable
I wasn't able to post this in the original thread (http://blogs.technet.com/b/exchange/archive/2013/11/13/exchange-server-the-road-ahead.aspx) so am

leaving it here instead.


The problems with Outlook 2010 and 2013 with Sync Issues due to deleted items when communicating with Exchange 2010, 2013 and Office365 that I had posted about in that old thread have been resolved via a Hotfix for the Outlook client:

http://support.microsoft.com/kb/2606009 ... the Hotfix was issued back in April 2014 but I have only just become aware of it.

Not applicable
Is the update for MS14-075 safe to apply to Exchange 2013 CU6 with the FIU (Exchange2013-KB2997209_2997847-x64-en) already applied?
Not applicable
@Renat Mateev - We are aware of and still working on resolving issues with Chrome and ECP. We are also investigating reports of calendar shift issues with the new time zone updates.


@ECMaster76 - Since you are running a private fix (FIU) applying MS14-075 on top of your private fix is not recommended. Taking this action could revert the issue resolved by the FIU. The fixes you received as an FIU have been resolved in CU7 (as is MS14-075).

CU7 would be the recommended path forward.

Not applicable
Good point publishing the security update also for CU6 (and SP1). That lets us apply it more quickly, while planning and performing schema update and testing CU7 more thoroughfully.
Not applicable
Please add Exchange 2013 set-mailboxsentitemsconfiguration support. One of the most requested features at customers!
Not applicable
You Guys REALLY need to do better field testing before release!

It's not the first time we have seen problems with there UR's lately.



/Klaus Ringe Nielsen

(Currently uninstalling)

Not applicable
@wits1 - We have unfortunately identify a problem with Outlook connectivity that was not caught in internal validation. As updated on the blog here, we are working on a fix and will release as soon as possible.



@RoyceEB - For now rolling back RU8 is the only action necessary to restore normal Outlook connectivity.

Not applicable
It wasn't only Outlook clients that were affected by the problems in RU8.

We are running McAfee groupshield on our Client Access/Transport servers and groupshield made RPCServ hang consuming 100% CPU which also brought the Exchange Transport service to a halt.

Uninstalling RU8 brought things back to normal again.

Not applicable
Is the ActiveSync with Exchange 2007 corrected (http://support.microsoft.com/kb/2997847/)?
Not applicable
I am floored. Obscure issues making it thru testing unnoticed is one thing, but the biggest use case of all (Outlook connectivity) not being identified in testing is just astounding. Especially with this release already having been delayed once, it seems

like there was ample time to find something this glaring. I am not saying I could do it better, but my confidence in servicing updates was already shaken after the last few releases so this really leaves me questioning the future of Exchange On-premises.

Not applicable
Anyone enabled succesfully TLS 1.2 for SMTP Communication?
Not applicable
Thank you sharing.
Not applicable
@Microsoft, PLEASE FOCUS on giving GOOD SERVICE to your Exchange Server (On-Premises) customers I.E. giving solid SPs, RUs and CUs.
Not applicable
What is the problema with backups before CU7, that CU7 is said to solve? I can't see anything about backup in the solved issues section of KB2986485. Please help to assess the urgency to install this CU7.
Not applicable
.. sorry I can see it has been corrected!
Not applicable
Microsoft has history of recalling updates after releasing it for their several products, not just exchange. I hope other updates for Exchange 2007 and 2010 has no issues with them...
Not applicable
Installed in production (2013CU7). Looks like working normally.

OWA sounds working again, great.

But ECP problems with Chrome >=37 not fixed.

Also, Russian time zone changes not completely fixed (I have many meetings in shared rooms which are not overlappings in Outlook 2013 in January 2015, but they overlappingshas non-correct time in OWA).

Not applicable
Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.

All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes. Note: OWA is not affected

Not applicable
PF hierarchy updates are a welcome addition, but are increases to the number of public folder mailboxes on the roadmap as well?
Not applicable
Super excited about the expansion on PF capacity. Keep up the good work.
Not applicable
Good job. Lets hope these are good releases that have received plenty of testing.
Not applicable
The KB's aren't showing up for any of them. Just says Oops, page not found..
Not applicable
Christmas came earlier than expected. :) Any changelog for the 2013 SP1 CU7 release?
Not applicable
I have a client that has installed a interim update to CU6 to help fix KB2997847, you previously advised when applying CU6 that "A reminder for those customers who installed the Interim Update which resolved this issue: it's NOT necessary to uninstall

the Interim Update prior to installing CU6." however I can't see any advise about this interim update before installing CU7?

Not applicable
Eh hem! After downloading and extracting CU7, then running "setup /PrepareSchema", should I be seeing "Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup"?
Not applicable
"Support for Public Folder Hierarchies in Exchange Server 2013 which contain 250,000 public folders"


Very disappointing.

Not applicable
Does the powershell policy problem (http://support.microsoft.com/kb/2810617) still apply to the Exchange 2010 SP3 RU8?
Not applicable
CU7 install keeps failing. The install keeps disabling the Exchange Services and then gives error that it can't start an Exchange Service. After failing, the install does not back out the install and renders the server unusable. Guess we will all be opening

a cases with PSS.


Error:

The following error was generated when "$error.Clear();

if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})

}

" was run: "Microsoft.PowerShell.Commands.ServiceCommandException: Service 'Microsoft Exchange Service Host (MSExchangeServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeServiceHost on computer...

Not applicable
After installing on several German Exchange Servers we have just Problems. Don't install!
Not applicable
I installed Exchange 2010 sp3 CU7 And CU8 yesterday, and today Outlook 2010 not working correctly in "Online mode". Users cannot send invites. "Operaion failed" error ocures and inbox not displaying items until restart. When using cached mode, everything

is OK. Registered incident in Premier Support.

Not applicable
After installing Exchange 2010 SP3 RU8 bumped into this issue:

http://support.microsoft.com/kb/980852


Server have Transport, CAS, Mailbox roles combined

Not applicable
Has anyone installed RU8 for Exchange 2010 SP3? Everything works fine?
Not applicable
Is MS14-075 safe to apply on Exchange 2013 CU6 w/ the FIU (KB2997209_2997847)?
Not applicable
After applying RU8 for Exchange 2010 SP3 users (Outlook 2010 Online Mode) are not able to delete messages or to confirm schedule requests. Anyone can confirm this? Now rolling back to RU6.
Not applicable
After installation of Rollup 8 on a SBS 2011 we couldn't access our calenders or send mail from our terminalserver (fully patched Windows 2008R2) with Outlook 2010. Uninstall of Rollup 8 fix the problem.
Not applicable
Not applicable
Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.

All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes. not affecting OWA

Not applicable
Same problem as wits1. Outlook clients are having coranaries all over the place, but OWA is fine.
Not applicable
Not applicable
Problems with outlook clients after applying this to Exchange 2010 SP3:


Getting a couple of times an hour:


Watson report about to be sent for process id: 11776, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.

ErrorReportingEnabled: False


and


An unhandled exception ('CrashNowException') occurred in Microsoft.Exchange.RpcClientAccess.Service.exe [11776]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Not applicable
"Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.

All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes. Note: OWA is not affected"


Same story here. "Cannot open this item" errors in Outlook but OWA not affected.

Not applicable
RoyceEB, our update was applied by Windows Updates and the other roll-ups were left in place. There were no interrim updates installed, however. We uninstalled RU8 (which required a download of the SP3 file for exchserver.msi) and things went back to normal.

What a mess though.

Not applicable
I'm having issues with Update Rollup 8 For Exchange 2010 SP3 with Calendars with all my Outlook Clients. Searching the internet, I found a lot of other users having the same issues. Uninstalling Update Rollup 8 For Exchange 2010 SP3 resolves the issue.
Not applicable
We had all kinds of trouble after instelling update rollup 8. Some users couldn't send email anymore. Others could not plan meetings in their calendar and so on. After we uninstalled rollup 8 everything works fine!
Not applicable
Your patchdays a getting worse each month!!!!!!!!!!!! KB3004394, Exchange 2010 SP UR8 etc.
Not applicable
Rollback of UR8 is not possible, Uninstall is asking for exchangeserver.msi?! HELP!!!
Not applicable
What has happened to testing and validating updates before they are released? Each time you pull an update within hours/days of releasing it you knock the confidence of any IT professional due to deploy it in, and the end result is that many will not deploy

it at all! The Exchange quality assurance testing needs to be improved, as this is becoming an all to familiar situation!

Not applicable
Well that solves the mystery and perhaps my biggest headache for today... Patch Tuesday goes out with a BANG for 2014
Version history
Last update:
‎Jul 01 2019 04:21 PM
Updated by: