The Exchange team today announced the availability of Update Rollup 13 for Exchange Server 2010 Service Pack 3. RU13 is the latest rollup of customer fixes available for Exchange Server 2010. The release contains fixes for customer reported issues and previously released security bulletins.
This is build 14.03.0294.000 of Exchange 2010, and KB3141339 has the full details for the release. The update file name is Exchange2010-KB3141339-x64-en.msp.
Note that this is only for the Service Pack 3 branch of Exchange 2010. Why? Exchange 2010 SP2 exited out of support on the 8th of April 2014 and will no longer receive updates. Customer must be on Exchange 2010 SP3 to receive updates.
Also note that Exchange 2010 transitioned into its Extended product support lifecycle phase on the 13th of January 2015. Exchange 2010 will now be serviced as per the extended support policy.
Issues Resolved
-
A new Office 365 Hybrid Configuration wizard (HCW) is used in Exchange Server 2010 that was bundled in the Exchange Management Console (EMC). This change makes sure that EMC always runs the latest version of the HCW that contains up-to-date experience when the HCW is initiated from the EMC.
-
An updated Secure/Multipurpose Internet Mail Extensions (S/MIME) Control for Outlook Web Access. The control is signed to use a SHA-2 compliant code signing certificate. After you install this update, an updated version of the control on the Exchange server will be replaced. Users who have installed the earlier version of the control into a computer's browser must log on to Outlook Web Access and download the updated control after the Exchange server updates are completed.
Important Notes
Now, before we rush off to download and install this there are a couple of items to mention!
-
Test the update in your lab before installing in production. If in doubt test…
-
Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment. This includes archive, mobility and management services.
-
Ensure that you do not forget to install updates on management servers, jump servers/workstations and application servers where the management tools were installed for an application. FIM and 3rd party user provisioning solutions are examples of the latter.
-
If the Exchange server does not have Internet connectivity then this introduces significant delay in building the Native images for the .Net assemblies as the server is unable to get to http://crl.microsoft.com. To resolve this issue, follow these steps:
-
On the Tools menu in Windows Internet Explorer, click Internet Options, and then click the Advanced tab.
-
In the Security section, click to clear the Check for publisher's certificate revocation check box, and then click OK.
We recommend that you clear this security option in Internet Explorer only if the computer is in a tightly controlled environment. When setup is complete, click to select the Check for publisher’s certificate revocation check box again.
-
-
Install the update from an elevated command prompt
-
Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. See KB981474.
-
Update Internet facing CAS servers first
-
Backup any OWA customisations as they will be removed
-
Uninstall any Interim Updates (IUs) before installing the RU. You will have received these private files directly from Microsoft.
-
Disable file system antivirus prior to installing the RU.
-
Restart server after RU has been installed and then re-enable file system antivirus
-
Test (yes, technically this is in here for a second time but it is very important!)
Cheers,
Rhoderick
