Description
This article will explain how to get different sets of custom registry into the inventory.
In order to generate the inventory, the local scheduler use a file called ldappl3.ldz, to learn more about that file and how the inventory works please watch the following e-learning video :
http://community.landesk.com/support/docs/DOC-22185
This process could be used for example in order to get certain set of custom registry data from laptops and another set of custom registry data from the workstations.To facilitate the understanding of the different steps, we will assume that we will create a first set of custom registry information called CustomWKS for the workstation and a second set called CustomLTP for the laptops.
1. Creating CustomWKS
In order to get custom data in our inventory we need to customize the ldappl3 file, to do so we have to modify the ldappl3.template in the following folder : C:\Program Files (x86)\LANDesk\ManagementSuite\ldlogon
Below are the different steps with the 9.0 and 9.5 version of LDMS.
To access the GUI in the console as below, go to Reporting / Monitoring > Manage Software List > Right click on Registry Items > Add
2. Save the files needed to get CustomWKS
Once you have clicked on "Make Available to Clients"some files will be generated :
Then you need to move those files to another location (create a new folder inside LDLOGON\CustomWKS for example) except the ldappl3.template.
In this new location, you will have the files needed to get your first set of custom registry information (CustomWKS).
3. Generation of the LDAPPL3 files for CustomLTP
Repeat the process reviewed in the part 1 of this article "to generate a new set of custom data or remove the custom data"
By default all the nodes managed will use the ldappl3 files in the folder by default (C:\Program Files (x86)\LANDesk\ManagementSuite\ldlogon).
So, if we want the workstations to use the CustomWKS files, we will need to modify the path of the related task in the Local Scheduler (the process that will load the ldappl3.ldz to run the inventory).
4 - Configure the Local Scheduler to use the CustomWKS files
To have a look at the different tasks handled by the local scheduler, you have to type the following command : 
First you need to remove the task concerned with the command: localsch.exe /del /taskid=<id>
To modify the path we can use a script on the Core that modify/add/remove tasks of the Local Scheduler as explained in the following document :
http://community.landesk.com/support/docs/DOC-5778
After that, you will be able to see in the task scheduler that it will use the CustomWKS ldappl3 files :
Now you need to deploy this script to your workstations, so they will use the CustomWKS and send to the Core the registry information needed.
Your other machines, the laptops will still use the ldappl3 files from the ldlogon folder and send back the information defined in those files.
