Exchange 2010 SP3 RU3 and 2013 CU3 Released & Known Issues


3/4/14: Blog Post: Known Issues with 2013 SP1
12/4 Update:
Added Known Issues list at the end

Today, after a few delays, both Exchange 2010 SP3 RU3 and Exchange 2013 RTM CU3 have been release! For more details on CU3 and a bit of a backstory on this release and the general quality issues Microsoft has had with Exchange recently see Tony Redmon’s post here: http://windowsitpro.com/blog/seeking-quality-exchange-2013-cu3

Exchange 2010 SP3 RU3: Download | KB2891587 | EHLO Blog Post
Exchange 2013 RTM CU3: Download | KB2892464 | EHLO Blog Post

I haven’t seen much about what updates are in 2010 SP3 RU3, but when I do find them I will update this blog.

For Exchange 2013 RU3 there are several key updates:

  • AD schema updates (so plan accordingly)
  • Addresses issues with 3rd party backup software, see KB2888315 for more details
  • Windows 8.1/IE11 no longer require the use of OWA Light
  • Usability improvements when adding members to new and existing groups in the Exchange Administration Console
  • Online RMS available for use by non-cloud based Exchange deployments
  • Improved admin audit log experience

The What’s New in Exchange Server 2013 and Release Notes should also be updated shortly to reflect changes in 2013 RTM CU3.

Note: Make sure you set PowerShell execution policy to “Unrestricted” before installing 2013 RU3, see KB981474 for details and steps.

Microsoft has also publicly stated that the next update to Exchange 2013 will be SP1 in early 2014 (aka as CU4). SP1 will provide Windows 2012 R2 support, S/MIME support in OWA, Edge Transport Server Role, and the various fixes and improvements expected in a SP. The Exchange Team also posted this EHLO blog: Exchange Server: The Road Ahead to dispel any myths that there won’t be an E16 or higher on-premise version.

  •  CU are basically a Service Pack that may include new features, but those features may not be documented. CU & SPs for Exchange 2013 are FULL installs, or in-place upgrades, with no un-install support. So make sure you test the CU2 BEFORE installing them in production. Microsoft is calling CU4 a “Service Pack” because this is the first time they are documenting new features and changes that were in the previous CUs. In addition, there are lifecycle requirements tied to “Service Pack” updates.

Reminder:  Customers in hybrid deployments where Exchange is deployed in-house and in the cloud, or who are using Exchange Online Archiving with their in-house Exchange deployment are required to maintain currency on Cumulative Update releases

Known Issues
Like before this is the list of issue I AM aware of, not an official list from  Microsoft. For my previous known issues with Exchange 2013 CU2 see: https://blog.jasonsherry.net/2013/07/09/exchange-2013-rtm-cu2-released/. I’ll add more details and linked to Technet Forums and KBs later this week. Comment on any issues you have come across that you are pretty sure is a bug based on others having the same issue, please include a link to TechNet forums post on the topic.

  • I need to review my CU2 issues list and check which of these issues CU3 resolves. On my to-do list 🙂
  1. Critical: 12/4 Outlook (all version) on Windows XP cannot access Exchange 2013 CU3 modern Public Folders, when their mailbox is on 2013 CU3 server
    • Only critical if you have Windows XP clients, which many organizations still do
    • Workaround: Have users use OWA or W7+ workstation
  2. Important: 12/4 Availability (Free/Busy) and OOF not working after installing KB2837618 or KB2825677 for mailboxes on Exchange 2007 in Outlook 2013
    •  The November Outlook 2013 KB2837618 security update, also in OL13 Oct update KB2825677 breaks Outlook 2013 if the user’s mailbox is on Exchange 2007
      • This issue is new to CU3
      • KB2825677 is now in Windows Update, so if you have Exchange 2007 you need to remove this update!
      • Users will see “Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later” error message when they click on their Automatic Replies (Out of Office) button.
    • Workaround: Remove updates and recreate Outlook profile, just removing the update doesn’t fix the issue
  3. Important: 12/4 Severe performance problems with IE8 and FF24 on Windows XP
  4. Important: 12/4 EAS proxy breaks after EAS App Pool crashes repeatedly
    • This is an issue with Exchange 2013 (RTM – CU3) when it is proxying EAS traffic to Exchange 2007 or 2010 based mailboxes
    • You will see Event ID 4999 | Error | MSExchange Common | With “Watson reported…” in the details
    • I’ve seen this issue at two clients, who were migrating from 2007 to 2013. In both cases users weren’t noticing any issues.
      • After migrating the last mailboxes to 2013 these errors went away
  5. Moderate: 12/4 EAS ExternalURL & InternalURLs for EAS are cleaned after installing CU3
    • This has been an issue since 2010 when doing a recovery operation and when installing 2013 CU1 and higher. I don’t recall which URLs are wiped but as a standard policy I create a “Set-URLs.ps1” script that I run after installing the CUs, and on initial setup
      • See Jeff Guillet’s post for more details on the history of this issue: bit.ly/1jmOg4l
    • Workaround: Reset them
      • CU1 & CU2 also cleared the OWA & ECP URLs, so at least those were fixed in CU3
  6. Minor: 12/4 Certificate based authentication not working
  7. Minor: 4/2/13 Exchange XML application configuration files are overwritten during cumulative update installation
    • Any customized per-server settings you make in Exchange XML application configuration files, for example, web.config files on Client Access servers or the EdgeTransport.exe.config file on Mailbox servers, will be overwritten when you install an Exchange Cumulative Update (CU). Make sure that you save this information so you can easily re-configure your server after the install. You must re-configure these settings after you install an Exchange CU.
    • From Release notes page

About jasonsherry

I am a 20 year Exchange consultant and expert. I currently work for Commvault as a Solutions Specialist for Microsoft Infrastructure For more info see my resume at: http://jasonsherry.org
This entry was posted in Exchange, Microsoft and tagged , . Bookmark the permalink.

10 Responses to Exchange 2010 SP3 RU3 and 2013 CU3 Released & Known Issues

  1. Pingback: Known Exchange 2010 SP3 RU2 issues | Jason (Izzy) Sherry's Blog

  2. Pingback: Exchange 2013 RTM CU2 released (Again on 7/29) & Known Issues | Jason (Izzy) Sherry's Blog

  3. Pingback: Microsoft Has Improved Exchange 2013 Quality, Has a Tough Road Ahead

  4. Nice article, but it needs some more attention. Don’t mix the RU3 CU3 words, it’s confusing. And SP1 early 2013? I need to find that download link! 🙂

    Like

    • jasonsherry says:

      Fixed the Early 2013 to say 2014. As for the RU3 and CU3, etc Microsoft calls the update roll-ups for 2007 & 2010 Roll-Ups but for 2013 they call them Cumulative Updates. I agree this is confusing.

      Like

  5. CU3 says:

    We have a customer that get their mail stuck in the outbox after the upgrade (for a while). They are running windows XP with office 2010 (Yes they runned into the modern public folder issue). If they hit Send/receive it say outlook needs to be connected. Although the indicator at the bottom right is saying that its connected. Have you seen this problem.

    Like

    • jasonsherry says:

      I’ve seen this issue, mostly commonly with the Transport service no picking up the e-mail to do various reasons across many versions. If the Transport Service is stopped message will set in the Outbox on Outlook and Drafts on OWA. But there isn’t a “known” issue with this in general with any release that I’m aware of.

      Like

  6. Mark says:

    Jason – Have you heard of anybody talk of their message tracking log formats changing with CU3? Specifically the file name of the hub transport tracking logs?

    Like

    • jasonsherry says:

      Yes they have changed, I had to ask around since I haven’t noticed this since I use cmdlets to get data from them and rarely look directly at the files.

      Like

  7. Pingback: Known Issues with Exchange 2013 SP1 | Jason (Izzy) Sherry's Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s