October 2017 CU for SharePoint Server 2016 is available for download

7 Comments

1. 

   Islam Khattab
   On 12. October 2017 Permalink

   I think it is important to highlight the following on your blog as it is stated as mandatory before applying this update:
   Registry information
   Important
   Follow the steps in this section carefully. Serious problems might occur if you change the registry incorrectly. Before you change it, back up the registry for restoration in case problems occur.
   After you install this update, you can follow these steps to control the metafiles optimization:
   Start Registry Editor:
   In Windows Server 2012, if you’re using a mouse, move it to the upper-right corner, go to Search, and then enter regedit in the search text box.
   Select regedit.exe in the search results.
   Locate and then select the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS\
   On the Edit menu, point to New, and then select DWORD Value.
   Enter BypassDboDropMember, and then press the Enter key.
   In the Details pane, press and hold (or right-click) BypassDboDropMember, and then select Modify.
   In the Value data box, enter 1, and then select OK.
   Note If you don’t want to bypass the behavior, you can set the value to 0.
   Exit Registry Editor.
   Security update deployment information

   Reply
   1. 

      Stefan Goßner
      On 15. October 2017 Permalink

      Hi Islam,
      from the KB article:
      As part of SharePoint database upgrade, the members of the db_owner role are deleted from the role, except for the “dbo” user and the user who is performing the upgrade. This is done for enhanced security to make sure that an errant account isn’t inadvertently left having the db_owner role privileges. However, there may be situations in which this behavior is not desirable. For example, RBS may be broken every time that an upgrade is run. In this situation, a registry key is added to bypass this behavior.
      With other words: this is not mandatory – this is optional and only applies to certain specific situations.
      Cheers,
      Stefan

      Reply
2. 

   TobiasMa
   On 17. October 2017 Permalink

   Hi,
   do i have to set the SideBySiteToken onto 16.0.4600.1002 or 16.0.4600.1000
   i would say 16.0.4600.1002
   (our sharepoint is english with a german languagepack)
   Technet:
   $webapp.WebService.SideBySideToken =

   Reply
   1. 

      Stefan Goßner
      On 18. October 2017 Permalink

      Hi Tobias,
      you always have to pick the highest applied build number.
      With other words: 16.0.4600.1002
      Cheers,
      Stefan

      Reply
3. 

   PriyaranjanKS
   On 29. October 2017 Permalink

   Hi Stefan,
   I did the October KB 4011217 Update and ran PSConfig. I could now create SPFx in SP 2016. However the configuration DB is at build 16.0.4600.1001 . The upgrade status in CA is “No Action Required” . I believe the build should have been ideally 16.0.4600.1002 , but in CA and PowerShell cmdlet “(Get-SPFarm).BuildVersion” shows “16.0.4600.1001” . Can you please shed some light on this. Is there something I am missing ?

   Reply
   1. 

      PriyaranjanKS
      On 29. October 2017 Permalink

      Hi Stefan,
      In fact your article https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
      helped me resolve this issue. On checking Upgrade Patch Status page, I could see 16.0.4600.1002 update installed . Cheers !

      Reply
4. 

   Mikhail Zhuykov
   On 31. October 2017 Permalink

   Thanks ))

   Reply