Patching SharePoint on SBS 2011: don’t forget to run PSCONFIG

Sharepoint 2010In SBS 2008, which uses SharePoint Services 3.0, when a SharePoint patch is applied via WSUS PSCONFIG is automatically run.

Microsoft SBS 2011 includes Microsoft SharePoint Foundation 2010, and the way that updates are applied to it is now a two-step process. When a SharePoint update is applied only the program files are updated, the databases are no longer automatically updated. SharePoint 2010 will run in compatibility mode with the new program files and older database version until they have been upgraded.

You can check if the databases need to be run either by using the SharePoint 2010 Health Analyzer or by running a PowerShell command.

Firstly the Health Analyzer Report can be accessed by running the Start, All Programs, Microsoft SharePoint2010 Products, SharePoint 2010 Central Administration program. Once in the program select Monitoring, Review problems and solutions.

Here you can see the bottom category indicates the databases are running in compatibility range, and recommends an upgrade.

Sharepoint 2010 Health Analyzer Report

The Second way is run the SharePoint 2010 Management Shell. Click Start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.

SharePoint 2010 Management Shell

Then run the following command:

(get-spserver $env:computername).NeedsUpgrade

If the result is True then you need to run PSCONFIG.

get-spservername needsupgrade true

Open an elevated Command Prompt.

Elevated Command Prompt

Go to C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN folder.

Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

PSCONFIG -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Once complete you should see the following.


And if you run the (get-spserver $env:computername).NeedsUpgrade command again you should see the following.

get-spservername needsupgrade false

A few words of caution:
On my test server the process took about 8 minutes, but I have very little data in SharePoint.

While the process is running CompanyWeb will be inaccessible.

Always (wherever possible) test patches before installing them on Production boxes.

Make sure you have a good backup first.

The official SBS Blog post detailing this process can be found at the link below.

0 thoughts on “Patching SharePoint on SBS 2011: don’t forget to run PSCONFIG