Best practices and approach when using Kbox breadcrumbs w/ custom inventory rules to deploy software packages?
I have been using breadcrumbs and Custom inventory rule in conjunction with smart labels to deploy software after the image drops and checks into the Kbox. The actual post imaging software deployment process works very well, the problem is almost too well. What I didn’t properly consider when mapping out this software deployment method was how to handle when software packages need/get updated or if they need to be uninstalled from the image. If the software version changes due to an update/patch/uninstall eventually the machine will check back and since it still has the registry key that is used to match on the custom inventory rule the initial software packages will try to reinstall again.
One example of this is when Adobe Reader 10.1.4 gets installed using breadcrumbs/smart label post installation. Then when patching runs and updates it’s to 10.1.7. Since the version # changed for Adobe Reader package it then tries to reinstall the version 10.1.4 again. I did come up with a workaround for this package so that this doesn’t happen.
Really curious to see how others have addressed this matter when using bread crumbs and custom inventory rules? I have thought of using script to delete the intial deployment registry key value that I used for the custom inventory to match on playing with the Smart labels to only look for a specific version of the software, or trying to find a way to have the custom inventory rule only run once. Any insight that anyone could share with me on how you’re using Breadcrumbs and custom inventory when it comes to updates and uninstalls would be greatly appreciated.