For the WebServices - These will be for example Update-AtriaMSOL for the Microsoft Online service, or Update-AtriaADFS for the ADFS component. For a full list of these, please see the "Notes" section at the bottom of the page.
If you run the Update- command on a component which doesnt need updating, the process will retrieve and redeploy the same version. This can be handy for solving problems, but it will slow the update down
if the component hasnt been deployed, and you attempt to run the update command, the process will likely fail (this is logged for improvement)
Start on the Platform provisioning server
(Typically it has most of the back-end components which are more likely to change, (i.e. components 1 through 8 above))
Find the components that need updating, update them in the above order
Update any web services on the machine at the same time
Move to the Web Server
this will also have more frequent changes
Repeat the same process
Install Atria.Tools.Setup-Bootstrap from Powershell Gallery
- [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
- Install-Script Atria.Tools.Setup-Bootstrap
- Atria.Tools.Setup-Bootstrap.ps1 -username 'any username' -PersonalAccessToken 'access token provided by Automate101'
Setting the Web Service credential
If this is the first time you are performing an upgrade, there is chances that the Atria Service Schema credential hasn't been set. Please run the below to set this (It is a one time configuration)