There are four components in the User Workspace Management products, formerly known as the AppSense products and DesktopNow suite:
- Configuration Files
- Servers and Databases (Personalization Server and Management Center Server aka Management Server)
Agent and Configuration File Compatibility
For the Ivanti Application Control, Environment Manager and Performance Manager agents, the version of their configuration files is determined by the console that creates them. The general principle is that an agent can use a configuration created by the current and two previous console versions – we refer to this as “N-2 compatibility”.
During an upgrade, this allows a phased rollout of new agents to all endpoints and XenApp/RDSH servers before delivering an updated configuration. See “Component Upgrade Sequence” below for the best process for upgrading components.
We consider a new version to be an increase in the first or second place in the version number: 8.3, 8.4, 8.5, 8.6, 10.0 and 10.1 are all new versions. Note that Feature Releases such as 10.1 FR1 and 10.1 FR2 do not count as new versions for the purposes of compatibility.
Agents can read and use configuration files from earlier console versions than N-2, but this is not a maintained approach and could result in unexpected behavior. When upgrading agents and configuration files from more than 2 versions back, it is best to upgrade them by no more than 2 versions in each step. While it might be possible to upgrade 3 or 4 versions in one jump, this is not a method that has been tested and could produce unexpected behavior.
When using an older configuration with a newer agent in which features have been enhanced or deprecated, the agent will behave predictably but might not offer full functionality until the configuration is upgraded.
Example 1: Environment Manager
|Agent Version||Configuration Verison||Maintained|
|10.0.525.0||8.4.*||No. Version 8.5 and 8.6 came between 8.4 and 10.0, so this would be 'N-3'|
|10.0.525.0||8.5.*||Yes, This will change to 'No' when maintenance ends for EM 8.5 in Dec 2017|
|10.1.336.0||8.5.* or earlier||No, this would be N-3|
Example 2: Application Control (formerly Application Manager)
In version 10.0 the URL Redirection and Custom Rules features were improved substantially. Application Control (Application Manager) agent versions 10.0 and 10.1 will work with an 8.9 configuration, but URL redirection and Custom Rules will be ignored. When the 8.9 configuration is upgraded in the 10.0 or 10.1 console then those features will be restored.
The End of Maintenance Policy and timetables are available here: https://community.ivanti.com/docs/DOC-46825
Agent and Server Compatibility
The Environment Manager Personalization Server, Management Server and File Director server (appliance) are all backwards compatible with older agent versions that have not reached their End of Maintenance date. In other words, new server versions are backwards compatible with any agent that is still within maintenance.
When using a new server with an old agent, server features that have been enhanced or deprecated will not be available.
New agents should not be used with older server versions – in many cases they will simply not connect.
For example: An Environment Manager 10.0 Personalization Server used with an Environment Manager 8.6 agent will continue using the FBR method of storing registry settings, and will not take advantage of the faster hive method until the agent is upgraded.
Agents that are no longer maintained will connect to new server components but this could result in unexpected behavior.
Console and Server Compatibility
Both Management Server and Environment Manager Personalization Server are configured by consoles that are installed as Windows applications.
The Management Center console version must match the Management Server version.
The Environment Manager console version must match the Personalization Server version, if one has been deployed – Environment Manager can be used as a standalone policy tool without a server.
Example of console and server version compatibility:
|Console Version||Server Version||Maintained|
Upgrading from Out-of-Maintenance Versions
When upgrading server and database infrastructure from more than two versions back, it is best to upgrade by no more than 2 versions in each step. While it might be possible to upgrade 3 or 4 versions in one big jump, this is not a method that has been tested and could produce unexpected behavior.
SQL Server Versions
The versions of SQL Server on the maintained platform list for Environment Manager Personalization Server and Management Center have changed over time. For example, SQL Server 2008 was dropped in version 10.0. You can see the list of maintained platforms and versions at https://community.ivanti.com/community/appsense.
Component Upgrade Sequence – EM, AC, PM, MC
More information is available in the documentation (https://help.ivanti.com/ap/help/en_US/dtn/10.1/Content/Install%20and%20Configure/Product%20Upgrade.htm#UpgradeEnvironmentManager) but, briefly, the correct order is:
- Upgrade the Personalization and Management Servers (if used). If the consoles are installed on the servers then they can be upgraded at the same time.
- The Server Configuration Portal will prompt the administrator to upgrade the databases. (See comment above about SQL Server versions – you might need to upgrade SQL Server too if the databases are not on a version which is a maintained platform).
- Upgrade any consoles that have not been upgraded in step 1.
Note: if you use the upgraded Environment Manager console to open an existing configuration file it will upgrade it. Do not deploy the upgraded configuration file until new agents have been deployed.
- Deploy the new agents to endpoints and XenApp/RDSH servers
- Finally, upgrade and deploy the configuration files
Component Upgrade Sequence – File Director and Insight
More information is available in the documentation (https://www.ivanti.com/support/product-documentation and click on “File Director”) but, briefly, the correct order is:
- Upgrade the File Director (or Insight) appliance using the patch provided.
- Note: Security Updates are distributed as patch files separately, and can be applied independently to server updates
- In the case of a clustered File Director environment the external SQL server database will be automatically updated. File Director 4.0 or later will patch the entire cluster during this process. This action is performed by the nominated Cluster Patch Master.
- Deploy the new File Director (or Insight) agents to endpoints.