Create a query or a report on a specific registry key (Screenshot Step by Step)

Version 7

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.0 and Older



    LANDesk Management Suite 8.7 and 8.8


    About pulling data from the different portions of the Registry

    It is important to point out the registry key locations we can pull data from. The inventory scanner is launched by the LocalSystem account user. The LocalSystem user account has access to all of the registry however if you were trying to gather data from HKEY_CURRENT_USER (HKCU) you would be pulling data that is for the LocalSystem user account and not the logged in user. This data would not be useable since the data that we would like to pull for would be the logged in user such as Jane Smith.There are 3rd party work arounds to this issue. You are able to use tools at (not supported by LANDesk). Other users on this forum have created batch files and vbscripts to run at startup for the logged in user and copies and places the data into HKLM. Please keep this in mind for the type of data you wish to pull.


    Step 1:


    On the client machine locate where the registry key data is. Here we have HKLM\SOFTWARE\FindMeInTheRegistry\HereIAm and we want the value of YouFoundMe.




    Step 2.



    On the core server go to the \Program Files\Landesk\ManagementSuite\ldlogon folder and open the ldappl3.template file with notepad or wordpad. Go to the Registry Info section and add your registry key information here with the following syntax:



    In this case we are looking for KEY=HKLM, Software\FindmeInTheRegistry\HereIAm, YouFoundMe, Custom Data - HereIAm - YouFoundMe



    Syntax: KEY=hkey name, key, value, landesk database attribute name





    Step 3.



    In the console go to Software License Monitoring and click on Make Avaliable to Clients.





    Step 4.



    Run a full inventory scan. You can do this with a managed script from the console. Please see the following post on creating a full inventory scan and using a scheduled task to run from the console.




    Step 5.



    Look at the inventory of the machine to ensure the registry key data is showing. We specified the information to be stored under Custom Data and to be defined as HereIAm.





    Step 6.



    Now we can create a query or report on this data. Here we select under Custom Data and highlight the key we are searching for and choose Exsists. This will show us all devices that have this registry key.



    NOTE: If Custom Data isn't showing up in inventory make sure that the data isn't being blocked. On the core go to Configure - Services - Inventory Tab. Click on Unknown Items and search for Custom Data and click Allow.