you're reading...

Patch SharePoint 2010 RTM to SP2 with latest CU

I was tasked with upgrading our SharePoint 2010 farm from RTM to the latest Cumulative Update (April 2014) to ease our migration to SharePoint 2013. I’d never really touched SharePoint before, so was quite unsure of the steps. After reading some contradicting articles online, here’s the steps I followed to successfully get to the April 2014 CU.


Ensure you log into all SharePoint servers with the account used for the installation of SharePoint 2010

Download the required updates. You only need the latest Cumulative Update (CU) since Service Pack 2. You can find a list of all updates over at technet

The updates to install are:

SharePoint 2010 Service Pack 1 (396MB): http://support.microsoft.com/kb/2460045
SharePoint 2010 Service Pack 2 (447MB): http://support.microsoft.com/kb/2687453
Latest SharePoint 2010 CU, in my case April 2014 (1.2GB): http://support.microsoft.com/kb/2878250

(Optional Maintenance Message) – You can enable a simple (or fancy if you like) maintenance message for the SharePoint site by placing a htm file called app_offline.htm into the root IIS folder of the SharePoint site. This triggers a function in ASP.Net that will take the site offline and display a custom message. You can download a sample file here to use. The file size has to be around 500 bytes or more for Internet Explorer to display the message otherwise you just get a 404 error.


1. As always, backup the servers and databases
2. Install Service Pack 1 on Central Administration Server
3. Install Service Pack 1 on any other farm servers
4. Run SharePoint 2010 Products Configuration Wizard on the Central Admin server

    – Click Next at the Welcome screen
    – Click Yes in dialog below about service resets/starting, as shown below

SharePoint upgrade warning

Warning message when upgrading SharePoint

    – The configuration database server and configuration database name will be listed. Ensure these are correct and click Next
    – SharePoint will begin and complete the component upgrades

Note: The first time running SharePoint 2010 Products Configuration Wizard after installation of Service Pack 1, Service Pack 2 and the Cumulative Update, I received a Configuration Failed warning at the end of the upgrade process.
To resolve this, re-run the SharePoint 2010 Products Configuration Wizard, you may be presented with options different than previously, i.e. for changing the Central Administration Server, etc. Do not make any changes to the configuration, instead just click next to the end of the wizard and it will re-run the upgrade.
After the upgrade is complete, the Central Administration Console opens offering a wizard to complete the SharePoint setup. Click the Cancel button next to “No, I will configure everything myself”

5. Repeat step 4 on all other Farm servers
6. Now reboot all Farm servers
7. Once all servers are up, check that the SharePoint site is loading correctly
8. The installation procedure for Service Pack 2 is the same as above, simply repeat steps 1 – 7 for all Farm servers starting with the Central Administration Server. (After SP2 installation, you may be prompted for a reboot, do so)
For the Configuration Failed message, see the note above in step 4
9. Again, the installation procedure for the Cumulative Update is the same as both SP1 and SP2, follow steps 1 – 7 to complete the installation.
For the Configuration Failed message, see the note above in step 4
10. Finally try and load a users My Site, if you get the message “An unexpected error has occurred”, please see my post here to rectify this


No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: