How to retreive the Run registry key from the clients and store it in the Inventory

For Version 8.8 and 9.0

Introduction

Modifying the LDAPPL3.TEMPLATE is possible to retrieve form the clients the registry values that we need but the only limitation is that we need to know in advance the name of the value stored in the registry.

For some specific registry keys is hardly possible to predict the name of the values and a good example for this is the Run registry key.

This article will explain how to retrieve all the content of this key and put it in the inventory

How to use the attached script

The attached script needs to be distributed in the LDClient folder of every client.

A modification to the file LDSCNHLP.INI is needed as well. The file is in the LDClient folder of the client ( C:\Program Files\LANDesk\LDClient )

Normally a standard LDSCNHLP.INI file should look like this one:

[EXECUTE WIN16]

[EXECUTE WIN32]
LAUNCH1=C:\Program Files\LANDesk\LDClient\ldcstm32.exe /s
TIMEOUT1=600

[DATA FILES]
DATA1=C:\PROGRA~1\LANDesk\LDClient\LDCUSTOM.DAT

We need to add now in the [EXECUTE WIN32] section a referral to the script GetRunKey.vbs that need to be deployed in the LDClient folder.

We need to add in the [EXECUTE WIN32] section a referral to the file that the script will generate: registry.dat

After our modifications the LDSCNHLP.INI file should look like this one:

[EXECUTE WIN16]
[EXECUTE WIN32]
LAUNCH1=C:\Program Files\LANDesk\LDClient\ldcstm32.exe /s
LAUNCH2=CSCRIPT "c:\program Files\LANDesk\LDclient\GetRunKey.vbs"
[DATA FILES]
DATA1=C:\PROGRA~1\LANDesk\LDClient\LDCUSTOM.DAT
DataNoPrepend1=c:\Program Files\LANDESK\LdClient\registry.dat

After these modification every time that the inventory scanner is executed the script will be executed as well and the registry.dat files regenerated.

The data will be available in the inventory under OS - Registry - Run Key

IMPORTANT NOTES

The script is given ''as is'' and the implementation of this solution need to be carefully tested before the implementation of it in production.

There are some parts not covered that I plan to cover in the future as:

• ability to parameterize the script so it will be possible to collect non only the Run subkey but other keys as well.
• ability to modify the agent configuration so the script will be automatically deployed and the LDSCNHLP.INI will contain already the right information.
• more solid error handling.
• prevent permission problems.

the script associated to the inventory will run under the identity of the user that launched the LANDesk Inventory Scan: check that the user has the right to read the registry key.

SCRIPT FILE

GetRunKey.vbs

For LDMS 9.5

This process has changed for LDMS 9.5.  In the Management Suite Console, go to Reporting and Monitoring > Manage File List.  When the Manage File List window opens, expand Custom Data, then highlight Registry Items, and select the blue ? for help on the tool bar.  This will explain the process of collecting registry keys and how to configure it.