Lines 17-22 begin with the hash or pound (#) symbol. You may want to ask before republishing too. Give the original author attribution in your script if you publish it. It’s OK to remove this information unless republishing the script in whole or in part somewhere else. That function isn’t needed since the script won’t be interactive. They’re referenced elsewhere in the script in a function named “ShowUsage”. Lines 4-5 give the name and version of the script. Let’s start at the beginning and pare this down to what’s needed. They’re useful not only for Paul when he’s reviewing his code but admins who are stealing and adapting his code. ![]() Many of those lines are just whitespace for readability. This EA will run during inventory and return license information back to the Jamf Software Server (JSS).Īfter downloading and opening the script, scroll to the bottom and note it has 264 lines of code. Let’s adapt it to work with Jamf as an extension attribute (EA). Paul has made Unlicense available for everyone on GitHub, but it requires interaction and only detects licensing for the current user. They need a tool to help with the transition. He wrote Unlicense because organizations are transitioning to Office 365 licenses to enable additional features not included with volume licenses. Its purpose is to detect whether a Mac is using a volume or Office 365 license and, optionally, remove the license to change to the other. He interacts with Mac admins in the #microsoft-office channel on Slack and has posted several scripts for managing Office. Paul Bowden with Microsoft is a developer for Office for Mac. But many can easily solve 95 percent of someone else’s need with a little adaptation. That’s because they’re written to solve a very specific need. Scripts are very personal to the administrator writing them. Those who write scripts and even script snippets expect their work to be stolen. The idea behind sites like GitHub, Stack Overflow and Jamf Nation is that as people collaborate, a much larger group benefits from observing their exchange of knowledge. ![]() That’s OK! The culture of scripters is one of sharing and teaching. Most scripters begin without knowing they’ve started. But knowing just a handful of Terminal commands and how to string them together will take an administrator’s effectiveness with Jamf from a 2 to a 10 - 11 if you’re into Spinal Tap. Most of it is GUI-based, drag and drop, or pick and choose. Jamf Pro doesn’t require administrators to know a scripting language before they use it. As I speak with new customers, one of the first questions I ask is, “Are you a scripter?” Often, the answer is “no”, even when I’m meeting with several Mac admins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |