/build/static/layout/Breadcrumb_cap_w.png

K1000: Find a set of installed fonts on mac os x with customized inventory

I'm trying to set up a custom inventory Rule which identifies the machines that are using the companies own fonts. 
No Problem on Windows but i can't seem to figure out the right way on Mac OS clients. 
I've created a custom inventory rule in the Software-Library which get's pulled every time an agent connects to the K1000.
But my Shellcommands, which return the wanted data on if you try the in the terminal, don't return anything. 

ShellCommandTextReturn(find /Users -iname "fontname*" | grep -i ".ttf")

ShellCommandTextReturn(find /Users/*/Library/Fonts/ -iname "fontname*")

I use the wildcard in the fontname because we've got about 20 different Fonts. Maybe the K1000 Agent does not support them?

Anybody has got an idea how to check for this properly?

Best
André

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: jknox 10 years ago
Red Belt
2
Not sure why that wouldn't work, you might open a support ticket for it.

As an alternative, you could try using a kscript that runs your command and outputs to a file, then use a custom inventory rule to read the output file.

find /Users/*/Library/Fonts/ -iname "fontname*"
kscript:  find /Users/*/LIbrary/Fonts/ -iname "fontname*"  > /your/data/location/fonts.txt

Then, for the CIR, use something like: ShellCommandTextReturn(cat /your/data/location/fonts.txt)
/your/data/location/fonts.txt
find /Users/*/Library/Fonts/ -iname "fontname*"

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ