![]() We’re making these tools ( Python source included) available here on GitHub. We feel it’s a useful debugging tool that can can show what should be present on a specific computer, if something seems to be missing. Cargo Ship is used to show how Jamf describes a specific machine, to show its printers, profiles, groups, etc. Tugboat has been designed to quickly on- and off-board machines, change ownership, update location and other inventory information. This can be quite daunting for new users, due to the enormous amount of information available there. The first of these tools: Cargo Ship and Tugboat use the Jamf Pro (referred to as Jamf for the rest of this article) API to drill into its depths and help our staff quickly perform tasks that would ordinarily require them to use the Jamf web interface. The repository will include the frameworks of custom applications we have written, Extension Attributes (EA’s) we’ve built to add functionality to our JAMF Pro and other scripts designed to automate tedious or time-consuming tasks. We’re calling the collection: SCL Jamf Tools. Continuing the tradition of building custom tools to enhance our existing environment, we’ve begun building creating a set of applications that allow us to quickly find and make changes to specific machines in the Jamf Pro database. We’ve supplemented our Radmind deployment with a rich set of utilities and scripts called Xhooks. Here at the Marriott Library we’re in the middle of our transition from Radmind to Jamf Pro as our macOS management system. You can see the complete code in github.You don’t need a bigger boat, you need custom tools. To make it easier to distribute this service I wrote an installer script that creates a launchd and a script. Please have a look on this article before you deploy API Credentials on local machines. ![]() Now I have created a new extension Attributes as a text field.įinally, we need a script that updates our extension attribute when it is called from launchd.Īfter the next erase, my extension attributes were updated and now I am able to monitor computers with this value. I created a new JAMF Pro user that only has the following rights: Since the erase process of macOS is processed very quickly, there is not enough time to execute a jamf policy and I had to switch to a somewhat dirty way. Now I was ready and could create a launchdaemon to monitor this file. I probably made the big breakthrough with a file that is created in the preboot volume shortly before the reboot. The application itself is located in the CoreServices folder: /System/Library/CoreServices/Erase\ Assistant.app/ First I analysed what happens on the file level and which processes are called. The idea is that I have a service (launchdaemon) that notices when I run the Erase Assistant and then updates a JAMF extension attribute I created. What can we do to ensure that an erase operation is logged in our client management system? The only question is whether we want to deactivate this helpful feature, especially when many users are in the home office. Of course, JAMF offers us a way to prevent this function. ![]() Apple has unfortunately failed to implement a kind of postflight action for this process.If the user bypasses the DEP process after the reset (offline enrolment), we would only notice this because our device does not deliver an inventory or a checkin. The disadvantage of this solution is that you as an administrator do not notice anything. Open System Preferences -> Click on “System Preferences” Similar to iOS, Mac users can now reset their Mac themselves in the system preferences. With the release of macOS Monterey, Apple has implemented a really helpful feature for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |