Static groups for software install?

[pandrum]

We have some software that we want users specifically request by calling/mailing our helpdesk, and then our helpdesk can assign the software to the users computer. Is static groups the best route for this?

For example a user wants SPSS 24. Sends a ticket to helpdesk, they log in and assign the computer to a static group called Install SPSS 24 that is scoped to a policy that installs SPSS 24. Any caveat with this or would you rather just add the computer directly to the policy instead?

[SeanA · Accepted solution]

It would be easier, and more manageable, if the help desk would assign the software to a static group. Especially if you need the static group scoping again for some reason (for example, you need to clone it and change all the <is> to <is not> to find all the targets that have not been assigned SPSS 24).

Plus, with access to only a static group--as opposed to the entire policy--it would be safer (depending upon how you have your JSS user/group permissions set).