This topic only applies to users who run:
- Windows 2008 R2 Datacenter
- Windows 2008 R2 Standard
- Windows 2008 R2 Web
Before you begin, Armor recommends that you review the pre-installation information, including firewall rules.
To learn more, see ANYWHERE Pre-Installation.
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
- In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
- Click Virtual Machines.
- 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.
- Copy your license key. You will need this information in a later step.
- 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; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\armor_agent.ps1 |
| Pre-Installation and Installation | You can use these scripts to:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\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; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA -silent |
In the above scripts, replace AAAA1-A11AA-AA1AA-AAAAA-1AAA with your specific license key.
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)
You can configure a custom location and provider to be displayed via API. This information is currently not available in AMP.
To add this option, edit the Armor Anywhere - Security agent configuration file on each host.
- In Windows, the configuration file is located at C:\.armor\etc\armor.cfg
- In Linux, the configuration is located at /etc/armor/armor.cfg
The options in the configuration file are PROVIDER and LOCATION.
Step 4: Review the status of the Armor Anywhere agent
- In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
- Click Virtual Machines.
- 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 Armor Support.
| Account | You will receive a notification when:
|
| Billing | You will receive a notification when:
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.
|
| Technical | You will receive a notification when:
|
You can only change the notification preferences for your own account. You cannot change the notification preferences for other user accounts.
- In the Armor Management Portal (AMP), in the top, right corner, click the vertical ellipses.
- Click Settings.
- Click Notification Preferences.
- 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.
- Click Update Notification Preference to save your changes.
Was this helpful?
| Your Rating: |
|
Results: |
|
0 | rates |