SP1 is now available for SharePoint Server 2013, Project Server 2013, Project 2013, and SharePoint Designer 2013!
Build number as seen in central admin after installation: 15.0.4569.1000 NOTE! The March PU Is not required prior to install SP1 on top of RTM version!
(see also the Sustained Engineering blog post)
The updates are available from the Microsoft Download Center today, as well as from Microsoft Update and the Windows Server Update Services (WSUS) catalog. After a 30-day period, SP1 will begin releasing as an automatic update through Microsoft Update. Visit these KB articles for more information on the SP1 updates for the MSI versions and how to get them.
Customers who have an Office 365 subscription are always kept up to date and will get the SP1 changes automatically in their next regular update.
SP1 for Exchange Server 2013 is also releasing today. Visit the Exchange team blog to learn more about it.
What’s new in SP1?
SP1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and related products. Among the functionality improvements and changes are the following:
A detailed list of SP1 fixes is available for download. Additionally, SP1 includes all the Public Updates (PU) and Cumulative Updates (CU) that have been released since the 2013 family of products first became available, up to the December 2013 CU and January 2014 PU.
Regarding the installation ensure to follow all guidelines on the following page: Software updates overview for SharePoint 2013
Note! As usual, you must run the PSConfig Wizard after installation to finalize the update!
Hi, Steve, thanks a lot for the great news. It seems we encountered a strange issue after applying the SP1 update. All our 3rd party software service accounts lost the dbo permission on the SharePoint databases and can no longer work unless the permission is manually set again. Is this the expected behavior? any insights would be greatly appreciated!
@George White:Hello and thanks for the heads-up, currently we are not aware of this specific issue and you should open a support case to follow up if this is a regression we might have overseen.I tested myself the Server SP1 on a standard Farm setup on either Straight RTM as well as on a patched Farm at Dec. 13 CU, both farm's went through fine and no issues were seen, so I think, this is really something we should investigate by a Support case since 3rd party software and hence service accounts are quiet common. So I'd really recommend to raise a case if you find this critical for your deployment.HtH, cheers, Steve