Create label groups for scripting & deployment purposes, not just organizational purposes
While there is an ability to create group labels in the K1000, these serve little purpose other than organizational purposes because the group label cannot be applied to a script which makes it basically useless. I would like the ability to create a group and then use that group however I want, just like any other label. Example: Deploy Script A to Building Z instead of manually selecting each label for Accounting, HR, Admin, etc.
You can make a smart label like:
Label Names = Label01 Or
Label Nems = Label02
Ernesto Lopez commented
Are there any updates on this request? this idea would prove very useful if implemented.
Stumbled upon this page while searching for the seemingly obvious bug as to why I couldn’t apply my scripts to a master label group that i had just created. We have around 800 computers across 51 departments. Each dept has a smart label, each with certain exclusions associated with that label. One mast label was created that included all 51 dept labels. The goal is to deploy a script to all 51 depts excluding the exclusions specified in said dept labels, "Without" having to add each one of the 51 dept labels to the script deployment. The goal is to be able to open the script and deploy it to "Master label group x" instead, which would achieve the same without the extra 102 clicks per script. To clarify the annoyance with this inability to assign scripts/ deployments to label groups, we have over 50 scripts this would apply to with more being added weekly. So that’s over 5000 unnecessary clicks.
Mark Buddemeyer commented
I think what the requester is saying is that he would like to be able to use lable groups for deployment instead of just for organization.
Let's say I manage a school district with 30 sites. I have a LDAP smart labels for the Staff Desktops, Student Desktops, Staff Laptops and Student Laptops for each site. So right away that's 120 lables.
What would be nice would be the ability to create 4 label groups (StaffDesktop, StudentLaptop, etc) to deploy things district wide without having to add 30 lables to a MI or Script.
The bottom line is that when you create a label group from the label management tab, choose action, new label group, the label which you just created cannot be used for any scripts or deployments. That is very frustrating because it would make it a lot easier if you could apply that newly created group to scripts. I understand that you can do smart labels but it seems to be the long way around instead of a straightforward group which can be utilized. As best I can tell, the label groups serve only for organizational purposes and cannot be leveraged for anything else.
Chris, I'm not sure I understand the request here.
You can create static and smart labels based on many criteria, including location, network, form factor, etc. These labels are supported within the scripting module to define scope of script deployment to the desired machines.
Can you provide a specific use case that you require?