You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 57 Next »

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

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure
  2. Click Virtual Machines
  3. Hover over the plus ( + ) icon, and then click the Anywhere Agent  icon.
    • If you don't have any agents listed, then click Deploy New Armor Agent. 
  4. Copy your license key. You will need this information in a later step.
  5. Select your operating system (Linux or Windows).  
 

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.

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

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.

[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
[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. 

[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.

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


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

telnet 146.88.106.210 443


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

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


Step 4: Review the status of the Armor Anywhere agent 

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure
  2. Click Virtual Machines
  3. Review the corresponding Status column. The Status column contains a green or red status to indicate if the server's agent has registered a heartbeat to Armor.
    • A green status indicates the server's agent has registered a heartbeat in the past hour. 
    • A red status indicates the server's agent has not registered a heartbeat in the past hour. 
      • After four hours without a registered heartbeat, the API will close all service endpoints (firewall ports).


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

Account

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.
Billing

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
Technical

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.