SharePoint 2010 patching

1. Verify your current patch level by matching the Build Number using these instructions:

https://technet.microsoft.com/en-us/library/dn789211(v=office.14).aspx#BKMK_2010

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=224


To see which build your farm is, go to Central Administration > System Settings > Manage servers in your farm (/_admin/FarmServers.aspx)

Or using Windows PowerShell: (get-spfarm).buildversion

To see which build your products are, go to Central Administration > Upgrade and Migration > Check Product and patch installation status. (/_admin/PatchStatus.aspx)

2. Download the applicable Cumulative Update (CU) or Service Pack.

A good recommendation is to always be one CU behind the current release for production environments to avoid issues that may be introduced by a new CU.  You can find the prerequisites listed in each KB article supporting a CU or Service Pack.

SharePoint 2010 Cumulative Updates are located here: http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

3. Copy the CU or Service Pack to each of the servers that have SharePoint installed. No need to install on SQL if it is a separate machine.

IMPORTANT: It is highly recommended to test your update on your development/test farm before proceeding with updates to the production environment.

4. Run the CU or Service Pack on each SharePoint server. I generally start with the Application Server that hosts Central Administration and run the CU on all Application Servers first before proceeding to the Web Front End Servers (WFE).

IMPORTANT: Do not run the SharePoint Products Configuration Wizard until all servers have had the CU or Service Pack installed and have been reset.

5.Reset each server

6.After the servers restart, run the SharePoint Products Configuration Wizard starting with the first Application server you installed in your SharePoint Farm (generally hosting Central Administration), all other Application Servers, and finally all Web Front End (WFE) Servers.

7.Reset each server

8.Verify the build numbers