Appsense DesktopNow 8.x Update Process

The following desribles the basic upgrade process that should be used for both major and minor release updates.
Major version changes should be checked in the documention for more details as there are some more caveats.

Pre-Reqs
Backup the database
Save out all the configurations (as MSI)
Take personalisation servers offline. (Disable NLB)

Update Order
Management Server  (may update database)
Management Console
Personalisation Server (may update database)
EM Console
Client Agents
Client Configurations

Server & Consoles
Update the Management server components first. This may perform a schema update on the database on the 1st server to be updated. Other servers will all need to be updated to recognise the updated schema.
The Management consoles will also all need to be updated at this point.
Personalisation Server should then be updated along with the EM console.

At this point agents and configurations can continue to work as there is forward compatibility.
Putting out Client Agents first is riskier as they are not tested against older management server.
However there is a risk as the consoles have new features that will not be supported by the agent.

Agents & Configuration
The configuration can be updated by simply opening the existing configuration, and answer YES to the upgrade prompt. The new Config & Agent can then be deployed by the management console.

Note : Personalisation Changes, 8.5 does not use "Session Data" and "Desktop Setting" as in past versions. This functionality is now part of "Windows Personalisation"
In version of 8.3 and 8 FR4 the conversion is handle by an migrate process that occurs as each users logs on. The older setting are kept and will show up as (legacy) in the Personalisation view. These setting can later be deleted with a script.