A quick heads-up that when you are running Exchange Server 2013, you should not install or update to .NET Framework 4.6. This version of the .NET framework is not only not supported, it may also cause your Exchange 2013 server to stop functioning correctly.
When you have updated from a previous version, a suggested workaround is to uninstall .NET Framework 4.6. However, with all the dependencies on the .NET Framework by Exchange Server, it maybe preferred, when you did install version .NET Framework 4.6, to migrate contents, i.e. mailboxes etc., to a new Exchange 2013 server, and decommission the one you installed .NET 4.6.
The Exchange Team released Cumulative Update 10 for Exchange Server 2013 (KB3078678) as well as Rollup 11 for Exchange Server 2010 Service Pack 3 (KB3078674). These version levels will be required for co-existence with Exchange Server 2016, which is to be released at a later date. The updates raise the version numbers to 15.0.1130.7 and 14.3.266.1, respectively.
Cumulative Update 10 contains the following fixes for Exchange Server 2013:
KB 3087126 MS15-103: Description of the security update for Exchange Server: September 8, 2015
KB 3094068 Permissions for a linked mailbox are added to an account in the wrong forest in an Exchange Server 2013 environment
KB 3093884 The link in a quarantined email shows an empty list for ActiveSync-enabled devices 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 3087571 Can’t edit or resend a delayed delivery message when you open the message from the Outbox folder in Exchange Server 2013
KB 3087293 “550 5.6.0” NDR and duplicated attachments when an encrypted email is sent in Outlook in Exchange Server 2013
KB 3080511 HTML forms aren’t available when the DisableFilter parameter is enabled in Outlook Web App in Exchange Server 2013
KB 3080221 LegacyExchangeDN attribute is displayed when you use Outlook Web App to view an appointment in Exchange Server 2013
KB 3079217 Outlook Web App replies to the wrong email address when an email has more than 12 recipients in Exchange Server 2013
KB 3078966 Outlook 2011 for Mac client displays emails as they come from the same senders in Exchange Server 2013
KB 3078443 Incorrect results are displayed when you search for an email that has a certain attachment name in Exchange Server 2013
KB 3078438 Performance issues occur in an Exchange Server 2013 environment that’s running BlackBerry Enterprise Server 5
KB 3078404 Can’t access a shared mailbox after you migrate from Exchange Server 2010 to Exchange Server 2013
KB 3076257 EWS returns a Success response code even if a batch deletion request isn’t completed in Exchange Server 2013
KB 3074823 No Send As audit events are logged when you use Send As permission in Exchange Server 2013
KB 3071776 “A problem occurred” error when you access shared folders in Exchang Server 2013 mailbox by using Outlook Web App
KB 3069516 Mailbox size and quota information are reported incorrectly in Outlook and Outlook Web App in Exchange Server 2013
KB 3061487 “FailedToGetRootFolders” error when you run an eDiscovery estimate search for archive mailboxes in Exchange Server 2013
KB 3058609 Wrong recipient is specified in an inbox rule that has the ForwardTo or RedirectTo option in Exchange Server 2013
KB 3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013
KB 2999011 Documents are partially indexed by Exchange search when they embed other documents in Exchange Server 2013
KB 2983161 Organization unite picker is missing when you create a Remote Mailbox in Exchange Admin Console in Exchange Server 2013
KB 3091308 Can’t install cumulative updates or service packs when MachinePolicy or UserPolicy is defined in Exchange Server 2013
For Exchange Server 2010 SP3, Rollup 11 contains the following fix:
KB 3092576 Exchange 2010 Information Store crashes randomly
Notes:
When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay current.
If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.
This Cumulative Update does include Active Directory changes when compared to the previous Cumulative Update. If you have deployed a version earlier than CU10, make sure you run setup /PrepareAD.
If you got an Exchange 2010 DAG, and want to properly update the DAG members, check the instructions 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 Exchange 2013 servers is irrelevant, unlike with previous generations of Exchange. Exchange 2010 Rollups are cumulative per service pack level, i.e. they contain fixes released in earlier updates.
You can download Exchange 2013 Cumulative Update 10 here and Exchange 2010 SP3 Rollup 11 here. The Exchange 2013 CU10 Language Packs are available here.
Exchange Server 2013 and Exchange Server 2016 enforces certain message size limits when it comes to client messages. These limits are in-place so clients can’t generate excessive load on your Exchange environment. These limits are determined for various access methods in multiple web.config files on Exchange Client Access Servers as well as Mailbox Servers.
Sometimes you may have good reasons to increase those limits. For example, when migrating to Office 365 using a product like MigrationWiz, you may want to increase the limit for Exchange Web Service (EWS) requests to allow for migration of larger items. Another example is when you want to allow for bigger attachments in Outlook WebApp (OWA). On TechNet, there’s an article on how to reconfigure these limits. However, the process consists of editing multiple web.config files, replacing multiple values in the same file, and following this process on each Exchange 2013/2016 server in your environment. This is not only labor intensive and prone to error, but becomes tedious when you consider that each Cumulative Update will overwrite your web.config files.
But do not despair. To execute these changes for OWA and EWS, I have created a PowerShell script which will perform these tasks for you.
Requirements Using the script requires Exchange 2013. You need to provide the server name (default is local server) or AllServers to apply to all Exchange 2013/2016 servers in your environment. The script will modify the web.config remotely using the system share (e.g. C$), using the location of the Exchange installation, and uses IISRESET tool to restart IIS. It will create a backup of the web.config before modifying it.
Notes:
The script checks for running in elevated administrator mode when running against the local machine.
Current version of the script requires Exchange Management Shell, to run Exchange cmdlets for checking installed roles a.o., as the web.config files which require editing depend on the installed roles.
For OWA, add ~33% to the value you want to specify to compensate for encoding overhead.
When connected to an Exchange server, the script processes the server hosting the EMS session last to prevent abortion caused by IIS reset.
Script currently runs against Exchange 2013 or Exchange 2016.
Usage The script Configure-ClientSizeLimits.ps1 uses the following syntax:
The Exchange team published an update for the Exchange 2013 Server Role Requirements Calculator as well. The new version number is 7.6.
Changes since version 6.6:
Added support for ReplayLagManager
Added support for PreferredMaximumActiveDatabases
Added new table that exposes theoretical CPU utilization for each mode (normal runtime, first server failure, second server failure, site failure, site failure + 1 failure)
Added Restore-DatabaseAvailabilityGroup scenario support in Distribution algorithm
Added warning about designs that include more than24 processor cores / server and 96GB of memory
Added support for DAGs without Administrative Access Point (default behavior is no administrative access point) in the CreateDAG script
Changed default for Deleted Item Retention in export file to be the highest profile value for Deleted Item Retention
Changed default for Circular Logging in export file to be true when using Exchange Native Protection
Added ability to save scripts and CSV files to OneDrive for Business
Fixed CreateDAG.ps1 script error for DAG creation without administrative IP address
Modified CreateMBDatabases.ps1 to ignore CircularLogging choice and modified CreateMBDatabaseCopies.ps1 to enforce CircularLogging choice
Fixed Export DAG list function to use the correct value for MaximumActiveDatabases
Added support for MaximumPreferredActiveDatabases and AutoDatabaseMountDial in Export DAG List function and createdag.ps1
Modified CreateMBDatabaseCopies.ps1 to remove sleep timer, improving copy creation significantly
Fixed createdag.ps1 to not generate an error when there is no alternate witness server provided
Fixes since version 6.6:
Fixed an issue that prevented the calculator from displaying results when site resilience was disabled while Active/Active (Single DAG) was selected
Changed Processor Cores/Server to not use a list drop down, thereby enabling customers to enter in configurations they are deploying.
Fixed bugs in Diskpart script with PrepareAutoReseedVolume switch and WhatIf processing
Fixed bug in Diskpart with escaping quotes in some languages
Fixed bug with display of lag copies in single site design
Fixed multiple databases / volume calculation to take into account symmetric designs that utilize an odd number of servers in a single site
Fixed scenario to count number of servers in A/P scenario where the only copy deployed in DR is a lagged copy
Fixed #NAME error in Database Copy Configuration table for standalone configurations
Updated DC1 memory sizing to take into account site failure mode for A/A (Single DAG) designs involving a 2 copy architectures
Updated Distribution Tab error reporting and Lastrow calculation
Fixed copy count validation formula for site resilient scenarios to not allow more copies in the primary datacenter than the number of servers
Added support for 10TB and 12TB capacity disks
Fixed run-time error on distribution tab when disabling site resilience
Fixed distribution error when disabling cross-site failover
Fixed bug in Distribution tab ActiveServer formula when modeling Cross Site Failover behavior
Fixed an issue with the distribution tab throwing an error when two files were opened at the same time
Fixed distribution algorithm where lagged copies were not always represented correctly
Blocked unsupported A/A (Single DAG) scenario where copy count is not the same in both datacenters
You can download the calculator here. For more information, please consult the list of changes here or Read Me here.
The Exchange Team released Cumulative Update 9 for Exchange Server 2013 (KB3049849). This update raises Exchange 2013 version number to 15.0.1104.5.
Cumulative Update reintroduces configuration of sent items for shared mailboxes, as was possible in Exchange 2010 but wasn’t available in Exchange 2013 yet. More information here.
Next to a security fix for MS15-064, this Cumulative Update contains the following fixes:
KB2983216 Category setting on an item in Outlook jumps the selection to the top of the list in an Exchange Server 2013 environment
KB2988660 Role assignment with custom write scope fails in an Exchange Server 2013 environment
KB3003978 Email messages are displayed with incorrect format in Outlook in an Exchange Server 2013 environment
KB3006849 GSSAPI-based Kerberos authentication protocol is not offered to IMAP clients in Exchange Server 2013
KB3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013
KB3032153 Recurring events in Calendar over DST are not adjusted on all ActiveSync devices in all Exchange Server environments
KB3040681 MapiExceptionTimeout error during a hierarchy synchronization process of multiple public folders in Exchange Server 2013
KB3040683 System WLM overrides do not work when you do on-premises installations in Exchange Server 2013
KB3049081 OwaDeepTestProbe probe fails intermittently on a server that installs the Mailbox server role in Exchange Server 2013
KB3049771 Outlook Web App logon page takes longer time than expected to time out in an Exchange Server 2013 environment
KB3050825 EdgeTransport.exe starts to crash when PriorityQueuingEnabled is set to “True” in Exchange Server 2013
KB3050877 Emails that are sent as a secondary mailbox are not saved in the delegate’s Sent Items folder in Exchange Server 2013
KB3055940 “Object reference not set to an instance” error when you install cumulative update in Exchange Server 2013
KB3056045 “Cannot find Template User object” error when you find contacts that use a consumer domain in Exchange Server 2013
KB3056133 Exchange Server 2013 Activation time of transport rule is not displayed in UTC time
KB3056413 SMTP connection fails when you log on with a child domain account and use NTLM authentication in Exchange Server 2013
KB3056817 Update adds the Let me select the message option in Outlook Web App in an Exchange Server 2013 environment
KB3056822 Dynamics CRM 2013 stops synchronizing items from mailbox in an Exchange Server 2013 environment
KB3060825 The MSExchangeDelivery service crashes when you receive an email message from a specific sender in Exchange Server 2013
KB3064393 “Bad Command. 12” error and IMAP CAPABILITY commands are not offered in an Exchange Server 2013 co-existence environment
KB3068681 RPC encryption requirement is re-enabled for RPC Client Access Service after you upgrade server in Exchange Server 2013
KB3069060 Recurring meetings are accepted when their time conflicts on the same room mailbox in Exchange Server 2013
KB3069501 Duplicate folders are created after a mailbox move in Exchange Server 2013 Enterprise
KB3071427 Outlook Web App still downloads web beacon contents when you forward email messages in Exchange Server 2013
Notes:
If the new Set-Mailbox parameters for Sent Items configuration, i.e. MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled, are not available after installing this CU, run Setup /PrepareAD /IAcceptExchangeServerLicenseTerms explicitly.
When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay current.
Previously released CU7 introduced changes to prevent restoration of pre-CU7 databases. Pre-CU7 users are advised to perform a full backup post-upgrade to CU7 or later.
Previously released CU7 added support for hierarchies containing 250,000 modern public folders. Consult this article for co-existence scenarios.
This Cumulative Update does not include schema or Active Directory changes when compared to Cumulative Update 7. If you have deployed a version earlier than CU7, 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 8 here; UM Language Packs can be found here.
A quick heads-up that when you are running Exchange Server 2013, you should not install or update to .NET Framework 4.6. This version of the .NET framework is not only not supported, it may also cause your Exchange 2013 server to stop functioning correctly.
EighTwOne (821) 