Versions Compared

Key

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

This topic only applies to users who run:

  • Windows 2012 Datacenter(all versions)
  • Windows 2012 R2 Standard
  • Windows 2012 Standard
  • Windows 2016 Full Desktop(all versions)
  • Windows 2019 (all versions)
Note

Before you begin, Armor recommends that you review the pre-installation information, including firewall rules. To learn more, see ANYWHERE Pre-Installation.

Note

For Windows 2012 users, when you install the Armor Agent, the corresponding Trend Micro agent may cause your system to reboot. Trend Micro is currently researching this issue.

Warning

Before you install the Armor Anywhere agent, you must remove any previously installed anti-virus software, such as Trend Micro, McAfee, etc. Afterwards, you must reboot your system. 


Step 1: Locate the Armor Anywhere agent

Excerpt Include
ESLP:Locate the Armor Agent (snippets)
ESLP:Locate the Armor Agent (snippets)
nopaneltrue
 

Note

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.

Code Block
themeMidnight
files:
  "c:\\Windows\\Temp\\armor-setup.exe":
    source: https://get.core.armor.com/latest/armor-setup.exe
commands:
  armoragentinstall:
    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
Tip

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

Description

Pre-Installation

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

Code Block
themeMidnight
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest https://get.core.armor.com/latest/armor_agent.ps1 -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
themeMidnight
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest https://get.core.armor.com/latest/armor_agent.ps1 -outfile armor_agent.ps1 ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA
Installation

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

Code Block
themeMidnight
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest https://get.core.armor.com/latest/armor_agent.ps1 -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.

...

Tip

The following example tests connectivity to api.armor.com over 443/tcp:

Code Block
themeMidnight
telnet 146.88.106.210 443


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

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

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)
nopaneltrue

...

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 Support Tickets.

...

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

Scrolltotop