The "Patch Management" screen on Jamf Pro tells me that we have zero (zero!) machines running the latest version of macOS, which is says is 11.0.1, but my machine (running 11.0.1) is reported by Jamf as running 10.16 ...
Looks like this is a problem that needs fixing at Jamf's end somehow
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.
Please let us know if you have any questions.
So the smart group for Big Sur should be???:
Operating System Version LIKE 11.0. OR Operating System Version LIKE 11.1.
Then add more ORs for each minor version, for when 11.2. is released?
I am trying to avoid getting any 10.11.x device in the mix. That will occur if you simply enter: " 11."
I could include greater than and less than, but what is the most efficient method for just Big Sur 11.
The jamf release notes state:
In Jamf Pro, create a new group with the version 11.x.x as criteria.
Some will think they literally should enter it in as 11.x.x. But I don't think of x as being any wildcard or valid entry for criteria.
before our upgrade to 10.25.2 I set up a Smart Group with 'operating system version' 'LIKE' 10.16 OR 11 and no problems after upgrade.
Machines that haven't checked back in yet are still showing up in the view results as 10.16.0 but those that checked in after the upgrade now report back as 11.0.1.
We had one deployed product on Catalina which is causing kernel panics on Big Sur and we're using this Smart Group to exclude it. Summary: I'll rest easy this weekend.
I upgraded to Jamf PRO 10.26.0 yesterday but none of our seven Macs running on Big Sur are reporting a version number beginning with 11 this morning. All but two have checked in since the upgrade and still show 10.16 in their inventory records. So something still isn't quite right, at least with our system.