What is the point of not being able to scope actions based on "latest version" smart group?

lopatoid
New Contributor

I mean, there is definitely not a technical limitation, but an artificial one. One can still make another smart group that includes the "latest version" smart group within it, and be able to scope actions based on it.

lopatoid_1-1718225446463.pnglopatoid_0-1718225403591.png

 

2 REPLIES 2

david2658
New Contributor

Hello,

Not being able to scope actions based on the "latest version" smart group can limit flexibility and control in managing software updates. This restriction means you can't automatically apply actions to devices with the latest software versions, potentially complicating maintenance and updates. It forces administrators to manually identify and manage devices with the latest versions, which can be time-consuming and error-prone.

AJPinto
Honored Contributor II

Being literal, arn't all technical limitations artificial limitations? It's not like you are trying to jump to the moon and that is physically impossible. Jamf has other limitations on policies to prevent techs from screwing stuff up, like ongoing+recurring check-in. Jamf is simply trying to put an extra barrier between you and jacking up something with a deployment.