Exchange 2013 CU6, 2010 SP3 RU7, & 2007 SP3 RU14 released & Known Issues


12/9/14 Update: 2013 CU7, 2010 SP3 UR8, & 2007 SP3 UR14 have been release:
https://blog.jasonsherry.net/2014/12/09/exchange-2013-cu7-2010-sp3-ur8-2007-sp3-ur15-released/

9/16/14 Update: Chrome 37 issue added
9/2/14 Update: More known issues added
8/31/14 Update: Do NOT install 2013 CU6, when co-existing with Exchange 2007, until you have this hotifx: KB2997209 or if you have or want to setup a hybrid relationship with O365 until you have KB2997355. See known issues for more details.
8/29/14 Update:  Known Issues added below. Microsoft released new updates packages for Exchange 2013 CU6 (2961810), 2010 SP3 RU7 (2961522), & 2007 SP3 RU14 (2936861) today. For full details see the Exchange Team’s EHLO post: http://blogs.technet.com/b/exchange/archive/2014/08/26/released-cumulative-update-6-for-exchange-server-2013.aspx

2013 CU6                   Download | KB2961810 | EHLO Post
2010 SP3 RU7            Download | KB2961522 | EHLO Post
2007 SP3 RU14          Download | KB2936861 | EHLO Post

Like all CUs for 2013 this one is also a full version of Exchange that can be installed as a 1st time install or will upgrading an existing install of 2013. Key updates in 2013 CU6 are the increase of Public Folder scalability to 100,000 folders, more info here, and a fix for the issue with the Hybrid Configure Wizard (HCW) failing on 1st run or when attempting to modify the settings, see KB2988229 for more info on the HCW issue. Like many of the CUs, CU6 also updates the AD schema. For more info on 2013 CU6 see Tony Redmond’s post here: http://windowsitpro.com/blog/exchange-2013-cumulative-update-6 Like all CU/RUs these contain the recent fixed and security updates, in additional all three contains the latest DST updates. I will add a known issues section to this post when I come run into or hear about issues with these updates.

2013 CU6 Known Issues:

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 and tagged , , . Bookmark the permalink.

6 Responses to Exchange 2013 CU6, 2010 SP3 RU7, & 2007 SP3 RU14 released & Known Issues

  1. Pingback: Ex2013 CU6 & Ex2007 coexistence issue for EAS | EighTwOne (821)

  2. Hi Jason,

    We have also picked up another issue:

    All our CU6 mailboxes have severe issues when using the Web App – Certain buttons do not work at all and the calendar, people and task buttons result in an endless “Loading…” page. When moving a user back to a CU5 mailbox server the problems are resolved…

    We have logged this with MS.

    I’m very disappointed with this release – We were severely impacted by the EAS issue for over a week not to mention the store crash problem…

    Like

    • jasonsherry says:

      Do you also have Exchange 2007 based mailboxes? Only store crash issue I’ve heard of is with co-existence with 2007.

      Different issue, but Chrome 37 breaks multiple OWA & ECP options. Haven’t heard about “Loading” issue yet.

      Like

  3. Pingback: Exchange 2013 CU7, 2010 SP3 UR8, 2007 SP3 UR15 released | Jason (Izzy) Sherry's Blog

  4. anon says:

    After applying CU7, I get this error then Exchange never recovers. Help?!

    Error:
    The following error was generated when “$error.Clear();
    upgrade-ExchangeServer -Identity $RoleFqdnOrName -DomainController $RoleDomainController

    ” was run: “Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn’t be performed because object ‘dc.domain.com’ couldn’t be found on ‘dc.domain.com’.
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory)
    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError)
    at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.UpgradeExchangeServer.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

    Like

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