Currently Liongard will only list local users in relation to things like the ever so important Administrators group.

The command the agents are using to populate this data does not also pull back accounts from other source (e.g. Active Directory, AzureAD etc.)

This causes issues when using metrics like "Windows Workstation: Local Administrators Group List" that are default because they ONLY report on local accounts. Meaning an Azure AD user can be in that group and Liongard does not raise it.

Adjust the current user or group command the agents runs on Workstations to pull back a proper list of users, not just when the principal source is "local"

I have submitted this before and decided I will continue to report this every time I need to re-explain it to users within my company. This is difficult to explain without them losing hope in Liongard's capabilities. Our alternative is to turn to running scripts in our RMM to gather this data accurately.