---
title: Agent Management
slug: neurons/help/en_us/agent-management
createdAt: 2026-11-05T08:02:07.971Z
---

The Agent Management page provides a list of all agent endpoints. From here, you can view the assigned policy, reassign or redeploy a policy, uninstall an agent, and remove an agent endpoint.

Devices display in this list as soon as the **Deploy** action has been requested to the device. To learn more about deploying to a device see [Agent Deployment](docId:_-upoV5z4YndrFDUFJCKN).

The name of the agent endpoint, agent policy installed, health, status, platform and installed date/time display for each agent endpoint.

## Agent Health

The **Health** column shows the overall health status relating to agent capabilities and platform checks, for each device:

- **Good** (green): Agent functioning as expected.
- **Moderate** (amber): Agent functioning, but not in optimal state.
- **Poor** (red): Agent not functioning.

The health status is automatically updated on each agent check-in.

You can select the **Agent Check-in** drop-down to filter the agent endpoint list by last agent check-in:

- **Within 7 days**: The agent has checked-in within the last 7 days.
- **Between 7 and 90 days**: The agent last checked-in between 7 and 90 days.
- **Over 90 days**: The agent last checked-in over 90 days ago.
- **Never**: The agent has never checked-in.
- **Duplicates**: The agent has been superceded by another agent that has registered with the same endpoint name.
  Duplicates can occur, in the Agent Management view, when endpoints are regularly re-imaged. Ivanti Neurons does not perform an auto-cleanup from this view. You can use the **Duplicates** filter to identify and remove unwanted, duplicate agent endpoints.
- **All**: All agent check-ins.
  When **All** is selected the **Agent Endpoint** column displays an icon to indicate the agent check-in state:
  - :inlineImage[]{src="https://api.archbee.com/api/optimize/9rfvxhrv8FA-8bxcK2IRv/c8shiezzTAdz0YN2xg04m_agent-health-late.png" alt caption size="10" width="22" height="22"} **late**: The agent has not checked-in within the last 7 days.
  - :inlineImage[]{src="https://api.archbee.com/api/optimize/9rfvxhrv8FA-8bxcK2IRv/kGSVHIXNQoymmfnyFLPhH_agent-health-missing.png" alt caption size="10" width="22" height="22"} **missing**: The agent last checked-in over 90 days ago.
  - :inlineImage[]{src="https://api.archbee.com/api/optimize/9rfvxhrv8FA-8bxcK2IRv/xEWY51DTWoFTrVVBQIsOO_agent-health-never.png" alt caption size="10" width="26" height="23"} **never**: The agent has never checked-in.
  - :inlineImage[]{src="https://api.archbee.com/api/optimize/9rfvxhrv8FA-8bxcK2IRv/Welh3AVix0ck9Hu93ymBc_agent-health-duplicate.png" alt caption size="10" width="22" height="21"} **duplicate**: The agent has been superceded by another agent that has registered with the same endpoint name.

In the table, click on an agent endpoint's health indicator: Good, Moderate, Poor, to view more detail. The **Agent Health** page appears. See [Agent Health ](docId\:wi5VLZ7n3z-tQdWcKqgRW)for more details.

## Agent Status

The **Status** column provides detail on the state of the endpoint. Hover over the Status information icon :inlineImage[]{src="https://api.archbee.com/api/optimize/9rfvxhrv8FA-8bxcK2IRv/7TdLVTmvHT8VgWOFrCxUs_info.png" alt="i icon" caption size="10" width="17" height="17"} for any agent endpoint for further details.

:::ExpandableHeading{customAnchorSlug="status"}
## Status values

**DeploySuccess**: Active

**DeployStarted**: Deployment started

**DeployResolved**: Deployment resolved

**DeployConnected**: Deployment connected

**DeployValidated**: Deployment validated

**DeployFilesCopied**: Deployment copied files

**DeployInstallerStarted**: Deployment installer launched

**UserRequestAssignPolicy**: Reassign policy requested

**UserRequestDeploy**: Deploy agent requested

**UserRequestRedeploy**: Redeploy agent requested

**UserRequestUninstall**: Uninstall agent requested

**ErrorDeployEnrollmentKeyExpired**: Deployment enrollment key expired

**ErrorDeployInvalidCredentials**: Deployment invalid credentials

**ErrorDeployInternal**: Deployment internal error

**ErrorDeployNameResolutionFailed**: Deployment name resolution failed

**ErrorDeployConnectToDevice**: Deployment unable to connect to endpoint

**ErrorDeployConnectToRegistry**: Deployment unable to connect to remote registry

**ErrorDeployValidationSkipped**: Deployment Hostname validation skipped

**ErrorDeployValidation**: Deployment Hostname validation failed

**ErrorDeployCopyFilesNoInstaller**: Deployment agent installer unavailable

**ErrorDeployCopyFilesFailed**: Deployment unable to copy files to endpoint

**ErrorDeployInstallerRemoteService**: Deployment unable to create the remote service

**ErrorDeployStartInstaller**: Deployment unable to launch installer
:::

## Actions

### Reassign Policy

To assign a different policy to an agent endpoint.

1. Select the check box next to the agent endpoint that you want to reassign a policy to.
2. Select **Actions&#x20;**> **Reassign Policy**.
   The **Reassign Policy** panel appears.
3. Select an **Agent Policy** from the drop-down, or enter the policy name to filter the list. Or, select **Use automated policy assignment** from the drop-down list.
   When you reassign an agent policy with automated policy assignment configuration, the existing device exceptions will be removed, and their policies will be assigned automatically with the new policy when the policy evaluation process is complete.
4. Click **Save**.
   The **Reassign Policy** panel closes.
5. On the **Agent Management** page, the Status updates to **Reassign policy requested**. Hover over the status to see who requested the policy change, on what date, and the name of the policy that was assigned.

### Redeploy Agent

To redploy an agent.

1. Select the check box next to the agent endpoint that you want you want to attempt redeployment for.
2. Select **Actions&#x20;**> **Redeploy Agent**.
   The **Redeploy Agent** panel appears.
3. Select the **Agent Policy** that you want to deploy, or enter the policy name to filter the list.
4. Select the **Enrollment Key**, or enter the name to filter the list. If you want to use a new key, select **Create New Key**: the [Create Enrollment Key](docId\:jnjdBpaU3Iilu-71ClMqJ) panel displays.
5. Select the agent endpoint that you want to use to **Deploy from**, or enter the name to filter the list. The drop-down lists the available agent endpoints that have a policy with the Deployment capability enabled.
6. If there are no valid credentials the Credentials drop-down is available. Select the **Credential&#x20;**&#x66;or the agent endpoint. Or, select t&#x6F;**&#x20;Create New Credential**: the [New Credential](docId:_-upoV5z4YndrFDUFJCKN) panel displays.
7. Click **Redploy** to attempt the deployment again.

### Uninstall Agent

To uninstall the Agent.

1. Select the check box next to the agent endpoint that you want to uninstall the agent from.
2. Select **Actions&#x20;**> **Uninstall Agent**.
   The **Uninstall Agent** dialog appears.
3. Click **Uninstall**.
   The agent is uninstalled and the agent endpoint is no longer visible in the list on the Agent Management page when refreshed.

::::ExpandableHeading
## Manually uninstall the Agent

:::ExpandableHeading
## Microsoft Windows

- To uninstall an Ivanti Neurons Agent on a Microsoft Windows endpoint, execute the following command:
  `C:\Program Files\Ivanti\Ivanti Cloud Agent\STAgentManagement.exe -uninstall`
- The uninstall log can be found at:
  `C:\ProgramData\Ivanti\Ivanti Cloud Agent\Logs\AGENT_uninstall.log`
- For an overview and explanation of possible parameters, execute the following command:
  `C:\Program Files\Ivanti\Ivanti Cloud Agent\STAgentManagement.exe /?`

For additional information, see this article in the Community: [How to uninstall the Ivanti Neurons Agent](https://forums.ivanti.com/s/article/How-To-Manually-Uninstall-the-Ivanti-Cloud-Agent).
:::

:::ExpandableHeading
## Apple macOS

1. To uninstall an Ivanti Neurons Agent on an Apple macOS endpoint, execute the following command from the Terminal or using a device management application:
   `/usr/local/com.ivanti.cloud.agent/IvantiAgent/bin/stagentctl uninstall`
2. Navigate to **Users & Groups** in system settings on the machine, and delete the `_ivantiNeuronsMacPatchAgent` account.
   Alternatively, use the command `sudo sysadminctl -deleteUser _ivantiNeuronsMacPatchAgent`.

- No uninstall log is left behind.
- For an overview and explanation of possible parameters, execute the following command:
  `/usr/local/com.ivanti.cloud.agent/IvantiAgent/bin/stagentctl`

For additional information, see this article in the Community: [How to manually uninstall the macOS Neurons Agent](https://forums.ivanti.com/s/article/How-to-manually-uninstall-macOS-Neurons-Agent).
:::

:::ExpandableHeading
## Linux

- To uninstall an Ivanti Neurons Agent on a Linux endpoint, execute the following command:
  `yum remove ivanticloudagent`
- The uninstall log can be found at:
  `/opt/ivanti/cloudagent`
:::
::::

### Remove Agent Endpoint

When an agent has been manually uninstalled from an endpoint, or if the status is not progressing, you need to remove it from the Agent Endpoint list.

1. Select the check box next to the agent endpoint that you want you want to remove from the list.
2. Select **Actions&#x20;**> **Remove Agent Endpoint**.
   The **Remove Agent Endpoint** confirmation dialog appears.
3. Click **Remove**.
   The agent endpoint is removed and is no longer in the list on the Agent Management page.

:::ExpandableHeading
## How to identify and remove inactive agents from devices

1. Navigate to **Agents&#x20;**> **Agent Management**.
   The **Agent Management** page appears.
2. The **Status&#x20;**&#x63;olumn indicates whether the agent is Inactive. Select the check box for the agent endpoints that you want to remove the agent from .
3. Select **Actions&#x20;**> **Uninstall Agent**.
   The **Uninstall Agent** confirmation dialog appears.
4. Click **Uninstall&#x20;**&#x74;o confirm the action.
:::
