Need some clarification about how Kace handles linked Managed Installs, Custom Inventory Objects and Smart Labels
I am trying to simplify my Managed Installs, Scripts, Custom Inventory Objects and Labels. I wanted to get a little clarification on the order/process that Kace does Inventory, applying Labels, and checking software.
I have a number of software titles that I want to be able to control the installation of new major versions via Managed Install, but am fine with Kace deploying the patches between major versions. This is one use case for this, but I have many others.
My current implementation has become a bit out of hand and I am wanting to streamline it and clean it up, but I have some questions before I move forward. Currently, I create Custom Inventory Objects that target specific settings, configs, registry values, and a number of others and I then use a Smart Label to determine the Machines this gets deployed to. One issue I am encountering is the issue of Kace being a 32 bit client running on 64 bit machines. You have to make custom objects that just try to do too much with 32 vs 64 bit logic. I have a few pieces of software that just exploded in the number of custom inventory objects I needed to deploy it to all of the proper devices. When I look at my Custom items and realize I am nearing 20 custom items to properly manage all of the versions and different configs for a odd piece of software I came to the conclusion that this just is not sustainable.
I am thinking of moving to a model where I just select the very first version of a software. Adobe Reader might be Adobe Reader XI (11.0.0) as a quick example. I then create a very detailed and precise Smart Label that defines the exact devices that needs Adobe Reader XI version 11.0.0 to 11.99.99 or whatever the range is for that major version. This is a very simplified example and I know can be done relatively easy in a Custom Inventory Object, but I see many people not doing them right on the forums since they are not taking 32 bit on a 64 bit client into account. My real use cases are not nearly this easy and are for more than just targeting a major version of a software title.
If I move to this new method, after installation the software will not be registered as being installed since the version != 11.0.0. However, my label should properly remove that device as it will detect it as being installed. My question would be is when and in what order does Kace recheck these items? Will the Managed Install trigger the 2nd and 3rd attempts at installation before running a new inventory or will it run an inventory prior to retrying an install? I could always add a runkbot 4 0 to the end of my installation so I know a new inventory is ran immediately after the Software is installed. I am just not sure if this will work exactly how I expect it to.