For SharePoint 2013 there is a compulsory Public update.
You can see this as a baseline but if you are planning to install CU's you need this installed.
There are specifics steps to follow with this PU update different to normal SP's and CU's.
Links and some details:
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx
The Server update include Foundation update and the Project update include Foundation and server.
Downloads:
Foundation: http://www.microsoft.com/en-us/download/details.aspx?id=36987
Foundation + Server: http://www.microsoft.com/en-us/download/details.aspx?id=36989
Foundation + Serve + Project: http://www.microsoft.com/en-us/download/details.aspx?id=36988
Steps to follow:
Do this for each server running search component in the order below: You might as well try and stop them anyway...Should say already stopped if services is not present.
Stop the SharePoint Timer Service, SharePoint Server Search 15, and
SharePoint Search Host Controller services (open a Command Prompt and run each
command in the order below):
NET STOP SPTimerV4
NET STOP OSearch15
NET STOP SPSearchHostController
NET STOP OSearch15
NET STOP SPSearchHostController
Remember my farm as below is clean with no Service application's installed yet
Install Package
It askes for a restart, i have restarted and stopped the services again after the restart.
It askes for a restart, i have restarted and stopped the services again after the restart.
Run the wizard
Restart services in this order:
NET START SPSearchHostController
NET START OSearch15
NET START SPTimerV4 After this i could not connect to the farm...
Restarted again
Still an issue...Inside Central admin my Central Admin site was not started...
Thanks Kirk, got allot of handy info from his blog: (http://blogs.technet.com/b/tothesharepoint/archive/2013/03/13/how-to-install-update-packages-on-a-sharepoint-farm-where-search-component-and-high-availability-search-topologies-are-enabled.aspx)
Each server will require a restart
No comments:
Post a Comment