Feature Requests

On behalf of Jim Barry @ Relentless The prefix of the inspector name is unnecessary, and more importantly, it does not match what's listed in our PSA, Documentation, and RMM solutions, resulting in confusion on our teams. When a new inspector is discovered, label it as the hostname and do not include the "Windows Workstation -" prefix. For my current inspectors with the prefix, I'd like Liongard to run a batch script to update the names and remove the prefix.

Large Prospect: Arch Tech Contact: Edward Wilson The Arch Tech team is looking to replace their current manual processes for pulling the following data. Bitlocker Keys Inactivity Screen Timeout BIOS Update Info Windows Updates Timestamp Hard Drive health They provided example scripts for us. Bitlocker Keys $BitLockerKeyInfo = Get-BitLockerVolume | Select MountPoint,KeyProtector | Sort -Property MountPoint $BitLockerKeyArray = @() ForEach ($item in $BitLockerKeyInfo) { $MountPoint = $item.MountPoint $RecoveryKey = string .RecoveryPassword if ($RecoveryKey.Length -gt 5) { $BitLockerKeyOutput = "BLRK $MountPoint $RecoveryKey" $BitLockerKeyArray += $BitLockerKeyOutput } else { $BitLockerKeyOutput = "BLRK $MountPoint None" $BitLockerKeyArray += $BitLockerKeyOutput } } Inactivity Screen Timeout $timeout = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System").InactivityTimeoutSecs if (!$timeout -or $timeout -gt 1800) { $passed = $false $results += " - Screenlock" } BIOS Update Info First Factor - BIOS has not been updated in more than 1 year $BIOSReleaseDate = Get-WmiObject -Class Win32_BIOS | Select ReleaseDate $BIOSDate = [datetime]::ParseExact($BIOSReleaseDate.ReleaseDate.Substring(0, 8), "yyyyMMdd", $null) if ($BIOSDate -lt (Get-Date).AddMonths(-12)) { $passed = $false $results += " - BIOS Updates" } Windows Updates Timestamp $lastWindowsUpdate = (Get-WmiObject -Class Win32_QuickFixEngineering | Sort-Object -Property HotFixID | Select-Object -Last 1).InstalledOn if ($lastWindowsUpdate -eq $null) { $lastWindowsUpdate = (Get-WmiObject -Class Win32_QuickFixEngineering | Sort-Object -Property HotFixID | Select-Object -Last 2).InstalledOn if ($lastWindowsUpdate -lt (Get-Date).AddMonths(-2)) { $passed = $false $results += " - OS Updates" } } elseif ($lastWindowsUpdate -lt (Get-Date).AddMonths(-2)) { $passed = $false $results += " - OS Updates" } Hard Drive health $DiskOutputArray = @() ForEach ($item in $DiskInfo) { $DiskID = $item.DeviceID $MediaType = $item.MediaType $DiskHealth = $item.HealthStatus $DiskOutput = "Disk $DiskID`: $MediaType $DiskHealth" $DiskOutputArray += $DiskOutput }

It'd be incredibly useful to be able to list active/inactive mapped drives on workstations. We commonly get requests to fix broken network drives, sometimes they are ones that were manually mapped outside of a group policy. We are left trying to track down what the previous path or drive letter was to get the user back up and running. This will likely need to be a script to enumerate all profiles on a system (in the registry) to get their path and drive letter. I'd then be able to metric and track changes on it for our service desk techs

Need to determine if there are machines in the environment that still have HDD's installed. They are no longer allowed under our minimum requirements and need to identify those machine so we can upgrade to an SSD or get a new machine. I just need to have some way to identify this in the data print view. Once the data is available, I can get the metric built.

We need to be able to confirm that all machine in the environment have sleep and hibernation disabled while plugged in. This is important because we run updates at night and machines that do not have the correct settings are likely to net get patched. Find a way to identify power settings and display either a summary, or break it down into specific power settings that we can filter out. Once the data is available, I can put the metric(s) in place. (Hibernation status and sleep status are the most important pieces here)

Jake Dean​​​​ | DIRECTOR, CENTRALIZED SERVICES | e: jake.dean@nettech.net | w: www.nettech.net Manages thousands of HP devices servers and workstations. Only reason they would have to keep Scalepad is for that, and they want to eliminate it. Get HP warranty info just like we do for HP & Dell

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.

I would like to be able to categorize and tag assets and devices within Liongard. I'd like to be able to give devices a hierarchy of importance so at a glance if systems go down we are able to see what's critical. customizable columns

The hot ticket for Rouse right now is getting Windows 10 machines to Windows 11. Your compatibility test is great, but we do need an additional feature. Machines that are in legacy BIOs mode will not do secure boot unless they are converted to UEFI. Your workstation agent does not report on that currently.

Needed for compliance reporting, the Classification for each and every patch for OS (Critical Updates, Security Updates, Update Rollups, Updates, Upgrades, Other).. We can get this info manually using power shell, but trying across several hundred machines for this basic info is daunting. Please add it to the data print as this field is important for any compliance reporting. NOTE: This is needed for both WIndows Server and Windows Workstation That each and every patch in the report has the classification field with it. NOTE: This is needed for both WIndows Server and Windows Workstation