⚐ Note: Before upgrading, verify that the database collation is at (SQL_Latin1_General_CP1_CI_AI).

⚐ Note: If you need to migrate the database collate: See Migrate Collate to Database

⚐ Note: In ADM system implementations in Onpremise environments, when migrating from versions equal to or lower than 9.22.0 to version 9.22.1 or higher, it is essential to perform an additional action related to the update folders (AgentUpdate) and recordings (Recordings) to ensure the correct visualization of audits and installation of the agents. The steps are listed below:

Folders to move

During the upgrade, the following folders and their contents must be moved from the original path of the repserver:

• %dir_Repserver%\AgentUpdate
• %dir_Repserver%\Recordings

%dir_Repserver% refers to the path configured for the Repserver default C:\Repserver\

To the directory configured for the Content Manager.

The structure must be preserved as is, that is:

• %dir_ContentManager%\AgentUpdate
• %dir_ContentManager%\Recordings

%dir_ContentManager% refers to the path configured for the Content Manager default C:\ContentManager\

Important: The exact names of the folders (AgentUpdate and Recordings) should be retained to ensure compatibility with system services.

Consequences of skipping this action

If these folders are not moved:

• Recordings will not be displayed correctly in audits.
• Inconsistencies will occur in system logs.
• Agents will not be able to be downloaded correctly.

1. Generate a backup of the database to be updated.
2. Stop the following Aranda services manually or by using Aranda DataBase Tools:

• Aranda Conserver V9
• Aranda Cruncher Catalog
• Aranda Cruncher Energy
• Aranda Cruncher File
• Aranda Cruncher Inventory
• Aranda Cruncher Patch
• Aranda Cruncher Usage
• Aranda License Windows Service
• Aranda Scheduler Windows Service
• Aranda Worker Windows Service
  1. Uninstall the Aranda Conserver Service and Aranda DEVICE MANAGEMENT programs from the control panel.
  2. Delete the records in the following folders:
• Delete the contents that are in the “%Program Files (x86)%\Aranda\Aranda Services” folder
• Exception of the ‘Downloads’ folder, because the patch catalog is saved in it.
• “%Program Files (x86)%\Aranda\Conserver” folder except for the ‘Data’ folder.
• “%inetpub\wwwroot\ADM” folder
• “%inetpub\wwwroot\RepServer” folder

⚐ Note:: Do not delete the contents of the Container, Repserver, and Conserver repositories.

1. Check the requirements before running the installer Aranda.ADM.Web.Installer.exe. View ADM Console Installation
2. Run the installer Aranda.Conserver.Installer.exe. Do not upload services until the repserver and the .config from the conserver’s folder. View Installation Conserver
3. Run Aranda DataBase Tools so that all files .config to point to the migrated database (see execution steps in the KB document).
4. Upload Aranda services, either by the Aranda DataBase Tools application or by the list of services:

• Aranda Cruncher Catalog
• Aranda Cruncher Energy
• Aranda Cruncher File
• Aranda Cruncher Inventory
• Aranda Cruncher Patch
• Aranda Cruncher Usage
• Aranda License Windows Service
• Aranda Scheduler Windows Service
• Aranda Worker Windows Service
  1. Verify the repserver connection from the web console.
  2. If you have the Mosquitto MQTT service, you must uninstall it View installation in the Uninstall Mosquitto MQTT Broker section, then run the MQTT broker installer Aranda MQTT Broker Installation
  3. Configure the file Aranda.Conserver.Windows.Service.exe.config what’s in the folder %Program Files(x86)%\Aranda\Conserver.
  4. Start the service Aranda Conserver V9.
  5. Verify that all Aranda services are running.

⚐ Note:
- If you are required to uninstall an Aranda product other than ADM, an error is generated when entering the ADM console and it will not be possible to access it.
- For the installation of the ADM and Conserver console, the server is required to have version 4.8 of the .NET framework (net48)
- Remember to update the agent of the different machines so that they can access the latest changes; For this we recommend:

Update by domain policy.
Update by agent distribution (Conserver on the client network).
Manual update.