K1000 Custom Inventory field

I'm wanting to use the custom fields in the K1000 to detect systems that have office installed but do not have outlook installed. I've used the Fileexists syntax very successfully to detect who uses office but is there a way to add file does not exist?


1 Comment   [ + ] Show comment
  • I'm using the CIR to detect the software and I've added the software installation media to that software application. We are going to have 2 different install media's. One that installs office with outlook and one that doesn't. I was going to modify the CIR to separate those 2 different installations. I can use the smart label to identify systems without outlook but that won't solve the issue of 2 different installers. Any suggestions? - ckubaska 3 years ago

Answers (2)

Posted by: airwolf 3 years ago
Red Belt
Custom Inventory Rules are designed to detect the existence of something (typically a software application).

The best practice approach is to use your CIR to detect the existence of the software, as you are doing now. Then, create a Smart Label to find the systems that do not have that object installed. Note: Smart Labels for devices are evaluated at inventory upload, so it may take a full inventory cycle after you create a Smart Label for the contents of that Smart Label to be completely accurate.
Posted by: n1md4 3 years ago
Second Degree Blue Belt
If you're on K1000 7.x
go to Software Catalog and upload your Installation to Microsoft Office 2013/2016 (whatever you have)
Then add the second installation media without outlook in the very same Software Catalog item (you can add notes!)

In Managed installations create 2 seperate MI based on Software Catalog (not inventory as in the past) one with outlook and one without outlook

Now you have your CIR Smart Labels as the desired targets for the seperate MI you just created.

This also adds up easy to Software Catalog Compliance and also license compliance. And if the installations are patched on clients you just haveĀ one software inventory item. And no fuzz if you have two software items and your installations got patched and then the MI with old version wants to install again because your custom software item with persistent software version does not match anymore and kace thinks it must redeploy the software.

another thing using the Software Catalog is, you don't have to enable every Windows 10 Build in your software item to get deployment going. if you deploy to Mac, it's a nightmare. Every few months you have to get through all software items to catch up the new builds. Sadly Software Catalog is not working for Mac Software

Don't be a Stranger!

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

Sign up! or login


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