I’m well aware that there’s a big “old dog/new tricks” aspect to my reticence to move away from configuration profiles to blueprints, but my primary hangup with even exploring Blueprints too much is the limited scoping capabilities. In particular, I find it really useful with a configuration profile to just be able to exclude a single computer from the scope to remove it for testing or other reasons. But with Blueprints being entirely smart group dependent, the only way I know of to do that would be to modify the smart group to not include a computer name, or maybe link the smart group to a static group, but that feels janky. Help me think through this please.
Talk Me Into Using Blueprints...
+17
+36I can’t comment on future releases (don’t want to promise something I can’t), but it’s fair to say blueprints is still evolving. Configuration profiles shouldn’t go away until blueprints can replace all the payloads.
I’ll include scoping in that too.
I would suggest using blueprints as much as possible, because they are the way forward (i.e. declarative management is Apple’s way forward).
It might not work for everyone, but you can create a static computer group for exceptions and add that to your smart group as a criterion. Instead of adjusting the scope of your blueprint, you’d be adjusting the static group.
+17Thanks,
+36I should add, if you live near one of the U.S. cities where we’re hosting a Jamf Nation Live roadshow over the next few weeks, be sure to attend. This will be an opportunity to get a glimpse of some things to come.
+17
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.