Upgrade from RES ONE Automation 10.2 or 10.2.100
Before you upgrade to Ivanti Automation 2023.1, make sure to meet the prerequisites.
- No database activity will be possible during the upgrade, because all Consoles and Dispatchers will be taken offline until the upgrade has been completed. We recommend to perform the upgrade at a quiet period.
- If you cancel the upgrade process, your environment will remain offline until the upgrade has been completed.
- When you upgrade, existing Add-ons will not be upgraded. They will not be removed, but Help will no longer be available. To upgrade these Add-ons, download the required Ivanti Connectors (formerly known as Automation Packs) from the Ivanti Marketplace, and install them manually. This requires Modify access on the Add-ons node in the Console.
- Make sure Microsoft .NET Framework 4.6.1 (Full version) or newer is installed on all computers on which you want to deploy a Dispatcher.
- Make sure Microsoft .NET Framework 4.5.2 or newer is installed on all computers on which you want to deploy Agent+.
Ivanti Automation 2023.1 uses certificates to encrypt communication between dispatchers and device agents.
Existing Legacy Agents won't be converted to Agents+, nor will they be upgrade to version 2018.1 or newer. Legacy Agent support is no longer available in 2018.1 or newer. In order to switch from Legacy Agent to Agent+, remove the Legacy Agents and deploy the Agent+.
TIP: You can make use of the Deploy Components > Deploy Agent using CSV file built-in task with a parameter for the target devices. At the scheduled time you can pass the parameter as a CSV file containing all the target devices.
NOTE: The Upgrade Pack for 2018.1 or newer won't prefill the credentials for connecting to the database. This is a security feature improvement.
- Run the Ivanti Automation Upgrade Pack (or select Ivanti Automation Upgrade Pack from the Ivanti Automation Installer) on the computer from which you want to upgrade. This computer must be running a Console or Dispatcher.
- If the computers that run the Dispatchers do not have Microsoft .NET Framework 4.6.1 (Full version) or higher and a supported version of Microsoft Windows installed and you continue the upgrade, the Dispatcher(s) will not be able to upgrade and are removed from those computers. To fix this, install the correct framework and deploy the Dispatcher(s) manually. The Upgrade Pack will show a list of Dispatchers that do not meet the requirements and are not be able to upgrade.
- Each Dispatcher needs to run a database driver that makes it possible to connect to the Datastore. If not, the upgrade will continue, but you will be notified to install the relevant database driver afterwards.
- Existing Agents will not be converted to Agents+ automatically.
- Follow the steps of the Wizard.
- During the upgrade process, all Consoles and Dispatchers will be taken offline. When the upgrade has completed:
- All Consoles and Dispatchers will come online again and are upgraded immediately.
- Legacy Agents won't upgrade automatically when they connect to an upgraded 2018.1 or newer Dispatcher. Legacy Agent support is no longer available in 2018.1 or newer. In order to switch from Legacy Agent to Agent+, remove the Legacy Agents and deploy the Agent+.
- The node Administration > Components shows two versions of the Dispatcher and Agent+ MSI file: a 64-bit version and a 32-bit version. When you deploy a new Dispatcher or Agent+, Automation will automatically use the correct MSI file, depending on the Operating System of the target computer.
In the Console, you can check the current version of Consoles, Dispatchers and Agents in the Version column of the Consoles, Dispatchers and Agents nodes.