Released: Exchange Server 2013 Cumulative Update 3


The Exchange team is announcing today the availability of our most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 3 for Exchange Server 2013 and updated UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 3 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 3 can be found in Knowledge Base Article KB 2892464.

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 attention to an important fix in Exchange Server 2013 Cumulative Update 3 which impacts customers who rely upon Backup and Recovery mechanisms to protect Exchange data. Cumulative Update 3 includes a fix for an issue which may randomly prevent a backup dataset taken from Exchange Server 2013 from restoring correctly. Customers who rely on Backup and Recovery in their day-to-day operations are encouraged to deploy Cumulative Update 3 and initiate backups of their data to ensure that data contained in backups may be restored correctly. More information on this fix is available in KB 2888315.

In addition to the customer-reported fixes in Cumulative Update 3, the following new enhancements and improvements to existing functionality have also been added for Exchange Server 2013 customers:

More information on these topics can be found in What’s New in Exchange Server 2013, Release Notes and Exchange 2013 documentation on TechNet.

Before you deploy Exchange 2013 CU3…

Here are some things to consider before you deploy Exchange 2013 CU3.

  • Active Directory schema and configuration update: Exchange 2013 CU3 includes Exchange related updates to the Active Directory schema and configuration. For information on extending the schema and configuring Active Directory, please review the appropriate TechNet documentation.
  • PowerShell Execution Policy: 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 KB 981474 to adjust the settings.
  • Hybrid deployments and EOA: 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 maintain currency on Cumulative Update releases.

Our next update for Exchange 2013, Cumulative Update 4, will be released as Exchange 2013 Service Pack 1. Customers who are accustomed to deploying Cumulative Updates should consider Exchange 2013 SP1 to be equivalent to CU4 and deploy as normal.

The Exchange Team

Comments (117)
  1. Anonymous says:

    I have the same issue the mailbox database server upgraded fine but the CAS just get this error no matter what I do. This is in a production environment and even when I restore from a backup we can no longer receive mail.

    Any help would be a life line!

    Raevmi 6 Dec 2013 9:09 PM #
    Someone an idea what is going wrong whit the update?

    Error:

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

    $feVdirName = “PowerShell (Default Web Site)”;

    $beVdirName = “PowerShell (Exchange Back End)”;

    $vdirName = “PowerShell”;

    $InternalPowerShellUrl=”http://” + $RoleFqdnOrName + “/powershell”;

    get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

    new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName “Exchange Back End” -Path ($RoleInstallPath + “ClientAccessPowerShell-Proxy”);

    new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName “Default Web Site” -AppPoolId “MSExchangePowerShellFrontEndAppPool”;

    ” was run: “The virtual directory ‘PowerShell’ already exists under ‘server01.xxxxxxx/Exchange Back End’.

    Parameter name: VirtualDirectoryName”.

    Thanks

  2. Anonymous says:

    CU3: It seems that it is not possible to export a certificate via EAC to an UNC-Path if the server name begins with a digit (0-9).

  3. Anonymous says:

    Wow, reading through the comments it seems this CU causes more issues than it fixes! I stayed away from CU2 for similar issues… shoddy, shoddy work.
    Maybe someday a stable CU will be released…

  4. Anonymous says:

    Exchange Team continues their form on releasing updates which screws up customer deployments!

  5. Anonymous says:

    CU3 is driving me to Madness. I have a Simple, Automated LAB Setupo thta provisions all my required Servers including AD. I found out on a Standalone 2013CU3 Server i receive the following error when using new-mailboxdatabase:An inconsistency in the Active Directory was detected: Database ‘MailboxDatabase01’ is expected to be in a database
    availability group but the value for its MasterServerOrAvailabilityGroup property (‘E2013N1’) is not valid. This may
    be a defect in the product and this should be reported to Microsoft Product Support.
    + CategoryInfo : InvalidOperation: (MailboxDatabase01:MailboxDatabase) [New-MailboxDatabase], Inconsisten
    tADException
    + FullyQualifiedErrorId : [Server=E2013N1,RequestId=ac98a62f-10f5-4709-8b73-d13eb1669f04,TimeStamp=10.01.2014 12:5
    6:26] ABC21501,Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase
    + PSComputerName : e2013n1.brslab.local
    You can find my whole Testing here: https://community.emc.com/blogs/bottk/2014/01/13/exploring-madness-with-exchange2013-cu3

  6. Anonymous says:

    Hi guys,

    Since installing CU3 I have many users with Outlook 2007 that are getting mail stuck in their outbox and the only way to resolve is to readd their mail profile.

  7. Anonymous says:

    Please help, currently we have no mail flow. I have restored server a number of time but what ever way we install we get this error while installing the FrontEnd Transport Role.

    Error:

    The following error was generated when “$error.Clear();
    $feVdirName = “PowerShell (Default Web Site)”;
    $beVdirName = “PowerShell (Exchange Back End)”;
    $vdirName = “PowerShell”;
    $InternalPowerShellUrl=”http://” + $RoleFqdnOrName + “/powershell”;

    get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

    new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName “Exchange Back End” -Path ($RoleInstallPath + “ClientAccessPowerShell-Proxy”);

    new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName “Default Web Site” -AppPoolId “MSExchangePowerShellFrontEndAppPool”;

    ” was run: “The virtual directory ‘PowerShell’ already exists under ‘JE.CAS.local/Exchange Back End’.

    Parameter name: VirtualDirectoryName”.

    Thanks

  8. Anonymous says:

    How do you update an UM Language Pack after CU3 install? This fails: C:Program FilesMicrosoftExchange ServerV15Bin>setup /AddUmLanguagePack:en-US /s: c:UM /IAcceptExchangeServerLicenseTerms Welcome to Microsoft Exchange Server 2013 Cumulative Update
    3 Unattended Setup UM Language Pack for en-US Performing Microsoft Exchange Server Prerequisite Check Prerequisite Analysis FAILED Unified Messaging language packs are already installed for the following cultures: ‘en-US’. The installation can’t proceed until
    the following language packs are removed from the list: ‘en-US’. For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AlreadyInstalledUMLangPacks.aspx The Exchange Server setup operation didn’t complete. More
    details can be found in ExchangeSetup.log located in the :ExchangeSetupLogs folder. C:Program FilesMicrosoftExchange ServerV15Bin>setup /RemoveUmLanguagePack:en-US Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup UM Language
    Pack for en-US The US English (en-US) UM language pack can’t be uninstalled. It’s required on all Mailbox servers. The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the :ExchangeSetupLogs folder.

  9. Anonymous says:

    I have just installed CU3 but now mail transport keeps stopping working.
    If I telnet the server on port 25 I get this error: 421 4.3.2 Service not available
    After I restart the Microsoft Exchange Transport service then it works again for a little while then stops again.

    Also prior to updating to CU3 I was on CU1 and had to uninstall KB2874216 otherwise the install of CU3 fails:(https://dirteam.com/blogs/davestork/archive/2013/09/25/failed-exchange-server-2013-cu2-install-due-to-security-update-2874216.aspx)

    Also after the failed install I had to manually re-enable all the Exchange services.

    I cannot really see any errors in Event Viewer related to the transport service or why it keeps failing.
    Everything was working fine on CU1.

    Please can someone suggest anything I can try to fix this?

    Thanks
    Robin

  10. Anonymous says:

    Pretty unlikely that we will see any RU that’s not causing additional problems. Dream on…

  11. Anonymous says:

    I just applied CU3 to my exchange 2013 servers, we are running 2010 and 2013 side by side. Before CU3 I was able to connect to the ecp via https://servername/ecp/?exchclientver=15 now after loggin in it redirects to 2010 owa. Any Ideas??

  12. Anonymous says:

    @Anonymous (Mon, Jan 13 2014 7:27 AM) (Karsten):

    Does the machine have the Clustering component installed but it is not forming a DAG? If yes, this is a known issue at this point, as Store checks both the presence of Clustering component as well as Active Directory state to determine if the server is a part of the DAG. We are addressing this scenario in SP1.

    If not – then please open a support case for this as it is unexpected.

  13. Anonymous says:

    @AlexAllen I run into the same issue. Even PowerShell couldn’t connect. It turned out to be an DNS issue. I put the fqdn’s of the virtual directories (which were still pointing to the Exchange 2007 server) in the hosts file and it worked.

  14. Anonymous says:

    @ Renat Matveev
    @ MIndaugas
    @ ExpertHLO
    @ Laurent
    Did anyone find the public folder solution to Exchange 2013 CU3 and Outlook 2077 on XP?
    “Cannot expand the folder. The set of folders cannot be opened. Your profile is no configured.”

  15. Anonymous says:

    The comment above was made by me. Didn’t realise I wasn’t signed in!

    Since installing CU3 on a perfectly functioning server which had been running CU1 I have had to write a script and add it as a scheduled task to restart the transport service every 15 minutes otherwise incoming email just stops. The only errors I can see are related to performance counters.

    I have now tried to install CU3 on a new server but it created 3 mailbox databases and all are dismounted and when trying to create another one I get this error:

    [code]
    Database is expected to be in a database availability group but the value for its MasterServerOrAvailabilityGroup property is not valid
    [/code]

    So on this new server I can’t even create any mailboxes.

    Should I set up another server on CU1 again?

    Thanks
    Robin

  16. Anonymous says:

    what about public for support for XP clients?

  17. Rhys says:

    support.microsoft.com/…/2892464

    Sorry, the page you requested is not available.

  18. berndk says:

    ….. "most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 3" CU 3 in Q4? And I guess your forgot to mention that this is CU3 Version 1.

  19. Tibor M says:

    @Rhys, it still replicating in Akamai network. You have to wait till it's replicated over the world.

  20. pesos says:

    and the file name actually reflects the version instead of being the same as the last few releases – yay!

  21. Tibor M says:

    So who will install it first? :D I don't want be first affected with new bugs :D

  22. Momet says:

    Can be CU3 installed over an existing installation which has CU2v1 installed? Or is it mandatory to deploy CU2v2 and then CU3?

    Any issues when directly upgrading CU2v1 to CU3 ?

    Thank you

  23. @Momet, yes, you can in-place upgrade from CU2V1 to CU3.

  24. LateToTheParty says:

    CU1 to CU3?

  25. Adrian Worthy says:

    Has this one been tested in your on-prem dog food environment?

  26. @Adrian – Cumulative Update 3 has been deployed in our internal dogfood environment as well as our Technology Adoption Partner environments prior to release.

  27. Nino Bilic [MSFT] says:

    @LateToTheParty – yes, you can do that.

  28. @LateToTheParty – Yes, direct upgrade from Cumulative Update 1 to Cumulative Update 3 is supported as well.  Customers can always deploy the latest Cumulative Update directly on a newly built server or upgrade from a previous release.

  29. Congrats says:

    Congrats team on this important, long-awaited release!

  30. Tell_us_here says:

    Gents :-)

    If you try Exchange 2013 CU3 On-Premises in your lab & run into issues, please let us know here, so we all know the issues here.

    Thanks

  31. Hayden says:

    Awesome news. Still on CU1, which we haven't had any issues with. Think I'll wait for you guys to test it out first :)

  32. Tibor M says:

    installed without any problems, takes ~40-60 minutes to install. I can confirm that bug which prevent forwarding external meetings disappeared. we didn't have any other bugs, so I cannot tell you more.

  33. Does CU3 requires enterprise or schema admin permission

  34. Tibor M says:

    @Tamer EL Bolkiny, yes because it's updating schema during setup

  35. Gavin says:

    I assume this update brings about compatibility with Windows Server 2012 R2 ?

  36. Grega_SLO says:

    @Gavin:

    Nope it does not.

    SP1 will bring this officaly.

    But they said that CU3 can work with 2012 R2 AD and as OS and I`m about to test this today :)

  37. Joking says:

    Installed it worldwide on all Exchange Servers.

    Not a single problem.

  38. Rick Eveleigh says:

    Can someone from Microsoft confirm or deny that CU3 officially enables support for Exchange 2013 with DCs running Windows Server 2012 R2 and also domain functional level of 2012 R2. Thanks

  39. Grega_SLO says:

    NO it does NOT.

    See here:
    technet.microsoft.com/…/ff728623%28v=exchg.150%29.aspx

    CU3 is already added but 2012 R2 not.

  40. So_Far says:

    One day after release, we have not heard anyone saying “CU3 broke Exchange 2013 On-Premises in the lab”.

    So maybe CU3 is the most stable out of the 3 CUs for Exchange 2013 On-Premises so far?

  41. Email Guru says:

    Upgraded all my servers to Exchange 2013 CU3, everything's fine and normal.

  42. ThommyG says:

    I'm currently installing it in our testlab. 4 hours passed and it's still performing step 14. The initial setup with CU2 on the same machine lasted about 50 minutes some weeks ago. But no errors so far ;-)

  43. M. Cope says:

    CU3 still doesn't support Windows 2012R2?

  44. Edward Huggett says:

    Can anyone confirm if the bug is fixed where emails dragged to desktop are converted to Rich Text from HTML? Also issues with Sending Emails as getting stuck in Outboxes.

  45. pesos says:

    So far so good on our 3-node DAG.

    Our DCs have been running 2012 R2 since its release, FWIW.

  46. hippiehacker says:

    @ Edward Huggett – did you mean that from shared mailboxes the mails got stuck in outbox? to prevent this you can use the following command

    Add-MailboxPermission -Identity <username> -User <username> -AccessRight FullAccess -Automapping $false

    and add the account manually

    for the RichText problem I hope this will be solved as well but as stated in social.technet.microsoft.com/…/move-message-with-attachment-from-one-mailbox-to-another-problem nothing changed to this behavior but funny enough with a simple vba MailItem.move event the mails stays in HTML Format :-)

  47. @Edward – The issue of HTML formatting being lost when a message is saved/moved outside of the source folder will be resolved in Service Pack 1.

  48. SimonT says:

    The setup.exe welcome message is :

    Welcome to Microsoft Exchange Server 2013 Cumulative Update 2 Unattended Setup.

    Someone forgot to update the number. :)

  49. Nino Bilic [MSFT] says:

    @SimonT  – thanks, looking into it…

  50. Korbyn says:

    Successful install for us.  Wanted to wait, but our executive was insistent on getting the Calendaring issue resolved ASAP (a first), which I'm glad to see resolve.  Has CU3 been deployed for Exchange Online yet, just wondering for our Office 365 clients who have been complaining to us for months?  Took a little longer then expected, but seemed solid, no issues.  Nice to see the thousands of RBAC messages stop, only had 3 days of logs because of it.  Now it's Transport log entries every 5 mins….

  51. @SimonT…sounds like you are running Setup.exe via the Exchange Management Shell, or via PowerShell.  You must run Setup at the Windows command line (cmd.exe).

  52. Dan Sheehan says:

    "Windows 8.1/IE11 no longer require the use of OWA Light"

    Hopefully this is in the works for Exchange 2010 as well.

  53. Dan Sheehan says:

    Nevermind… I didn't read the comments on the sparse Exchange 2010 SP3 RU3 post where customers figured it was included in the RU3.

  54. SimonT says:

    Hi Scott.

    I'm running the update via Command Prompt. If you want, I can send you a screenshot. I try via the Exchange Shell at first but it's fail because it could not update the Shell.

  55. JamelH says:

    I see the same thing as SimonT ,

    Welcome to Microsoft Exchange Server 2013 Cumulative Update 2 Unattended Setup

    Languages

  56. @Simon and @Jamie…in that case, you may be using the wrong bits, or you may have remnants of CU2 left in your TEMP folder(s).  Please verify that you have downloaded CU3 from http://aka.ms/E15RTMCU3, and that your TEMP folders are empty before running Setup.

  57. Brian Bohanna says:

    Failed on Step 17 of 18… I'm trying the install again to see if it works… I'll post the error if it reoccurs.

  58. Brian Bohanna says:

    [11/26/2013 20:11:05.0225] [1] The following 1 error(s) occurred during task execution:

    [11/26/2013 20:11:05.0225] [1] 0.  ErrorRecord: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported.

    [11/26/2013 20:11:05.0225] [1] 0.  ErrorRecord: System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported. —> System.NotSupportedException: Specified method is not supported.

      at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)

      — End of inner exception stack trace —

      at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

      at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)

      at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)

      at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

  59. BrianBohanna says:

    Sorry.. Here's the rest…

    11/26/2013 20:11:05.0256] [1] [ERROR] The following error was generated when "$error.Clear();

             $configFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "GenericAppPoolConfigWithGCServerEnabledFalse.config");

             $rpcProxyCLRConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeRpcProxyAppPool_Cafe_CLRConfig.config");

             $windir = $env:windir;

             [System.Array] $appPoolsExcludedFromWorkstationGC = "msexchangerpcproxyapppool","internalexchangesharedapppool";

             $appPools = &"$windirsystem32inetsrvappcmd.exe" "list" "apppool";

             foreach($appPool in $appPools)

             {

                 $startIndex =  $appPool.IndexOf('"') + 1;

                 $numChars = $appPool.SubString($startIndex).IndexOf('"');

                 $appPoolName = $appPool.SubString($startIndex, $numChars);

                 # Do not enable Workstation GC for AppPools that Allocate greater than 50MB/s at their peak e.g. MSExchangeRpcProxyAppPool

                 if ($appPoolName.ToLower() -eq "msexchangerpcproxyapppool")

                 {

                     $c= &"$windirsystem32inetsrvappcmd.exe" "set" "apppool" "$appPoolName" /CLRConfigFile:"$rpcProxyCLRConfigFilePath";

                     Write-ExchangeSetupLog -Info ($c)

                 }

                 elseif ($appPoolsExcludedFromWorkstationGC.Contains($appPoolName.ToLower()) -ne $true)

                 {

                     # We'll set this whether or not the app pool exists.  Failures are ignored.

                     $a= &"$windirsystem32inetsrvappcmd.exe" "set" "apppool" "$appPoolName" /managedRuntimeLoader:"";

                     $b= &"$windirsystem32inetsrvappcmd.exe" "set" "apppool" "$appPoolName" /CLRConfigFile:"$configFilePath";

                     Write-ExchangeSetupLog -Info ($a + " " + $b)

                 }

                 else

                 {

                     Write-ExchangeSetupLog -Info "Skipping $appPoolName since it should remain as Server GC";

                 }

             }

           " was run: "Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported.".

    [11/26/2013 20:11:05.0256] [1] [ERROR] Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Message'. Specified method is not supported.

    [11/26/2013 20:11:05.0256] [1] [ERROR] Specified method is not supported.

    [11/26/2013 20:11:05.0256] [1] [ERROR-REFERENCE] Id=CafePostSetupComponent___SelectedAppPoolsToGCServerFalseCafe Component=EXCHANGE14:CurrentReleaseSharedDatacenterSetup

    [11/26/2013 20:11:05.0256] [1] Setup is stopping now because of one or more critical errors.

    [11/26/2013 20:11:05.0256] [1] Finished executing component tasks.

    [11/26/2013 20:11:05.0506] [1] Ending processing Start-PostSetup

    [11/26/2013 20:22:02.0489] [0] End of Setup

  60. @Brian Bohanna, I would suggest creating a thread in the Exchange forums on TechNet for your issue where we have a specific Setup/Deployment forum. It is a lot easier to help with specific issues there instead of it getting lost among other unrelated comments here. This should be the setup forum URL. social.technet.microsoft.com/…/home

  61. BrianBohanna says:

    @ Brian Day – Thanks, I was just furnishing the request for experiences requested by the thread here. I'll send it on over there.

    Cheers!

  62. Tibor M says:

    almost 24 hours deployed in production environment without any problems. It looks really stable now. I hope that SP1 will be as same stable as CU3 now and we are looking for getting S/MIME back in OWA.

  63. jwpmzijl says:

    While installing CU3 on a fresh install of Exchange 2013 the install process wouldn't get past step 9 installing setup languages. I waited patiently for 2 hours but then I started analyzing what was happening. It turned out that forefront endpoint protection was blocking it (or at least scanning took 25% of compute power – 4 processors). After disabling Endpoint potection CU3 setup went ahead.

  64. lewis_saint says:

    ARGH. When will Exchange 2013 support Public Folders over Exchange Web Services (EWS)? My entire migration has been held up for over 9 months, as I have many Outlook 2011 clients needing access to public folders. This was a known issue with Microsoft up until CU2, and I was promised that this would be resolved in CU3. I don't see any mention of EWS in the support.microsoft.com/…/2892464 – can anyone shed any light?

  65. After the upgrade has stopped working on the Connection Filtering Agent  (antispam)

    and the integration OWA and Lync

  66. Matheo says:

    Is the problem with adding delegated permissions resolved? In mailbox properties in EAC on the delegation tab, adding a user to Full Access Permission of the mailbox quite often results in a message that says the user is already in the list of AD permissions, but it is not showing there nor can I access the mailbox using this account. Sometimes adding again and again until the user shows on the list resolves the problem, sometimes I have to wait hour or two to be able to add a user (message still appears that it is in the list already) and it shows in the list and I am able to access the mailbox. My servers are not very exhausted, resources are OK.

  67. Laurent says:

    I have found an issue.

    Since CU3 installed, the couple XP-Office 2010 (more than 300 computers in my case) cannot anymore access to PF. Windows 7 – Office 2010 is working fine…

  68. David says:

    Has anyone been able to see if this fixes the rendering issue when using Exchange 2013 OWA to access E2K10 mailboxes?  Or do we still have to cripple the web.config as usual?  I didn't see anything in the fix notes (or missed it).

  69. ExchangeDude says:

    Can't wait to find all the bugs in this release.  Bad history so far with 2013 updates

  70. Chris Meehan says:

    With both CU2 and CU3 I have had experiences with Antimalware Services (2012 R2 Endpoint Protection) impacting the amount of time to progress through the upgrade steps, to the point where progress is completely halted. I have to kill the antimalware service to continue. I couldn't find any recommendations around this in the setup checklist or any deployment resources on TechNet. Is there something we should do in regard to SCCM 2012 endpoint protection when preparing for a cumulative update install?

    Thanks for the great work. -Chris

  71. zpider99 says:

    Can anyone confirm or disclaim Laurent's situation with XP-Office2010 no access to PF after CU3 installation?

  72. Wolfgang says:

    Still no German CU3 UM language Pack available.. when will it be released?

  73. sog says:

    From my experience I can tell that Windows XP often has problems with authentication, users are asked for login credentials when starting Outlooks no matter which office (2007 – 2010) is used. I tried some tricks to make it working, but in general it's a huge waste of time. If possible get rid of Windows XP, you will save yourself a lot of trouble.

  74. Klaus R. says:

    @Wolfgang: actually it is, I downloaded it from here: http://www.microsoft.com/…/details.aspx

    Choose English, click on download, you can then select the languages you need, german is among those.

  75. Edward Huggett says:

    Installed CU3 on top of CU2v2 – all went smoothy except it reset some IIS settings to default for owa, and the Transport services did not start up automatically upon reboot. Seems stable. Running Server 2012.

  76. Greg says:

    Hi!

    We are getting more and more complaints about firefox and owa.

    See image: http://imgur.com/TZPKf1F

    Never happened with CU2…

    Any idea?

  77. Dmitry Razbornov says:

    @Aleksey Medvedovskiy  :

    Dude, when you`ve integrated Lync & OWA, you`ve made custom settings in files Exchange, right?

    Because the server was removed, your settings are gone ;]

    Simply take a file with settings thumbprint of certificate from a backup and replace it.

  78. I have Exchange 2013 CU2, trying to install CU3. Setup exited with error "[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 go.microsoft.com/fwlink for more information."

  79. # says:

    @Matheo, I thin that the issue that you describe is by design :)

    The Information Store have some cache….. technet.microsoft.com/…/bb684892.aspx, this is link for older exchange version because I cannot find info regarding this for version 2013 :(

    It will be great if someone from MS can explain more about this IS cache, is there any changes in 2013 ?

  80. @Dmitry Razbornov says:

    Yes, that's right! I fixed a this problem. Remains an unresolved issue with the anti-spam.

  81. ExpertHLO says:

    @ Laurent, I am still on CU2 the modern PF access from Windows XP is tricky. I found it working with a specific auth config only.

  82. Mike says:

    Really using a lot of memory. I have 4gb assigned to this VM.  CU2 averaged about 50-60% memory usage. CU3 is killing me at 98-100% memory usage….

  83. pesos says:

    4GB for an exchange server?  yikes

  84. MIndaugas says:

    @ExpertHLO

    Can you share how did you manage to make WinXP work with Modern Public Folders?

  85. Dan says:

    Smooth update at all, only Autodiscover didn't work for about an hour after, maybe it needed some time to reconfigure itself. HM service, that we had often to start manually in CU2, seems to start fine on boot in CU3.

    Can we apply the .NET 4.5.1 update or does Exchange 2013 require plain 4.5?

  86. CU3_1 week_70 Comments says:

    CU3 has been out 1 week now, and it looks like No major issues have been reported here after 70 comments.

    So it looks like CU3 is stable :-)

  87. Eike says:

    Hey guys,

    great work! Thank you. An issue what I've experienced with every CU, even CU3, is, that the update sets the external EAS Url to $null. The internal stays as it was.

  88. Frank says:

    @Sog

    "From my experience I can tell that Windows XP often has problems with authentication, users are asked for login credentials when starting Outlooks no matter which office (2007 – 2010) is used. I tried some tricks to make it working, but in general it's a huge waste of time. If possible get rid of Windows XP, you will save yourself a lot of trouble."

    With XP/2003 this happens when the hostname used in the rpc over http settings and msstd setting is not the common name of the exchange server certificate but one of the SAN names. Then XP/2003 fails to connect and you get an endless loop.

  89. Nimbus says:

    I wish our CU3 upgrade went as well as others here. Tried to upgrade our 2013 CU2 servers in our test domain running Server 2008 R2 SP1 and the following lovely error appears after an hours wait!

    Organization Preparation                                                                          FAILED

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

            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom

    ainController $RoleDomainController

    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".

     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof

    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff

    ected.

    Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros

    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a

    ffected.

    Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang

    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.

    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

  90. @Greg: Having the very same problem on different Windows Server 2008 R2 systems. Firefox takes around 1.6GB RAM on computers having only 2GB available, which leads to complete freeze… The only way how to work with Firefox is to kill the owa tab as soon as the RAM usage grows up to around 1,4G and reopen it again (which usually takes around 1.5 minutes).

    Anyone else having the same problem?

  91. Greg says:

    @Sebastian Machat:

    OMG I just realised that :S

    Firefox CPU usage is 25% and RAM is climbing as hell….

    Maybe this is FF/JAVA issue?

    Regards,

    Greg

  92. Greg says:

    Huh, take a look at this: shrani.si/…/insanemem.png

  93. Simpi says:

    Jesus, make the 2012 r2 support happen.

  94. Kiwi Computer Guy says:

    CU3 has completely killed my Exchange – /ecp /owa all get 'This page cannot be displayed', outlook can't connect.  I can get into PowerShell and things seem to be there, the SMTP receive connector is working.  So what has happened to the IIS side????

  95. Henrik says:

    CU3 removed the HTTP Redirect on the Default Web Site and also enabled SSL on the same site.

  96. Brian says:

    Same here – CU3 removed the HTTP Redirect on the Default Web Site and also enabled SSL on the same site.

  97. @Henrik/Brian, are you talking about the default
    https://mail.contoso.com/ to
    https://mail.contoso.com/owa redirect that adds /owa to the end of the URL, or a custom HTTP to HTTPS redirect you previously configured manually?

  98. Brian says:

    This redirect ‘Use IIS Manager to simplify the Outlook Web App URL and force redirection to SSL’ from

    technet.microsoft.com/…/aa998359(v=exchg.150).aspx

  99. Brian says:

    Also lost my Lync integration in the web.config on both mailbox servers:

    <add key="IMCertificateThumbprint" value="CERT_THUMBPRINT" />

    <add key="IMServerName" value="FQDN_LYNC_POOL" />

  100. Dan says:

    Now in production we have an XP-only issue with Outlook 2010 / CU3: Secondary mailboxes don't synchronize any longer in caching mode. Win7 works fine. lots of users complaining, XP's still alive.

  101. I can confirm that also lost access from WinXP to Public Folders (tested on Outlook 2007/2010). In RPC logs it is visible, that server gives wrong Public Folders GUID=0000-00000-0000… than said it isn't equal to Public Folder Mailbox GUID and redirect again. Infinite loop appears. In Windows 7 and OWA (tested with Outlook 2007/2010/2013) all fine. Need patch :(

  102. Alex says:

    We also have  trouble with Firefox 24. Any Fix available?

  103. unifiedteam says:

    Still no turkish CU3 UM language Pack available.. when will it be released?

  104. Dan says:

    My mentioned problem with not syncing cached shared mailboxes in Windows XP is a follow-up error of the broken public folders.

    Outlook stops creating caching connections to the server after the failed attempt to connect to the PF store. If I manipulate the MAPI Profile so that PF would not be accessed, shared Mailbox synchronization works again.

    So we need to get the PF thing fixed…

    As Renat stated:

    OUTLOOK.EXE,14.0.7108.5000,Cached,,,,ncacn_http,Client=MSExchangeRPC,,,PublicLogon,1144 (rop::WrongServer),00:00:00…,"Logon: Public, …-PublicFolders in database …; Redirected: guid 00000000-0000-0000-0000-000000000000 from rpcServerTarget  is different from public folder mailbox guid 94606287-5604-4873-abc7-91693cab7a4e to which the client intends to logon, suggested new server: …,RopHandler: Logon: ,,

  105. Raevmi says:

    Someone an idea what is going wrong whit the update?

    Error:

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

             $feVdirName = "PowerShell (Default Web Site)";

             $beVdirName = "PowerShell (Exchange Back End)";

             $vdirName = "PowerShell";

             $InternalPowerShellUrl="http://&quot; + $RoleFqdnOrName + "/powershell";

             get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

             new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccessPowerShell-Proxy");

             new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

           " was run: "The virtual directory 'PowerShell' already exists under 'server01.zabicki.local/Exchange Back End'.

    Parameter name: VirtualDirectoryName".

    Thanks

  106. ABCFED says:

    Just experienced this issue upgrading from Exchange CU2 to CU3 2013. The SMTP receive connector intermittently would stop working and start sending out a "4.3.2 service not available" error. Had to delete and re-create the "default fronted hub transport" receive connector.

    The issue and fix were identical to this:

    social.technet.microsoft.com/…/exchange-2013-stops-receiving-external-email-after-about-8-hours

  107. ABCFED says:

    One more thing. After updating to CU3 I had to re-adjust the IIS active sync to allow for windows authentication after applying CU3. Clients were popping up asking for credentials.

    Seems fairly stable now.

  108. @Eric – We will include a workaround for the FireFox Version 24 issue in the SP1 release.  We have also reported this issue to FireFox development team.

  109. My transport rule, which uses regex ^$ for subject to catch emails with empty subjects, stopped working since I installed CU2. I installed CU3 recently – still it does not work. Is that a known bug? How should I report it?

  110. Gerard says:

    CU3 itself does seem stable, getting it installed was a huge challenge!

    The first challenge was to get past the "Prerequisite Analysis", because it kept complaining about mscorsvw having open files, with a different process id's each time I retried this. Eventually it would continue.

    It seems that upgrading CU2 to CU3 through the GUI setup is broken. We tried this on two servers, and on both we got this warning after the step that uninstalls the old version:

    "An unexpected error has occurred and a Watson dump is being generated: A reboot is required to complete file operations on '{4934D1EA-BE46-48B1-8847-F1AF20E892C1}'.  Reboot the machine, and then run setup again."

    After rebooting the machine and running setup again, it would then quit immediately after checking to see if enough space is available. The log files contain no indication about the cause.

    After the GUI install had failed running setup with /mode:Upgrade did seem to work, but this would eventually crash with some PowerShell error, so Exchange was basically not upgradable anymore.

    Fortunately I had created a checkpoint for our production Exchange VM, so I could rollback. Then I ran setup /mode:Upgrade and this ran without errors. Well almost…

    Of course I had the usual crash in the Mailbox services role because the DiscoverySearchMailbox exists, I still have to delete this mailbox before every upgrade and re-create it afterwards. An issue that many people encountered and reported, but which the Exchange team apparently doesn't think is important enough to fix. I've had this since Exchange 2010 SP1.

    We had a couple of users (both Outlook 2010 and 2013) that were unable to connected to certain shared mailboxes after installing CU3. Usually repairing or recreating the profile in Outlook fixed this, but still strange..

    After the installation I noticed that the ExternalUrl for the ActiveSyncVirtualDirectory was empty, causing issues for new employees that tried to configure mail on their phone. Strange that the Get-ActiveSyncVirtualDirectory reports an "IsValid : False".. even after deleting and recreating the virtual directories. They do work though.

  111. Marco Novelli says:

    Update from CU2 to CU3 was super-slow but successful

    I had the (little) issue with ExternalUrl for the ActiveSyncVirtualDirectory empty

  112. Crystal Chadwick - Sr. Exchange Admin says:

    I just did the upgrade from CU2 to CU3 last night on six Windows 2012 servers and I didn't have issues on any of them except one, and it was related to Trend Micro restarting itself during the install after I had unloaded it hours before.  After that the gui install would just crash a few checks in even after restarting the system so I was getting pretty worried.  I played around with the windows SMS Agent Host service and Windows Installer service, and eventually got the gui to run again.  The app event log tipped me off to those services.  After that little hiccup, and after it took about an hour to install on some of my servers, I am pretty relieved to have it running in my mixed 2010 and 2013 environment without any issues today.  

    I took the following precautions to avoid any issues:  I set the execution policy to unrestricted on each system, I ran setup 'as administrator' and I completely unloaded Trend Micro before running.  I also noticed it would not start the install if I had an Exchange powershell window open, so I recommend logging off any other users who might have an instance running as well.  I'm the only Exchange admin in my company so I didn't have to worry about that but I could see it possibly being an issue.

    I did not experience the issue with the discoverysearchmailbox that Gerard mentioned, and my external URL for activesync was not altered.  

  113. * Please enter a name says:

    Nico,

    So you are saying that just by installing the Failover Clustering, if it is not utilized by an Exchange DAG, the update will fail? Is there any way to bypass this check? It is difficult to understand how the product was released in the state it is in currently. Is it just a dead on scramble to barely make your release dates with Exchange 13 or what is the mixup?

  114. Kevin Nelson says:

    How much memory for the MSExchangeRPCPorxyAppPool consume? In CU2 there was a memory leak in the app pool that kept causing our Exchange servers to have performance issues and support confirmed it as a bug and assured us it would be fixed in CU3. Now that I have applied CU3 after running for 3 days this app pool is at 5gb or RAM and rising. Is this expected behavior? I would love to know what others are seeing.

  115. ANOO says:

    Absolut det är inte tillgänglig på en sidan. Exchange Server det behövs så många sidor till om man klara eller inte. Eller hur?

Comments are closed.