Ok, just installed January 2018 CU on SharePoint 2013 farm which was not patched since SP1 before that. It seems the bug from one of the security updates introduced in March 2015 is still there and ruins InfoPath forms.
There is a blog with a solution for that (thanks Kate). Looks like no one reported this to MS since this was not fixed, and now it’s probably too late.
I’ll repost the solution here in case the source will go down, looks like it was not updated for a while… Continue reading
SharePoint patching is always tricky. Difficult to test, difficult to roll back in case of issues, you name it. And every SharePoint pro has the own way to do patching which has been proved reliable and efficient. But now we can rely not only on our own experience and blogs like this one. We have a source of sacred knowledge, passed down from Microsoft itself. Common, grab it faster from Technet Gallery: SharePoint Build to Build Update Playbook
If you are still reading, here is my opinion on this playbook:
- Having any playbook is much better than having no playbook at all. So this will definitely help you if you don’t have a formal approach to updating SharePoint.
- Since every SharePoint deployment is unique, there is no “one size fits all” approach. This playbook requires some adaptation for your customers’ SharePoint deployment. Worth mentioning that the playbook is not version-specific. Some tasks are not applicable for SharePoint 2010, like the one related to distributed cache.
- I would say that many of the tasks mentioned in the playbook can be and should be scripted. For instance, preparation steps like testing content DBs or verifying that there is no verbose logging enabled can be scripted easily.
Happy patching, folks!