EN
Español
English
Português
    ADM Console Update

    Before upgrading the ADM console, you should consider the following recommendations:

    FOLDERS TO MOVE: During the upgrade, if they exist, the following folders and their contents must be moved from the repserver repository

    • %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: Keep the exact names of the folders (AgentUpdate and Recordings) to ensure compatibility with system services. Keep.

    CONSEQUENCES OF OMITTING THE 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.


    To update the ADM console, consider the following instructions:

    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  
    

    3. Uninstall the Aranda Conserver Service and Aranda DEVICE MANAGEMENT programs from the control panel.

    4. Delete the records in the following folders:

    - Borrar el contenido que se encuentra en la carpeta “%Program Files (x86)%\Aranda\Aranda Services”
    - Excepción de la carpeta ‘Downloads’, debido a que en esta se guarda el catálogo de parches.  
    - Carpeta “%Program Files (x86)%\Aranda\Conserver” a excepción de la carpeta ‘Data’.  
    - Carpeta “% inetpub\wwwroot\ADM”  
    - Carpeta “% inetpub\wwwroot\RepServer”  
    

    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
    

    5. Verify the repserver connection from the web console.

    6. 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

    7. Configure the file Aranda.Conserver.Windows.Service.exe.config what’s in the folder %Program Files(x86)%\Aranda\Conserver.

    8. Start the service Aranda Conserver V9.

    9. 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.