Hi Carla,
it is impossible that you installed December CU because this CU is planned to be released next week.
It should include the fix.
Cheers,
Stefan
Hi Carla,
it is impossible that you installed December CU because this CU is planned to be released next week.
It should include the fix.
Cheers,
Stefan
Oh, ok, sorry! That’s what I was told by my team 😉
Thank you very much!
Does this apply to modern pages as well, or just classic pages? It is working for classic pages, but not on modern.
Hi Stefan, We are planning to install November 2019 sharepoint2013 CU. Kindly confirm is there any Regressions.
Hi Stefan,
We had observed this issue when upgraded to October 2019 CU in our test environment, access delegation mails were sent out to Deleted users’ manager, can you please provide me details on it, what got changed as such and a cause of triggering such mails, I have tried google a lot to get more details on it but no luck. Also, can you please share comparison document between RTM and October 2019 CU.
Thanks.
Hi Samir,
I have not heard about such an issue and would suggest to open a support case for this.
Cheers,
Stefan
Hi Ilaiyaraja,
this always depends on which fix level you are right now.
Cheers,
Stefan
Hi Leonard,
afaik this applied to both but this has been fixed already with July 2019 CU.
Cheers,
Stefan
Hi Sir,
I am not able to download security update KB4011127 from given link this is showing (404 – file or directory not found ) error could you please provide any other link form where can i download the security update
Hi, this fix is meanwhile unsupported.
Everything older than May 2018 CU is unsupported per our support policy.
See here for details:
https://blog.stefan-gossner.com/2017/05/15/updated-product-servicing-policy-for-sharepoint-server-2016/
As our fixes are cumulative it is not necessary to install that old fix.
Install a recent fix and it will include this security fix.
Cheers,
Stefan
What do you do if you have windows server 2012 R2 installed?
Hi James,
SharePoint Server 2013 with SP1 supports Windows Server 2012 R2.
Cheers,
Stefan
Hi Stefan,
What about compatibility levels? in the following article its suggested that the performance of SP2016 would increase and SQL resources would decrease in case of using SQL2012 Compatibility level (110) instead of SQL 2014 or SQL 2016 (120 or 130).
This is probably because Microsoft changed the Cardinality Estimator on SQL 2014.
unfortunately, Microsoft didn’t mention anything about this for SP 2013 in any document that i’ve looked in to.
What would be your suggestion for SP2013 in that case? 110 or 100?
Hi Guy,
the article was only required as – at the time it was written – SharePoint Server 2016 did not take care of correctly adjusting the compatibility level.
Current patch levels of SP2016 update the compatibility level during database upgrade installations / patching.
SharePoint Server 2013 supports the highest compatibility level of the support SQL server versions and you do not have to manually adjust it.
Cheers,
Stefan
I maybe early, however I am getting https://www.microsoft.com/en-us/download/details.aspx?id=100723 We are sorry, the page you requested cannot be found.
The URL may be misspelled or the page you’re looking for is no longer available.
Same on the KB link – https://support.microsoft.com/en-us/help/4484181/december-10-2019-update-for-sharepoint-enterprise-server-2016-kb448418 same error. Maybe too early / fast. 🙂
Hey Stefan,
is this not a fix for SharePoint? https://support.microsoft.com/de-de/help/4484177/december-10-2019-update-for-sharepoint-server-2019-kb4484177
Thx
Peter
Hi Stefan,
Thanks for the update. Currently production Farm is April 2019 CU and Test Farm August 2019 CU.
Thank you 🙂
calendar overlay fix included?