Feature Requests

Many modern desktop environments have non-persistent servers which are all image based and will frequently be rebuilt from the GOLD image. Deployment of an agent via RMM or GPO keeps adding a new agent and appending to (1) or (2) etc which then requires manually moving the inspector. This is inefficient to keep re-aligning the inspector to a new agent Logic rules for when a new agent attempts to connect to Liongard: * Does the HOSTNAME already exist? * Is it coming from the same Source IP? * Is the current Heartbeat down? If yes to all 3 > treat new agent as if old agent returning heartbeat.

We have multiple inspectors that would benefit from being able to use a self-hosted global inspector due to IP restrictions, or have local agents be able to inspect 'public-facing' systems like SSL certificates. We should at least be able to use a self-hosted global agent in all the same scenarios that we would use the LionGard on-demand agent.

The "Instance URL" section has a hint of " us1.app.liongard.com " and has confused a couple of users There is no error when they click continue mentioning that this is required, and for users on us1 especially, they may believe it's automatically filled out Either have a small popup stating that instance URL is not filled out, or put the hint underneath the textbox, rather than inside of it.

To provide additional clarity into out Outdated vs EOL Agents. Also, provide an Column for End of Life Agents, so we can identify EOL vs Supported OS Agents. Have an Dedicated Category, for End of Life/Support Agents. Remove them from the "Outdated" Agents, because Outdated agents implies that you can update them, but for the EOL OS Agents, you cannot update the Liongard Agent.

The Upload Speed Test is causing one of my clients to hit their bandwidth limits as a lot of endpoints are running the test at the same time. This function was enabled automatically after agent install and is crippling one of my most important clients’ network when the speed test runs. The ability to create agent setting templates so this setting or other settings can be modified in bulk for a group of agents or environment. Or just the option to change a setting across agents in bulk.

Can we get this function back? "we have removed the AD inspectors' ability to auto-discover other Windows Servers. If you have any other questions or need more information, please do not hesitate to reach out. " Bring it back.

When importing devices, we have over 2000 agents to deploy across multiple customers. Sometimes, these PCs will have the same hostname. When attempting to bring in these devices, it will deny any other PC that is attempting to be brought in by that name resulting in an error "INVALIDMSG = An agent with the same name was already found. Please select a different name or remove the agent from Liongard first." Example "SHIPPING-PC" in 1 customer environment already assigned // deployed to another customer with a PC named "SHIPPING-PC" and this device was denied. Ideal would be an automatic/temporary addition to the name to allow for device to be brought into console.

I'm looking to have the Mac Agent fully functional since I am a Mac-only shop. Have a fully functional Mac agent like the Windows one.

Name of the partner or prospect and the role(the specific user and email) Bill Krauss, Applied Tech Solutions inc The name of the company Applied Tech Solutions Are they a prospect or a partner? Partner While at roar con the partner mentioned they are running into limitations with the global agent with the amount of systems they run on it. They mentioned they'd be okay if this agent had access to either max resources on the server or ability to provide the agent more resources to run more runs concurrently would also be okay They are using multiple servers and agents but having one larger agent would provide easier management of the devices

On behalf of partner: aus2/Origin84 Partner runs almost all ARM Macbooks, if they do not install the rosetta translation layer, they cannot install the agent Partner wishes for native ARM architecture support for our agent Is this something we can do with node.js? Is this something we are planning on? If so, where on the roadmap is it? Use a native ARM architecture node.js executable for the Mac agent