Introducing PowerShell: Custom inventory of Registry Keys

Learn how vScope's PowerShell integration lets you collect custom registry keys, control access with Just Enough Administration, and build more flexible IT inventories.

With PowerShell, you can now enjoy a more flexible and customizable approach to documenting and reporting on your IT assets. In the latest update of vScope, you can create more custom reports and IT documentation by including information about Windows Registry Keys.

By using PowerShell for your Windows inventory, you also benefit from more granular permission settings, a concept known as Just Enough Administration. There’s much to explore, so let’s dive right in!

Cherry-pick registry keys

vScope’s current inventory methods—WMI (Windows Management Instrumentation) and WinRM (Windows Remote Management)—have long been the backbone of Windows OS information collection. The introduction of PowerShell complements these methods by offering a more nuanced and flexible approach.

Printscreen of Windows Registry

In vScope 3.29, you can now add registry keys to the Windows PowerShell credential and let vScope collect every key nested under the specified key. These values can be turned into tags from Discovery.

What are Windows Registry Keys?
A Windows Registry Key is a fundamental concept in the Windows operating system. It stores low-level settings for both the OS and applications. The registry contains values, configurations, and instructions essential for system and software functionality.

A few examples…

Here are some use cases where collecting registry keys can be useful:

Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Purpose:
Enable automatic login for a specific user account (e.g., for kiosk mode or auto-boot systems).

2. Power Settings

Key:
HKEY_LOCAL_MACHINE\SYSTEM\Current\Control\SetControlPower

Purpose:
Control system power-saving features and sleep settings to optimize energy use.

3. Default Browser

Key:
HKEY_CLASSES_ROOT\http\shell\open\command

Purpose:
Specify the default system-wide browser by modifying the path in this registry entry.

4. AutoCAD License Server

Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\Rxx.x\ACAD-xxxx:409AdLM

Purpose:
Configure the license server and licensing mode (standalone/network) for AutoCAD deployments.

5. Java Update Notifications

Key:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy

Purpose:
Enable or disable update notifications for Java across the environment.

Enhanced Permission Management with Just Enough Administration (JEA)

A simple diagram on how Just Enough Administration works

Another major update in vScope is support for Just Enough Administration (JEA). This feature allows IT admins to define precise, role-based access control to systems.

By integrating JEA, you can delegate only the permissions necessary for vScope to gather data—nothing more. This not only improves security but also streamlines administrative workflows and compliance.

Prepared for future customizations

We’re committed to expanding the PowerShell connector. Expect further enhancements that allow even more flexibility when customizing IT asset inventories and discovery tags.

Here’s the full guide on how to get started with PowerShell, Registry Keys, and Just Enough Administration.

Need help getting started? Get in touch

Introducing PowerShell: Custom inventory of Registry Keys