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?

Thanks
Cindy
1 Comment   [ + ] Show Comment

Comments

  • 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?
Please log in to comment

Community Chosen Answer

1
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.
Answered 10/19/2017 by: airwolf
Tenth Degree Black Belt

Please log in to comment

Answers

0
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
Answered 10/23/2017 by: n1md4
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share