HomeLiongardRequest a DemoKnowledge Base

Deployment via N-able RMM Platforms

Suggest Edits

❗️

Liongard Agent MSI Name Change

Starting with version 2.0.2, the Liongard Agent MSI package was renamed to "LiongardAgent-lts" as part of our new brand messaging.

Deployment scripts using the old naming conventions (RoarAgent.msi, ROARURL, ROARACCESSKEY, etc.) will still work if necessary, but we do recommend updating the scripts when possible to ensure consistency across the platform.

New installations using the MSI will change the Windows service name to "Liongard Agent." Upgrading an existing installation will leave the service name as "Roar Agent."

On-Premises Agent Overview

On-Premises Agent Installation Best Practices

  1. Install On-premises Agents on Domain Controllers
  • We support On-premises Agents installed on servers; however, installing an On-Premises Agent on a Domain Controller will result in more Inspector auto-discovery, and therefore, less manual work.
  1. Generally, install One On-premises Agent per Network
  • Our Agents speak across VPN tunnels
  • Our Agents DO NOT speak across Active Directory Domains, so if you have two Active Directory Domains in one network, then you'll need an Agent within each Active Directory Domain.
  1. Install an additional On-premises Agent on any server NOT tied to an Active Directory Domain
  • The additional Agent will auto-activate an Inspector for the local Windows server, and that Inspector will auto-discover a Network Discovery, Hyper-V, and/or SQL Server Inspectors if present
  1. Agent Names must be unique. Include a unique identifier in the Agent script to ensure all Agents will have a unique name.

👍

On-Premises Agent Installation = Inspector Auto-Discovery

When you roll out an On-premises Agent, there is a potential for the auto-discovery of several other Inspectors:

  1. Upon install, an On-premises Agent will auto-activate an Inspector for the local Windows Server
  2. After the Windows Inspector runs, it will auto-discover an Active Directory Inspector
  3. Once activated and successfully run, the Active Directory Inspector will auto-discover Inspectors for any additional Windows servers within its Domain
  4. Once activated and successfully run, the Windows Inspectors will auto-discover Inspectors for any installed Hyper-V or SQL Server Inspectors
  5. After the first Windows Inspector runs, it will also auto-discover a Network Discovery Inspector
  6. After the Network Discovery Inspector is activated, it will auto-discover Inspectors for several makes/models of network devices. See our Network Discovery Inspector docs for more information.

Script Overview

❗️

Warning: Partners must review the script in its entirety before use.

This is a basic script that enables mass deployment of the Liongard Agent to managed systems.

It is a good starting point and should be modified to meet your needs.

The script below provides for a basic install of the Liongard Agent via either one of N-able's RMM platforms using our MSI installer.

  • The script requires variables associated with your Liongard instance to be manually input, but it does dynamically look up the system name to complete the install.
  • This script will be supported on a best-effort basis.

This script can:

  • Install an On-premises Agent.
  • Upgrade an On-premises Agent. If the Agent is already detected on the target machine, it will download and run the MSI installer to upgrade the Agent.

This script will not prompt for Agent "description," and it requires the entry of a service username and password.

There is some automation built-in to the script, in that the POSH inside of the AMP will dynamically look up the computer name for you. If you have an Environment that requires multiple Agents, as long as you are running the installation on the same Environment with the same credentials, etc., you can mass run the script.

Download and Install the Script

Liongard Agent for N-able script

Updated 4 months ago