Home > ldms_client > ldms_client

ldms_client

Description

LDMS_Client is back!!!  It’s been re-written into Autoit to make it easier to maintain and to expand the number of people who can support it.  There is now a single installer that installs the configuration tool and extracts a second installer for the clients.  The configuration tool (Config_LDMS_Client.exe) will not only configure the ldms_client.ini file, but it will also copy it to the ldlogon directory for you as well as create a Distribution Package for you automatically in the LDMS Console.  There’s some new features like Display Name for users from Active Directory, and Logical to Physical drive mapping.   All Documentation below is being updated.  For suggestions on things to add to the tool or for help with the tool e-mail me.

Documentation

  • Overview – How it works, including detailed execution information
  • The list of what this inventory extension tool collects
  • Installation – Getting ldms_client installed and distributed
  • Some reports that use extended data
  • Sample output
  • Future Features being worked and/or evaluated

Features in LDMS_Client:

  • Change Collect PST files to collect any file or file extension, configurable in the ldms_client.ini Thanks to Ryan Cheesman
  • Added the collection of Windows Scheduler Tasks  Thanks to Rob Fry
  • Auto update ldms_client.exe and ldms_client.ini  from the core’s LDLogon directory if newer than local copy
  • Added a /configini option to the command line of LDMS_Client that runs after install to setup the collection of the .dat file correctly for x86 and x64 Operating Systems automatically
  • Computer’s FQDN
  • Uninstall Strings from the Registry (32 and 64 bit) Thanks to Craig Greenfield
  • Detection if primary owner is a local administrator
  • Check to see if TPM chip is enabled (Windows 7 only)
  • Collect PST files
  • Collect HKCU specified registry keys
  • Mapped drives for the currently logged in user
  • User Profiles sizes
  • User’s Display Name in Active Directory
  • Collect Battery Information
  • Disk Fragmentation status
  • Logical to Physical Drive Information
  • Computer’s Management Gateway Status
  • Microsoft License Keys

Downloads

LDMS_Client 3.2.2

Installer: LDMS_Client-Setup 3.2.2

Just the client file: Just the client LDMS_Client_Install 3.2.2

Source Code: LDMS_Client-Source

Updates:

  • Changes to Produkey to fix the problem with first time downloading and executing it doesn’t create a file called Program1 on the root of the drive.

Pre 3.0.0 Version

This is the last version that Jack did in Perl.  It only supports version 8.8 of LANDesk Management Suite.  We’re leaving it up here in case someone still wants to use the Mac version of this code or if they want to develop on the Perl code based.  If you’re looking for the source to the Perl code please email us at irishmn76@droppedpackets.org.

Server installation file:  LDMS_Client-Setup

Client installation package: Just the client ldms_client

  1. fry_rob_g
    March 11th, 2011 at 00:59 | #1

    Denny! Congrats on your kid! Long time again man. Glad to see you updated DroppedPackets… looks great.

    So, I’m currently working on a project which is requiring me to use the Windows Scheduler on Landesk managed computers because the Landesk scheduler is… well… ancient. Because of this I’m now also needing to inventory Windows Scheduled tasks. Interestingly enough a friend of mine turned me onto AutoIt. There was already some code on their site for win2k3 & xp which I’ve update and now works for win2k through win2k8 r2 systems. However, on vista and above the total # of Windows Scheduled tasks is quite large, so I’m wanting to model the data instead of using custom. And this is where I’m running into issues with the one-to-many relationship.

    Now my questions… first, can/should this be in ldms_client, or does it exist somewhere else already? I looked all over the place because I didn’t want to reinvent the wheel. If not… would you like to work together to make it so? Second, is there a super duper secret way to get the custom one-to-many data in the DB?

    –thanks and I look forward to hearing from you again.

  2. mferro
    March 11th, 2011 at 04:30 | #2

    Hi Denny
    Does this work in Windows 7 64bit?… i was able to install it on the core and distribute to a win7 client. but when the inventory run i get an error: Unable to launch custom inventory application C:\Program Files (x86)\LANDesk\LDClient\LDMS_CLIENT.EXE
    the ldms_client.exe is definitely present ..
    thanks

    • denny
      March 11th, 2011 at 15:10 | #3

      Yes it does, but we have to add a section to the ldscnhlp.ini. I’ll email you the updated ini file so it works on Win 7 64-bit.

  3. mich
    March 16th, 2011 at 14:37 | #4

    I tried the latest version 3.1.2 Beta and ran into a serious issue with German 64-bit Windows.
    Seems like some path is not correct in ldms_client because after a restart it creates a file “Program” without extension in c:\
    This file causes serious trouble because if it exists many applications simply freeze or refuse to start. (Like ldms_client, AutoCad 2009, …)
    If you delete the file, it reappears after the next restart.
    When I uninstall ldms_client, the file stops to reappear.
    Could you please look into this?

    Thanks a lot for all the work you have done and still do for us LanDesk admins.

    • denny
      March 16th, 2011 at 14:59 | #5

      Thanks for the feedback and yes I’ll start looking into that right away. I don’t have a German 64-bit version, so can you tell me where the landesk\ldclient folder is located on a German OS?

      thanks,
      Denny

  4. mich
    March 16th, 2011 at 15:21 | #6

    @denny
    That’s the weird thing.
    The Folder would be “C:\Programme (x86)\LANDesk\LDClient”
    but it is also accessible with
    “C:\Program Files (x86)”
    or
    %ProgramFiles(x86)%
    because Win7 virtualises these directories for different languages.
    So I don’t really understand why it seems to work for others, but not for me.

    • denny
      March 17th, 2011 at 16:51 | #7

      Interesting. In the code I’m calling EnvGet(“ProgramFiles(x86)”) for 64-bit OS, so I’m wondering why that’s not being resolved? I’m continuing to work on 3.1.3 which I hope to have out soon. I’ll see if I can’t make a few more safety checks to ensure I don’t do that.

  5. mich
    March 18th, 2011 at 08:09 | #8

    @denny
    Hmm.
    I just installed the 3.1.3 on the core and created a new package with the 3.1.3 client.
    I rolled out the client to one of the “problem”x64-machines.
    After the rollout I restarted the client and started an inventory scan.
    This is what I got:
    —————————
    Inventory Scanner
    —————————
    Unable to launch custom inventory application C:\PROGRAM FILES\LANDESK\LDCLIENT\LDMS_CLIENT.EXE.
    —————————
    OK
    —————————

    The “Program” file is not there yet.

  6. rbeck
    May 6th, 2011 at 20:14 | #9

    @denny

    I have 3.2.1 installed and I’m running into the same issue with the “c:\Program” file, except mine is appearing on 32-bit Windows 7 and 32-bit Windows XP systems. It appears to be related to Produkey because the “c:\Program” file contains product key info.

    Let me know if you need me to provide any additional info.

  7. jabramson
    May 17th, 2011 at 14:16 | #10

    I am testing the 3.2.2 version and it seems to going well but for one part. When execfindfile is enabled I am getting an error. Line 9527 (File”c:\program files\landesk\ldclient\ldms_client.exe”); Error: Subscript used with non-array variable.

    What is good about this version is I am no longer seeing the ldms issue on my windows7 64 bit devices any longer.

    I don’t know if this is possible with what you are developing but is it possible to add a location awareness based on preferred servers. It would be a nice enhancement to the inventory if it could report the preferred server that is used. Perhaps either by reading the preferredserver.dat file and reporting the server name or comparing the system IP and reporting the server name and details that is listed in the preferred server target list.

    Thanks for all your great work on this.

  8. SGillis2
    May 31st, 2011 at 19:06 | #11

    A great set of tools/info but I have a quick question for anyone that may be able to help…

    I’ve successfully installed the Core portion as well as a handful or so on client machines to test and everything seemed to install without issues. What I am running into however, is that I have to go into Configure-Services-Inventory Tab-Unknown Items and ‘Allow’ every entry for ‘LDMS_Client’ that I’m looking for. We have a need to find the size of the pst’s on our machines but with 3000+ PCs, and then several different profiles and the possibility of more than one pst per profile, this could become quite time consuming. I would also love to eventually get into the other categories that are included at some point.

    Is there an easy way to ‘Allow’ the entries without having to go one-by-one????

    Thank you in advance!!
    Scott

    • denny
      May 31st, 2011 at 20:23 | #12

      The only way to get around that problem is either turn off the database schema protection, or to model the data before hand. Here’s a document on how to model the data:

  9. SGillis2
    June 2nd, 2011 at 11:29 | #13

    @denny
    Thanks for the reply, Denny. I was somewhat afraid of that! :)

    I didn’t see a document or link on your reply, can you post again by chance?

    Thanks again!
    Scott

  10. ShafiqulHaque
    August 7th, 2011 at 16:42 | #15

    Hello!

    I posted some comments on the ldms_client collection page a few days ago, and see that some of my questions are answered here.

    The other observations are still unanswered. Would one of you experts please reply to let us know if there are solutions to some of the observed issues.

    Anyway, how do I send my small modifications to the code for your review?

    Thanks and regards,
    Shafiqul

  11. aaron.dilapi
    August 11th, 2011 at 20:56 | #16

    I would like to be able to use this, however the client is not installing correctly on 64-bit systems I’ve tested it with. ldms_client.exe is being put into the LANDesk Agent folder which is under Program Files (x86) but the LDSCNHLP.INI file that is being created references this path:

    LAUNCH1=C:\PROGRAM FILES\LANDESK\LDCLIENT\LDMS_CLIENT.EXE

    Is this something that needs to be fixed in the setup and/or is there a way to make sure that ldms_client is deployed correctly to machines regardless of the version and architecture of Windows?

  12. aaron.dilapi
    August 11th, 2011 at 21:05 | #17

    @aaron.dilapi

    I tried modifying the paths in the LDSCNHLP.INI to use Program Files (x86) but now I’m receiving this error when kicking off a scan:

    AutoIt Error
    Line 9385 (File “C:\Program Files (x86)\LANDesk\LDClient\ldms_client.exe”):

    Error: Variable used without being declared.

    Other comments:

    Although I installed 3.2.2 (according to this website although I can’t find version information anywhere in the install or config utility) the Distribution Package that was created says 3.2.1 in the description.

    On the Hardware tab of the Configure LDMS_Client utility “Fragmentation” is misspelled.

    • denny
      August 12th, 2011 at 17:01 | #18

      Have you tried running the ldms_client.exe /config on the machine to get all of that fixed?

  13. aaron.dilapi
    August 12th, 2011 at 19:15 | #19

    I just tried running the suggested command… I’m not sure what it is supposed to do but it pops up the same AutoIt error regarding Line 9385 that I quoted above.

    I was under the impression that since the LANDesk deployment task that was automatically created by LDMS_Client was used to push this out that it would “just work”. Are further steps needed? I believe I correctly followed all of the steps in the installation instructions for LDMS_Client.

  14. denny
    August 15th, 2011 at 16:58 | #20

    Can you please email me a zipped copy of your ldms_client.ini, ldms_client.log, and ldscnhlp.ini file so I can figure out what’s happening? Thanks, Denny@aaron.dilapi

  15. Haefele
    August 23rd, 2011 at 11:00 | #21

    Hi, I get an error Line 10243 (File “C:\Program Files(x86)\Landesk\LDClient\ldms_client.exe”): Error: Variable used without being declared.

    Could you tell me what this could be?

  16. malco
    October 6th, 2011 at 09:37 | #22

    Hi, a couple of years back I was working on Power Management and remember the LDMS_Client being able to inventory Dell bios settings for WOL. I don;t see it as a feature anymore, has it been deprecated or is it still possible?

  17. GuptaM
    October 10th, 2011 at 09:10 | #23

    I am also receiving the following error:
    AutoIt Error
    Line 9385 (File “C:\Program Files (x86)\LANDesk\LDClient\ldms_client.exe”):

    Error: Variable used without being declared.

    Any solutions?

  18. thogland
    October 10th, 2011 at 19:40 | #24

    @denny
    I get this line 9385 error when trying to install to Server 2008R2 64bit. It apparently installs itself into the scanner, but fails to do whatever magic follows, so inventory scans now give this error as well. It also put ‘program files’ instead of ‘program files (x86) into ldscnhlp.ini… Running as myself or as administrator makes no difference, as does correcting ldscnhlp.ini.

    Works fine on Win7/64, but not SVR2008R2 x64.

  19. thogland
    November 16th, 2011 at 19:13 | #25

    …And now I’m getting the exact same error when trying to install it on a Windows Server 2003 R2 32bit system. Tried interactively and with the silent command line created by the config program.

    Has there been ANY progress on why this ‘unknown variable’ error randomly occurs?

    • denny
      November 17th, 2011 at 15:07 | #26

      I haven’t done any testing on 2003, just 2008. I am having problems re-producing the error, so I haven’t been able to make any progress on it. Is it not creating a ldms_client.log file or anything?

  1. February 19th, 2011 at 10:57 | #1
  2. September 9th, 2014 at 12:08 | #2
  3. September 10th, 2014 at 03:08 | #3
You must be logged in to post a comment.