📝 Liongard Product Enhancement Request

📌 Title:

Enable Broad Registry Value Collection from HKEY_LOCAL_MACHINE\SOFTWARE via Windows Inspector

❗ Problem:

Partners need to automatically collect and document configuration data for third-party applications installed on Windows systems. Many of these applications (such as TeamViewer) store unique identifiers, licensing data, or configuration values in the Windows Registry — specifically under the HKEY_LOCAL_MACHINE\SOFTWARE key. Currently, Liongard does not provide visibility into these registry paths.

💡 Proposed Solution:

Enhance the Windows Agent Inspector or build a dedicated Windows Registry Inspector to:

Recursively collect and return all keys/values under HKLM\SOFTWARE

Include support for common registry data types (REG_SZ, REG_DWORD, etc.)

Store this data in the system export for downstream documentation and reporting

✅ User Story:

As an MSP Engineer, I want Liongard to collect all registry data under HKEY_LOCAL_MACHINE\SOFTWARE, so that I can automatically document third-party application configuration values — like TeamViewer Client ID — without maintaining custom scripts or logging into each system.

💥 Value Proposition:

Provides MSPs with deep visibility into installed software configurations

Enables automated documentation of settings that are otherwise only accessible within an app UI (e.g. TeamViewer)

Reduces reliance on custom PowerShell scripts or manual RMM tasks

Makes Liongard more comprehensive as a single source of truth

🔍 Example Use Case:

TeamViewer Client ID is stored at:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer\ClientID Data

Today, partners must log into each system or open TeamViewer to retrieve this manually. With registry support, this ID could be automatically collected and reported by Liongard.

⚙️ Technical Notes:

No third-party API integration is required

Uses Liongard’s existing Windows Agent to access local registry

Collection could be recursive (entire HKLM\SOFTWARE) or, in future iterations, allow for filtered keys

📈 Impact & Urgency:

Primarily supports documentation workflows

Initial request from a partner related to TeamViewer, but many applications store critical metadata in registry

Not an urgent/critical feature today, but has broad potential utility across MSPs for audit, licensing, and onboarding workflows

🚀 Suggested Next Steps for Product Team:

Evaluate if the current Windows Inspector already accesses registry data

Scope out registry key collection under HKLM\SOFTWARE

Ensure safe handling of sensitive or large binary keys

Consider opt-in filtering or key targeting for performance in large environments