Failing here as well. I've heard that Jamf 10.21 is failing to download the jamf binary client during enrollment due to MDM client changes in Big Sur. The client download is rumored to be fixed in Jamf 10.22.
Luckily, upgrading an existing machine maintains the jamf binary and the machine remains managed.
I'm on 10.25.1 and it's working normally. I believe Big Sur was officially supported starting in version 10.25.
The problem I'm noticing is that the test client I have is being added as 10.16.0 instead of 11.0.1. Not sure if JAMF will update this so it will reflect the actual version name, but I rely heavily on smart groups for config profiles and policies related to 10.15 machines, 10.14 machines, etc.
Intel macs will be listed as 10.16, ARM macs will be version 11. This is intentional and has to do with how versioning works in macOS now. https://eclecticlight.co/2020/08/13/macos-version-numbering-isnt-so-simple/ https://www.jamf.com/jamf-nation/discussions/37295/big-sur-version-number
Hello, thanks for the post and the discussion around this. Sorry for the confusion.
Apple reports Big Sur in two different ways depending on if the binary checking the OS build was built on previous versions of Xcode or the newly released version of Xcode 12.
Starting with Jamf Pro 10.25.2, released today, the Jamf Pro management framework has been updated with Xcode 12 so it will now report Big Sur as macOS 11.
Rebuilding our Jamf Management Framework on Xcode 12 for Jamf Pro 10.25.2 will allow Automated Device Enrollment (AKA DEP) to be successful on hardware that ships without Rosetta. Of course, the previous supported features of User Initiated Enrollment (UIE) and management of Big Sur already exists in 10.25.1.
Please let us know if you have any questions.
@retroroscoe Since yesterday before 10.25.2 upgrade some of devices began reporting as OS Version 11.X, and a test Mac with Big Sur reporting as 11.X now fails to enroll, after Setup Assistant and retrieving profiles the account payload is not being respected and when on Desktop the Jamf binary is not being installed and only profiles are in place.
Cloud instance upgraded to 10.25.2 and same behaviour, going to test some more devices.
Has anyone experienced an issue with PreStage enrollment packages? The management history for Big Sur machines shows the packages “installed” but the bits never get on the machine. Nothing in the install.log either. Cloud JSS 10.25.2.
Jamf support has not been helpful in troubleshooting this.
We were upgraded to 10.26.0 over this past weekend and I was able to re-enroll my MBA with M1 chip without issue. Prior to that, we were on 10.25.1 and experienced the exact same issue mentioned, "The pre-stage registration is displayed and the profiles are installed, but the Jamf binary is not installed". If you are already on Jamf 10.26.0, try the following command to wipe and reinstall Big Sur so Prestage enrollment runs again.
sudo softwareupdate --fetch-full-installer '/Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall' --eraseinstall --agreetolicense --forcequitapps --newvolumename 'Macintosh HD'
I noticed an issue on at least one computer yesterday (MacBook Pro with Touch Bar, Intel), where I would boot to recovery, wipe the drive, reinstall Big Sur and during the setup wizard it would reboot again after the first one or 2 settings to complete installation. It would then come back up and be at the Remote Management screen where it looks like it's working ok. However, once I create my account and log in, there is no Jamf Binary installed. This is on 10.26 Jamf Pro Cloud. I am able to use the quick add package from there to install the binary but if this becomes more widespread, this is less than ideal.