11/9/2023 0 Comments Jamf extension attributes github![]() Or ensure you’re able to remote into a computer. Doing this allows you to easily check if SSH is enabled, and if it isn't, enable it. To take the power of extension attributes one step further, combine them with policies within Jamf Pro. To do this, create an extension attribute that gathers the amount of times a battery has cycled, and use that information in criteria of a smart group to automatically email you when the battery of a device is running low. One of the most useful parts of extension attributes is leveraging them for criteria in smart groups. You didn’t think I’d forget about scripts, did you? With scripts - many of which are readily available on Jamf Nation -you can find out when the last CrashPlan backup ran, whether or not SSH is enabled, or locate the serial number of a Thunderbolt display connected to a computer.Ĭreating powerful workflows with extension attributes For mobile devices, these attributes can be used as a variable in configuration profiles, which allow you to put the "Graduation Year" or other useful information on the lock screen of the device. You can even grab an LDAP attribute not mapped to the Jamf server by default - such as "Graduation Year" - for scoping purposes. You can also create a drop-down menu that designates a device as "out for repair," allowing you to exclude it from different workflows. You can create a field that allows admins to enter the "Retired Date" of a device so you can keep track of the devices that are no longer managed by your server. These can be in the form of a text field, drop-down menu, LDAP mapping or script.Įxtension attributes can be used in many powerful ways. So how do you do it? Extension attributes are an excellent place to start.Īn extension attribute allows you to collect extra inventory from your computers or mobile devices. A build notification is sent to Slack or can be set for email.IT is a world where more times than not, interactions with users go something like “I need help…” instead of “Everything is going great.” And when the former happens, it’s your job to be the problem solver. ![]() Scripts and Git2JSS live in a repo in GitHub, a webhook calls a Jenkins workflow that pulls down the repo and uploads the changes (or all) scripts and extension attributes to Jamf Pro. That’s where Git2JSS came in!Īt a high level, Git2JSS looks at the previous commit and the current commit for changes to scripts and extension attributes and uploads those changed resources to the Jamf Pro server using the REST API. Jenkins can 'build' the GitHub repo, but they needed something to look through the repo and send each item to the Jamf Pro server. ![]() Once implementing Jenkins, Schmidt and LaShomb then needed something to take their repository of scripts and get them into the Jamf Pro server. If the job didn’t build successfully (i.e., no new package created) then the DP Sync and Jira job would not run. It will then also create a story in Jira for testing the application. For instance, as LaShomb explained, Target’s AutoPKG workflow will run and if a package is created successfully, it will kick off a DP sync job that also resides in Jenkins. One of the great things about Jenkins is chaining jobs together based on success or fail criteria. Schmidt and LaShomb use Jenkins as their CI tool at Target. This is where GitHub, Jenkins and Git2JSS can help. Today’s session, led by Brad Schmidt and Brian LaShomb of fellow Minnesotan company Target, dove into a timely topic often on an IT administrator’s brain – getting their scripts under version control. ![]() There’s a lack of version control, lack of change approval and collaboration and review are manual. It can be difficult to manage code that lives in a web application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |