Ok… this post has been in “draft” some time and is well overdue for publishing.
SharePoint 2013 has well and truly landed now and if you haven’t already, you really should be pushing the installation of the March 2013 CU. Generally speaking, the community and early adopters consider the March 2013 CU a mandatory update for SharePoint 2013. Here at risual, we are no exception to this an highly recommended this CU. If you need assistance, get in touch and we’ll help you plan and deploy with minimal disruption.
Albeit a very brief post, I will overview the general guidance and installation steps needed to carry out an upgrade of the public Cumulative Update for SharePoint Server 2013 or SharePoint Foundation 2013. This post is focused on smaller environments (all SharePoint services on one or two servers) and should not be applied to larger environments (that utilise high availability and more complicated Search topologies, for example). Such guidance should be taken from this TechNet article, or of course you could always have a risual consultant visit to lend a helping hand 🙂
- First things first, download the appropriate update package for your edition of SharePoint; SharePoint Server 2013 or SharePoint Foundation 2013
- Log onto your SharePoint server that hosts Central Administration and stop the following system services, in this order (very important!)
- SharePoint Timer Service (SPTimerV4)
- SharePoint Server Search 15 (OSearch15)
- SharePoint Search Host Controller (SPSearchHostController)
- The next step is to execute the update package (the newly download 1.7GB ubersrvsp2013 file) but one observation that you should be aware of is once you agree to the usual software licence terms, the upgrade starts and without confirmation (which effectively leaves your web services returning a 503 Service Unavailable to IIS)
- Once the initial upgrade process has completed, you will be prompted to perform a system restart
- Now run the SharePoint Products Configuration Wizard (PSConfig) on your Central Administration server and complete the wizard ensuring no configuration changes are made
- Once PSConfig has completed and you’re back into Central Administration, now is the time to patch the second server, if applicable
- Remember once the patch has installed and the server has restarted, run PSConfig and ensure a successful completion
So the update has finished, well done, but you’re not done just yet. You now need to verify that the upgrade has actually completed and you’ve not left your environment in a doomed state.
- Open Central Administration and navigate to the “Upgrade and Migration” page then “Check Upgrade Status”
- Observe that your sever shows “Succeeded” for the latest entry
- Now navigate to “Manage Severs in the Farm” and check the Configuration Database Version is showing “15.0.4481.1005”
- In true belt-and-braces fashion, navigate back to “Upgrade and Migration” and click “Check Product and Patch Installation Status”. Verify the server is reporting the new build version. Note that unless you also upgraded the Language packs, they will show as the previous version (for example, 15.0.4420.1017)
Congratulations, you are now running the latest CU for SharePoint 2013! Enjoy!