Versions Compared


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

Table of Contents


This topic only applies to users who run:

  • Windows 2012 Datacenter
  • Windows 2012 R2 Standard
  • Windows 2012 Standard
  • Windows 2016 Full Desktop

Before you begin, see ANYWHERE Pre-Installation.

Step 1: Locate the Armor Anywhere agent

Excerpt Include
ESLP:Locate the Armor Agent


  1. In the Armor user interface, on the left-side navigation, click Infrastructure
  2. Click Add Core
  3. Click your operating system (Amazon Linux, CentOS, and Redhat). 
  4. Locate and copy your license key. You will need this key later in the installation process. 
  5. Download and execute the armor-agent.deb file. 

Step 2: Download and install the Armor Agent


ESLP:Locate the Armor Agent (snippets)


For Amazon Web Services users who:

  • Use Elastic Beanstalk to run their instance's applications, and
  • Run Windows 2012 R2,

Review the following example to understand how to install the Anywhere agent. Afterwards, you can skip to the Test your connection step.

Step 3: Validate the Core

titleInstall Output and Logs
A successful install will have the following output
Code Block


yum install armor-agent.rpm


Modify the configuration file at /etc/armor/armor.config to use your license key. Use the following script as an example: 

Code Block
titleConfigure Agent
sed -i -r 's/license=<license key>/' /etc/armor/armor.cfg


Run the following command: 

Code Block
titleStart Agent
service armor-agent start
    test: if not exist 'c:\\.armor\\opt\\armor.exe' exit 0
    command: c:\\Windows\\Temp\\armor-setup.exe /verysilent /license=AAAA1-A11AA-AA1AA-AAAAA-1AAAA
    ignoreErrors: false
    waitAfterCompletion: 5

You must replace AAAA1-A11AA-AA1AA-AAAAA-1AAA with your specific license key.

Step 2: Download and install the Armor Anywhere agent

There are three types of scripts that you can use to install the agent. 

Script type



You can use these scripts to verify that your environment is compatible with Armor Anywhere. These scripts will not install the agent.

Code Block


Selecting previously unselected package armor-agent. (Reading database ... 179956 files and directories currently installed.) Preparing to unpack armor-agent.deb ... Unpacking armor-agent ( ... Setting up armor-agent ( ... ===================================================================== The Armor Agent has been installed. You will need to register it by placing the license key provided by Armor into the configuration file located in /etc/armor/armor.cfg and starting the armor-agent service. ===================================================================== Processing triggers for ureadahead (0.100.0-16) ... * Starting Armor Defense Agent armor-agent started

After the Armor agent has completed installation, its sub-services will install after the first heartbeat completes. You can follow the armor.log to view the status.

Code Block
tail -f /var/log/armor.log

The logs for a completed agent install will look similar to:

Code Block
titleSample Output
PS C:\Users\Administrator> cat C:\.armor\log\armor.log time="Jan 13 21:19:22" level=info msg="Provider Found" key= provider=Azure time="Jan 13 21:19:22" level=info msg="OS Found" distro=Windows time="Jan 13 21:19:22" level=info msg="Registering Armor Core agent" time="Jan 13 21:19:26" level=info msg="Initial registration complete. Begin adding Armor..." time="Jan 13 21:19:26" level=info msg="Applying Armor Server Hardening" time="Jan 13 21:19:26" level=info msg="Installing Armor Anti-Virus support" time="Jan 13 21:19:45" level=info msg="Installing Armor Logging support" time="Jan 13 21:19:49" level=info msg="Installing Logging Certificate" time="Jan 13 21:19:49" level=info msg="Installing Armor Monitoring support" time="Jan 13 21:19:55" level=info msg="Validating Hash..." time="Jan 13 21:19:55" level=info msg="Hash validated"
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest -outfile armor_agent.ps1 ; .\armor_agent.ps1
Pre-Installation and Installation

You can use these scripts to:

  • Verify that your environment is compatible with Armor Anywhere
  • Install the agent
Code Block
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest -outfile armor_agent.ps1 ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA

You can use these scripts to install the agent. These scripts will not verify your environment for compatibility. 

Code Block
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest -outfile armor_agent.ps1 ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA -silent

Step 3: Test your connection

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

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


The following example tests connectivity to over 443/tcp:

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)

Include Page
ESLP:Update Armor Agent configuration file (snippet)
ESLP:Update Armor Agent configuration file (snippet)

Step 4: Review the status of the Armor Anywhere agent 

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

Step 5: Configure your notification preferences

Armor recommends that you configure your account to receive notifications for Account, Billing, and Technical events.

These notification preferences do not relate to support tickets.

To update your notification preferences for support tickets, see Armor Support.


You will receive a notification when:

  • A password expires in 14 days.
  • A password expires in 7 days.
  • A password expires in 24 hours.
  • A password has expired.

You will receive a notification when:

  • An invoice has posted. 
  • An invoice is past due (2, 10, 15, 25, and 30 days).
  • A payment method will soon expire (1, 15, and 30 days).

You can configure a user to become the primary billing contact for an account. This user will receive billing notifications. Additionally, this user will be listed in the Bill to field in an invoice. 

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Account.
  2. Click Users
  3. Locate and hover over the desired user. 
  4. Click the vertical ellipses. 
  5. Select Set as Primary Billing Contact
  6. Click OK

You will receive a notification when:

  • A virtual machine will be deleted or downgraded.
  • CPU, disk, and memory utilization is at more than 90% for 5 minutes.
  • Ping, SSH (Linux), or RDP (Windows) fails for 5 minutes.

You can only change the notification preferences for your own account. You cannot change the notification preferences for other user accounts.

  1. In the Armor Management Portal (AMP), in the top, right corner, click the vertical ellipses.
  2. Click Settings
  3. Click Notification Preferences.
  4. Use the slider to make your desired changes. 
    • Select Alert to receive notifications in the top bar in the Armor Management Portal (AMP). 
    • Select Email to receive notifications through email. 
    • You can select both notification options.
  5. Click Update Notification Preference to save your changes. 

Was this helpful?
Rate Macro