Home

The Exchange team is announcing today the availability of our most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 5 for Exchange Server 2013 and updated UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 5 represents the continuation of our Exchange Server 2013 servicing and builds upon Exchange Server 2013 Service Pack 1. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved in Exchange Server 2013 Cumulative Update 5 can be found in Knowledge Base Article KB2936880. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 5 today. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 5 as well.

Note: Some article links may not be available at the time of this post's publication. Updated Exchange 2013 documentation, including Release Notes, will be available on TechNet soon.

We would like to call your attention to a couple of items in particular about the Cumulative Update 5 release:

  • Based upon customer feedback, we have introduced improvements to OAB management for distributed environments. You can read more about this in a post by Ross Smith IV on the Exchange Team blog. Customers who have deployed Multiple OAB Generation Mailboxes are advised to read this post to help avoid unnecessary OAB downloads.
  • Cumulative Update 5 includes a Managed Availability probe configuration that is frequently restarting the Microsoft Exchange Shared Cache Service in some environments. The service is being added to provide future performance improvements and is not used in Cumulative Update 5. More information is available in KB2971467.

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

Cumulative Update 5 includes Exchange related updates to Active Directory schema and configuration. For information on extending schema and configuring the 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 KB981474to 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., CU5) or the prior (e.g., CU4) Cumulative Update release.

The Exchange Team

87 Comments
Not applicable
Great job, team! Update was successful! But there was a problem for customers MAPIHTTP - Outlook does not connect when the proxy in Internet Explorer. Necessary to address the exceptions.
Not applicable
Hi, any update on KB 2958434 - Users cannot access mailboxes in OWA or EAS (Exch. 2013 SP1) when mailbox database (Exchange 2007) is removed? I really need a fix for this as I need to re-provision the Exchange 07 server as soon as possible,m if not yesterday...

Thanks!

Not applicable
Thanks for this, never forget unrestricted.
Not applicable
Is Exchange 2013 CU5 meant to be applied against Exchange 2013 SP1? Or is it just meant for Exchange 2013 (and previous CU's)?
Not applicable
@FrankWater - The "MDB Ping" issue has been resolved and will be shipped in Cumulative Update 6.


We are not currently tracking any work in EWS related to Plain Text handling in Calendars. To properly address this request, I encourage you to report the problem to Support Services.

Not applicable
@Exchange Queries - We have no further details to share on the Shared Cache Service at this time. As indicated above, this is being added to improve system performance and is not used in the Cumulative Update 5 release. Fully enabling this feature is currently

targeted for Cumulative Update 6.

Not applicable
What about the error during setup if there are not unique receive connectors?



e.g.: 1 receive connector has 0.0.0.0:2525 the other one has 0.0.0.0:25


Is there a solution, because setup stops in the middle and Exchange is not working anymore? The only solution I used, was to delete one of these receive connectors in ADSI.


Details regarding this error:

ExchangeSetup.log:96380:[07.01.2014 14:09:02.0949] [2] [ERROR]

The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "ServernameAuthSMTP Relay".



Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.

Not applicable
@Brent: Thanks for answer, but by my opinion it is definitely defect. Sound in OWA disappeared since SP1 update, I tested this on all my servers - everywhere the same. Also another people from different organizations confirming this issue to me. Unfortunately

my company doesn't have support assurance on Exchange Server, I can't open case. It is not critical bug, but it is very annoying, when tab in browser is not active, no any notification about new mail (soundpopup windowsicon change).

Not applicable
nice job
Not applicable
Hi Went to install CU5 on a server that only had CU1. It check all perquisites ok, then after it had disabled all the exchange services it failed with "Unable to install because a previous Interim Update for Exchange Server 2013 Cumulative Update 1 has

been installed".


Bit of googling told me I had to uninstall KB2874216. Uninstalled this. try to restart CU5 update and it fails without any error just after checking disk space. Ok so more googling find that remote registry has been disabled and need to start this. Still no

good - give up for the evening. Spend half an hour un-disabling all the services that the faulty CU5 update did.



Now my exchange is sort of working, but find I'm unable to send email in or out. SMTP is listening but as soon as anything tries to talk to it it disconnects.


This is rubbish Microsoft.

Not applicable
The EWS plain text calendar body issue is not fixed in this CU.


See:


http://social.msdn.microsoft.com/Forums/exchange/en-US/88e78151-088b-4a2f-9a4d-003be7323ae9/e2013ews...

Not applicable
The MDB ping warning 'Ping of mdb '0afbb5dc-b967-4ebd-acb0-15f85b8bad53' timed out after '00:00:00' minutes. Last successful ping was at '29-5-2014 14:02:31' UTC.' is also still present in this CU.



This false warning exists since RTM!

Not applicable
I understand, that it isn't bug tracker or forum, but here is many people, who migrating to CU5... Can anybody confirm problem in CU5 with creating Rooms via ECP? (Open ECP->Recepients->Resources-> + -> Room Mailbox)?


When creating appears error: Cannot open mailbox ..../ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=servername/cn=Microsoft System Attendant. I tried to re-create all Arbitration mailboxes - doesn't helped. The worst in this

- nobody can access created room's calendar, even if they have Full Access rights. Found workaround - moving created room mailbox on any oher mailbox database, then access rights begin to work. I didn't have such issue prior CU5 update...

Not applicable
@Renat, there are no changes to Public Folder scalability in CU5.
Not applicable
Hi any possibility to adjust the default transaction log volume available disk space ? At the Moment SCOM drives us crazy - nobody need's 100GB of free disk space .... - this issue has been adressed at MEC, but still present Regards Max
Not applicable
no answer from MS sind 1.June:

Hi any possibility to adjust the default transaction log volume available disk space ? At the Moment SCOM drives us crazy - nobody need's 100GB of free disk space .... - this issue has been adressed at MEC, but still present.

What about EventId 6003 - why the path "D:MonitoringDiagnosticLogsMSExchangeHMHost" is hard coded ?

Regards Max

Not applicable
During Exchange 2013 CU5 update, we get below error. It has problem stopping WinMgmt so setup fails. Has anyone see this issue and fix for this problem?

ErrorRecord: Service 'WinMgmt' failed to reach status 'Stopped' on this server.

Thanks!

Not applicable
Are there any fixes related to content indexing in this release? We're seeing strange issues with content indexes, where we're forced to stop the exchange search services on all our servers and remove the index, and then rebuilding it. This also affect

seeding to new database copies, where it nearly immediatly fails.. our only solution then is to seed with -DatabaseOnly.

Not applicable
I have identified a bug in CU5. CTS Exchange Technical Support did manage to recreate this issue, and confirmed that it is a bug. My customer have a mix Exchange 2007 and Exchange 2013 organization. When CU5 is installed, OWA redirection when FBA is turned

off on both 2007 and 2013, is broken.

Not applicable
I have the same issue as JohnBlair. After the update from UR3 to UR5, the ECP site takes a couple of minutes to load. This is the same for admins as users modifying their options. Once they are in, it responds well. Sometimes it times out and fails.
Not applicable
@BK-Exchange and @HS Gurvey:

You can manually stop Existing Exchange services "Windows Management Instrumentation" and "Microsoft Exchange Health Monitoring". When they will be in "Stopped" status - run setup again. This errors says that server was too slow or service just hangs, that

timeout at stopping appears.

Not applicable
The workaround for "MAPI over HTTP may experience poor performance when you upgrade to Exchange 2013 SP1" is wrong. The paths set are not formed correctly. Ie: missing "Microsoft" in path name to Exchange location. Works when manually making it an absolute

path.

It is unclear if you should add both the FrontEnd/CAS and the Mailbox parts to a multi-role server?

Not applicable
Wooo-Hooo, already planned to apply update!

Thanx, Team!

Not applicable
Hi, any update on KB 2958434 - Users cannot access mailboxes in OWA or EAS (Exch. 2013 SP1) when mailbox database (Exchange 2007) is removed? I really need a fix for this as I need to re-provision the Exchange 07 server as soon as possible,m if not yesterday...

Thanks!

Not applicable
Hi has EventId 6003 - "MSExchangeHMHost: Failed to create the log directory: D:MonitoringDiagnosticLogsMSExchangeHMHost because of the error: Could not find a part of the path 'D:'.. Logs will not be generated until the problem is corrected." fixed

?

Not applicable
Broken since SP1 OWA sounds are NOT fixed in CU5.

Thread:

http://social.technet.microsoft.com/Forums/sharepoint/en-US/bcc6f2d2-bd50-4af2-a5ef-6db20463e9bb/owa-2013-sp1-new-mail-notification-sound-missing?forum=exchangesvrclients

Four month gone (facepalm)

Not applicable
@Max Grillenberger - From what I have seen, EventID 6003 has not been fixed - I still have these errors when MSExchangeHM is started after installing CU5.
Not applicable
Thanks, going to try it in the lab 1st and then we are going Exchange Server 2013 CU5 in the Prod :)
Not applicable
Hi, has KB2938292 been fixed? Please update the doco if so. Cheers (http://support.microsoft.com/kb/2938292)
Not applicable
@Renat Matveev I have seen this same (or similar) issue on servers with CU3 and SP1/CU4. I recommend you open a case with PSS.
Not applicable
Another one question to MSFT team: Was any performance improvements made with public folders in CU5? I don't see anything about PF in kb2936880, but in my company they became working much faster after update than on previous CUs...
Not applicable
to Renat Matveev: I would say more - online data archives and shared mailboxes also open faster.
Not applicable
@mikerydz, there were some changes to reduce the likelihood of hitting this condition (shorter cache lifetimes), but it is not something can be entirely removed easily without impacting overall performance of the system (if there was no cache at all).

You should be able to remove those old databases sooner in CU5 compared to what SP1 would have exhibited.

Not applicable
Are the issue with redirecting owa http to https resolved in this release?
Not applicable
@Aleksey - We are aware that the Outlook Client is not using the 'Bypassing local addresses' IE Proxy settings with MAPI-HTTP. We are working on a resolution for this.


@Renat - Your issue does not appear to have been raised to the engineering team as a defect, and does not appear to repro in all environments. Please work with support services to investigate so that this issue can be properly resolved for you.

Not applicable
@ADBL - Yes, KB2938292 is resolved in CU5. It was inadvertently missed in the release KB. We will provide an update soon.
Not applicable
We too are having issues once loading cu5. These could be related to other issues in the environment. Our ECP site is slow and often does not respond. Also users are having issues when booking conference rooms using the room finder. I have an open ticket

with Microsoft and will let you know the results.

Not applicable
Trying to install CU5 I'm getting an error similar to the one posted by BK-Exchange on June 13, which has still not been answered. In my case the service which cannot be stopped is MSExchangeHM. The message is "Microsoft.Exchange.Configuration.Tasks.ServiceDidNoReachStatusException:

Service 'MSExchangeHM' failed to reach status 'Stopped' on this server.

PLEASE RESPOND.

Not applicable
@Renat

I had this problem with all 2013 versions, it's not specific to CU5 I think.

After creating a new resource I have to wait for about a minute before I can apply further settings (auto booking, booking limits, ...). I assume that Exchange need some seconds to create internal structure of the mailbox or something like that.


An other annoying thing: ECP seems to happily switch between site DCs at every read/write access, so I often get strange (harmless) errors, because replication didn't complete yet. ECP writes an object to DC1 and hopes 1ms later to read this from DC2.... The

DomainController switch at the powershell commands doesn't affect reading AND writing, so it won't help.

Not applicable
Is there any fixes related to IMAP service in CU5?
Not applicable
HI,


Could you please explain in more detail the functionality of Shared Cache Service that will be doing in future...I hope their is already a service "Microsoft Exchange Migration WorkFlow" in an unknown history ...

Not applicable
@Brent: I opened a case about the EWS issue early March, case number is 114030711243824. It was confirmed as a bug in SP1, but it isn't fixed yet.
Not applicable
I'm not so sure CU5 is bug free.


Is anyone else suffering with messages getting stuck in the submission queue with the error "A storage transient failure has occurred during content conversion" when TNEFEnabled is set to $False on remote domains? No 3rd party transport agents and AV ruled

out.


This never happened when we were on CU3 and I know it was a bug in both Exchange 2010 SP1 and Exchange 2013 RTM that supposedly got fixed, but CU5 seems to have re-introduced it.

Not applicable
@Renat Matveev I did a transition two days ago from Exchange 2010 to Exchange 2013 CU5 and have no problems with room creation or calendar viewing, I checked seconds ago. Reach MS support there's no other way.
Not applicable
@northsider, CU5 is meant to be applied to any version of 2013.
Not applicable
@ Dintid: Could you please email me and give me the details about issues you have found? We are not sure that we understand the problem / workaround you are mentioning. Please email me at ninobATmicrosoft DOT com.
Not applicable
In before anyone else!
Not applicable
Lab time!
Not applicable
So does CU5 come before or after 2013 SP1? If it comes after, I thought it would be Exchange 2013 SP1 CU1. Hopefully this will fix the daily BSOD (or at least shed some light on it) being caused by ServiceHealthMSExchangeReplForceReboot
Not applicable
Hello,


This update fix the bug with sound for new mail in OWA ?


Thanks.