SharePoint security fixes released with January 2017 PU and offered through Microsoft Update

15 Comments

1. 

   Scott
   On 10. January 2017 Permalink

   No security Fixes for SP2010 also = no CU for SP2010 since no feature updates since end of life? Correct?

   Reply
   1. 

      Stefan Goßner
      On 10. January 2017 Permalink

      Correct 🙂

      Reply
2. 

   James
   On 12. January 2017 Permalink

   Question since the November and December PU are included in the January Secuirty update it is safe to assume we can jump to the January 2017 update correct?

   Reply
   1. 

      Stefan Goßner
      On 12. January 2017 Permalink

      For which Product version?
      In November and December we did not have security fixes for SharePoint 2016 and that is the only one we have in January.
      Also be aware that security fixes are cumulative per component. So you cannot assume that a security fix in January will include the security from December or November.

      Reply
3. 

   msekkappan
   On 25. January 2017 Permalink

   Stefan, do I need to run PSConfig.exe after installing the January 2017? The patch status says “Update for Microsoft SharePoint Enterprise Server 2013 (KB3141481) 64-Bit Edition” is installed

   Reply
   1. 

      Stefan Goßner
      On 25. January 2017 Permalink

      There is not a single fix for SharePoint which does NOT required psconfig.
      https://blogs.technet.microsoft.com/stefan_gossner/2015/09/09/why-we-recommend-require-to-run-the-configuration-wizard-also-for-security-fixes/
      Cheers,
      Stefan

      Reply
4. 

   Peter
   On 2. February 2017 Permalink

   Hello Stefan, is it a bug in this PU?
   The incremental crawl runs only 1m 30sec, after patching, the incremental crawler runs after psconfig 55m 🙁
   The perfomance from the SQL-Server gows down.
   thx
   Peter

   Reply
   1. 

      Stefan Goßner
      On 2. February 2017 Permalink

      Hi Peter,
      from what I know this has not yet been reported.
      I would recommend to open a support case with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply
5. 

   Henning Eiben
   On 21. February 2017 Permalink

   I just installed the security fix on my SP2016-box, and after running the PSConfig-Wizard I got two errors:
   Exception: Cannot open database “sp2016_SecureStore” requested by the login. The login failed.
   Exception: Cannot open database “sp2016_BusinessDataCatalog” requested by the login. The login failed.
   Looking at the database the user executing the config-wizard doesn’t have permission. DBO of those databases is the farm-account (which I’m usually not using to log-on).
   Checking with an SP2013-box this is the same. My setup-account has no permission, just the farm-account and the services-account. So far I never had a problem. Maybe the upgrade is supposed to be executed by the timer-job, which is running as the farm-account?
   So far I’ve upgraded only using the wizard, not the commandline psconfig.exe – or do I have to run the psconfig as farm-admin? I guess I would also need to add the farm-admin to the local admin-group (which he currently is not).

   Reply
   1. 

      Stefan Goßner
      On 21. February 2017 Permalink

      Hi Henning,
      that has not changed.
      See here:
      https://technet.microsoft.com/en-us/library/cc678863.aspx
      section “Setup user administrator account”
      Cheers,
      Stefan

      Reply
      1. 

         Henning Eiben
         On 21. February 2017 Permalink

         Well, that is true for my setup account – with the exception to the following databases:
         – BusinessDataCatalog
         – SecureStore
         – Sync
         I installed SP2016 using the famous AutoSPInstaller … So I suppose I should grant the setup-account ShellAdmin-Access in order to successfully run the upgrade?

         Reply
         1. 

            Stefan Goßner
            On 21. February 2017 Permalink

            Give it a try!

            Reply
            1. 

               Henning Eiben
               On 22. February 2017 Permalink

               OK, that did work – however, since (as recommended by https://technet.microsoft.com/en-us/library/cc678863.aspx#SharePoint administrative accounts) the SharePoint farm service account is not a local-admin it cannot assign shell-admin permissions. So at first I had to make the farm-admin a local admin, then start an elevated shell as farm-admin grant the setup-account shell-access and then issue the psconfig-command as the setup-account. And of course retract the farm-admin from the local admins prior to logging out of the system.
               Seems like quite som hassel – but, finally it did work – well, after running upgrade-spcontentdatabase on a couple of databases, which didn’t got upgraded properly by psconfig.

6. 

   laurent
   On 14. March 2017 Permalink

   hello Stefan,
   i met this alert on my SharePoint 2013 Platform ” Security Update for Microsoft SharePoint Enterprise Server 2013 (KB3054813) 64-Bit Edition 15.0.4753.1000 Missing/Required”
   could you help me to fix it?
   my SharePoint informations are:
   DisplayName : Microsoft SharePoint Server 2013
   DisplayVersion : 15.0.4571.1502
   DisplayName : Language Pack for SharePoint and Project Server 2013 – French/Français
   DisplayVersion : 15.0.4571.1502
   kind regards,

   Reply
   1. 

      Stefan Goßner
      On 14. March 2017 Permalink

      Hi Laurant,
      I would suggest to open a support ticket with Microsoft on this.
      Cheers,
      Stefan

      Reply