How to Install SharePoint 2013 Service Pack 1

upgrade service packAs many of you have heard, Microsoft has released Service Pack 1 (SP1) for Microsoft SharePoint Server 2013… again.

To be clear, they originally released the SP1 patch toward the end of February this year. They soon realized, however, that the installation of the first release created some issues which were preventing customers from installing future updates. Microsoft deactivated the download pages to prevent any further installations.

To view a list of issues that are fixed, please visit my SharePoint 2013 SP1 announcement blog.

Now that Microsoft has released the corrected version, let’s walk through the SP1 installation together.

At Fpweb.net, we have installed the updated Service Pack 1 on a few lab and production environments and have not seen any issues thus far.

Download SharePoint 2013 SP1:

Before we can install the Service Pack, we must first download it. There are separate downloads depending on your version of Foundation or Server. Unlike former SharePoint patches, you do NOT have to install both the Foundation and Server patches if you are running SharePoint Server.

Service Pack 1 for SharePoint Foundation can be downloaded here.

Service Pack 1 for SharePoint Server can be downloaded here.

SharePoint 2013 Service Pack 1 Download

Please be sure to read the details of the patches before downloading. The installation package is 1.3 GB for Server and 403 MB for Foundation. Ensure you have the necessary disk space available before downloading.

Install SharePoint 2013 SP1:

Once you have downloaded the correct media using the steps above, we can begin the install process. As with any SharePoint patch, this must be installed on every server in your SharePoint farm. This includes Web Front End server and Application servers, if applicable.

Let’s get started…

  1. From your SharePoint server, browse to the file location of your download.
  2. Double-click the officeserversp2013-kb2817429-fullfile-x64-en-us.exe file (assuming you kept the default filename).file location of your download
  3. From the Service Pack 1 for Microsoft SharePoint Server 2013 (KB2817429) 64-bit Edition window, be sure to select the checkbox next to Click here to accept the Microsoft Software License Terms.Microsoft Software License Terms
  4. Click Continue
  5. This will start the installation process and you will see the following progress window until the progress is completed. start the installation process*Please note: you will see a few windows similar to the above that will appear and disappear. The majority of the process will display the above message: Please wait while the update is installed. When the installation is completed you will see this message:installation is completed
  6. You may NOT be required to reboot depending on your server. If you are required, please reboot at an acceptable time for your business.

Repeat steps 1 through 6 on all SharePoint servers. Once all servers have the Service Pack 1 bits installed, this does not mean the SharePoint farm is upgraded yet. To actually upgrade the schema, you must run the SharePoint 2013 Products Configuration Wizard. This also needs to be completed on each server, but you can only do this portion one server at a time.

Running the SharePoint 2013 Products Configuration Wizard:

  1. From your SharePoint server, browse to the start menu. If using Windows Server 2012, search for SharePoint 2010 Products Configuration Wizard. Click to Open.SharePoint 2010 Products Configuration Wizard
  2. You will immediately know if the Service Pack installation was successful based on the message you see on the Configuration Wizard welcome window. Notice the message “This wizard will upgrade SharePoint Products”, which differs from the normal message of “This wizard will help you repair SharePoint Products. Click Next to continue or cancel to exit the wizard…” Click Next here.This wizard will upgrade SharePoint Products
  3. You will then see a warning message letting you know that a few services will be restarted during this upgrade process. Click Yes. Please noteUnless you have a high availability farm, your site will be unavailable throughout this process.services will be restarted during this upgrade process
  4. At the Completing the SharePoint Products Configuration Wizard screen, click Next.
  5. This will run through the upgrade sequence. When the wizard is completed, click Finish.

Repeat steps 1 through 6 on all SharePoint servers.

The installation is now completed and your farm has been upgraded to SP1.

Verify Installation for SharePoint 2013 Service Pack 1:

Now that you have successfully installed Service Pack 1 for SharePoint 2010, you need to verify the build number to be absolutely certain that the installation was successful. The easiest method to do so is:

  1. Browse to Central Administration from any SharePoint server. Again, if running Windows Server 2012, go to the Start menu and search for SharePoint 2013 Central Administration. Click to open.SharePoint 2013 Central Administration
  2. From the Central Administration home page, select Manage Servers in this Farm from the System Settings section.Manage Servers in this Farm
  3. From the Servers in this Farm page, under the Farm information section, you will see the Configuration Database Version. This should read 15.0.4569.1509. This build number tells us that this has been successfully upgraded to SP1.

Hope that helps! As always, please comment if you have any additional questions.

VN:F [1.9.22_1171]
Rating: 8.9/10 (19 votes cast)

About Fpweb.net Crew

Our business is centered on bringing enterprise-class strategy, support, and security to your hosted or managed platforms no matter where you choose to deploy your environment. We specialize in providing managed services, cyber security, and expert, USA-based, 24/7 Absolute Support® on-premises, or in any cloud.
This entry was posted in SharePoint Tips & Tricks and tagged , , , , , , . Bookmark the permalink.

13 Responses to How to Install SharePoint 2013 Service Pack 1

  1. Ben says:

    Got Blog post, but i have one question, what about the PsConfig command, are you saying that is not needed?

  2. -mrkcc says:

    Excellent. Thanks.

  3. Jerry says:

    I do not know why my installed version is 15.0.4571.1502 not as you mentioned 15.0.4569.1509. I have installed the SP1 mark 2 version.

  4. Bill says:

    @Jerry That is the correct version – 15.0.4569.1506/9 is the version of SP1 that was withdrawn.

  5. Jesse says:

    Thank you! This worked perfectly for updating a SP 2013 dev machine hosted in Azure.

  6. Panoone says:

    You don’t state here that the CA server, then the Search server (and any other application servers in your farm) should be patched BEFORE the WFEs.

    I’m pretty sure this is still the case and a critical process to follow.

  7. Neil Thomson says:

    The actual build number after installing from download on Jul 18,2014 is 15.0.4569.1000

  8. henry says:

    We got an error of “Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Failed to upgrade SharePoint Products” when run the Sharepoint 2013 Products Configuration Wizard. After detach all content databases and run the configuration wizard again, it worked.

  9. Doula.K says:

    Awesome… Post

  10. Mark Davis says:

    I have a standalone development farm, and my config database version is 15.0.4615.1000. I don’t remember installing the service pack, and the content, search, et. al., databases have a create date of 2/18/14. Is this likely to mean I’m up-to-date with cumulative updates, or does it mean I have updates (e.g., security updates) that need to be removed before I install SP1? Thanks for this awesome tutorial!

  11. Pingback: PortalCrunch SharePoint & Drupal | Upgrading to SharePoint 2013 Service Pack 1 (SP1)

  12. Philips says:

    In a configuration with 2 servers : one for web and the other for Sql Server should SP1 be applied on each server?

  13. Anon says:

    @Panoone
    That’s never been the case

Leave a Reply

Your email address will not be published. Required fields are marked *

Let's make sure you're human first: *