Released: Exchange Server 2013 Cumulative Update 5


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

Comments (87)
  1. Anonymous says:

    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.

  2. Anonymous says:

    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!

  3. Anonymous says:

    Thanks for this, never forget unrestricted.

  4. Anonymous says:

    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.

  5. Anonymous says:

    Is Exchange 2013 CU5 meant to be applied against Exchange 2013 SP1? Or is it just meant for Exchange 2013 (and previous CU’s)?

  6. Anonymous says:

    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.

  7. Anonymous says:

    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

  8. Anonymous says:

    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.

  9. Anonymous says:

    @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.

  10. Anonymous says:

    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!

  11. Anonymous says:

    @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.

  12. Anonymous says:

    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.

  13. Anonymous says:

    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?

  14. Anonymous says:

    @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.

  15. Anonymous says:

    nice job

  16. Anonymous says:

    @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.

  17. Anonymous says:

    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…

  18. Anonymous says:

    @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).

  19. Anonymous says:

    @Renat, there are no changes to Public Folder scalability in CU5.

  20. Anonymous says:

    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!

  21. Anonymous says:

    Thanks, going to try it in the lab 1st and then we are going Exchange Server 2013 CU5 in the Prod :-)

  22. Anonymous says:

    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!

  23. Anonymous says:

    @northsider, CU5 is meant to be applied to any version of 2013.

  24. Anonymous says:

    @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.

  25. Anonymous says:

    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…

  26. Anonymous says:

    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 …

  27. Anonymous says:

    @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.

  28. Anonymous says:

    Are the issue with redirecting owa http to https resolved in this release?

  29. Anonymous says:

    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

  30. Anonymous says:

    Wooo-Hooo, already planned to apply update!
    Thanx, Team!

  31. Anonymous says:

    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
    ?

  32. Anonymous says:

    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.

  33. Anonymous says:

    @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.

  34. Anonymous says:

    @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.

  35. Anonymous says:

    Is there any fixes related to IMAP service in CU5?

  36. Anonymous says:

    Hi, has KB2938292 been fixed? Please update the doco if so. Cheers (http://support.microsoft.com/kb/2938292)

  37. Anonymous says:

    @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.

  38. Anonymous says:

    @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.

  39. Anonymous says:

    @ADBL – Yes, KB2938292 is resolved in CU5. It was inadvertently missed in the release KB. We will provide an update soon.

  40. Anonymous says:

    to Renat Matveev: I would say more – online data archives and shared mailboxes also open faster.

  41. Anonymous says:

    @ 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.

  42. Anonymous says:

    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.

  43. Anonymous says:

    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.

  44. Anonymous says:

    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.

  45. Shawn Harry says:

    In before anyone else!

  46. Shawn Harry says:

    Lab time!

  47. 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

  48. Anexus says:

    Hello,

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

    Thanks.

  49. Sathishg1 says:

    Hi
    Could you please explain about My office 365 organization is hosted by 21 Vianet in Hybrid Configuration Wizard

  50. Thanks! This CU fixes many important issues. I have a question regarding this one:
    http://support.microsoft.com/kb/2942609 The article mentions that the application pool on the CAS server crashes, I believe this should read the Mailbox server. Is that correct?

  51. Astrup says:

    Dear Exchange Team,

    What about the issue with "Folder views in Outlook are not updated when you arrange by categories"??
    You released a fix for this in UR6 for Exchange 2010, KB2925273.
    Is it not fixed in CU5 for Exchange 2013??

  52. David says:

    I’m curious about the status of KB2938292 too. It sais on the KB page that it will be included in CU5 but it isn’t listed as being included with CU5.

  53. Morten Nielsen says:

    In the release notes regarding MAPI over HTTP, there is a section "MAPI over HTTP may experience poor performance when you upgrade to Exchange 2013 SP1". The Work around lists 2 sets of commands to run: One set on CAS servers and one set on MAilbox servers.
    What if you run all roles on your servers. Do we run both sets of command on the servers?

  54. Eddy68 says:

    The installation of Exchange 2013 CU5 demaged my Exchange 2013 SP1 server – The Transport Server Role crashed! *** :-(

  55. Eddy68 says:

    The installation of Exchange 2013 CU5 demaged my Exchange 2013 SP1 server – The Transport Server Role crashed! *** :-(

  56. Rich says:

    What does "maintain currency on cumulative update releases" mean?

  57. EXCHANGE LOVER says:

    Are the issues with redirecting owa from http to https resolved in this release?

  58. K-Meister says:

    Just tried to install CU5 on our Exchange 2013 SP1 MailboxCAS server and ran into an error message on the installer, 5/29/2014. I installed Exchange 2013 to start testing on last Sunday 5/25/2014 which was successful.

    The only thing different about today is that the Schema FSMO role was on DC01 (see below) during the initial installation and then moved back to its originating DC named DC02. I hard coded a healthy domain controller on the MailboxCAS server using Exchange’s
    Powershell Console. I also made sure that the MailboxCAS’s Windows OS could only see the healthy DC as well. Here is the error message we are receiving, see below. Can someone please assist?

    Error:
    The following error was generated when "$error.Clear();
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController –

    ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

    " was run: "Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: An Active Directory error 0x51

    occurred when trying to check the suitability of server ‘DC02.askcts.com’. Error: ‘Active directory

    response: The LDAP server is unavailable.’ —> System.DirectoryServices.Protocols.LdapException: The LDAP

    server is unavailable.
    at System.DirectoryServices.Protocols.LdapConnection.Connect()
    at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean

  59. K-Meister says:

    Here is the rest of the error message.

    needSetCredential)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithLogging()
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.TryBindWithRetry(Int32 maxRetries,

    ADErrorRecord& errorRecord)
    — End of inner exception stack trace —
    at Microsoft.Exchange.Data.Directory.TopologyDiscovery.SuitabilityVerifier.CheckIsServerSuitable(String

    fqdn, Boolean isGlobalCatalog, NetworkCredential credentials, String& writableNC)
    at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType,

    String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
    at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType,

    String partitionFqdn, NetworkCredential networkCredential, String serverName, Int32 port)
    at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean

    isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
    at Microsoft.Exchange.Data.Directory.ADDataSession.GetReadConnection(String preferredServer, String

    optionalBaseDN, ADObjectId& rootId, ADRawEntry scopeDeteriminingObject, DualSearchMode dualSearchMode)
    at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType,

    DirectoryControl& responseControl)
    at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextResultCollection()
    at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.GetNextPage()
    at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.d__0.MoveNext()
    at

    Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.d__2`1.MoveNext()
    at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.FindByAccountName[T](String

    domainName, String accountName)
    at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean

    terminatePipelineIfFailed)".

  60. pete says:

    Was the issue with some ActiveSync users not being able to connect their device (http://support.microsoft.com/kb/2958434 ) fixed in CU5? There appear to be some very frustrated customers out there regarding
    this:
    http://social.technet.microsoft.com/Forums/en-US/291b583f-f228-4502-b7f0-604499fd8d37/error-databaseguidnotfound?forum=exchangesvrmobility

    We just completed a deployment, and are plagued with the same thing.

  61. Brent says:

    After upgrading to Exchange 2013 CU5 Outlook WebApp for Mobile has replace all Icons with pictures (cats/dogs/rain clouds/telephones). You see this if you go to OWA from a mobile device.

  62. Jice says:

    @ Max Grillenberger
    Try that : get-mailboxserver | %{$server = $_.name; Get-MonitoringItemIdentity dataprotection -Server $server | ? {$_.name -like "LowLogVolumeSpaceMonitor"} | %{add-ServerMonitoringOverride $_.identity -Server $server -ItemType Monitor -PropertyValue 20000
    -Duration 60.00:00:00 -PropertyName MonitoringThreshold} }
    SCOM will shuted up during 60 days, or you can use applyversion if you prefer :
    http://technet.microsoft.com/fr-fr/library/jj218628%28v=exchg.150%29.aspx
    (20000 = 20 GB)

  63. Brent says:

    After upgrading to CU5 Outlook Mobile Access is messed up. IF you go to OWA from your mobile phone the normal icons that used to be present (arrow, unread, read, trashcan) are no longer there, they are replaced with what looks like random clipart (a golf
    flag, telephone, airplane, dog, cup of coffee). Has anyone else seen this?

  64. Mindaugas says:

    Wondering about same case as mikerydz – KB 2958434.

    In my case it is not Ex2007. I created new DAG running Ex13SP1 and I was migrating mailboxes form the Ex13CU3 DAG… Same behavior..

    I had a case open, but support have not gave me any answer yet… Grr…

  65. greg says:

    Getting this critical error when updating from CU3 to CU5. The really bad part is that the critical error has taken our server offline and no email is being delivered. Error:
    [06/04/2014 14:29:02.0919] [1] [ERROR] The following error was generated when "$error.Clear();

    install-CannedAddressLists -DomainController $RoleDomainController

    " was run: "Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on Cedar.pbtf.com. The object ‘CN=All Distribution Lists,CN=All Address Lists,CN=Address Lists Container,CN=Port Blakely Tree Farms,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=pbtf,DC=com’ already exists. —> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists……….

    [06/04/2014 14:29:02.0919] [1] [ERROR] Active Directory operation failed on Cedar.pbtf.com. The object ‘CN=All Distribution Lists,CN=All Address Lists,CN=Address Lists Container,CN=Port Blakely Tree Farms,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=pbtf,DC=com’
    already exists.

  66. sigh says:

    This broke our install. If you have two nic’s and a connector on each nic, it has a cry at the transport install phase and fails to install and thereby breaking the entire install. FYI.

  67. Arjan says:

    A cosmetic bug in the update: when you run setup in unattended mode, it still shows CU2:
    "Welcome to Microsoft Exchange Server 2013 Cumulative Update 2 Unattended Setup"

  68. Arjan says:

    Never mind my last comment about CU2.
    I forgot to run the correct setup.exe from PowerShell.

    PS C:installex2013cu5> .setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 5 Unattended Setup.

  69. streamofstars says:

    Does anybody know if the CU5 also resolves the problem described in
    http://support.microsoft.com/kb/2938053 ? There is a fix available in KB2938053 but it was supposed to be included in CU5 so the fix from KB2938053 would no be required.

  70. Anonymous says:

    Can I install this CU5 on Exchange 2013 with SP1 already installed?

  71. EasternPromise says:

    What about the problem with illegal XML comments in Global Assembly Cache (GAC) introduced in SP1 that broke third party transport service agents? Does this CU5 fix it or should I install MS FIX first (http://support.microsoft.com/kb/2938053)?

  72. Brian says:

    Is Exchange 2013 CU5 meant to upgrade Exchange 2013 SP1? Or is just for Exchange 2013 (and prior CU’s)?

  73. KB2938053 says:

    Issue http://support.microsoft.com/kb/2938053 – is it fixed in CU5?

  74. John-transport-fan says:

    How about transport agents problems (as per
    http://support.microsoft.com/kb/2938053), have you fixed in CU5?

  75. Anonymous Pole says:

    There is not a single word about the problem with illegal XML comments in Global Assembly Cache what caused inability to install third party transport agents after updating Exchange 2013 with SP1 (see
    http://support.microsoft.com/kb/2938053). Does CU5 address this problem or do we still need to apply KB2938053?

  76. tom says:

    CU3 database schema was 0.126, so SP1 is 0.127 and CU5 0.128?

  77. user says:

    Exchange 2013 CU5 (maybe on other 2013 versions the same):

    Outlook Web App – new mail – show from – when i click From, there is no option to choose a different From address!

    For example, on Exchange 2010 webmail, there is an option to change From address to something else.

  78. direktorn.com says:

    And once again Lync-OWA is gone.

  79. Erik says:

    Are there any fixes related to the content index in this CU? We’re experiencing some pretty strange faults with the content index, where the indexes go into a FailedAndSuspended state. We then rebuild them (seeding a copy doesn’t work) and it works for
    a few days, until they suspend again.

  80. Zachary N says:

    Had a problem with active directory topology service not starting during the upgrade. The service path was not encapsulated with " " and it caused the shell to say it was an invalid win32 file. Fixed it by finding the path in registry and kept hitting
    f5 during the install and then changed it in the registry once the change reflected. First tried blocking permissions to the key and the install put up an access error. So far.. CU5 is a big style crimpper. Our installation is installed on the D: drive.

  81. matt s says:

    Just did a fresh installation with CU5 and I get no notification sounds in OWA.

  82. Troy Nolen says:

    Any idea when CU6 will be released? I am happily on 2013 SP1 in coexistance with 2007 SP3 RU12 and I am leery of updating to CU5 based on what I am seeing here. Especially this: "But there was a problem for customers MAPIHTTP – Outlook does not connect
    when the proxy in Internet Explorer. Necessary to address the exceptions. "

    I use http proxy and have exceptions. I thought that was an Outlook issue fixed in SP1, if applying CU5 breaks that again, I cant have that happen

  83. Joe says:

    After 2 months, I still don’t see the updated documentation..
    Where are the instructions for setting up the Certificate-based authentication for EAS feature that was enabled in Exchange 2013 CU5?
    I have been searching and cannot find any documentation that goes along with this feature of CU5.

  84. Pigu says:

    mazakane,

    start the shell

    Get-ServerComponentState

    "your servername"

    every componont which is not "active" activate with:

    Set-ServerComponentState -Component ServerWideoffline -Identity mail -Requester HealthAPI -State Active
    Set-ServerComponentState -Component HubTransport-Identity mail -Requester HealthAPI -State Active
    and
    and
    and

    look into the registry
    hklm > software > ms > exchange server > v15 > server
    at health there must be 1:1 not 1:0

    restart the transportrole Service and Exchange is online again.

    to install cu5 set the receive connectors to Default and disable the sendconnectors

Comments are closed.