⚐ 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.
In this release note you will find:
- ADM installation in a new database.
- ADM migration to version 9.22.1
- Manual Conserver Update
- Updating the conserver through a Distribution project
- Automatic Agent Update, Console version 9.22.1 will only be compatible with agent versions 9.21.2 or more.
- ADM is released with common version 9.10.0.10
- ADM is released with tests in the 9.5.49 unified database
⚐ Note: Starting with this version 9.22.0, at least the SQL Server 2019 engine is supported.
Integrated projects:
- Aranda.ARC.Controller 9.5.1.5
- @aranda/aranda.remote.control: 1.1.5
⚐ IMPORTANT: - Remember that in joint installations between Aranda products, you must have the same compatibility as the Common version.