8

The guidance and "best practice" up until the August 2011 CU is to install SPF Service Packs and CU's on Server edition. From August 2011 the packaging process has changed and you only need one package to install. So in order to install SP1 + June CU do this: (the Microsoft recommendation is to install June CU directly after SP1, there are a couple of nasty ...


7

Will it require a downtime? Of course, Yes, it will require! In SharePoint 2013/2010/2007, Running the SharePoint Configuration Wizard will require downtime even you have high availability environment. Note: The zero downtime patching has been introduced In SharePoint 2016, but you must have high availability environment to perform it.


6

you should not run the PSConfig after the windows / OS patches or updates. But now a days MSFT include the SharePoint patches in the windows updates, so if you noticed SharePoint patch install along with the windows then you need to run the PSConfig. we block the windows updates and manually install the windows updates. We never run the config wizard after ...


5

Yes you are right, the build number for April 2017 CU is 15.0.4919.1003 But I advise you to don't trust the build number in Manage Servers in Farm, it often gives you a wrong indication about installed fixes. Stefan Goßner discussed the reason in details at SharePoint patching demystified I quoted some One reason might be that you looked at the KB ...


5

July 2017 CU is enough for you. Here is more information about updates.


4

No IIS will be down while you're running PSConfig. On how to keep the users out see What is the best practice for redirecting users when sites are being upgraded?


4

That's correct! if you ever need to confirm which update/revision of SharePoint you are running, without accessing the binary files themselves, these version numbers correspond to the version numbers reported in SharePoint Central Administration. You can find this by going into the Operations tab, and under Topology and Services, select Servers in Farm. ...


4

Try the following: clear configuration cache http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx Find current pv value using: stsadm -o getproperty -pn command-line-upgrade-running if -pv value is yes, change to No. If no change to Yes stsadm -o setproperty -pn command-line-upgrade-running -pv No re-run ...


4

I think you dont need to install the hotfix And MS14-202 due to fact that latest CU include all the previous fix.I would do the following way. Install the Service Pack 1 Mark 2.( as this is base line for future updates. Now install the June CU 2016( requirement for it is Service Pack 1). You can get more info from this official blog :June 2016 CU for ...


4

I would install a new SQL Server to the level that you require, such as SQL Server 2008 R2. Tehn I would backup from source SQL and restore to destination SQL, with the same permissions and settings as the source SQL. Then I would run cliconfg on my SharePoint Server(s) and create an alias from the source SQL to the destination SQL and restart services and ...


4

SharePoint 2010 is supported on SQL 20018 R2 SP3, so no, there shouldn't be any issue installing the service pack onto your SQL Server. I'd test (if at all possible) on a test system first, simply to ensure that any other solution installed within the SharePoint farm also continues to function as expected once the service pack is installed. Obviously you ...


4

According to MS, SharePoint does not have a single, specific build version (https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/). The reason is due to SharePoint being made up of different sub products. Some update the farm version, others update the version in the config db and others simply ...


4

There is no "official" recommendation from Microsoft to always install the latest CU for SharePoint. SQL Server has such an advice. BUT: If you open a Microsoft Support Case, you will get told to patch your SharePoint-Farm before the case will continue. If you really ask for "maximum damage": A completely broken farm and the need to fully restore the farm ...


4

The root cause of your issue represented in you have installed September 2015 CU before installing August 2015 CU. September 2015 CU has been released without "Server" or "Uber" packages that mean if you are not in an urgent need for a fix included in September 2015 CU you should consider waiting for a CU release that includes "Server" or "Uber" packages. ...


4

SharePoint 2016 doesn't have 'CUs', instead they're Public Updates, which are similar in function, but different in that the recommendation is to apply Public Updates as soon as possible and keep current with them, unlike the CU process which was 'apply only as required'. There are no separate security updates for SharePoint 2016, that's correct. And with ...


4

It's really the other way around. First you update Windows Server (both the SQL Server and Windows Server which hosts SharePoint) using Windows Updates. When this is done, update SharePoint, starting with application servers. Make sure the PSCONFIG runs successfully before moving on to the next server. See: Tips for Patching SharePoint 2013


4

First, you should be aware of the SharePoint Security Fixes that included within the Windows Update will not be reflected until running the SharePoint Configuration Wizard Second, It's recommended to don't include the SharePoint Security Fixes with the windows update to avoid your current confusion. However, if you will install the SharePoint Security ...


4

First, you got this error message "The expected version of the product was not found on the system" Because of the cumulative update that you are trying to install ("April 2013") is lower than the current build number of your farm that is "The SharePoint version is SharePoint Server 2013 SP1 (15.0.4569.1506)," Second, it's known issue that occurs when ...


4

Short and sweet: Flush the BLOB Cache.


3

On the impacted FE, run: psconfig -cmd applicationcontent Reference: https://technet.microsoft.com/en-us/library/cc263093%28v=office.14%29.aspx


3

Your patch levels are different. Install May 2015 CU or MS15-046 to the production server, depending on what was installed in dev/test.


3

Finally the popularity trend is resumed. However for the past few days that have zero count, the statistic cannot be recovered (maybe there is some way to recover but not that I aware). By default, all the SharePoint log are stored in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\. In my environment, the Log directory was ...


3

It requires that all services be highly available (FE, Distributed Cache , Search, MMS, and so on). Patches may require a restart of any one particular server, hence the HA requirement. The goal is that there are no schema updates, which is what takes a farm down across the board during Config Wizard. That's what 'zero downtime' means. EDIT 4/12/06: The ...


3

That's correct. Security patches and other hotfixes can certainly update the Farm Build #, but it does not mean the corresponding Cumulative Update is installed. In order to identify which component has been updated, in Central Administration, under Upgrade and Migration, Check product or patch installation status. This will list each individual product and ...


3

Upgrading / Patching of SQL server is not big issue as compare to patching the SharePoint server. You have to plan it properly. First thing, you have to apply the patches in lower environment and test the behavior of both SQL as well as SharePoint. Once satisfied then move to production. For Production You have to schedule a downtime as it will interrupt ...


3

In some exceptional cases, the CU does not update the configuration database version in Central Administration like Oct CU 2013. And in this case, you can get the configuration database version from SQL Server by opening Content Database > the versions table. Check the version number with versionID 00000000-0000-0000-0000-000000000000. Or by checking ...


3

Did you look at the build-number in CA -> System Settings -> Manage Servers in this farm -> Configuration Database Version. Unfortunately the Config-DB build number does not always match the build of a (cumulative) update. The best ressource to check success of your installation is CA -> Upgrade and Migration -> View product and patch installation status. ...


3

Here is very good explanation about the issue you mentioned. when looking at the SharePoint foundation KB article there are rare cases that the patch level listed in the central administration is lower than the version number in the KB article. The reason for this is that different fixes are added to the CU at different times. Some fixes modify ...


3

The below is answer for your question. 1: Yes Microsoft releases patches every month starting from April 2016. 2: SharePoint 2016 CU Software updates include any update, update rollup, service pack, feature pack , critical update, security update, or hotfix. in one patch. 3: ZDP refers to two things: (I) Redundancy in the farm enabling the patches to ...


3

Since you have SharePoint 2010 Service pack 2 already installed, you can directly install the July 2017 Cumulative Update. It will include all the updates from August 2013 to June 2017. Reference - July 11, 2017, cumulative update for SharePoint Server 2010 I would however recommend that you follow the best practice and install the (N-1) update i.e the ...


Only top voted, non community-wiki answers of a minimum length are eligible