The idea behind the web-based upgrade is a great one, and I thank the developers for bringing this to us. However, as with most things, this new feature could use a bit of improvement. In our case, the SolarWinds services re-start themselves too soon. This causes most upgrades to fail, due to file conflicts. And the same goes when the Config Wizard runs. We devised a workaround but it is very time-consuming and cumbersome. Our work-around involves the following process
- RDP into the respective SolarWinds server to be upgraded
- Stop and disable all the SolarWinds services on the server
- Install the upgrade and/or hotfix on the server
- Confirm that all the SolarWinds services are still disabled. This, since many times, one or more services are re-installed and put back into Automatic status.
- Run the Config Wizard on the server
- Watch for the right time when to re-enable the SolarWinds services. In the case of the core server, this is just when the Website Optimization stage begins. For the APE's, about 15 or 20 minutes after the Config Wizard begins.
We have a lot of Solarwinds servers in our environment. You can imagine how the above process can get old very soon. Thus, I believe, it would be great if the web-based upgrade wizard not only stopped the SolarWinds services but kept them stopped until the right time. Are you too having issues like these? If so, I would very much appreciate your vote.
Have a great day!!! 
