Home > ldms_client > ldms_client overview

ldms_client overview

September 22nd, 2010 Leave a comment Go to comments

Overview

LANDesk’s client inventory system is very powerful in that it can be easily extended. On a Windows system, you just edit LDSCNHLP.INI to call your script/program/whatever, then read its BNF-formatted output. Simplicity itself, right?

Unfortunately, it gets a lot less simple when you’ve pushed out five different scripts and deployed some new clients, and who knows what system is scanning for what extension. This program attempts to solve that problem, by providing a single extension and dat file which implements all the handy extensions as subroutines. Its configuration is read at runtime from a configuration file on the core server, so the administrator can turn parts on and off centrally.

ldms_client.exe runs as an inventory extension on Windows clients, gathering additional information for use in inventory. Its configuration is read at runtime from a configuration file on the core server. That configuration file is produced and edited with the Config_ldms_client.exe program.

This structure allows administrators to turn “extra” inventory scanning components on and off throughout the environment on an as-needed basis.

There’s obviously a lot of room for growth, which the infrastructure allows for.

Execution details

Windows: LANDesk’s ldiscn32.exe reads ldscnhlp.ini and sees it’s supposed to launch ldms_client.exe.  ldms_client.exe uses LANDesk’s sdclient.exe to pull down ldms_client.ini from the core, reads what it should scan, and scans for it. It then writes the scan results into ldms_client.dat, which ldiscn32.exe reads and sends to the core as part of its inventory update. To complicate matters, some things that ldms_client.exe scans for need to run as a local user, so it may use the LANDesk startasuser.exe utility to launch ldms_client_regreader.exe, and MappedDrives.exe.

Current Features

  • Find PST files and their size
  • Read Current_User keys from the registry
  • Get the logged in User’s Display Name from Active Directory *NEW
  • Get Battery Information
  • Get LANDesk Management Gateway Settings
  • Profile Size of every user on each system
  • Drives Mapped by the current logged in user
  • License Keys for Microsoft applications (Produkey required)
  • Map Logical Drives to the Physical Drives *NEW
  • Fragmentation Percentage of all fixed drives
  • TPM Chip information (Windows 7 only) *NEW


Categories: ldms_client Tags:
  1. craig
    October 7th, 2010 at 16:43 | #1

    Will LDMS_Client work on LANDdesk 9.0 sp1?

    • admin
      October 7th, 2010 at 17:47 | #2

      The current release that is posted here does not work with 9.0. However it is currently being re-written and the new version will support 9.x as well as work on Win 7 including 64-bit. Please check back here in a couple of weeks to see the new version.

  2. ccbysh
    January 1st, 2011 at 12:57 | #3

    Good Tool,

  3. denny
    January 10th, 2011 at 13:40 | #4

    @craig
    It does now. 9.0 SP2 is fully supported with the latest release. Check out the link under blogroll to get the latest version.

  1. No trackbacks yet.
You must be logged in to post a comment.