June 2016 CU for SharePoint Server 2016 is available for download

18 Comments

1. 

   Markus Hintner
   On 15. June 2016 Permalink

   Hi Stefan,
   is there a reason why you no longer put language independent and language dependent files in one Uber-package?
   Thanks, Markus

   Reply
   1. 

      Stefan Goßner
      On 15. June 2016 Permalink

      Hi Markus,
      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.
      Cheers,
      Stefan

      Reply
2. 

   Piotr Siódmak
   On 15. June 2016 Permalink

   https://support.microsoft.com/en-us/kb/3115181
   “Upgrade of Search Service Application and re-crawl are required for the fix to take effect.”
   Is it full re-crawl or incremental?

   Reply
   1. 

      Stefan Goßner
      On 15. June 2016 Permalink

      Hi Piotr,
      from my understanding you need to do a full crawl.
      Cheers,
      Stefan

      Reply
3. 

   Jussi Palo
   On 15. June 2016 Permalink

   Hi,
   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.”?
   Thanks!

   Reply
   1. 

      Jussi Palo
      On 15. June 2016 Permalink

      Great, looks like the Get-SPEnterpriseSearchMetadataCrawledProperty now properly returns crawled properties although the KB description is incorrect.

      Reply
      1. 

         Jussi Palo
         On 15. June 2016 Permalink

         But Search Crawl is no longer working, apparently because I woult need to figure out how to “upgrade” my Search Service Application.

         Reply
      2. 

         Erik
         On 27. June 2016 Permalink

         Hi,
         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!
         BR,
         Erik

         Reply
         1. 

            Markus Ihloff
            On 31. March 2017 Permalink

            Hi,
            could you solve this error? We are still facing this issue even though we are on Jan 2017 CU.

            Reply
4. 

   Adrian
   On 18. June 2016 Permalink

   Hi Stefan,
   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,
   Adrian

   Reply
   1. 

      Stefan Goßner
      On 20. June 2016 Permalink

      Hi Adrian,
      all SharePoint fixes are cumulative.
      Cheers,
      Stefan

      Reply
      1. 

         Adrian
         On 27. June 2016 Permalink

         Thank you, cheers! No more hand picking individual hotfixes.

         Reply
5. 

   Joe
   On 22. June 2016 Permalink

   Hi Stefan,
   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

   Reply
   1. 

      Stefan Goßner
      On 22. June 2016 Permalink

      Hi Joe,
      I’m not sure what you mean.
      May CU:
      sts2016-…exe: 195476016 bytes
      wssloc2016-…exe: 370110112 bytes
      June CU:
      sts2016-…exe: 285612864 bytes
      wssloc2016-…exe: 405628104 bytes
      So both files are bigger in June than in May.
      Cheers,
      Stefan

      Reply
6. 

   Andy
   On 5. July 2016 Permalink

   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,
   Andy

   Reply
7. 

   Islam Khattab
   On 17. July 2016 Permalink

   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.

   Reply
8. 

   Andreas Zinic
   On 27. September 2016 Permalink

   Hi Stefan,
   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….) 😉
   Kind regards
   Andy

   Reply
   1. 

      Stefan Goßner
      On 27. September 2016 Permalink

      Indeed – a copy&paste error 😉
      Thanks for the heads-up!

      Reply