Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Step 1: Stop the service and uninstall the agent

For Windows users

The agent installation file is located at: C:\.armor\
  1. Stop the service: C:\.armor\opt\armor stop
  2. Uninstall the agent: C:\.armor\opt\armor uninstall

For Linux users

The agent installation file is located at: /opt/armor/
  1. Stop the service: /opt/armor/armor stop
  2. Uninstall the agent: /opt/armor/armor uninstall

Step 2: Remove the agent from the Armor Management Portal (AMP)

You can remove the instance through AMP or through an API call

Method 1: Remove the agent through AMP

When you uninstall the agent, the corresponding virtual machine (or server) will be displayed in AMP in a disabled status.

Before you can remove the agent, the agent must be in a Needs Attention state.

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
  2. Click Virtual Machines.
  3. Locate and hover over the desired virtual machine. 
  4. Click the vertical ellipses. 
  5. Click Delete
  6. Mark Delete now
  7. Click Delete VM

Method 2: Remove the agent through an API call

You can use the DELETE /vms/core/{coreInstanceId} API call to remove an instance.

Delete an agent


To learn more about the Armor API system, see Armor API Guide.

Method 3: Automatic removal after inactivity 

When Armor has not received one of collects the following points of telemetry for 7 days, the server object will be automatically removed from AMP:

  • Armor Agent Heartbeat
  • Armor Supervisor get-tasks
  • Trend Micro Heartbeat
  • Filebeat log
NoteIn any scenario where one or more services are removed or malfunctions, but another service continues to operate, this process will not automatically remove the server object from AMP.

After 7 days, if Armor does not receive one of the following points of telemetry, then the specific object will be removed; however, the agent will continue to run. 

Step 3: Verify disconnection 

After you uninstall the agent, Armor recommends that you test the connection for each previously configured firewall rule.

To verify a disconnection to an Armor service endpoint, use the telnet command.


The following example tests connectivity to over 443/tcp:Troubleshooting:

Code Block
telnet 443

For Windows systems without the telnet feature installed, you can also use PowerShell:

Code Block
new-object System.Net.Sockets.TcpClient('', 443)


Step 4: Review the status of the Armor Anywhere agent 

Excerpt Include
ESLP:Review the server status (snippet)
ESLP:Review the server status (snippet)