%ProgramData%\UniversalAutomation\database.db
. The database will not be deleted during an upgrade of any kind. Any schema updates to the database will happen the first time you start up the new version of Universal. You may wish to backup your database before performing an upgrade.%ProgramData%\UniversalAutomation
. Configuration files may be updated or transformed during an update. This will happen the first time that the new version of Universal server is started. You may wish to backup your configuration files before performing an upgrade.appsettings.json
file that is included in the application installation directory will be overwritten during upgrades. To avoid losing your settings in this file, consider installing it into the %ProgramData%\PowerShellUniversal
folder. Universal will look at this folder first for configuration settings. ​web.config
file that is included in the application installation directory will be overwritten during upgrades. If you have moved your web.config file to an alternate location, it will not be overwritten. When creating an IIS website, you can simply include the web.config
file in the web app's directory and have the binaries stored in a different location.%ProgramData%\PowerShellUniversal
during startup of the Universal server. During an upgrade, these files are not deleted. This ensures that dashboards will continue to run on the previous dashboard framework and component versions.%ProgramData%\UniversalAutomation\Repository
. While the upgrade should not affect these files, you may want to backup the files before upgrading.Install-PSUServer
, you can use the Update-PSUServer
cmdlet to upgrade the system. Update-PSUServer
and optionally specify the path to where the executable is stored. -IISWebsite
parameter of Update-PSUServer
.Unblock-File
on Windows to unblock all the files extracted the ZIP. If you do not, PowerShell Universal will not function properly.web.config
file.