Some configuration profile payloads and settings available in Jamf Pro may differ from their implementation in Apple’s tools. For more information, see the following Apple documentation: You can use Jamf Pro to create a configuration profile or you can upload a configuration profile that was created using third-party software, for example, Apple's Profile Manager or Apple Configurator.īefore creating a configuration profile, you should have basic knowledge of configuration profile payloads and settings.
mobileconfig) that provide an easy way to define settings and restrictions for devices, computers, and users. Worst case scenario is the device will need to be backed up, wiped and OS re-installed to go through provisioning again.Configuration profiles are XML files (. Or if you want to look at devices in a one-off situation, you can tell which secure token & volume owner users and their admin status. Once you’ve got these extension attributes scripts running in your Jamf environment, you can then start to run reports against computers that do not have secure token users and/or volume owner users and take steps to remediate. If an unsupported architecture, the result will be: If no user is found to have be a volume owner, the result will be: If a user is found to be a volume owner, the results will be displayed as: The Volume Owner Users extension attribute will report all Volume Owners on Apple Silicon Macs. Unsupported File System: (File System Type).If an unsupported file system is found, the result will be: If no user is found to have a secure token, the result will be: Non-Admins: user1, user2 (or “None” if none found).Admins: user1, user2 (or “None” if none found).If a user is found to have a secure token, the results will be displayed as: The Secure Token Users extension attribute will report all user accounts who have a secure token. I created two extension attributes to track Secure Token users and Volume Owner users a while ago but never wrote a blog post to cover them. Needless to say, it’s useful to track this information in Jamf Pro. Ideally, you don’t have any Macs like this in your environment. If you’re running newer versions of macOS, Apple has tried to close all gaps where a managed device might be configured without a secure token or volume owner user. Whether a user is an administrator or not, can also determine whether there are certain tasks that can be performed.Īpple goes into better detail in this enterprise focused deployment guide over the concepts of Secure Tokens, Volume Ownership and Bootstrap Token.
If there are no users who have volume ownership, you may find yourself unable to perform OS updates. This can happen in at least two important scenarios that come to mind: OS upgrades and OS updates. Most recently, with Macs running on Apple silicon, Apple introduced the concept of volume ownership which determines which users are authorized to make changes to the volume. If there are no users who have a secure token, you may find yourself in a position where you cannot enable FileVault or unlock FileVault. With the introduction of APFS, Apple introduced secure tokens which allow users to unlock FileVault.
0 kommentar(er)
