I am about to run the following command in production but I would like a solid understanding of what could break. We ran this command on QA environments, but we don't know if everything is in fact running, as far as we can tell it is, but I would like to know if there is a possibility that this could break things such as workflows, features or anything else.
Here is the command:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
According to documentation: There are actually 3 commands in one:
- psconfig.exe –cmd upgrade
- psconfig.exe –cmd applicationcontent
psconfig.exe –cmd installfeatures
Psconfig.exe -cmd upgrade => Perform SharePoint upgrade. This command is automatically executed when running the SharePoint Products configuration Wizard if SharePoint needs to be upgraded.
inplace b2b ==> If b2b is chosen, then an in-place build to build upgrade will be performed. The other option is v2v (version to version)
force ==> The SharePoint Products Configuration Wizard stops any currently running upgrade actions, and then restart upgrade.
-cmd applicationcontent ==> Manages Shared application content
-cmd installfeatures ==> registers the SharePoint features in the server farm that are located on this server.
We will take a full farm backup (using SharePoint 2010 backup feature) to backup/restore the farm in place in case there is something wrong. Is this the recommended approach?
According to one user the last time they did this on the farm the workflows were gone. Is there a possibility of this happening after this command is ran on all farm servers?
Thank You for reading.