👍

Agent Version 4.0.0 and Newer

In May of 2022, Liongard simplified the Windows .msi file to ensure that the Windows Agent could be deployed with minimal effort. The parameters below are applicable to Agent version 4.0.0 or newer.

As detailed below, many parameters are optional. Deploying Agents in mass, across multiple customers, should be easier than ever using the same simplified one-line command.

Deploying the Liongard MSI via Deployment Tool

If you would like to deploy Liongard's .msi file with your deployment tool, please refer to the vendor's Knowledge Base library for the appropriate steps.

Command line switches for deployment can be found below.

Download the Agent (PowerShell)

Invoke-WebRequest -Uri https://agents.static.liongard.com/LiongardAgent-lts.msi -OutFile ./LiongardAgent-lts.msi

Deploy Agents via Command Line or RMM

Liongard's MSI can be invoked for a silent install from the command line or for scripting via the RMM.

The only required fields are "LIONGARDURL," "LIONGARDACCESSKEY," and "LIONGARDACCESSSECRET."

msiexec /i LiongardAgent-lts.msi LIONGARDURL=yourinstance.app.liongard.com LIONGARDACCESSKEY="yourkey" LIONGARDACCESSSECRET="yoursecret" /qn

Optionally, you can pass the following parameters:

• If you wish to add a description to the agents, include "LIONGARDDESCRIPTION"
• If you wish to choose a different directory to install the Agents, you can use the "INSTALLLOCATION" variable. If your custom path has spaces or special characters, then be sure to surround the location with triple double quotes to allow it to escape correctly in PowerShell. Otherwise, you do not need to use double quotes to escape the path.

If you do not provide "LIONGARDAGENTSERVICEACCOUNT" and/or "LIONGARDAGENTSERVICEPASSWORD," then the service will default to installing as a Local System.

For On-premises and Endpoint Agents, if you do not pass in the "LIONGARDENVIRONMENT" parameter, you will have to assign the Environment in Liongard by navigating to Admin > Agents.

The Agent Name field is automatically populated with the hostname of the target system; however, it can be customized if necessary. To do so, use the parameter LIONGARDAGENTNAME="YourCustomName"

📘

Deploying via PowerShell

If you are deploying agents via PowerShell and your variables include spaces, commas, or dollar signs ($), you will need to include escape characters.

Spaces Example: LIONGARDENVIRONMENT= `“Exact Environment Name Inc.`”

Comma Example: LIONGARDENVIRONMENT= "`" Exact Environment Name, Inc.`""

Dollar Sign Example: LIONGARDAGENTSERVICEPASSWORD= "Pa`$swordHere"

msiexec /i LiongardAgent-lts.msi LIONGARDURL=yourinstance.app.liongard.com LIONGARDACCESSKEY="yourkey" LIONGARDACCESSSECRET="yoursecret" LIONGARDAGENTNAME="Friendly Name of Your Choice" LIONGARDENVIRONMENT="Exact Environment Name, Inc." LIONGARDAGENTSERVICEACCOUNT="mydomain\domainadmin" LIONGARDAGENTSERVICEPASSWORD="mypassword" LIONGARDDESCRIPTION="optional description" /qn

Troubleshooting Agent Issues

If you are having issues with your Agent, please review our Troubleshooting Agent Issues Documentation.

Allowlisting Liongard

On-premises Agent Allowlisting

If any of your networks heavily filter outbound traffic, you may need to allowlist some hosts in order for the Agent to send data back to Liongard. There may be other situations where you need to allowlist the Liongard platform itself. If so, please see How to Properly Allowlist the Liongard Platform.

Self-Hosted Agent Allowlisting

Once the Self-Hosted Agent is installed, you will most likely need to allowlist the Agent IP address on the device being inspected.

• Inbound and Outbound Traffic from the Self-Hosted Agent Machine to the Target Device: The static IP address of the machine for which the Agent is deployed.
• Outbound from the Self-Hosted Agent to Liongard: Full outbound requirements can be found in our How to Properly Allowlist the Liongard Platform documentation.