Getting Started - Monitoring Agents
This guide covers the installation and configuration of the Monitoring Agent, available for the following computer Operating Systems:
- Manual Installation
- Site Installation Package
- Asset Tracking Only Installation
- Apply Monitoring Template during Agent Installation (Windows)
- Windows Agent Installation FAQs
- Monitoring Templates - Installation
- Update the Advanced Monitoring Agent
- Uninstall the Advanced Monitoring Agent
- Supported Linux Distributions and Builds
- Required User Permissions
- Install, Update and Remote - Red Hat Family
- Install, Update and Remote - SUSE Family
- Install, Update and Remote - Debian Family
- Register the Linux Monitoring Agent with the Dashboard
- Register the Linux Monitoring Agent as an auto-start service
- Download the Mac Agent from the Dashboard
- Install the Mac Agent on the workstation
- Register the Mac Agent against the Dashboard
- Update the Mac Agent
- Uninstall the Mac Agent
- Site Installation Package - Remote Worker
- Adjusting Connection Settings
- General Settings
- Change the Agent service logon account
- Configure the server overdue Alert settings
- Update the Advanced Monitoring Agent
- Start/Stop the Agent from the command line
- Backup Configuration
- Amend Linux Monitoring Agent Settings, Checks and Default Alerts from the Dashboard
- Agent Communication: Proxy Configuration and Force HTTP
- Start or Stop the Agent: Application or Daemon
- Starting and Stopping the Agent Daemon automatically
- Rerun the 24x7 and Daily Safety Checks
- Amend Mac Agent Settings, Checks and Default Alerts from the Dashboard
- Configure Proxy Settings
- Place the Agent Offline
- Rerun Checks from the Agent console
Reduce the time taken to install Windows Agents as well as ensure each device matches the exact Check and threshold requirements with the option to apply a Monitoring Template regardless of the installation method. Automatically apply a template based on device type, Client or Site as well as choose the template during a manual install.
Dashboard and Monitoring Agent Communication URLs
Depending on the company's security policy a firewall or other web monitoring software may be deployed to filter internet connections. To avoid any potential Dashboard or Agent communication issues, we would suggest whitelisting the URLs featured in Dashboard URLs and Agent Communication URLs as well as those listed in Features URLs where there is the intention to deploy any of these features (Take Control, Web Protection, Managed Antivirus, Network Discovery etc).
Virtual Machines, Cloned or Provisioned Computers
As part of the installation process, we assign each Agent a unique identifier to ensure that when the Agent uploads data it is registered against the correct device.
Problems may occur when after installing the Agent, the computer is then imaged or cloned. When the image or cloned computer starts, the installed Agent uploads data against the identifier for the donor computer.
To avoid this scenario, we suggest imaging or cloning a computer before installing the Agent. Then install the Agent on the image or clone after it has started.
When was the Monitoring Agent installed?
For audit purposes it can be useful to know when the Monitoring Agent was installed on the device and this is returned in both the User Audit Report (filter on Action: Add and Event: Device) and Device Inventory Report
Date and time of the Agent on the Dashboard
The date and time reported on the Dashboard for the Agent, Checks and Automated Tasks etc. is based on the local time of the computer the Agent is installed on.
Site Installation Packages
Remote Worker installers are available for Windows and Mac devices, Group Policy Object installers are on available for Windows. Site Installation Packages are not available for Linux.
To avoid any potential problems with the Agent, we recommend that you only upgrade the Agent to a newer version and never downgrade to a previous release. If there is a requirement to install an earlier version of the Agent we would suggest uninstalling the current version first.
It is not possible to protect the Agent from uninstall and once initiated, an uninstall cannot be stopped.
Once installed on the device the Monitoring Agent runs a local asset scan uploading this hardware and software information to a dedicated Asset Tracking Dashboard.