Working with Extension Attribute Templates

Nothing feels more satisfying than making your own Extension Attribute and having it work first try. But did you know Jamf Pro has templates ready for you?

a month ago   •   2 min read

By macstuff
Table of contents

Extension Attribute templates

You might know this or not, but Jamf builds in nifty extension attributes for you. Something that was already built for a customer,  that Jamf thinks is incredibly handy to go with the products or just something that is regularly asked for.

Head over to; "Settings > Computer Management > Extension Attributes > + New From Template". And be amazed by everything you didn't know you needed!


Warning about using it

DON'T OVERDO IT! I mean it! :D - If you want to slow down your database, know that the more you collect the bigger your database becomes. Think about implementing things like "Battery percentage" or "Battery Fully Charged" and think; when is the next time I'm really going to need this?

Think about your intentions in collecting this information. You've collected; "Jamf Protect - Last Check-in", great! Now what? Build a plan! Make something that you can use either daily or weekly. Build it with Smart Computer Groups and make an action when the device hasn't had its Jamf Protect check-in done for a couple of weeks or days. You can build remediation to automatically repair Jamf Protect if it's broken or send email notifications on membership change.

Point is, think about that plan before you start collecting things like "DNS Servers" or "Search Domains".


Testing

Even though these extension attributes were created by Jamf, that doesn't mean you can blindly implement these extension attributes and trust Jamf with all your heart. I know, temping to do this but remember, they're still scripts! Every script you put into your instance should be tested. Run it on your test device or your working device - all fine. As long as you don't push it out without testing it first!

Extension attributes run at each inventory update. This means that each time you run an update inventory after installing an app via a policy with maintenance configured it will run all those scripts on the device.

Remember, you're responsible for your own actions!


It's a short article but I figured it would be a good share! Loads of people ask me for extension attributes that Jamf has technically already build. Maybe I'll build some workflows to share based on these templates! :)


Something you want to see? Something you want to know? Email me at [email protected] and I’ll consider it!

Feedback about my site or content? Contact me at [email protected]

Spread the word

Keep reading