Managed Installations via labels
I need to push a managed installation to a majority, but not all, of the assets in my KACE inventory. There are too many to search for one at a time to select, so I thought using the label attribute to make it easier. I dont see a way to easily apply a label to a large amount of assets at once. I was imaging something like a csv template upload, or atleast a type of syntax I could use in a text box to list all the Inventory assets I want to include in the label(something like asset1; asset2;etc).
With that being said, is labels even the right solution for this problem? I am open to all suggestions.
The issue is as follows: A software which is installed on many machines needs to be uninstalled and a new software needs to be installed. So the best practices is: 1. create a smart label with the machines who have this software installed (an example is seen here. https://support.quest.com/kb/4276707 ) 2. link the Uninstallation of the old software and the installation of the new one to this smart label 3. enjoy the full automation
I would use SMART Labels.
These are SQL queries against special features of the devices.
As an example, many people have smart labels of machines in a special location, if a specialsoftware is installed or not or similar.
If you find similarities between the machines you want to target, create a Smart label for that and target the MI to these labels you want.
This is Best Practices.
As Nico says labels is the way to go, as they underpin all KACE functionality. If you don’t need to push to all machines what is your criteria? What is it that defines a device that doesn’t need the software.
Build a smartlabel for that and then build a second smart label that includes all devices that are NOT in the first smart label.
Basically you just need to give a bit of thought of what you are taelrgettignand build the labels
Criteria is random. There is an application that is used by roughly 75% of all end users and I need to uninstall that software and replace with another. There is no location information that I could use to associate with a label as every department, location, OU, etc. has at least 1, but not all end users using this software. They are manually given access by another team who manages the user accounts for that software. If AD groups could be used (and we do have LDAP setup so it should be able to read AD), then I think we have an AD group set up with all of the users for notifications for that software. That would be targeting the users though, and not the machines themselves.