Recently I came across the error below when upgrading a SharePoint 2016 farm. Expected product behavior and simply a case of training SharePoint Administrators to use PSCONFIG.EXE command line instead. Cheers!
Command line error.Invalid parameter.
stsadm–oupgrade command has been replaced by psconfig.exe-cmdupgrade
Recently I wanted to create a SharePoint 2016 lab environment. With Excel Services moving out of the SharePoint 2016 product, we now need to plan for an instance of OOS. Below are the steps I followed and screenshots of the process.
Install Windows Server 2012 R2 (en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso)
NOTE – Windows Server 2016 seems to be missing Ink and Handwriting Support.
Run PowerShell to install IIS
# from https://docs.microsoft.com/en-us/officeonlineserver/deploy-office-online-server
The latest version (0.42) includes new PowerShell code for parallel execution of “Upgrade-SPContentDatabase.” This was implemented with “Get-Job” and PowerShell job management to remote sessions.
The more user content databases you have, the greater the time savings. Below are summary statistics from patching a 9 server SharePoint 2013 farm with 200 SQL content databases in just 4 hours. Each of the 9 servers will spawn 4 PowerShell remoting runspaces for “Upgrade-SPContentDatabase.” With 36 concurrent worker threads, the queue of 200 content databases now becomes only 6 deep.
Instead of waiting 200 units of time to process content databases serially, we now only wait 6 units of time for the upgrade database phase.
Larger farms with more user content (and databases) will see significant overall time savings considering how a majority of the traditional patching timeline is processing all content databases. The binary EXE phase runs with all content databases removed (Dismount-SPContentDatabase ) so PSCONFIG can complete sooner. After that is done, content is introduced again (Mount-SPContentDatabase) and upgraded (Upgrade-SPContentDatabase).
As we get closer to the August release of SharePoint 2016 Preview I wanted to create a local virtual machine and try things out. Below are steps with dozens of screenshots. Now I’m ready for the big day to install.
Ideally matching the latest generation of all Microsoft products will give a more integrated experience. Often in the past I’ve seen where features are disabled or less than optimal if another software layer is older. For example, SharePoint 2013 Business Intelligence has many features which only work with SQL 2012. Yes, you can run older SQL 2008R2 but some features will be missing.
Here’s counting down to the SP2013 release … cheers!