When upgrading the Secure Store database to SharePoint 2016, you may encounter an error if you have applied the May 2017 CU to SharePoint 2013. This CU increments the Secure Store database schema and prevents the upgrade to SharePoint 2016. The error message you’ll see in ULS will be similar to this. SharePoint Server 2016 is looking for a schema version of ‘18.104.22.168’ while the schema on the database was incremented to ‘15
For quite a few years the advice many consultants and administrators would hand out regarding SharePoint updates (hotfixes, security fixes, and of course Cumulative Updates) was “wait and thoroughly test”. Waiting was easy, but testing is always hard. In my personal experience, most companies do not have adequate test harnesses to cover the amount of basic testing that should occur in a production-like environment. This sometimes made
The SharePoint 2016 May 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/help/3191880 SharePoint Server 2016 (wssloc): https://support.microsoft.com/help/3191884 Office Online Server: https://support.microsoft.com/help/3191915 Office Updates: https://support.microsoft.com/help/4020152 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
The SharePoint 2013 May 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/3191911 SharePoint Server 2013: https://support.microsoft.com/help/3191913 Project Server 2013: https://support.microsoft.com/help/3191912 Office Web Apps 2013: https://support.microsoft.com/help/3191888 Office Updates: https://support.microsoft.com/help/4020152 Consider using the SharePoint Patch Cmdlets available at SharePoint
With the release of the April 2017 Public Update, it is now possible to determine MinRole Compliance via PowerShell without any reflection! The process is simple, and as before, it returns a boolean value of true if compliant, false if not, and no value is returned when using the Custom role. To check on all servers in the farm, use: The output will be similar to: And that’s it!
The SharePoint 2016 April 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/en-us/help/3178718 SharePoint Server 2016 (wssloc): https://support.microsoft.com/en-us/help/3178721 Office Online Server: https://support.microsoft.com/en-us/help/3127895/ Office Updates: https://support.microsoft.com/en-us/help/4016803 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your f