The Exchange Team released Cumulative Update 11 for Exchange Server 2013 (KB3099522). This update raises Exchange 2013 version number to 15.0.1156.6.
Apart from a Daylight Savings Time update, documented here, this Cumulative Update contains the following fixes:
- KB 3120594 Appointment on the Outlook calendar isn’t updated to a meeting when attendees are added
- KB 3108345 “The app couldn’t be downloaded” error occurs when you try to install an application from the Intranet in Exchange Server 2013
- KB 3108011 Error message occurs in Outlook after you change a single instance of a recurring meeting by using an iOS device
- KB 3107781 Exchange ActiveSync device doesn’t keep messages for 30 days as configured
- KB 3107379 Noderunner.exe consumes excessive CPU resources by parsing an attached document in Exchange Server 2013
- KB 3107337 Mailbox migration from Exchange Server 2007 to Exchange Server 2013 is very slow
- KB 3107291 Exception occurs when you run the Invoke-MonitoringProbe cmdlets to set probes for IMAP and POP3 in Exchange Server 2013
- KB 3107205 “Custom error module does not recognize this error” error when OWA web parts fail to load
- KB 3107174 Pages that use the People pop-up URL don’t load in Chrome when you access OWA or the Exchange Server Administration Center
- KB 3106613 Outlook Web App shows partial contacts in an Exchange Server 2013 environment
- KB 3106475 POP3 and IMAP4 are not supported to use TLS protocol 1.1 or 1.2 in Exchange Server 2013
- KB 3106421 Very long URLs in an email message do not open in OWA in Internet Explorer
- KB 3105760 Exchange Server 2016 mailbox server can be added to an Exchange Server 2013 DAG
- KB 3105690 Outlook clients that use MAPI over HTTP to connect to Microsoft Exchange Server 2013 mailboxes are intermittently disconnected
- KB 3105685 The lsass.exe process leaks an amount of handles in Exchange Server 2013
- KB 3105654 Cannot edit Inbox rules in Outlook Web App by using Chrome
- KB 3105625 ActiveSync device downloads emails while it’s in quarantine in an Exchange Server 2013 environment
- KB 3105389 WSMan-InvalidShellID error when you create remote PowerShell sessions in an Exchange Server 2013 environment
- KB 3100519 No responses are sent from a room mailbox when a booked meeting extends beyond the date you set in Exchange Server 2013
- KB 3093866 The number of search results can’t be more than 250 when you search email messages in Exchange Server 2013
- KB 3088911 Inline attachments are sent as traditional when you smart forward an HTML email in an iOS device in Exchange Server 2013
- KB 3088487 IOPS Write increase causes email delivery delays in an Exchange Server 2013 environment
- KB 3076376 IMAP clients that use Kerberos authentication protocol are continually prompted for credentials in Exchange Server 2013
- KB 3068470 “Something went wrong” error in Outlook Web App and ECP in Exchange Server 2013
- KB 3048372 Exchange Calendar items are shifted incorrectly when some Windows DST updates are applied
- KB 2968265 OWA cannot be accessed after you upgrade Exchange Server 2013
Notes:
- This CU introduces an important change in the mechanism how Exchange Management Shell sessions will be initiated as of Exchange 2013 CU11 (and to be introduced in Exchange 2016, as well), called Mailbox Anchoring. More on this later in this article.
- When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay current (version N) or be one version behind (N-1).
- Cumulative Update may include schema or Active Directory changes (e.g. Role-Based Access Control). Make sure you run PrepareSchema /PrepareAD. If you want to speed up the Cumulative Update installation process, you can temporarily disable certificate revocation checking as described here.
Note that Cumulative Updates can be installed directly, i.e. no need to install RTM prior to installing Cumulative Updates. Note that once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles. The order of upgrading servers is irrelevant, unlike with previous generations of Exchange.
Finally, and I can’t emphasize this enough: For any Hotfix, Rollup, Service Pack or Cumulative Update, I’d recommend to thoroughly test this in a test and acceptance environment first, prior to implementing it in production. When you lack such facilities, hold out a week or two and monitor the comments on the release article or TechNet forum for any issues.
You can download Exchange 2013 Cumulative Update 11 here; UM Language Packs can be found here.
MAILBOX ANCHORING
This CU introduces an important change in the administrative model. In short, you need to home your administrative mailbox on the Exchange platform level you want to administer Exchange from (mailbox anchoring), as you will connect (or be proxied) to an Exchange Management Shell (EMS) session on that host. In other words, use an administrative account with a mailbox on Exchange 2013 to administer Exchange 2013, use an admin mailbox on Exchange 2016 for Exchange 2016. The logic behind this is to work around mixed-version environment issues, as newer Exchange versions may introduce changes, like new or enhanced cmdlets but also deprecated functionality. New general recommendation is to keep arbitration mailboxes as well as administrative mailboxes on the most current version.
If the admin has no mailbox, or if it’s unavailable, arbitration mailboxes – primarily SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} – are considered for hosting your EMS session. Also, that ‘Connected to <Server>’ message when you open up an EMS session will no longer always mean your EMS session is hosted on that server; it could mean your EMS session is being proxied through there, which can create challenges when you’re running multiple sites with low bandwidth links – you may need to move your admin mailbox around or create one for local administration to enjoy better response times. You can only discover which host your session runs on by inspecting the local environment, using elements like the env:COMPUTERNAME variable or [System.Net.Dns]::GetHostName().
Also, it might be wise to spread administrative mailboxes over different servers or databases, in case your arbitration mailboxes become unavailable together with that one administrative mailbox, as you need to recover one of those just so you can set up an EMS session. The last resort for running an EMS cmdlets – against all best practices and recommendations, as it bypasses Role-Based Access Control for example – is to load the Exchange module using Add-PSSnapIn. But be advised, you may not have all required permissions, for example your admin account may not have direct Active Directory permissions (and which is one of the reasons you shouldn’t just load the snap-in under normal circumstances).
The Exchange Team put up a separate blog to explain this change in behavior here.
Like this:
Like Loading...
The Exchange team published an update for the Exchange Server Role Requirements Calculator, the tool to aid you in properly sizing your Exchange Server 2013 or Exchange Server 2016 deployment.![iTunes-Podcast-logo[1]](https://eightwone.files.wordpress.com/2012/07/itunes-podcast-logo1-e1341277366970.png?w=584){kind=logo}
Episode 60
