-->

Tuesday, August 26, 2014

Exchange 2010 SP3 RU7 and Exchange 2013 CU6 Have Been Released

MS has released Exchange 2010 SP3 RU7 and Exchange 2013 CU6 (26AUG14).

For Exchange 2010 SP3 RU7:

You can grab it
here, and of course the normal order of install is the same:

1. CAS (with internet-facing first)
2. Hub Transport and Edge Servers
3. Mailbox servers
4. Unified Messaging servers

Here's a list of fixes in 2010 SP3 RU7:
 

  "HTTP 400 - Bad Request" error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment
  Outlook Web App logon times out in an Exchange Server 2010 environment
  Event 4999 is logged when the World Wide Web publishing service crashes after you install Exchange Server 2010 SP3
  Email messages that contain invalid control characters cannot be retrieved by an EWS-based application
  S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment
( Email attachments are not visible in Outlook or other MAPI clients in an Exchange Server 2010 environment
  eDiscovery search fails if an on-premises Exchange Server 2010 mailbox has an Exchange Online archive mailbox
  Assistant stops processing new requests when Events in Queue value exceeds 500 in Exchange Server 2010
  S/MIME certificates with EKU Any Purpose (2.5.29.37.0) are not included in OAB in Exchange Server 2010
  Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010


For Exchange 2013 CU6, grab it
here, and the install order is the reverse of Exchange 2010, but internet-facing servers are still first:

1. Mailbox Servers
2. CAS Servers
3. Edge Servers

Here's a list of fixes in 2013 CU6:
  Duplicate mailbox folders after migration to Exchange Server 2013
  Hybrid Configuration wizard error "Subtask CheckPrereqs execution failed" for Exchange Server 2013
  EMS takes a long time to execute the first command in an Exchange Server 2013 Cumulative Update 5 environment
  RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
  AutodiscoverSelfTestProbe fails when external URL is not set for EWS virtual directory in Exchange Server 2013
  AutodiscoverSelfTestProbe fails when external URL is not set for ECP virtual directory in Exchange Server 2013
  The ServerWideOffline component is set to Inactive after Exchange Server 2013 prerequisite check fails
  "532 5.3.2" NDR when you send an email message to a hidden mailbox in an Exchange Server 2013 environment
  Removed Default or Anonymous permission for Outlook folders cannot be restored in an Exchange Server 2013 environment
  "Topology service cannot find the OWA service" when you perform an eDiscovery search in Exchange Server 2013
 Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
  OAB generation arbitration mailbox can be removed or disabled in an Exchange Server 2013 environment
  The Enter key submits duplicate sign-in forms to Outlook Web App in an Exchange Server 2013 environment
  You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
  Incorrect voice mail message duration in an Exchange Server 2013 environment
  You cannot add attachments, delete or move many email messages in bulk in Outlook Web App
  MAPI/CDO client cannot connect to Exchange Server 2013
  You cannot disable journaling for protected voice mail in an Exchange Server 2013 environment
  Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
  Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment
  OAB generation fails if FIPS is used in an Exchange Server 2013 environment
  Blank page after you sign in to Exchange Server 2013 EAC (formerly ECP)
  Folder Assistant rule does not work correctly in an Exchange Server 2013 environment
  EAS device cannot sync free/busy status if an item is created by EWS in an Exchange Server 2013 environment
  Message routing latency if IPv6 is enabled in Exchange Server 2013
  "Something went wrong" error in Outlook Web App may show an incorrect date
  Users cannot access mailboxes in OWA or EAS when mailbox database is removed

No comments:

Post a Comment