Remote Monitoring & Management Help

Getting Started Agent

Client and Site

All Agents are associated with a Client and Site, which can be a physical or logical designation and to get you up and running we have already created a Client and Demo Site based on the company details you signed up for you trial with.

To begin monitoring and installing features for Windows such as Take Control,Managed Antivirus, Patch Management and Backup & Recovery you can either use this Client and Site or create a new combination from the File menu on the Dashboard. It is also possible to create a Client and Site when installing the Windows Agent manually.

Windows Agent Deployment

The Agent is available from the Agent menu on the Dashboard and can be deployed in one of two ways, Manually or through the Site Installation Packages (Group Policy or Remote Worker)

Manually Installation

From the Agent menu on the Dashboard select the required version, there will normally be a production Agent as well as the current Release Candidate.

Once downloaded on to the target server or workstation, extract the compressed file and run the Agent executable to begin the process.

Enter the Agent Key login details (included in the registration email) when prompted and run through the installation wizard configuring the Checks as required.

After testing all checks - and navigating back to amend any settings if necessary - select the account the Advanced Monitoring Agent service is to run under, by default the Local System account, to begin monitoring.

Site Installation Package Deployment

From the Dashboard Agent menu go to Download Site Installation Package, enter the Agent Key password (from the registration email) then choose the Client and Site combination, the Agent version to base the package on and Proxy settings (if necessary) then proceed to download the required installer. Once installed the Advanced Monitoring Agent runs under the Local System by default, although this can be amended post-installation on the device if required.:

Group Policy Installer: This installer is designed to be used with Group Policy software installations.

Remote Worker Installer: This is a silent, single-click installer designed to be sent out to users who are not always connected to the company network.

To speed up Windows Agent deployment it is possible to create Installation Templates containing pre-configured monitoring checks with the option to assign the template at the overall device level (server or workstation) down to specific Clients or Sites.

The templates are created either from an existing Agent installation via the Server or Workstation drop-down, Create Monitoring Template or from Settings, Monitoring Templates

Please note on a manual Windows Agent installation it is possible to select any of the account Monitoring Templates for that device type (server or workstation) from the Installation Template drop-down, although it is still possible to tweak any checks during the installation process.

Linux Monitoring Agent Deployment


To download, install and update the Linux Monitoring Agent we suggest adding our repository reference to the device.

Red Hat Family - Quick Installation Guide

There are a number of ways to reference the repository for automatic deployment using YUM (Yellowdog Updater, Modified) including add a .repo file in the /etc/yum.repos.d directory or creating a repository reference to /etc/yum.conf. Entering the contents of the .repo file from the repository server for the required distribution and architecture.

Regardless of the method used, after adding the repository it may be necessary to import the required GPG key and this can be achieved with the rpm import command, referencing the repomd.xml.key in the repodata directory of the repository:

# rpm --import http://repos.*/rmmagent/distribution/repodata/repomd.xml.key

Once the repository is setup, to deploy the Agent rmmagent.rpm package run the yum install command including the architecture of the device the Agent is to be installed upon (i.e. i386 or x86_64)

# yum install rmmagent.i386

# yum install rmmagent.x86_64

Manual deployment using RPM (Red Hat Package Management)

The Agent is available as an RPM file and as such it can be automatically installed from the command line with the rpm –Uhv command pointing to the location of the package for this distribution and architecture, for example its repository position:

# rpm -Uhv http://repos.*/rmmagent/distribution/architecture/rmmagent-*.rpm

Once installed it is necessary to register the Linux Monitoring Agent with the Dashboard by navigating to the Agent installation directory and applying the following command:

# cd /usr/local/rmmagent

# ./rmmagentd –i

When prompted input the Agent Key Username and password then select the required Client and Site then select Y to Start Agent Now ? and run as a daemon.

The Linux Monitoring Agent can be registered as a service that will start automatically when the server enters runlevel 3 using chckconfig which updates the runlevel information for system services with –add the service and then–list to ensure this was successful.

# chkconfig --add rmmagent

# chkconfig --list rmmagent


Permissions: to retrieve all of the required information it is necessary to install and run the Agent as root (super-user).

Proxy: where communication is through a proxy on the network, the pak.xml file contained in /usr/local/rmmagent directory must be edited before registration to take account of this. Amendments to the proxy settings may be applied post-registration in agentconfig.xml in the rmmagent directory.

Accesse Deniedit is normal to see one or more Accesse Denied error messages while the Agent attempts to locate the correct territory system instance.

Dashboard Control:as there is no management console for the Linux Monitoring Agent, any changes (change Agent settings, add or edit Checks) are configured from the Dashboard.

Asset Tracking

After installation the Agent scans the local device to retrieve the asset information uploading this to the Dashboard, where it is available in the Asset Tracking section once processed.

Check Configuration

Checks are configured via theChecks drop-down on the Dashboard, with the option to apply this change to individual devices or to multiple machines via the Dashboard with changes automatically synchronized to the Agent. For the Windows Agents it is also possible to configure the Checks from within the Agent console itself.

There are two types of Check:

24x7 - which run every five or fifteen minutes on servers and thirty or sixty minutes on workstations

Daily Safety Checks - run once per day primarily to monitor scheduled jobs such as backups, Antivirus updates etc

Change Agent SettingsFrom the Dashboard select the device in the north pane and either double-click or right-click on the device name or go to Edit,Edit Device (from the Server or Workstation drop-down select Edit Device) to display the Edit dialog. With the option to amend settings including the Site and Device the Agent is registered against, the frequency of the checks as well as offline (maintenance mode) behavior. For the Windows Agents it is also possible to change the settings from within the Agent console itself.