- #Jamf pro 10.27 release notes Patch#
- #Jamf pro 10.27 release notes password#
- #Jamf pro 10.27 release notes free#
#Jamf pro 10.27 release notes free#
Your Jamf Pro server, including any free sandbox environments, will be updated to Jamf Pro 10.28 based on your hosted data region below. You can view the latest list of titles here. We will continue to add titles to the feed, independent of Jamf Pro releases and will communicate the addition of new titles via in-product announcements.
#Jamf pro 10.27 release notes Patch#
Jamf has expanded its list of patch management titles to the app feed within Jamf Pro, to now offer hundreds of software titles, including many of the most commonly installed apps by Mac users, at no additional cost. We’re also excited to deliver a number of additional improvements including the ability to automatically deploy the Jamf Protect package for a more streamlined integration workflow.
Compatibility and new feature support are based on testing with the latest Apple beta releases. Self Service incorrectly displays policies for Unmanaged Macs and should probably be smart enough to display an error that this Mac is Unmanaged rather than blindly showing you policies that you can't possibly run in an Unmanaged state.Jamf is prepared to deliver same-day support for Apple’s latest releases as they become available.
#Jamf pro 10.27 release notes password#
Enrolling using a QuickAdd with Random Password causes the Mac to become Unmanaged only with Jamf Pro 10.27, and may be a bug specific to the Jamf binary itself.Ģ.
So in my mind there appears to be two bugs here:ġ. The same test with the 10.19 version of a QuickAdd against our PROD environment running 10.26 shows that everything enrolls correctly as managed, the binary successfully upgrades to 10.26 (and shows this version in inventory) and Self Service policies run without error.
However, this time I noticed one additional quirk in that the Mac enrolled and ran an initial inventory but strangely reports that the Jamf binary version is still 10.19 while on the Mac itself the binary was actually upgraded to 10.27. In our DEV environment running Jamf Pro 10.27, that QuickAdd caused the same error and also showed the Mac as Unmanaged. I also tested older QuickAdd packages I still had laying around for both our DEV and PROD instances that were generated using Recon 10.19 and using a Random Password. I tested this theory on a Mac that was successfully enrolled, and stayed Managed, which I then manually unmanaged it in the JSS Web Interface and found that you get the same results in seeing the "This item is no longer available" error in Self Service.Īddtionally, I tested QuickAdds with Random Password vs Specify Password against our Jamf Cloud PROD instance (running Jamf Pro 10.26) and found that this error does not occur for either type of QuickAdd. The curious thing that I found is that in the case of using the QuickAdd with Random Password it appears to enroll the Mac and successfully run an initial inventory, but the Mac becomes Unmanaged! Since policies cannot be installed on Unmanaged Macs you will get this error in Self Service. Additionally, the password I specified was fairly simple all lower case letters and numbers and only 12 characters in length. If I enroll using a QuickAdd package that has this set to Specify Password then all of my Self Service policies work fine. What I found was that when I enroll using a QuickAdd package that was created with the "Method for Setting Password:" drop-down set to Random Password, I will consistently get the error with all of my Self Service policies. I did several tests enrolling a test Mac running macOS 10.15.7 (fully patched) using QuickAdd packages. GUI: Verify the installed versions of the GUI and CLI displayed on the Preferences pane. I tested against our Jamf Cloud DEV instance that was recently upgraded to Jamf Pro 10.27. After installing or upgrading to Jamf Pro 10.27.0 or later, confirm which version of Jamf Pro Server Tools you have installed by doing one of the following: CLI: Execute the following command: jamf-pro -version. To add my data point, I found a repeatable way to cause the "This item is no longer available" error in Self Service.
0 kommentar(er)
