Exchange 2010 SP3 Update Rollup 11 released and installation tips

Microsoft Exchange 2010 SP3 Update Rollup 11 Installtion tipsEdit: Update Rollup 18 is now available for Exchange 2010 SP3 see the post Exchange 2010 SP3 Update Rollup 18 installation tips.

On 15th September Microsoft released the Exchange 2010 SP3 Update Rollup 11.

I’ve installed this on my test SBS 2011 server, it took just 7 minutes 45 seconds from start to finish, by far the quickest update yet and my test server isn’t very powerful, so I wouldn’t expect it to take much longer than this in production.

The new update has been available for a few weeks now, and I have not seen any issues reported with it so I suspect it is safe to deploy in your production environment.

If you are doing a migration to Exchange 2016, then Exchange 2010 SP3 Update Rollup 11 is the minimum version that will be supported in a coexistance environment.

The Update Rollup 11 for Exchange Server 2010 SP3 contains the fixes for the security issue that is described in KB3078674 and the following Microsoft Knowledge Base (KB) articles:

The update can be downloaded from here.

The official Exchange Team blog post can be found here.

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 know 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 is a useful articles you may want to check out for further reading prior to installing the update rollup.

In larger multi-server envrionments 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

Related Posts:

1. Exchange PowerShell: How to enumerate Distribution Lists, managers and members

2. How to install Exchange 2013 (SP1) on Windows Server 2012 R2

3. Exchange Server and Update Rollups Build Numbers

4. Exchange 2013 Initial Configuration Settings multi-part series

5. Exchange PowerShell: How to check the number of items in the Inbox, Sent Items, Deleted Items and Junk Email

2 thoughts on “Exchange 2010 SP3 Update Rollup 11 released and installation tips

  1. john merrick

    Hi Carl –
    Thanks so much for the the tips. Brilliant!

    Quick question, When applying RU11 – should we still follow the order of installation. In our case we have the CAS/HUB on the same servers.
    1. Client Access Server (if you have multiple sites internet facing sites first)
    2. Hub Transport
    3. Mailbox
    4. Unified Messaging

    please advise when you have a moment and thanks again.

    Cheers, John

    1. Post author

      Hi John, for larger envrionments the same rules apply:
      Exchange update rollups work across multiple server roles. Because the update rollups aren’t segmented for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2010 servers in your environment.
      For Exchange 2010 configurations, the recommended order in which to apply the update rollup is as follows: Client Access server, Hub Transport server, Mailbox server, and Unified Messaging server.
      If you have multiple Active Directory sites and have deployed a Client Access server in the proxy sites that aren’t Internet-facing, apply the update rollup to the Internet-facing Client Access servers before you apply the update rollup to the non-Internet-facing Client Access servers. For more information about Client Access to Client Access server proxying, see Understanding Proxying and Redirection.
      Source: Technet Exchange Server 2010 Service

Comments are closed.