Allow the use of label groups for deployment and ACLs
Label groups cannot currently be used for anything other than organizing multiple labels. I would like the ability to utilize label groups for deployments and setting ACLs more easily.
Thank you for your UserVoice suggestion. This request has aged without many votes, so we are going to close it and free up your votes. If you still feel that it should be reconsidered, please feel create a new UserVoice request. Thank you again for your contribution!
Having the ability to add a label group to deployments would be fantastic. That way it would be possible to organise labels into groups, as we already can, and then rather than having to add all separate labels to the deployment of a script just add the label group that contains all the required labels.
Craig Johnson commented
I find the Lab Groups lacking. If I can assign label groups to computers then I can nest various labels into a group and add the group(s) to a computer instead of adding tons of labels to a machine.
Just a quick heads up. If you assign each machine a user (add a user field to the asset and voila) you could control your scripted installs to specific users assigned to the machines by calling vbs files that instigate an sql query and query to ensure that the current user is the one that is set to it.
For instance, we use this method to, during imaging, set the local admin user to the assigned user, and on certain scripts to only (even though they can see them) run if the user fields match. Might help you work a solution for now.
We have 6 primary label groups. Inside those label groups are IP and Hostname based labels for computers. I need to be able to assign ACLs to those groups to prevent the wrong folks monkying with machines that aren't theirs and potentially deploying things to those groups instead of adding each label individually.