# Application Control Plus Agent Troubleshooting Tool
Last Updated On: 06 Oct 2026
Application Control Plus works on the principle of agent server communication, where the agents residing on end-user machines contact the central server once every 90 minutes as per the agent refresh policy. In addition, the agents will contact the central server during device startup and user login instances. The agent troubleshooting tool supported by Application Control Plus allows end-users to troubleshoot the agents and restore connection rather than requesting their IT administrators to look into the issue. Once the troubleshooting process completes, the tool generates a detailed report showing what failed and the recommended fix.
> **Who can use Agent Troubleshooting tool?**
>
> End-users can initiate it themselves via the agent tray icon. IT administrators can also run it remotely by connecting to the endpoint.
## Understanding the need for troubleshooting agents
The Application Control Plus agent might go down due to network level issues or issues that breaks the agent service. IT administrators can view the live status of the managed agents under the Scope of Management view. When an agent is marked "down" (indicated with red color monitor icon), IT administrators can remotely connect to those endpoints and troubleshoot it. Likewise, end-users can check the status of their agent by accessing the tray icon. Whenever the agent icon is down, end-users can access this tool and troubleshoot their agent. Once the troubleshooting process is done, the tool will provide a detailed report on the agent communication issues and the fix.
Run the tool also when a computer with the agent installed does not appear in Inventory, Scope of Management or the console.
## How do I run the Agent Troubleshooting Tool?
> **Note**
>
> If the troubleshooting tool executable is unavailable or missing from its installation folder entirely (for example, after a manual install or a "repair agent" action), or the tool shows a startup error such as "Required component missing: UEMS_Agent_CommonUtilDll.dll", this indicates the agent installation is likely corrupted or incomplete. Uninstalling from Control Panel does not remove all leftover files. Use the [Agent Cleanup Tool](https://www.manageengine.com/products/desktop-central/desktop_agent_uninstallation.html) to fully remove the agent, and then reinstall the latest agent downloaded from **Agent > Computers > Download Agent**.
> **Note**
>
> The tool requires a supported operating system. On an operating system that has reached end of support (for example, Windows XP), the tool can crash midway through the scan instead of completing.
### Windows
Two methods are available on Windows — via the tray icon (recommended for end-users) or directly via the file path (for remote or command-line use).
**Method 1 — Agent Tray Icon**
- Locate the Application Control Plus agent icon in the Windows system tray (bottom-right taskbar).
- Right-click the icon and select **Agent Troubleshoot > Troubleshoot**.
- A new window opens. Click **Start Troubleshooting** to begin the diagnostic scan.
- View the results. Click any component for detailed status and linked KB articles.
**Method 2 — Command Line / Direct File Path**
Navigate to the agent installation directory and run the executable directly:
> **Example**
>
> If you have installed the agent in the C drive, the file path would be:
>
> `C:\Program Files (x86)\ManageEngine\UEMS_Agent\bin\agent_troubleshooting_tool.exe`
#### Running a connectivity check remotely without a visible popup
Running `agent_troubleshooting_tool.exe` directly displays a graphical window on the end user's screen, which may not be suitable when checking many devices at once. As an alternative, IT administrators can test connectivity without any visible popup using the console's remote execution feature:
1. In the Application Control Plus console, navigate to **System Manager → Command Prompt / PowerShell (Run as SYSTEM)** for the target device.
2. Run the following to test connectivity to a specific server or Distribution Server address and port:
```powershell
Test-NetConnection -ComputerName
-Port
```
Use port 8383 for the Agent-to-Server connection and port 8384 for the Agent-to-Distribution Server connection. If the result shows `TcpTestSucceeded : False`, the port is blocked at the network or firewall; ask your network team to allow it, and then click **Scan Again** in the tool.
> **Note**
>
> The `tnc` command above performs a connectivity test only. Running the full graphical troubleshooting tool itself requires GUI access, so someone must be physically at the end-user machine — it cannot be run purely remotely over a network share.
This performs a targeted connectivity test without launching the full graphical tool or interrupting the end user.
If you run the troubleshooting tool, the output will appear like this one shown in the below image:

> **Note**
>
> - The troubleshooting tool scans once every 24 hours and caches the result. To fetch a fresh scan, click **Scan Again** inside the tool.
> - The above image consists of an agent that is directly managed by the central server (OP) without a distribution server.
#### What does the tool check — and how do I read the output?
The troubleshooting action diagnoses primary network-level issues and displays the results graphically. Each component shows one of three states: **Pass** (healthy), **Warning** (potential issue — click for details), or **Error** (failed — click for the KB article with resolution steps). Here is a list of components checked:
- Agent Binaries
- Agent Identity
- Agent Service
- Antivirus
- Active Directory Connection Status
- Distribution Server Connection Status
- Notification Server Connection Status
- Application Control Plus Server Connection Status
- WMI Connection Status
- RDS Connectivity (displayed as "RDS Gateway" in the tool)
> **Note**
>
> When you click on each component, it will display detailed information about its status. Clicking the **Scan Again** button will fetch the current connection status.
#### How do I act on the results?
Click the component showing a warning or error. This expands the detailed status and links directly to the KB article for that specific issue. Follow the KB steps to resolve it, then click **Scan Again** to confirm the component is now healthy. If the issue persists, use **Export** to package all diagnostic data and contact ManageEngine Support.
#### Common remarks shown by the tool and what to do
| Remark / status shown in the tool | Where it appears | What it means and what to do |
|---|---|---|
| The remote server returned an error: (401) Unauthorized | Application Control Plus Server Connection | The agent version does not match the server build. Uninstall the old agent completely, restart the computer, and install the latest agent from **Agent > Computers > Download Agent**. |
| No response received from the TS Tool utility | Application Control Plus Server Connection | A common cause is that the GlobalSign and DigiCert root certificates are missing on the endpoint. Import the certificates by following the steps in [Agent Communication Failure](https://www.manageengine.com/products/desktop-central/agent-communication-failure.html), restart the computer, and click **Scan Again**. |
| The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel
Failed to establish secure connection since one or more received certificates are expired | Application Control Plus Server Connection | The server's SSL certificate has expired. Renew the certificate and upload it in the console; the agent then communicates again. See [Troubleshoot SSL Errors](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-ssl-troubleshoot.html). |
| Port not Reachale (spelling as shown in the tool) | Application Control Plus Server Connection | The port is blocked at the network or firewall. Test it with `Test-NetConnection -ComputerName -Port 8383` and ask your network team to allow the port. |
| Agent failed to fetch Notification server details from the central server | Notification Server Connection | The Notification Server details are fetched after the agent communicates with the server successfully, and refreshed within 90 minutes. If the error stays, check the Agent Version as well; an outdated agent can cause it. See [Agent stuck on an old version](https://www.manageengine.com/application-control/help/device-onboarding/agent-troubleshooting-tool.html#outdated-agent). |
| Diagnosis Incomplete, or Agent Version followed by "(agent not upgraded)" | Summary / Agent Version | The agent is older than the latest agent version of the server. Update or reinstall the agent as described in [Agent stuck on an old version](https://www.manageengine.com/application-control/help/device-onboarding/agent-troubleshooting-tool.html#outdated-agent). |
#### Agent stuck on an old version and not auto-upgrading
If an agent has remained on an old version for an extended period despite server upgrades, run this tool first to confirm the agent can reach the Central Server, Distribution Server, and Notification Server — agents cannot upgrade while any of these connections are failing. If all components pass but the agent is still not upgrading, manually uninstall and reinstall the latest agent version — see [Agent Uninstallation Methods](https://www.manageengine.com/products/desktop-central/desktop_agent_uninstallation.html).
To check whether the agent is outdated, compare the **Agent Version** shown in the tool with the latest version in the **Agent Version** table under **Agent > Summary** in the console. A version followed by "(agent not upgraded)" in the tool means the agent is older than the latest version. An outdated agent can cause these symptoms:
- The computer does not appear in the console even though the agent is installed.
- The Notification Server Connection, RDS Gateway or Application Control Plus Server Connection (for example, "(401) Unauthorized") checks fail.
- The computer stays at **Approval Status: Pending** without ever appearing under **Computer(s) for Approval**.
Very old agent installers can also fail onboarding after security enhancements to the server. To resolve it, uninstall the old agent, download the latest agent from **Agent > Computers > Download Agent** (do not reuse an installer you downloaded earlier), and install it. If the agent was deployed through GPO, update the installer used by the GPO to the latest agent as well.
#### Components in detail
- **Agent Service:** Displays the status of the Agent service, showing if it is running or not. If a warning or error message appears, clicking on the service provides access to attached KB articles for issue resolution.
> **Note**
>
> The ManageEngine UEMS - Remote Control service remains in a stopped state and only operates during a remote connection. Only ManageEngine UEMS - Agent service and ManageEngine Unified Endpoint Security - Agent run regularly.
> **Note**
>
> If the ManageEngine UEMS - Remote Control service has been deleted, you can recreate it from an administrator command prompt without reinstalling the agent:
>
> `sc create "ManageEngine UEMS - Remote Control" binPath="C:\Program Files (x86)\ManageEngine\UEMS_Agent\bin\dcrdservice.exe"`
**Agent Identity:** Displays details about the agent machine name, OS Name, Last bootup time, OS install date, Identifying number, and UUID. An error indication occurs if the agent machine was imaged from another machine and has not fully recovered.
**Agent Binaries:** Verifies successful extraction of agent binaries during installation and upgrade. Warning/error flags indicate unsuccessful extraction. (Example: Sample binaries like Software Metering Report, USB Report, Notification Server Client, Inventory Management, Patch Management)
**WMI Connection Status:** Windows Management Instrumentation (WMI) consists of specifications from Microsoft designed to streamline device and application management across a network of Windows computing systems. When the agent fails to retrieve WMI details from Windows, it triggers an error. This failure hampers Helpdesk requests, preventing their transmission to the server and impeding the functionality of UUID details and related functions.
**Active Directory Connection Status:** Displays the result of the Active Directory connection, providing domain and group details to which the machine and user are joined. In case the Active Directory connection fails, domain details cannot be updated, and patches and configurations related to the domain will not occur.
**Antivirus:** Lists installed Antivirus software and their associated GUIDs (Globally Unique Identifiers). Only the antivirus that is registered as active with Windows is reported; an antivirus that is installed but not set as the active one is not listed.
**Application Control Plus Server Connection:** Displays the connection status between the agent and server, automatically checking ping and port connection with server address. It showcases all addresses used by the agent to contact the server. Server-related issues are highlighted in the error column, with reconnection steps mentioned in the attached KB articles.
If the connection fails with a 403 error against the server domain, make sure the domains for your data center are whitelisted. See [Agent Communication Domains](https://www.manageengine.com/products/desktop-central/help/domains-required-for-agent-communication.html).
For **Application Control Plus Cloud**, the troubleshooting tool will display the agent's connection with the server through all cloud addresses. For Cloud agents, all agent-to-server refresh and on-demand functions occur via the cloud addresses. The tool may still list a Notification Server entry for Cloud agents; if it shows an error that clears once the computer shows as healthy in the console, it was a stale result, so click **Scan Again**.
- **Distribution Server:** Verifies the Agent-to-Distribution Server connection using ping and port connections. When the agent operates under the Distribution Server, all agent configurations, patch deployments and upgrades occur through the Distribution Server. It automatically validates the ping and port connection with the Distribution Server address. Any server-related issues will be displayed in the error column with reconnection steps in the attached KB article.
> **Note**
>
> The Distribution Server component will only be listed in the Agent Troubleshooting Tool if the agents are managed under the Distribution Server. If this component is not visible, the agent communicates directly with the Central Server.

> **Note**
>
> If the Distribution Server check fails, run `telnet 8384` from the agent machine in Command Prompt. If the message "Could not open connection to the host, on port 8384: Connect failed" appears, allow port 8384 inbound on the Distribution Server machine's firewall (also check any antivirus or third-party firewall), and confirm that the Distribution Server machine is running. For further steps, see [Distribution Server Troubleshooting](https://www.manageengine.com/products/desktop-central/onboarding/troubleshooting/dstroubleshooting.html) and [Agent Ping Communication Fails](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-agent-communication-failed.html).
> **Note**
>
> To troubleshoot the Distribution Server itself, log in to the Distribution Server machine and run `C:\Program Files (x86)\ManageEngine\UEMS DistributionServer\bin\dstroubleshooting_tool.exe`. This is separate from the agent-side `agent_troubleshooting_tool.exe` described on this page.
- **Notification Server Connection:** The Notification Server manages all on-demand actions executed by on-premise agents — remote connections, on-demand configurations, and patch deployments. The notification server necessitates a 10-minute idle connection for live status updates. Any connection issues are updated in the remarks column. To verify the 10-minute idle connection, click **Start** in the Notification Server Summary.
If the Notification Server connection fails, make sure the DMS domains for your data center and port 443 listed on [Agent Communication Domains](https://www.manageengine.com/products/desktop-central/help/domains-required-for-agent-communication.html) are allowed. For further steps, see [Troubleshoot Agent Offline Issues](https://www.manageengine.com/products/desktop-central/help/device-onboarding/troubleshoot-agent-offline-issues.html) and [On-Demand Task: Agent Unavailable](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-ondemandtasks-agent-unavailable.html).

- **RDS Connectivity:** Verifies whether the agent can establish Remote Desktop Service (RDS) sessions with the server successfully. The tool shows this check as **Connectivity - RDS Gateway**, with a status for each of these rows: `assist.zoho.com:443`, `gateway.zohoassist.com:443`, and **Remote control components**. Each row shows **Successful**, **Failed** or **Not Found**. A **Failed** status means the gateway address is not reachable; allow the domain and port 443 as listed on [Agent Communication Domains](https://www.manageengine.com/products/desktop-central/help/domains-required-for-agent-communication.html) and see [RDS Gateway Communication Failure](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-rds-gateway-communication-failure.html). A **Not Found** status with the remark "RDS components not available" means the remote control components are missing from the agent. Reinstall the latest agent, or start a Remote Control session from the console, which installs the RDS component automatically.
#### Troubleshooting Summary
The Troubleshooting Summary provides detailed information on system details, agent-specific details such as version and installed location, firewall configurations, and the connection status of all agent components.

The summary also shows these System Information fields:
- **Approval Status:** Shows whether the computer has been approved by the administrator.
- **Pending:** The computer is waiting for administrator approval. Communication with the server is blocked until it is approved. Approve it from **Agent > Computers > Computer(s) for Approval**. See [Approve Computers & DS](https://www.manageengine.com/products/desktop-central/how-to/waiting-for-approval.html). The **Computer(s) for Approval** tab is available only when approval is enabled under **Agent > SoM Settings > Approval Settings**.
- **Approved:** The computer is approved and can communicate with the server.
- **Unknown:** The approval state is not available to the tool. Check the Agent Version too, as an outdated agent was the cause in the reported cases.
- **Trusted Communication:** Shows whether trusted communication is enabled between the agent and the server.
- **Agent Version:** The installed agent version. Compare it with the latest agent version in **Agent > Summary**. See [Agent stuck on an old version](https://www.manageengine.com/application-control/help/device-onboarding/agent-troubleshooting-tool.html#outdated-agent).
- **Machine Name:** The computer name reported by the agent.
> **Note**
>
> A computer can show **Approval Status: Pending** even though it is not listed under **Computer(s) for Approval**. The common cause is an outdated agent version. Uninstall the agent, download the latest agent from **Agent > Computers > Download Agent**, and reinstall it.
When you read the exported `Troubleshoot_Summary` file, the following combinations are common:
| What the export shows | What it usually means |
|---|---|
| Approval Status: Pending and an old DCAgentVersion | The agent is outdated. Reinstall the latest agent. |
| Approval Status: Pending and the version is current | The computer is waiting for approval. Approve it under Computer(s) for Approval. |
| "Agent failed to fetch Notification server details from the central server" | Expected until the agent communicates with the server successfully. The details are fetched within 90 minutes. If it persists with an old agent version, reinstall the latest agent. |
#### Where are the agent logs — and how do I share them with support?
Agent logs are accessible directly inside the tool via **View Logs**, segregated by component (system information, configuration, patch, and others). Log files are stored at:
`C:\Program Files (x86)\ManageEngine\UEMS_Agent\logs\`
- For patch installation failures, check `dcpatchinstallaccess.log` and `dcpatchmgmt.log`. If the patch failed to download, check the Distribution Server logs.
- `Internet_Connection.log` keeps the date-wise IP address history of the computer. The console does not store IP address history.
- On older installations, the agent folder can be `DesktopCentral_Agent` instead of `UEMS_Agent`.
- Agent logs cannot be viewed or downloaded from the web console. Collect them from the computer, or use **Support > Create Support File**.
- If the log folder cannot be copied or compressed in place because the agent service is using it, copy the folder to another location, such as Downloads, and then compress the copy. Do not force-close `agent.exe`.

If the KB articles linked inside the tool do not resolve the issue, click **Export** to package all troubleshooting data into a single report and share it with ManageEngine Support.

> **Tip**
>
> Before contacting support, export the troubleshooting report first. This allows the support team to diagnose the issue faster without additional back-and-forth.
> **Note**
>
> If both the tray icon **Troubleshoot** option and `agent_troubleshooting_tool.exe` are unavailable, the agent installation is likely corrupted. Open Registry Editor, right-click `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AdventNet\DesktopCentral\DCAgent`, select **Export**, choose **Selected branch**, save the file, and share it with ManageEngine Support.
Related pages: [Agent Ping Communication Fails](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-agent-communication-failed.html), [Agent Communication Failure](https://www.manageengine.com/products/desktop-central/agent-communication-failure.html), [Troubleshoot Agent Offline Issues](https://www.manageengine.com/products/desktop-central/help/device-onboarding/troubleshoot-agent-offline-issues.html), and [port requirements for agent-server communication](https://www.manageengine.com/application-control/help/device-onboarding/REPLACE-URL-secure-wan-agent-server-communication.html).
### macOS
For version 11.4.2544.01.M and above, the troubleshooting tool will be available in the macOS agent.
1. Navigate to the agent tray icon in the menu bar and select **Tray Icon > Troubleshoot > Run troubleshooting tool**.

> **Note**
>
> If the agent tray icon is not shown in the menu bar, open Activity Monitor and search for `dcagenttrayicon`. If the process is not running, launch `/Library/ManageEngine/UEMS_Agent/bin/dcagenttrayicon.app` to restore the icon.
2. Alternatively, open Terminal and run: `/Library/ManageEngine/UEMS_Agent/bin/troubleshoot`

3. To view available options, run `troubleshoot --help` in Terminal.

> **Note**
>
> Running the tool without any options will execute all the checks listed below (network, service, and info) at once.
#### What does the tool check on macOS?
**Server connectivity details:**
- Connection status with the main Application Control Plus server
- Connection status with the Distribution Server (if the agent is managed under a remote office with a DS)
- On-demand functionality to verify if the agent can receive and execute on-demand actions from the server
**Service and Process Details:**
- Checks whether all services required for the agent to function are running properly
- Reports any services that are inactive or have failed
**Agent and Server Information:**
- Agent version and installation directory
- Server address and communication details
- MDM enrollment status and MDM server address (if the machine is enrolled in MDM)
The tool shows these labels in its output:
| Label in the output | What it means and what to do |
|---|---|
| Agent binaries present / Agent data present / Required services are loaded | The agent files and the services required for the agent are available on the computer. |
| CENTRAL SERVER CONNECTION - OK / DOWN | Shows whether the agent can reach the Application Control Plus server. If it is DOWN, check the server address and port 443. |
| DISTRIBUTION SERVER CONNECTION - NOT ENABLED | The agent is not managed under a Distribution Server, so this check does not apply. |
| ON-DEMAND CONNECTION (DMS) - DOWN | The on-demand server is not reachable, so remote control and other on-demand actions fail. Allow the domains listed on [Agent Communication Domains](https://www.manageengine.com/products/desktop-central/help/domains-required-for-agent-communication.html). |
| DOWNLOAD SERVER - DOWN | The agent cannot reach the download server. Allow the download server domain for your data center from the same page. |
| [!] Multiple Hostnames found | More than one host name is set on the computer (for example, a name with a "-1" suffix). The agent uses the host name as the computer name; see the hostname note below. |
| This device has not been approved yet, hence skipping network check | The computer is waiting for approval. Approve it under **Agent > Computers > Computer(s) for Approval**. See [Approve Computers & DS](https://www.manageengine.com/products/desktop-central/how-to/waiting-for-approval.html). |
> **Note**
>
> For Mac agents, the host name is used as the computer name. To check it, run `hostname` in Terminal. To change it, run `sudo scutil --setHostName `. The computer name is updated in the console at the next 90-minute refresh cycle.
#### Where are the agent logs — and how do I share them with support?
Log files are stored at: `/Library/ManageEngine/UEMS_Agent/logs/`
To generate a detailed support dump, run: `troubleshoot --dump`
The dump is saved to: `/Library/ManageEngine/UEMS_Agent/logs/UserLogs/dumps/`
> **Note**
>
> The --dump option can be used to generate an information dump that can be shared with ManageEngine support for further analysis and troubleshooting.
## How do I verify agent connectivity to the server manually?
If you wish to verify the agent—server connection without running the full tool, use the following steps:
**To check if the necessary ports are open:**
```text
telnet
```
- A blank screen indicates a successful connection. The same steps are applicable to check the Agent-DS connection as well.
- The default port is 8383 for the Agent-Server connection and 8384 for the Agent-Distribution Server connection.
- If the command prompt reports that `telnet` is not recognized, enable the Windows Telnet Client feature, or use `Test-NetConnection -ComputerName -Port ` in PowerShell. `TcpTestSucceeded : True` indicates a successful connection.
**To check data transfer:**
- Open the Application Control Plus server console in a browser from the agent machine. If the console fails to load, a firewall or network restriction is blocking the data transfer channel between agent and server.
**To test file downloads from the agent machine:**
```text
https://:/client-data/ns-status-details.xml
```
- If a .xml file is displayed and available for download, it denotes a successful connection.
- If the file is not displayed or the page returns an error, the request is not reaching the server. Check the port with the steps above and review the firewall or proxy settings.