NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
When SharePoint Server Distributed Cache is unhappy in a farm, you may see page loads error, 404s not found, API failures, and similar. Having a well configured Distributed Cache will ensure healthy page renderings. PowerShell notes below. Credit to one awesome long term SP engineer for the snippets below. Thank you. Cheers!
To check the status of the Distributed Cache Servers, run this command on each Farm from a DC machine.
There can be only one IsLeadHost=True server in a Farm. If there is more than is IsLeadHost=True servers your Farm will act unstable and people will see page load errors. We traditional set the lowest server name alphabetically in a Farm as IsLeadHost. Change the DC Farm so that Service Status=DOWN on server.
Also notice our default DC cache size is only 819 MB. MSFT formula = 24GB-2GB=22GB/2GB=11GB. Typical recommendation for a 24GB server is no more than 8GB Cache size. If running 24GB RAM on WFE, we should allocate 6GB (1024*6=6144 MB).