![]() ![]() ![]() So you could be waiting anything from almost 24 hours, to almost a week for this profiles to be deployed (depending on your configuration). Most Jamf Pro customers have their Jamf inventory submission (or “recons”) set to once per day, or once per week. ![]() These profiles could manage a variety of items including some to suppress and affect the user experience, and others that are required for security tools to operate. This meant the device would need to be updated / upgraded, then submit an inventory whenever the next trigger was hit before it received the profiles. Until very recently, Jamf Pro only used OS version data collected by their jamf agent for version comparison in smart groups. Rinse and repeat for any other OS-specific payloads. For example, to deploy a PrivacyPreferencesPolic圜ontrol payload to only macOS 10.14 or newer devices, I would set a target smart group that selected those devices. It seemed this was an issue with an easy answer: scope the deployment of OS-specific profiles to smart groups of devices that meet that OS. In this post, I’ll share a short script I used to achieve this with Jamf Pro. What was needed was something to flag and trigger the installs as soon as the device was updated. Mac Admins soon realised that if these settings were deployed on an OS that doesn’t support them, they’ll often not take affect if the device was updated until they were redeployed. Each of these had a minimum OS required for them to work. Over the years, Apple have released a number of new and helpful profile payloads such as PPPC, System Extensions and the like. Migrating macOS Devi… on Migrating macOS Devices from o…ĭazwallace on Moving devices from Adobe Shar… Richard Glaser on Changes to Docker Desktop for… Stephan Peterson on Submit Jamf inventory update o… Recommended workflow to deploy Adobe software with Jamf Proĭeploying Docker Des… on Changes to Docker Desktop for….Submit Jamf inventory update on OS changes.Speaking at London Apple Admins for Beginners.Re-homing your Mac Admin – MacAD.UK 2023.Use the Jamf Nation beta discussion area or contact Jamf via with any questions regarding the beta. Īs always, the beta program is operated under non-disclosure, so please do not share any information regarding your testing on any public forum, including the non-beta sections of Jamf Nation. Once you receive the invitation click on "Join this group Hub" to access the forum. There will be a short delay between enrollment and Jamf Nation beta forum access - you will receive a notification in Jamf Nation or via email to join the beta forum. Once you’re enrolled you’ll see a link to the Beta Forum. Please enroll in the Beta Program under Product Feedback at. How to join the beta: We’ve also made some changes to the Beta enrollment process with our new Jamf Nation platform. Make sure to join the beta and accept the email invitation to the forum to get access to the linked posts. We hope this will make it much more convenient for you to test and let us know what you think. We're excited to announce as of Jamf Pro 10.47.0 Beta 2 in addition to the Release Notes we'll be using Jamf Engage Guides to call out new features and enhancements directly in your Jamf Pro Beta Instance! You'll find links to Beta Forum posts in the guide for each feature we'd like special feedback on. ![]()
0 Comments
Leave a Reply. |