--- title: "Agent Setup and Testing" slug: "agent-setup-and-testing" description: "This document shows how to register and setup a Decisions Agent. The Agent can be added and downloaded from the System>Designers>Agents Folder. Properly setting up an Agent, will allow Decisions the ability to interact with files on a separate system, via Decisions processes, regardless of firewall settings. " updated: 2025-12-19T23:45:29Z published: 2025-12-19T23:45:29Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Agent Setup and Testing Admins must install the ASP. Net core Bundle on the agent server.The ASP. Net core version should be similar to the Decisions using the .NET core version. Refer to the [Installation Guide](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-8.0.22-windows-hosting-bundle-installer) for more details. Without this, the Agent will fail to communicate or connect with the server by not responding in a timely manner. Other Core Runtime versions do not contain the required DLLs. Please check the server has this installed before proceeding. ## Overview Configuration requires adding and registering an [Agent](/v9/docs/introduction-to-agents), installing it to a machine, and implementing it into the Decisions environment. Protocol Agents are directly affiliated with network security as well as other aspects. ### Prerequisites - Users should have, at minimum, Can Use [permissions](https://documentation.decisions.com/v9/docs/setting-folder-permissions) on a Designer element to use its function with Agents. - When registering an Agent, the Decisions instance Portal Base URL can not be localhost. To adjust the Portal Base URL, refer to [Changing the Portal Base URL.](https://documentation.decisions.com/v9/docs/changing-the-portal-base-url) --- ## Setup 1. Navigate to **System > Designers > Agents** and click ADD/REGISTER AGENT. 2. Provide a **Title**and optionally a **Description**, then click REGISTER AGENT.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-24_11h08_06.png) 3. Right-click the newly added Agent from the Agents Folder and select **Download****Agent**. 4. Extract the contents of the .zip file. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-24_10h52_40.png) 5. From the extracted folder, install the **DecisionsAgent.msi** file. The agent will create all its files under **C:\Program Files (x86)\Decisions Agent**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-24_10h53_28.png) 6. After the Agent installs, from the extracted folder, copy over**AgentSettings.xml** and **PortalPublicKey.key** to `C:\Program Files (x86)\Decisions Agent`**.**![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-24_10h55_30.png) 7. On the local machine, search for and open **Services**. 8. Locate the **Decisions Agent Service**, right-click, and select **Start**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-24_10h57_06.png) 9. If the agent does not start with a pop-up dialog Message, "**Error-1064 Windows could not start the Decisions Agent service on Local Computer"**. Navigate to the `C:\Program Files (x86)\Decisions Agent`. Open the **AgentSettings.xml** file and check the **PortalBaseURL**. Enter the IPv4 address with the port number on which the Decisions is installed. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1681900213584.png) 10. Start the Decisions Agent Service. --- ## Testing The Agent Dashboard at **System > Designers > Agents**displays all Deployed Agents and Recent Agent Actions. The Any Unknown Client entity suggests the client is not yet identified. 1. Navigate to **System > Designers > Agents > Test Agent**. Ensure that the STATE of the Agent is **Complete**. A Complete status indicates the client has been identified and is ready for communication. 2. Under **Deployed****Agents**, right-click the Agent and select **Ping****Agent**. Pinging the Agent checks to see if the Agent is available. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1766187856252.png) 3. After the notification displays, refresh the **Recent Agent Actions**to ensure the **Ping action**is executed. 4. Right-click the Ping Action and click**View Results**. If applicable, the resulting data from the Agent Action will display. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1766187811824.png) --- ## Agent Instructions Status To check the agent activity, users can navigate to the agent folder to view the Agent Activity Dashboard. The following table describes all the states of Agent. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1766187782823.png) | State | Description | | --- | --- | | Queued | The Instructions are queued for delivery to the Agent. | | Sent to Agent | The Instructions have been received by the Agent. | | Complete | The agent has completed the request, and the results have been posted to the server. | | Failed | Agent encountered an error when processing the instruction. | | Forwarded | Agent Sent result for specific server {0}, but was received by this node instead and had to be forwarded to another node. | --- ## Confirming if an Agent is in Polling Mode Agents can enter polling mode if no ports are available, leading to performance issues. 1. Right-click on a Deployed Agent and select **View Last Status**. If the agent is properly configured, View Last Status will display **Live Connection: True**. The Agent is currently in polling mode if this message is not shown.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1766187699980.png) --- ## Uninstalling and Removing an Agent If a user needs to remove an Agent or the Agent needs to be updated and replaced with a new version, Agents in **Decisions**can be uninstalled from the **File****System**. 1. From the File System, open the **Control****Panel**. Under **Programs,** select **Uninstall a Program**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-05-13_16h01_07.png) 2. From the **Programs and Features**window, locate **Decisions Agent**, select it, then click **Uninstall**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1681898441459.png) 3. Confirm the uninstall by selecting **Yes**. This will remove the Decisions Agent from the windows. 4. To remove the agent from the Decisions, navigate to **Settings > Designers > Agents**. Navigate to the Agent, **Right-click > Manage > Delete Folder**. This will remove the agent from the Decisions server permanently. --- For further information on Integrations, visit the [Decisions Forum](https://community.decisions.com/categories/Integrations).