EN
Español
English
Português
    Known Issues
    • Cada vez que se apague el servidor donde está instalado el conserver, valide que el servicio esté arriba; en algunas ocasiones el servicio no inicia ArandaConserverWindowsServiceV9 al cargar el sistema operativo.
    • El conserver depende de servicios propios del sistema operativo para poder ser iniciado automáticamente. En ocasiones windows intenta iniciar el servicio `ArandaConserverWindowsServiceV9` antes de los servicios propios requeridos del sistema operativo y se presenta una falla.

      Workaround: Enter the machine where the conservator is installed and upload the service manually.

    • En el resumen de una actualización pendiente no es posible visualizar la arquitectura en la que se aplica dicha actualización; por restricción del proveedor no es posible obtener esta información antes de descargar la actualización.

      Workaround: View the update details after downloaded; Below the name is the installer with the version and architecture.

    • No es posible instalar parches con extensión .iso . Se detectan las máquinas que lo necesitan, pero no se aplica el parche desde la consola.

    • Due to vendor restriction, it is not possible to apply OS updates with .iso extension.

      Workaround: In the following link you can see an example of script for Windows 10-1809 OS update using version Windows installation assistant (https://docs.arandasoft.com/adm-ts/en).

    • If you save the device mapping and then update the mapping information in the service directory again, the mapped information will be removed from the device filters.

      Workaround: Perform the service directory mapping configuration and then configure device mapping.

    • When a Remote Control Support session with Aranda Remote Control (ARC) expires and the window is not updated, taking remote control launches the Specialist Viewer, but it closes immediately.

      Workaround: Reload the page to update the information or reauthorize the support session.

    • In the AI configuration, you may encounter an error when editing an endpoint, however, the changes made are saved.

      Workaround: Reload the page to update the information

    • In device groups, it is only displayed in the main listing until it reaches a subgroup within the parent group. If there is another subgroup within that subgroup, it is not displayed in the hierarchical main list.

      Workaround: If you want to check the hierarchical list of groups, you can do so from the User Groups menu. Get the name of the group, and then search for it in the Device Groups menu using the search filters.

    • When importing devices by name, if the name contains special characters that are valid depending on the operating system (for example, macOS), an error occurs invalidFileContainsNames and the device is not imported.

      Workaround: Completely close the File Import modal so that the system allows the same file to be reloaded, changing its name to the IP of the device.