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 Installation Best Practices
- 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.
- 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.
- 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
- 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:
- Upon install, an On-premises Agent will auto-activate an Inspector for the local Windows Server
- After the Windows Inspector runs, it will auto-discover an Active Directory Inspector
- Once activated and successfully run, the Active Directory Inspector will auto-discover Inspectors for any additional Windows servers within its Domain
- Once activated and successfully run, the Windows Inspectors will auto-discover Inspectors for any installed Hyper-V or SQL Server Inspectors
- After the first Windows Inspector runs, it will also auto-discover a Network Discovery Inspector
- 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.
The script below provides for a basic install of the Liongard Agent via ConnectWise Automate using our MSI installer.
- The script takes in variables associated with your Liongard instance such as the URL, Access Key ID and Secret, and completes an install.
- This script will be supported on a best-effort basis.
The current version of this script does not set the Agent service's "Run As" user or associate the Agent with an Environment upon install. The script can be modified to meet your particular needs by modifying the parameters passed into our MSI install. Full details of how the MSI is parameterized are available on our MSI Installer documentation page.
Download the Automate Installation Script
Then, import it into your ConnectWise Automate instance. System > General > Import > XML Expansion
The imported script is named "Roar-Agent Installer."
- Open the script and populate the variables (lines 1-4) from your Liongard setup
- Create Ticket: Whether or not you would like a service ticket created for a failed install
- Roar URL: Insert your Liongard URL (e.g., roar.app.liongard.com)
- Roar Access Key: Insert your Liongard Access Key generated from your Liongard instance. This can be found in Liongard by selecting your user account name in the top right corner > Account Settings > Access Tokens > Generate a New Token
- Roar Access Secret: Insert your Liongard Access Key Secret from the steps above
- Assign the Agent to an Environment
- This script does not assign the Liongard Environment to the newly installed Agents, so newly installed Agents will need to be assigned an Environment from the Admin > Agents screen in Liongard.
- If your Automate instance has access to company names that precisely match the Liongard Environment names, this script can be expanded to add that information as a part of the scripted process by adding the ENVIRONMENT= parameter to the msiexec.exe call.
- Additional details of how our MSI installer is parameterized are available in the MSI Installer documentation.
Thanks to Liongard partner Matthew Weir for sharing the above ConnectWise Automate script. If you'd like to share how your team is using automation with Liongard, email us at [email protected]
Updated 2 months ago