Office 365, Windows Server, Exchange, PowerShell, Hyper-V and VMware tips and tricks (but no more SBS!)
Microsoft released the Exchange 2010 SP3 Update Rollup 18 on 6 July 2017.
I installed Update Rollup 18 on my test SBS 2011 server this morning and it took 11 minutes 30 seconds from start to finish, so I wouldn’t expect it to take much longer than this in production.
Please test before installing into your production environment. Maybe even wait a few days or a week or two from the release date to make sure the QA is up to scratch on it.
For migrations to Exchange 2016, Exchange 2010 SP3 Update Rollup 11 is the minimum version that will be supported in a coexistance environment.
The update can be downloaded from here.
There is no mention of Update Rollup 18 on the official Exchange Team blog at the moment(24/07/17).
While looking for others experience of installing the update rollup I’ve come across a few suggestions that might help speed the install up and a few best practice tips.
1. Reboot the server prior to installing the update rollup. If it has been up for a while a reboot will make sure it is in a known good state.
2. Run the update from an elevated command prompt.
3. In Internet Explorer, deselect “Check for Publisher’s certificate” and “Check for server certificate revocation”, from Internet Options, Advanced tab, Security options.
4. Disable antivirus software.
5. Have a full backup and a system state backup of the server.
6. Make sure the SBS console is closed if installing the update on SBS 2011.
7. Backup any OWA customisations you have in place.
8. Stop any Backup Exec services if you have it running locally.
While the update is installed it will automatically stop Exchange and IIS services, and restart them again once complete.
Once the update has finished, remember to undo the changes made in steps 3 and 4 above.
The Microsoft Technet http://technet.microsoft.com/en-us/library/ff637981.aspx is a useful article you may want to check out for further reading prior to installing the update rollup.
In larger multi-server environments apply Exchange 2010 Service Packs and Update Rollups in the following order (source: Technet) :
1. Client Access server
2. Hub Transport server
3. Mailbox server
4. Unified Messaging server
0 thoughts on “ Exchange 2010 SP3 Update Rollup 18 installation tips ”
Thank you for the Exchange 2010 SP3 Update Rollup 18 tips. Now, the download won’t take as long because of your suggestions. If only salesforce backup, was as clear cut. Will continue to check the Technet article for more information.
Thank you for the tips
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Carl Gray is an IT professional and technology blogger based in the UK.
With 20 years of industry experience, he is currently a Senior Technical Consultant specialising in PowerShell, Office 365, Windows Server, Exchange Server, Hyper-V, VMware, Veeam and Dell hardware.
OxfordSBSGuy.com is a way of sharing (and remembering) some of the more common and complex problems encountered and solved in the daily toil of IT consulting. Enjoy!
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Update Rollup 22 for Exchange 2010 Service Pack 3 is now available. It contains 2 changes and 1 documented new fix and all previously released fixes and security updates for Exchange 2010 SP3. Note that mainstream support for Exchange 2010 has already ended.
- VC++ 2013 runtime library is now required.
- Added support for Windows Server 2016 domain controllers.
- KB4295751: EWS impersonation not working when accessing resource mailboxes in a different site in Exchange Server 2010 SP3
Today is patch Tuesday for September 2018 and contains a security advisory bulletin for Exchange 2010. Due to the way that Exchange 2010 is serviced, security updates are released as a new update rollup (RU). Separate updates were also released for Exchange 2013 and Exchange 2016.
This is build 14.03.0419.00 of Exchange 2010, and KB 4458321 has the full details for the release. The update file name is Exchange2010-KB4458321-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.
Exchange 2007 is no longer supported, updates are not provided once a product has exited out of extended support.
This release of Exchange 2010 addresses the security issues described in:
The below are the normal notes to consider before deploying an Exchange RU. In this case, the below must also be tempered with the fact that there are security fixes.
There are a couple of items to mention:
- Test the update in your lab before installing in production. If in doubt test…
- Follow your organisation’s change management process, and
factor the approval time into your change request.
- Provide appropriate notifications as per your process. This may be to IT teams, or to end users
- Place the server into SCOM maintenance mode prior to
installing, confirm the install then take the server out of maintenance mode.
- Place the server into Exchange
maintenance mode prior to installing, confirm the install then
take the server out of maintenance mode.
- 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.
- I personally like to restart prior to installing updates. This helps identifies if an issue was due to the RU or happened in this prior restart, and also completes any pending file rename operations. 3rd party AV products are often guilty of this.
- Restart the server after installing the CU.
- Ensure that all the relevant services are running.
- Ensure that event logs are clean, with no errors.
- 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!)