| Note |
|---|
Before you begin, Armor recommends that you pre-installation information, including firewall rules. To learn more, see Armor Anywhere Agent 3.0 Pre-Installation. |
...
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 Add an Armor Agent.
Copy your license key. You will need this information in a later step.
Select your operating system (Linux or Windows).
...
Armor recommends installing the Armor Agent with all Security Services. Documentation on installing the Armor Agent only can be found below.
Step 2: Install the Armor Anywhere Agent
...
Step 3: Review the status of the Armor Anywhere agent
...
In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
Click Virtual Machines and click on the corresponding VM.
On the VM detail page, you can view information about the VM as well as the services installed on the server and their corresponding health.
The State 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.
| Note |
|---|
The State of each Armor Service will show Pending for two-hours after installation. After two hours, the State should accurately reflect the health of the service. |
| Note |
|---|
To access troubleshooting documentation for each Armor Security Service, click on the name of the service in the sub-agent health table. |
...
...
Installing the Armor Anywhere Agent Only
If you need to install the Armor Agent and Armor Security Services one by one, Armor recommends following the specific order outlined below to utilize the benefits of Recommendation Scans.
Recommendation Scans provide a good starting point for establishing a list of rules that you should implement for FIM and IPS. During a recommendation scan, the Armor Agent scans the operating system for installed applications, the Windows registry, open ports, and more. Recommendation Scans provide the rules and policies that will be auto applied by FIM and IPS, so auto apply features for those services must be turned on. Similarly, there is nothing for FIM and IPS to auto apply unless a Recommendation Scan is run.
...
The BIOS UUID is required by the Armor Agent, to ensure uniqueness of the device. The BIOS UUID must be readable by the operating system. If the BIOS UUID is not available to the operating system please check with your provider.