SharePoint security fixes released with September 2016 PU and offered through Microsoft Update

8 Comments

1. 

   Mario Alvares
   On 26. September 2016 Permalink

   Hi Stefan,
   Are the fixes in PUs cumulative ? In other words, does the Sep 2016 PU include fixes in all previously released PUs ?
   Thanks,
   Mario

   Reply
   1. 

      Stefan Goßner
      On 26. September 2016 Permalink

      Hi Mario,
      they are cumulative per component – but there are no “Uber” PUs.
      See here for details:
      https://blogs.technet.microsoft.com/stefan_gossner/2014/08/18/sharepoint-patching-demystified/
      Cheers,
      Stefan

      Reply
      1. 

         Mario Alvares
         On 26. September 2016 Permalink

         Thanks Stefan.
         Let’s say I have not installed the PUs for the last year, and want to catch up. I don’t want to install a CU (with Uber packages), since I only want security updates.
         Is there any easy way to determine what PU fixes need to be installed for each component so that I’m up to date? Essentially, I’m looking for some way to get a list of just the latest PU fixes for each component I would need to install to be up to date with all the latest PU fixes. Of course, I could download every PU fix for the last year, and install them all in chronological order, but then I will end up installing some fixes that are superseded by future fixes of the same component, which would be redundant and a waste a time.
         Thanks,
         Mario

         Reply
         1. 

            Stefan Goßner
            On 27. September 2016 Permalink

            Hi Mario,
            you can enable Microsoft Update on the machine and let Windows tell you what is missing.
            Cheers,
            Stefan

            Reply
            1. 

               Mario Alvares
               On 27. September 2016 Permalink

               Thanks Stefan – Good suggestion.
               However, I’ve read some comments on your other blog posts, where Windows Update shows that an update is needed even though the update was included as part of a previously installed CU. To avoid this situation, I was thinking about installing the PU fixes in reverse chronological order (Sep first, then Aug, then July etc.) . In this case, if an older fix for a component has been superseded by a newer fix (that is already installed) for that same component, then the older fix will state that it no longer applies, and will refuse to install, correct ?
               Do you see any issues with this approach ? Appreciate your time and help !
               Thanks,
               Mario

            2. 

               Stefan Goßner
               On 27. September 2016 Permalink

               Hi Mario,
               your assumption is correct.
               Cheers,
               Stefan

2. 

   Shyam
   On 25. October 2016 Permalink

   Hi Stefan,
   I am new to managing SharePoint servers, i recently joined a new job and found that SharePoint is not updated after SharePoint 2013 SP1, we have 2 web front ends, 2 application servers and 2 database servers, i want to update them to the latest SharePoint 2013 update available today, would you be kind enough to help me with the correct process to achieve this. Thank you so much in advance.
   Regards,
   Shyam

   Reply
   1. 

      Stefan Goßner
      On 28. October 2016 Permalink

      Hi Shyam,
      to upgrade from SP1 to the latest CU just download and install it using the links in the following article:
      https://blogs.technet.microsoft.com/stefan_gossner/2016/10/11/october-2016-cu-for-sharepoint-2013-product-family-is-available-for-download/
      Afterwards run the SharePoint configuration wizard.
      Ensure to take backups of SharePoint and SQL databases before applying the fix ensure.
      Cheers,
      Stefan

      Reply