http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346
Service Pack 1 has been rereleased. Please read this blog post to see how to tell the the two SP1s apart
Now that the SharePoint 2013 beta is on the streets, it’s time to start keeping track of those glorious build numbers. This blog post will have all the build numbers, their friendly names, how to get them, and what I know about them. Just like my SharePoint 2010 Build Number post, let me know if there are things I can change, or any content I should add.
To see which build your farm is, go to Central Administration > System Settings > Manage servers in your farm (/_admin/FarmServers.aspx)
Or using Windows PowerShell: (get-spfarm).buildversion
To see which build your farm is at with Fiddler, open the site in question and view Inspectors > Headers and under Miscellaneous check the build under MicrosoftSharePointTeamServices header.
To see which build your products are, go to Central Administration > Upgrade and Migration > Check Product and patch installation status. (/_admin/PatchStatus.aspx)
To greatly reduce the time it takes to patch a SharePoint 2013 server, read this blog post by Russ Maxwell, Why SharePoint 2013 Cumulative Update takes 5 hours to install? It explains why the process takes so long and provides a handy script that makes the patch install much more quickly. Do yourself a favor and check it out.
Follow SP2013Patches on Twitter for immediate updates when this list changes or I add a regression to a patch.
Get an email when I change this page. (Third party web site)
ShortURL: http://www.toddklindt.com/sp2013builds
SharePoint 2013
Office Web App 2013
To see which version of the OWA (also called the "Web Access Components" or "WAC") use the following PowerShell:
Workflow Manager 2013
To see which version of Workflow Manager and Service Bus are installed, use the following PowerShell:
or
When you install Workflow Manager CU 1 you also have to install Service Bus CU1. Also make sure you patch the Workflow Manager client on SharePoint servers that are not running the Workflow Manager service. See more details on how to patch Workflow Manager on Andrew Connell's blog.
tk
|
No comments:
Post a Comment