Note to self

We're having some fun with sharepoint patching this week. I dusted down some old notes and re-acquainted myself with the patching process. Step 1 - find the service accounts! Step 2 - Use the 5 hour script by Russ Maxwell https://blogs.msdn.microsoft.com/russmax/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install/ Step 3 - if you use the script, remember to enable the disabled services (I'm looking at you, IIS Admin service) Step 4 - If psconfig fails (or claims that products arent installed), remember Get-SPProduct -Local and try again Step 5 - If PSConfig fails at the application file stage (merging xml) check the web.config files for comments <!-- blah blah --> Step 6 - Resume the search service application Happy patching!

Why would you bother! I hear myself cry. Surely 2012R2 or 2008 is more appropriate. Well, thats true, but when building a homelab to test patching, and you dont have 2012R2 or 2008 in your hyper-v templates, you have to play with the cards you're dealt. So, pre-requisites thanks to Roger : http://roger.dilsner.com/install-sharepoint-foundation-2013-windows-server-2016-solution/ Import-Module ServerManager Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Met