More info about my extension attributes can be found HERE. This allows me to monitor progress in the Jamf Pro Dashboard… As root does not / should not have a SecureToken, it does not impact my testing in any way. Those EA’s run from the Jamf Binary during inventory updates within the root context. Hence the use of the extension attributes to grab the status of the system. Without knowing the exact behaviour in macOS Big Sur at the start of my testing, this could potentially corrupt my findings. This is very important, because logging in with any local admin account on a token-less macOS Catalina system, generated a SecureToken for that account. I’m using extension attributes in Jamf Pro to check the SecureToken holder, the Bootstrap token, FileVault status, etc… This to avoid having to login with any account when it’s not a part of my test. As things look really good, I don’t expect any changes in the official public release. Reason for this is that I want this post to go out the moment Apple pushes the public availability of macOS Big Sur.
Jamf Pro policies to create additional accounts, bind my Mac, etc…Īs you can see above, I’m testing on the Release Candidate 2.
Extension attributes to report SecureToken, Bootstrap and FileVault. Instead I’m going to focus on pure statements and work my way towards a new flowchart! Now the wait is over, and I must say I’m really happy with the changes which macOS Big Sur brings regarding FileVault! Things really got a lot less complicated to understand! Let’s have a look!įor those who are new to FileVault, I would still suggest to review my macOS Catalina flowchart in order to fully appreciate the changes which macOS Big Sur brings.įor this post I’m going to try to keep things as simple as possible, meaning that I’m not going to share screenshots of each test and command line validation of my findings. This to avoid wrong assumptions caused by unexpected behavior native to beta versions and / or incompatible Jamf Pro versions. Here we are! A new major macOS has been released so there is no escaping from checking what macOS Big Sur brings us in view of FileVault, SecureToken and Bootstrap!Īpart from doing a few spot checks when I heard about some rumored changes during the beta period, I deliberately postponed doing a full test until the release candidate was ready. I'll verify everything once again when full public Apple documentation is available. Please not that all my findings are based on previous understanding of FileVault in macOS Catalina and testing in Big Sur. I have been testing with 10.24.2 and 10.25.1įurthermore: The change regarding the creation of the Jamf Management Account discussed below is something I'm adding in this post as it may also impact edge case manual manipulations on a token-less macOS Catalina. Hi all! DISCLAIMER: Please wait for the official communication from Jamf regarding the Big Sur compatible Jamf Pro version.
0 kommentar(er)
