Comments for Stefan Goßner

I would like to install SP1 and CU to withour SP1 farm. Is it necessary to run PSConfig before install CU? Is it enough to run PSConfig after continuous install SP1 and CU?

It is sufficient to run it once at the very end.

Sounds good! Thank you for your confirmation.

Thank you. It got fixed after running language independent package.

In reference to this page: https://support.microsoft.com/en-us/help/20170912

Why does it state that PSConfig is required for SharePoint 2010/2016 but not for 2013?

Thank you for your assistance. Your blog has proven to be the most helpful thing on the Internet (at least for me)!

Seems to be a bug in this KB article.

cheers,
Stefan

We are having the same issue after installing July CU. We are opening a ticket. Any chance the September CU would fix the issue?
Karine Bosch

Hi Karine,
I checked in our system but haven’t found any hotfix request for similar symptoms. So I doubt that a fix is avail or even in the works right now.
Cheers,
Stefan

Hi Stefan,
There are some error in your article:
1) SharePoint 2010 instead of SharePoint 2013
2) A more direct link would be: https://support.microsoft.com/en-us/lifecycle/search?alpha=Microsoft%20SharePoint%20Server%202013

Thanks,
Andy.

Hi Andy,
thanks for the hint! I fixed the typo.
The link was intentional to ensure that the whole 2013 server suite (including SharePoint Foundation) is listed.
Cheers,
Stefan

Hi Stefan,
Isnt the mainstream support ending on 4/10/2019 for all CUs released between April 2017 Public Update to March 2018 Public Update?

Thanks
Simon

Hi Simon,
mainstream support is associated with the product – not with a specific patch level.
Mainstream support for SharePoint 2013 will end on April 10th, 2018.
Cheers,
Stefan

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

No Communications Site for on prem?? Wow…. Guess they were too busy announcing 2019 to even worry about giving us old guys the new features.. VERY frustrating.

Hey Stefan,
SP2013 is going away but not in Office 365. It looks like the code base is still SP2013. I know this might not be something you care to comment on but with SP2016 and SP2019 coming, do you know if the SP2013 code base in Office 365 is moving forward as well?

Hi Stefan,
Could you please tell us What’s “Not Applicable” refer to at Mainstream Support End Date for Microsoft SharePoint Server 2013?

Wow, nice ))

Sure. it is not applicable as there is SP1 out and the lifetime is now defined for SP2013 with SP1.
Cheers,
Stefan

Thank you so much!

Hi John,
there seems to be a misunderstanding: all active SharePoint development happens in SharePoint online of Office 365. Every couple of years the code base in SharePoint online is packaged (with some required modifications) as a new SharePoint OnPremise version (SharePoint 2016, SharePoint 2019).
So the code base of SharePoint Online on Office 365 is years ahead of SharePoint 2013.
Cheers,
Stefan

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Yamashita

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Yamashita

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Saran M

Comment on September 2017 CU for SharePoint 2013 product family is available for download by E Veal

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on July 2017 CU for SharePoint 2013 product family is available for download by Karine Bosch

Comment on July 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Andy

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Stefan Goßner

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Simon

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Stefan Goßner

Comment on October 2017 CU for SharePoint Server 2016 is available for download by Islam Khattab

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Jeremy

Comment on Mainstream support for SharePoint 2013 will end in 6 months by John

Comment on Mainstream support for SharePoint 2013 will end in 6 months by M.Qassas

Comment on March 2017 CU for SharePoint 2013 product family is available for download by Mikhail Zhuykov

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Stefan Goßner

Comment on Mainstream support for SharePoint 2013 will end in 6 months by M.Qassas

Comment on Mainstream support for SharePoint 2013 will end in 6 months by Stefan Goßner