Recently Microsoft released SharePoint Server 2013 SP1(February 25th 2014 to be precise) full of new features and bug fixes SP1 will be a critical update to SharePoint Server Farms over the next coming months… so what exactly is fixed and new to SP1? Click here to find out the full list
Now that we know the changes and fixes involved with SP1, let’s install SP1.. this how to guide will cover end to end Installing and configuring SP1, but I strongly advise you to run the Service Pack on a dev environment first.
Installing SP1 Binaries
First you will need to download the SharePoint Server 2013 Service Pack 1 package
What Servers should I Install Service Pack 1 on? Which Server(s) first?
This is a very important step and can be detrimental to your end result, make sure you run SP1 on your App Servers or the server(s) that run Central Administration first before installing on any other server, it is also important to note that Service Pack 1 will need to be installed on any Server that has SharePoint Installed and is connected to your farm or the consequences being that server will be no longer of use until it is upgraded.
Once downloaded and copied onto each SharePoint Server,
Accept the Microsoft Software License Terms & click Continue
Your Installation will to detect your current Installation & begin to install the Service Pack 1 files.
Once the Installation is complete on your SharePoint Servers I generally reboot each server, it’s something that I found has worked in the past but I do recognize it’s probably me over analyzing, so feel free not to reboot the servers.
If I check my Servers farm status now you will recognize my database version is still 15.0.4420.1017 (RTM SharePoint Server 2013)
You will also recognize that the Status of each of my SharePoint servers have a status of ‘Upgrade Required’ which brings us to the second part of the article… and the place where most Upgrades go wrong!
SharePoint Products Configuration
So now we are up to running the SharePoint Products Configuration Wizard to upgrade each SharePoint Server in the farm, again I suggest that the server running Central Administration is upgraded first and only run one sever upgrade at a time, this may be an old tale but it’s certainly a rule I apply.
If you receive a prompt around not being logged in as the right user you should use the account that was used for farm configuration originally.
Run ‘SharePoint Products Configuration Wizard’
If you receive a prompt click Yes
Done, My Server has now been upgraded – now to rinse and repeat on the rest of my SharePoint Servers in the farm
Once Successful you will notice your Config Database version has now changed to 15.0.4569.1000 (SP1) and that all servers in the farm status is ‘no action required’… now you need to test, test, test every little bit of functionality in the farm J