EN
Español
English
Português
    Self-Diagnostic Agent

    This agent allows you to diagnose the ADM modules required for the agent’s operation. It includes communication tests to the ADM site, verification of the site and station communication ports, validation of permits, and review of the status of the services that the modules require on the equipment. To perform the self-diagnosis, follow these steps:

    1. Download and save the package Aranda.Diagnostics.ADM.Agent.Web.9.x.x.x.exe.


    ⚐ Note: The Policies It is not available in version 9.25.2 of the Self-Diagnostic Agent.

    ⚐ Note: Since version 9.25.2, only tests for ARC remote control have been performed. No tests are run for file transfer, gateway remote control, or the old LAN remote control.

    ⚐ Note: Starting with version 9.25.2, when the self-diagnostic tests are completed, the created test devices are automatically inactivated; they are only visible in the console while the test is in progress. The same is true if the test is canceled or interrupted unexpectedly.


    2. Run the file as administrator Aranda.Diagnostics.ADM.Agent.Web.9.x.x.x.exe. Once executed, a window of the computer’s default browser opens with the local address of the machine and port 5080. The tool is available in Spanish, English and Portuguese.

    ⚐ Note: The tool takes the language from two sources: the web interface (steps, buttons, and labels) uses the browser’s language, and the test result messages and the icon notices in the notification area use the Windows display language. If these settings do not match, the information is combined in both languages, including the downloaded report. Therefore, it is recommended to configure the browser and Windows in the same language. When the settings correspond to a language other than English or Portuguese, the tool is displayed in Spanish.


    There are two ways to set up self-diagnostics before starting it: automatic and manual.

    ⚐ Note: The fields Local Turn, Port and Using SSL correspond to the configuration of the TURN server that uses the remote control (ARC): its IP/DNS, its port and whether the connection uses SSL/TLS. In Cloud environments hosted in the Aranda Software, the fields Local Turn and Port they can be left empty: when starting the self-diagnosis, the tool checks whether the entered URL belongs to that infrastructure and, if so, uses the default settings. If the URL does not belong to that infrastructure, fill in both fields; otherwise, tests 27 and 28 are failed.


    Self-diagnostics with automatic configuration

    When you enable this option, the tool first checks whether the agent is installed and, if so, validates which modules it has enabled in the agent’s database. Once this option is selected, the tool updates the information in the following fields and marks only the modules detected in the agent’s database as selected:

    Field Description
    State Indicates whether the agent is installed on the station.
    Version found Indicates the version of the agent installed on the station.
    Setup Date Indicates the date on which the agent profile was set up at the station.

    Once the agent information is detected, click the Start Diagnosis.


    Self-diagnostics with manual configuration

    This section is enabled when the Automatic configuration is disabled. With it you can perform self-diagnosis to specific modules: Inventory, Distribution, Remote control and Patches. To use this setting, fill in the Server URI with the URL of the node you want to diagnose (example: https://dnsconsola.com/Repserver or https://dnsconsola.com/Conserver).

    Once the URL is entered, select the modules you want to diagnose. If you enable the Remote control, fill in the fields Local Turn, Port and Using SSL as indicated in the previous note. Once you have filled out the necessary information, click on the Start Diagnosis.


    3. Once the diagnosis has started, the progress of each test is displayed according to the modules activated at the beginning. The progress bar advances at the end of the tests and indicates the number of tests to be performed and the missing ones. At the bottom of the bar, successful tests are counted, with alerts, errors and pending.


    At the bottom of the screen are the buttons Cancel and View Report. The latter is enabled when all tests are finished or when you click Cancel before they finish.

    4. When the tests are complete, click the View Report To view the results: Successful, alerted, and failed tests, as well as the total diagnostic time. In the visual map of findings by module, you can see the percentage of successfully completed tests and the number of tests that were performed on each module.


    5. The bottom shows the detail of each test performed; if a test presented any alerts or errors, its detail is displayed. In this section you can also search by module (General, Inventory, Distribution, Patches or Remote control) or by test title, and filter by status (All, Errors, Warnings, Correct u Omitted).


    Filter by Name


    Filter by module


    Filter by Status


    6. At the end of the report, find the options to download the results in a file JSON or PDF, Run again diagnostics with the same settings entered at startup or starting a New diagnosis with another configuration.


    7. If you close the browser window, the process continues to run in the background. To reopen it, go to Taskbar > Notification Area > Show Hidden Icons and locate the self-diagnostic tool icon. Double-click on it to open the window again, or right-click to see two options: Open Diagnostic and Get out. The latter completely shuts down the process of the self-diagnostic agent.


    Explanation of each test performed by the self-diagnostic agent and possible errors

    The following describes each test performed by the self-diagnostic tool and any possible errors that may occur due to local firewall or antivirus restrictions, network issues, or missing console configurations:

    1. Equipment architecture verification.

    Verify the operating system architecture and folders Program Files.


    2. Windows Management Instrumentation (WMI) service status.

    The status of the Windows Management Instrumentation (WMI) service is queried and checked for In Execution.


    Example of error:


    This error is caused by a service failure Windows Management Instrumentation (Winmgmt). Check that the service is enabled and started, and that it is not blocked by a domain policy.

    3. Query using the Windows Management Instrumentation (WMI) service.

    A basic query is performed that requests the edition, version, and architecture of the operating system.


    Example of error:


    The most common causes of this error are:

    • The service Windows Management Instrumentation (Winmgmt) is enabled, but the user doesn’t have permissions on the component Control WMI. Contact your administrator to assign permissions.
    • Firewall-level blocking of the port used by WMI.
    • Corrupt or non-existent namespace in the module Control WMI.
    • DCOM Disabled for Computer in Module Component Services.

    ⚐ Note: Although it is recommended that you run the utility as an administrator, for WMI-related tests validate the execution with an end user who is not an administrator, for environments where UAC is used. The most common errors with the WMI service occur with users who do not belong to an administrator group and do not have execution permissions.

    4. Validation of privileges of the user running the tool.

    Validates whether or not the user running the self-diagnostic tool belongs to the administrators group, and whether the tool is running as an administrator.


    Example of an alert:


    5. Verification of the ADMIN$ share.

    It is validated by a query if, among the shared resources, the resource exists ADMIN$ with access to the C:\Windows path, or if there is a domain policy that blocks access to this resource.


    Example of error:


    The most common causes of this error are:

    • The tool runs with a user who belongs to the administrators group, but is not the built-in Windows administrator. In that case, validate that the registry value exists LocalAccountTokenFilterPolicy = 1 in the following path:
    • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    • The resource is restricted from access by using the record value AutoShareWks = 0 in the following path:
    • Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    • The resource is not shared in Managing Teams > Shared Folders > Shares.

    6. Checking for antivirus exclusions in Microsoft Windows Defender.

    Validates if there are exclusions in the operating system’s antivirus Microsoft Windows Defender that may affect the functioning of the agent.


    Example of error:


    The most common cause of this error is:

    • You don’t have sufficient permissions. For this test, we recommend running the Self-Diagnostic Agent as an administrator if the user has UAC restrictions.

    7. Verification of the geolocation service and location permissions.

    The Geolocation Service (LFSVC) to check if it’s enabled and running. It also checks to see if there’s a domain policy blocking location services.


    Example of error:


    The most common causes of this error are:

    • The Geolocation Service (LFSVC) It is not enabled or has access restrictions by domain policy.
    • There are domain policies that restrict access to the location. If any of these registry values (DisableLocation, DisableSensors, DisableWindowsLocationProvider) exists with DWORD = 1, remove it from the following path:
    • Team\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors

    8. DNS/TCP verification.

    A TCP connectivity test is performed to the host and port configured in the file appsettings.json, DNS resolution is verified, and response times are captured.


    9. HTTP verification to the supplied base URL.

    The HTTP response of the supplied base URL is checked to confirm that it responds correctly, and response times are captured. This test only applies to the Repserver node; it is ignored for the Conserver node.


    Example of error:

    Tests 8 and 9 share the same failure scenario: a possible restriction of communication to the URL being tested. Validate that the computer has an Internet egress, review the network restrictions configured in the firewall, and add the exception for the node URL.

    10. Verification of download of the default agent profile.

    The URL where the default dialed agent profile is stored in the console is queried. The query returns, in JSON format, the profile configurations and captures the response times.


    Example of error:


    • This error can occur when pointing to a Conserver, due to the absence of the resource in its file storage path. Run the self-diagnostic test again: During the first run, which generates the error, the Conserver processes the task that requests the resource and stores it.
    • If the error persists when retrying, it may be due to the absence of the storage path configuration for the Server you are pointing to. For more information, see Communications.

    11. Verification of the available version of the ADM agent.

    The latest available version of the ADM agent is queried. The output displays the available file name, identifier, and download date, and the response time is captured.


    Example of error:


    No version data is available because the task responsible for downloading this information has not been executed. For more information, see Deploying Agents.

    12. Agent installer verification.

    It verifies that the ADM agent’s .EXE resource exists on the storage path configured for the queried node.


    Example of error:


    • The error may occur when pointing to a Conserver, due to the absence of the resource in its file storage path. Run the self-diagnostic test again: During the first run, the one that generates the error, the Conserver processes the task that requests the resource and stores it.
    • If the error persists when retrying, it may be due to the absence of the storage path configuration for the Server you are pointing to. For more information, see Communications.

    13. Node connectivity test.

    Connectivity to the detected node is tested with the automatic configuration or to the one entered in the manual configuration, and it is verified that it responds appropriately.


    Example of error:


    This error is caused by a communication failure with the diagnosed node. Check that the Conserver service is operational and running, and verify the firewall rules.

    14. Device registration.

    A request is sent to the console to create a test log with random data and verify that the devices are registered correctly.


    ⚐ Note: If your console version is lower than 9.25.2, when you finish the self-diagnostic tests, it is recommended that you delete the test logs created in the console. If there are multiple tests, filter them by status No inventory and agent 9.12.2110.106Select More options > All and then Remove devices.

    Example of error:


    This error is caused by a communication failure with the diagnosed node. Check that the Conserver service is operational and running, and verify the firewall rules.

    15. Verification of operation of remote administration over LAN network.

    If the EnableServerNotification is set in False, it is verified at the station that port 9025 is available and that no other programs or services are using it. If the agent is already installed, it is verified that the port is associated with the agent process and in listening mode.


    Example of error:


    If you have the agent installed, check in Network > Resource Monitor > Listening Ports that the process Aranda.Agent.ACOREService.exe is running with port 9025. Validate that the column Firewall Status indicate Allowed, not restricted; If not, check your firewall rules.

    16. Verification of the operation of remote administration by outbound connection.

    If the EnableServerNotification is set in True, a request is sent using the WebSocket protocol to the site identified in the registration procedure (test 14). The utility verifies that the plug-in is installed and that the site is protected with HTTPS.


    Example of error:


    The most common cause of this error is:

    • Lack of HTTPS configuration on the diagnosed node. For more information, please refer to the following link:

    17. Notification site verification.

    The Repserver/notificationmessage site is verified to be available and response times are captured.


    Example of error:


    This error can occur because the server is saturated and therefore times out, or because of incorrect configuration in the site’s connection string.

    18. Minimum TLS verification.

    The version of the TLS cryptographic protocol handled by the site to which the diagnostic test points is verified.


    Example of error:


    Verify that the server meets the minimum requirements, such as the minimum supported version of TLS (1.2). For more information, see the note Things to keep in mind of the article Requirements.

    19. Verification of the MQTT/IoT Action Submission Component.

    A pre-validation is carried out by verifying whether the parameter DeviceMessageConfiguration is configured in the database. If it exists, a connectivity test is performed to the MQTT using the IP/DNS and port configured in that component.


    ⚐ Note: In the current version, it is not possible to perform a connectivity test to the IoT component configured in DeviceMessageConfiguration.

    If the parameter does not exist DeviceMessageConfiguration, is validated if an MQTT is configured in the file Web.config of the Repserver and a connectivity test is performed using the IP/DNS and port configured in that component.


    Example of error:


    • Check to see if the firewall rules have any restrictions for the IP or DNS configured in the MQTT component by port 1884.
    • Validate that the server’s MQTT service is operational.
    • Verify that the IP/DNS and port are set in the file Web.config of the Repserver.

    ⚐ Note: This test is only performed when the node ingrested or detected, in manual or automatic configuration, is a Repserver.

    20. Validation of the MQTT Action Submission Component.

    A connectivity test is performed to the IP/DNS and port configured in the file appsettings.json of the Conserver.


    Example of error:


    • Check to see if the firewall rules have any restrictions for the IP or DNS configured in the MQTT component by port 1884.
    • Validate that the server’s MQTT service is operational.
    • Verify that the IP/DNS and port are set in the file appsettings.json of the Conserver.

    ⚐ Note: This test is only performed when the node ingrested or detected, in manual or automatic configuration, is a Conserver.

    21. Inventory shipment verification.

    A test file is uploaded to the storage path configured for the diagnosed node.


    ⚐ Note: When you finish the self-diagnostic tests, it is recommended that you delete the test files created in the storage path configured for the diagnosed node. These files are stored in the Exception.

    Example of error:


    The most common causes of this error are:

    • There is no valid local file storage or blob storage path configured for the node you are targeting. For more information, see Communications.
    • You don’t have read and write permissions on the local or blob file storage path configured for the node you’re pointing.

    22. Validation of the WebSocket component for remote control.

    A request is sent using the WebSocket protocol to the site identified in the registration procedure (test 14). The utility verifies that the plug-in is installed and that the site is protected with HTTPS.


    Example of error:


    The most common cause of this error is:

    • Network restrictions configured in the firewall. Add the exception for the DNS and port shown in the output.

    23. File Verification vncSettings.json or rfbSettings.json.

    Files are verified vncSettings.json or rfbSettings.json, the AcceptRfbConnections of False to True to run the following remote control tests and the service starts Aranda Remote Control VNC.


    Example of error:


    The most common causes of this error are:

    • The files do not exist in the path C:\Program Files\Aranda\Aranda Remote Control\Workstation.
    • You do not have permissions to modify the file. For this test, we recommend running the Self-Diagnostic Agent as an administrator if the user has UAC restrictions.
    • The agent Aranda Remote Control Workstation It is not installed.

    24. Service verification Aranda Remote Control Workstation.

    The service is consulted Aranda Remote Control Workstation to verify if it is enabled and running.


    Example of error:


    The most common causes of this error are:

    • The service Aranda Remote Control Workstation is disabled.
    • The agent Aranda Remote Control Workstation It is not installed.

    25. File Verification Aranda.ARC.Workstation.exe and Aranda.AVS.VNC.Application.exe.

    Files are verified for existence Aranda.ARC.Workstation.exe and Aranda.AVS.VNC.Application.exe.


    Example of error:


    The most common causes of this error are:

    • The files do not exist in the path C:\Program Files\Aranda\Aranda Remote Control\Workstation.
    • The agent Aranda Remote Control Workstation It is not installed.

    26. Service verification Aranda Remote Control VNC.

    Service status is checked Aranda Remote Control VNC.


    Example of error:


    The most common causes of this error are:

    • The service Aranda Remote Control VNC is disabled.
    • The agent Aranda Remote Control Workstation It is not installed.

    27. Testing TCP connectivity to the IP/DNS of the TURN server.

    A TCP connectivity test is performed to the IP/DNS entered in the field Local Turn or, if the field is empty in environments housed in the infrastructure of Aranda Software, to the default setting.


    Example of error:


    The most common cause of this error is a restriction on the firewall for egress to the Internet. If so, add the exception for the IP/DNS that shows the test result.

    28. Test of connectivity to the TURN server port.

    A TCP connectivity test is performed to the port entered in the field Port or, if the field is empty in environments housed in the infrastructure of Aranda Software, to the default setting.


    Example of error:


    The most common cause of this error is a restriction on the firewall for egress to the Internet. If so, add the exception for the port that displays the test result.

    29. Test of message exchange between server and station.

    The Exchange plug-in is used to exchange messages between the TURN server and the station where the self-diagnostic agent is running.


    Example of error:


    The most common causes of this error are:

    • There is a restriction in the firewall for egress to the Internet. If so, add the exception for the IP/DNS and the port that displays the test result.
    • The agent Aranda Remote Control Workstation It is not installed.

    30. Remote control test using RFB/VNC.

    The RFB protocol and the Aranda Remote Control VNC to simulate a remote control to and from the same station where the self-diagnostic agent is running.


    Example of error:


    The most common causes of this error are:

    • The service Aranda Remote Control VNC is disabled.
    • The agent Aranda Remote Control Workstation It is not installed.

    31. Verification of the number of processes running the service Aranda Remote Control VNC.

    Verify that during test 30, two service processes are running Aranda Remote Control VNC: one as SYSTEM and one as the user running the self-diagnostic agent.


    Example of error:


    The most common causes of this error are:

    • The service Aranda Remote Control VNC is disabled.
    • The agent Aranda Remote Control Workstation It is not installed.
    • You don’t have sufficient permissions. For this test, we recommend running the Self-Diagnostic Agent as an administrator if the user has UAC restrictions.

    32. Restoring changed files and services.

    As a last step, the files are restored vncSettings.json or rfbSettings.json to its initial state, changing the AcceptRfbConnections of True to False. In addition, the service is stopped Aranda Remote Control VNC and the processes that the self-diagnostic agent has initiated with that service.


    Example of error:


    The most common causes of this error are:

    • The service Aranda Remote Control VNC is disabled.
    • The agent Aranda Remote Control Workstation It is not installed.
    • You don’t have sufficient permissions. For this test, we recommend running the Self-Diagnostic Agent as an administrator if the user has UAC restrictions.

    33. Verification of the available version of the ARC agent.

    The latest available version of the ARC agent is queried. The output displays the available file name, ID, and download date, and the response time is captured.


    Example of error:


    No version data is available because the task responsible for downloading this information has not been executed. For more information, see Deploying Agents.

    34. ARC Agent Installer Verification.

    It verifies that the ARC agent’s .EXE resource exists on the storage path configured for the queried node.


    Example of error:


    The most common causes of this error are:

    • The error may occur when pointing to a Conserver, due to the absence of the resource in its file storage path. Run the self-diagnostic test again: During the first run, the one that generates the error, the Conserver processes the task that requests the resource and stores it.
    • If the error persists when retrying, it may be due to the absence of the storage path configuration for the Server you are pointing to. For more information, see Communications.

    35. Testing the Updates Module.

    This test varies depending on the update module:

    1. Full Updates Module: the URL used by the ADM agent to download the update catalog is tested and verified, and the resource exists and is available.


    Example of error:


    The most common causes of this error are:

    • The update catalog has not been downloaded. For more information, see Download the catalogue.
    • The error may occur when pointing to a Conserver, due to the absence of the resource in its file storage path. Run the self-diagnostic test again: During the first run, the one that generates the error, the Conserver processes the task that requests the resource and stores it.
    • If the error persists when retrying, it may be due to the absence of the storage path configuration for the Server you are pointing to. For more information, see Communications.
    1. Lite Updates Module: Two tests are performed. The first validates access to the Microsoft catalog URL, and the second validates the status of the service Windows Update (wuauserv).


    Example of error:


    The most common causes of this error are:

    • Network restrictions configured in the firewall. Add the exception for the URL catalog.update.microsoft.com.
    • The service Windows Update (wuauserv) is disabled. Verify that it is enabled; it does not need to be started, as it starts or stops automatically when you manually check for updates or when the ADM agent performs the update inventory.

    36. Proof of access to the user’s TEMP folder.

    Access to the user’s temporary folder is validated: C:\Users\Nombre_Usuario\AppData\Local\Temp.


    Example of error:


    This error is caused by a restriction of NTFS permissions by a deny rule. To verify this, run the following command in PowerShell as an administrator, replacing “Nombre_Usuario” with the user you are performing the diagnostic test with:

    • icacls “C:\Users\Nombre_Usuario\AppData\Local\Temp”

    In the following link you will find the self-diagnostic agent executable: Self-Diagnostic Agent.