In my environment I have some smaller clinics that have the Kace agent on them. These machines are not managed by me, but do have the Kace agent for inventory/auditing purposes.

Since I really do not know what all is in these clinics a solution we came up with was to mark the machines using a custom inventory rule to identify them. For PCs I provide a reg key that those clinic techs include in their image. For the Macs I have a plist file. I then take that data and generate reports that are sent to those techs monthly so they know what's on their machines. Both the reg and the plist include the same four digit number for both, and I reference that in the report.


RegistryValueReturn(HKEY_LOCAL_MACHINE\SYSTEM\Department, Dept, TEXT)


PlistValueReturn(/Library/Application Support/Dell/KACE/department-info.plist, Department, TEXT)

Since Kace now supports more flavors of Linux I was asked how to go about marking those Linux machines with a department ID. I'm looking for something I can include this same four digit number on Linux machines to add to these reports. I'm thinking of using FileInfoReturn(), but not sure if this is the best option? 

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



You can use FileInfoReturn() or ShellCommandTextReturn(). I would put your file somewhere out of the way (maybe /etc), and put your 4 digit department number in the file. Using the ShellCommandTextReturn() you could then pull the number out of the file. Or using the FileInfoReturn() you could pull back the name of the file (if you create an empty file and use the 4 digit number as the name).

Answered 06/25/2013 by: erik.ragan
Senior Yellow Belt

  • That sounds good. I'm assuming it would be something like FileInfoReturn(/etc/Kace, name, TEXT)?

    Also since I no almost nothing about Linux OSs, the /etc should be standard across the board? We have almost every version depending on the clinic. If I create it for when it should work for all?
Please log in to comment