The product group released the June 2016 Cumulative Update for SharePoint Server 2016 product family.
The KB articles for June 2016 CU are available at the following location:
- KB 3115181 – Update for SharePoint Server 2016 June 2016 (language independent)
- KB 3115184 – Update for SharePoint Server 2016 June 2016 (language dependent fixes)
- KB 3115134 – Update for Office Online Server 2016 June 2016
The download for June 2016 CU is available through the following link:
- Download Update for SharePoint Server 2016 June 2016 (language independent)
- Download SharePoint Server 2016 June 2016 (language dependent fixes)
- Download Office Online Server 2016 June 2016
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
SharePoint 2016 June 2016 CU Build Number: 16.0.4393.1000
The language independent Fix updates the configuration database schema version to the number above.
You can use the SharePoint Server 2016 Patch Build Numbers Powershell Module to identify the patch level of all SharePoint components.
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Blog: June 2016 Office Update Release
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
is there a reason why you no longer put language independent and language dependent files in one Uber-package?
the number of packages is much smaller (only 2) compared to dozends of packages in 2010 and 2013.
Missing a package is more unlikely through this as you only have to keep track of 2 packages.
“Upgrade of Search Service Application and re-crawl are required for the fix to take effect.”
Is it full re-crawl or incremental?
from my understanding you need to do a full crawl.
Interesting that the in KB3115181, it says “Schema management UI doesn’t list crawled or managed properties.” while the actual issue is that PowerShell is not showing crawled properties (https://social.technet.microsoft.com/Forums/en-US/749301b1-c798-4d39-8cf0-5698603c1d26/crawled-properties-not-shown-via-powershell?forum=SP2016), while UI is showing them just fine. Let’s see if it still fixes the actual issue.
Another thing, any idea what “upgrade” means in same KB: “Note Upgrade of Search Service Application […] required for the fix to take effect.”?
Great, looks like the Get-SPEnterpriseSearchMetadataCrawledProperty now properly returns crawled properties although the KB description is incorrect.
But Search Crawl is no longer working, apparently because I woult need to figure out how to “upgrade” my Search Service Application.
I still have the problem that I can’t fetch crawled properties with PowerShell. They are visible in the UI but no trace of them in the database or through PowerShell. I have even recreated the Search Service Applicaiton. Did you have to do anyting else in order to fix this problem?
Thanks in advance!
could you solve this error? We are still facing this issue even though we are on Jan 2017 CU.
are the listed download the cumulative updates or just the individual fixes?
I.e. to get my 2016 farm fully updated, do I just have to install the 2 listed June updates (as with CUs), or will I have to install the April and May updates as well to avoid missing components (as with individual fixes)?
Thank you and kind regards,
all SharePoint fixes are cumulative.
Thank you, cheers! No more hand picking individual hotfixes.
I noticed that the June 2016 CU is smaller than the May 2016 CU. If I am doing a new install of SP 2016, do I need to install the April and May updates to be up to date? Thanks is advance
I’m not sure what you mean.
sts2016-…exe: 195476016 bytes
wssloc2016-…exe: 370110112 bytes
sts2016-…exe: 285612864 bytes
wssloc2016-…exe: 405628104 bytes
So both files are bigger in June than in May.
Hi, I still have the problem that I can’t fetch crawled properties with PowerShell. Installed new SP2016 Farm with CU JUN 2016. Reset Index several with Full Crawl several times no success. Did anyone succeed after JUN 2016 CU ?
Thks and best rgds,
I am facing the same issue even after updating June CU, Restarting the Box, Provisioning a new Search Service Application and restarting the search services.
using “Get-SPEnterpriseSearchMetadataCrawledProperty” returns only the Out of the Box “Default” properties, and all the custom crawled porpoerties properties are not listed, although all the custom crawled properties are listed in the Search Schema UI page in Search Administration, Anyone could help or point what I may be missing.
just one quick note to you. Seems you Forget to update the first two sentences in every CU Blog, since it is always the “second CU for SharePoint Server 2016 after RTM” (in june, july, August….) 😉
Indeed – a copy&paste error 😉
Thanks for the heads-up!