![]() In a nutshell, it gathers policy and profile information from the Jamf database and then pulls down individual computer records and presents that information in a condensed, easy to digest format. ![]() The idea behind Cargo Ship was an offhand remark about how cool it would be if we could quickly see what policies and groups a computer belonged to. We’re excited to see what other teams are able build! Cargo Ship Both tools share a large percentage of code, feel free to mix and match with your code. Included on the project page are additional code snippets for interacting with various databases. We’ve trimmed out the sections that are specific to the Marriott and provided them as a framework for others to add in functionality unique to their needs. 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. When included as an extension attribute string a smart group can be created with matching (is, is not, regex, etc.) criteria to target Macs as needed.You don’t need a bigger boat, you need custom tools. Login_mechs_authdb.py - Return a list of all authorization mechanisms.įor example, default macOS mechanisms are returned like below. Nomadlogin_mechs.py - Return a list of NoMAD Login and Jamf Connect authorization mechanisms used during macOS login window authentication process. To help in those situations (and probably others) I’ve written two Jamf Pro extension attributes. It’s also been observed by a few people that authorization mechanisms can be reset back to defaults after a major OS upgrade - High Sierra to Mojave for example. If not then a quick authchanger -reset can get the system back to a healthy state. It may also be useful to know if authorization mechanisms were set back to defaults after using NoMAD Login or Jamf Connect in your deployment workflow. Otherwise NoMAD Login or Jamf Connect may not run with the desired mechanisms or at all. In those cases it may be useful to report on authorization mechanisms to ensure they’re set correctly. There are plenty of other use cases though where NoMAD Login is used as a persistent login window replacement. From then on out users would use the stock macOS login window they’re used to. My previous posts about NoMAD Login + Jamf Pro deployment workflows assumed that once a local account is provisioned NoMAD Login will be uninstalled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |