Home > ldms_client > ldms_client collection

ldms_client collection

September 22nd, 2010 Leave a comment Go to comments

Item Does
ldms_client version Computer.”LDMS_Client”.”ldms_client.exe”.”version”
Battery Information Computer.”LDMS_Client”.”Battery”.”Manufacturer”
Computer.”LDMS_Client”.”Battery”.”Manufacture Date”
Computer.”LDMS_Client”.”Battery”.”Install Date”
Find Microsoft Outlook PST Files Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”File Location”
Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”File Size”
Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”File Name”
Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”Number”
Computer.”LDMS_Client”.”Custom Data”.”Email”.”PST Files”.”Total Disk Size”
Computer.”LDMS_Client”.”Custom Data”.”Email”.”PST Files”.”Number of PST Files”
LANDesk Client Information Computer.”LDMS_Client”.”LANDesk Management”.”Broker Configuration Mode”
Collect Microsoft Product Keys (requires produkey.exe) Computer.”LDMS_Client”.”Licenses”.”$product”.”product_id”
Collect Registry Keys from HKCU Computer.”LDMS_Client”.”Registry”.”HKey_Current_User”.”$key”.”$subkey”
Mapped Network Drives Computer.”LDMS_Client”.”Mapped Drives”.”$drive”.”RemotePath”
Disk fragmentation percentage Computer.”LDMS_Client”.”Defrag”.”Drive Letter$”.”$Driveletter”.”$Letter”
Computer.”LDMS_Client”.”Defrag”.”Drive Letter$”.”$Driveletter”.”Volume Size”.”$Size”
Computer.”LDMS_Client”.”Defrag”.”Drive Letter$”.”$Driveletter”.”Fragment Percentage”
Computer.”LDMS_Client”.”Defrag”.”Drive Letter$”.”Condition”.”Recommendation”
AD Display Name Computer.”LDMS_Client”.”User AD DisplayName”.”$displayname”
Profile Sizes Computer.”LDMS_Client”.”Profile Sizes”.”$username”.”$size”
Logical to Physical Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”DeviceID”.”$id”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Interface”.”$interface”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Partition Count”.”$count”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Total Disk Size”.”$size”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Partition”.”$DrivePart”.”Drive Letter”.”$letter”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Partition”.”$DrivePart”.”FreeSpace”.”$size”
Computer.”LDMS_Client”.”Hard Drives”.”$Physical#”.”Partition”.”$DrivePart”.”Partition Size”.”$size”
TPM Chip (Win 7 only) Computer.”LDMS_Client”.”TPM Chip”.”Exists”.”True/False”
Computer.”LDMS_Client”.”TPM Chip”.”Activated”.”$Activated”
Computer.”LDMS_Client”.”TPM Chip”.”Enabled”.”$enabled”
Computer.”LDMS_Client”.”TPM Chip”.”Owned”.”$owned”
Computer.”LDMS_Client”.”TPM Chip”.”ManufacturerID”.”$ID”
Computer.”LDMS_Client”.”TPM Chip”.”Manufacturer Version”.”$version”
Computer.”LDMS_Client”.”TPM Chip”.”Chipset Version”.”$version”
Computer FQDN Computer.”LDMS_Client”.”Computer FQDN”.”$FQDN”
Uninstall Strings Computer.”LDMS_Client”.”Registry”.”Uninstall Keys”.”$Key”.”$Value”
Categories: ldms_client Tags:
  1. ShafiqulHaque
    August 5th, 2011 at 10:20 | #1


    I need to scan for number of PST files and their total sizes on our computers, and this looks to be a very good solution. I have downloaded the v3.2.2 of the tool and have successfully pushed it to a few test computers.

    A few observations and challenges:
    – The collection structure shown above for PST files is different than what v3.2.2 is returning. Unlike Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”File Location”, as shown, it is returning Computer.”LDMS_Client”.”Email”.”*.pst”.”File Name”.”File Location”, which makes it very difficult to create and run any query! Plus, although v3.2.2 adds modified & created dates attributes, it does not post Computer.”LDMS_Client”.”Email”.”PST Files”.”$number”.”File Name” attribute anymore.

    Has anyone else observed the same, or I somehow have an incorrect version?

    I have taken an attempt to modify the source code to make the objects and attributes similar to the structure displayed, but I am wondering if anyone else may have already done so and have a well tested version.

    – Also, we are using LDMS 9.0 SP2, so when inventory data is sent to the core, it is not showing up in the computer inventory until “Unknown Items” are selected to ‘Allow’. The challenge is; several hundred such entries are expected from our computers, and having to ‘Allow’ one at a time can be very tedious, especially since the current interface does not allow Shift+Select bulk selection, and ‘Allow’!!

    In my assessment, data modeling may be the solution to do away with the need to manually allow all incoming inventories. Unless, of course, I uncheck the “Block Unknown Inventory Items” checkbox, which I believe may not be a good idea.

    Has anyone successfully updated the data model for this so that any objects and attributes under Computer.”LDMS_Client”.”Email”.”PST Files” will be allowed automatically?

    In addition, I discovered, if a PST file is named with a “ – ” (space-dash-space), then up to the “-“ (dash) it becomes an object and remaining part of the attribute is broken up and posted incorrectly as a (PST) file name attribute!

    Has anyone else also seen this, and may already have a solution?

    Thanks and regards,

  2. denny
    August 8th, 2011 at 14:35 | #2

    Shafiqul, you can submit the code updates to me via email at irishmn76@droppedpackets.org. You are correct that the count is now left out and that a – in the name would cause a problem. Those will have to be code changes to make it account for a – in the file name. Finally I would not uncheck the allow unknown inventory items. It’s better to create a new xml file and run coredbutil.exe pointing at the new xml to extend the database schema. Check this out for how to do the modeling: http://community.landesk.com/support/docs/DOC-2538#comment-5068

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