Skip to main content

Hello Jamf Nation,

 

Today we are releasing Jamf Pro 10.42. Highlights of this release include:

 

Declarative Device Management Support

Apple's Declarative Device Management is a modern management protocol that allows managed devices to proactively and autonomously apply their own management settings with less communication from the Jamf Pro server. When you upgrade to Jamf Pro 10.42.0, Declarative Device Management is automatically enabled on eligible devices.

 

Configuration Profiles for Managed Login Items

Jamf Pro now includes two predefined configuration profiles containing Managed Login Items payloads, installed by default on eligible computers in System Settings > Privacy & Security > Profiles. These configuration profiles prevent end users from disabling certain background services of apps installed by Jamf in System Settings > General Settings > Login Items > Allow in the Background.

 

App Installers Enhancements

This release introduces several enhancements for App Installers.

 

To learn more about this release and the product issues it addresses, review the release notes here.

 

Cloud Upgrade Schedule

 

Your Jamf Pro server, including any free sandbox environments, will be updated to Jamf Pro 10.42 based on your hosted data region below. Review this guide if you need assistance identifying the Hosted Data Region of your Jamf Cloud instance.

 

Hosted Region Begins Ends
ap-southeast-2 21 October at 1300 UTC 21 October at 2200 UTC
ap-northeast-1 21 October at 1400 UTC 22 October at 0000 UTC
eu-central-1 21 October at 2200 UTC 22 October at 0800 UTC
eu-west-2 21 October at 2300 UTC 22 October at 0600 UTC
us-east-1-sandbox/us-west-2-sandbox 22 October at 0000 UTC 22 October at 0900 UTC
us-east-1 22 October at 0400 UTC 22 October at 1700 UTC
us-west-2 22 October at 0700 UTC 22 October at 2000 UTC

Who made this change and said "yeah this looks better??"


I totally agree. Why take something that was intuitive and people are familiar with and turn it into something totally confusing, half-baked and honestly it doesn't look good. Please bring back the old design.

And honestly you guys at JAMF should spend your time fixing your buggy system and adding useful things like a UI for the Managed login items instead of wasting it on something that nobody asked for.

I totally agree. Why take something that was intuitive and people are familiar with and turn it into something totally confusing, half-baked and honestly it doesn't look good. Please bring back the old design.

And honestly you guys at JAMF should spend your time fixing your buggy system and adding useful things like a UI for the Managed login items instead of wasting it on something that nobody asked for.


“Why take something that was intuitive and people are familiar with and turn it into something totally confusing, half-baked”


System Settings 🙄

“Why take something that was intuitive and people are familiar with and turn it into something totally confusing, half-baked”


System Settings 🙄


I meant design/UI-wise.

I totally agree. Why take something that was intuitive and people are familiar with and turn it into something totally confusing, half-baked and honestly it doesn't look good. Please bring back the old design.

And honestly you guys at JAMF should spend your time fixing your buggy system and adding useful things like a UI for the Managed login items instead of wasting it on something that nobody asked for.


Wholeheartedly agree with you.

Is anyone else experiencing issues with device records not pulling up in 10.42.0?  The web page just spins when opening certain device records.

Is anyone else experiencing issues with device records not pulling up in 10.42.0?  The web page just spins when opening certain device records.


Yes, we have multiple S/N we can't load, and I have an active ticket with Jamf to fix this. First they asked if they could take down our Jamf instance to fix the issue, I said yes, then I got a reply from another staff asking me to do more troubleshooting instead of taking down the instance to fix the problem.

Really wonder sometimes about their support. 

Yes, we have multiple S/N we can't load, and I have an active ticket with Jamf to fix this. First they asked if they could take down our Jamf instance to fix the issue, I said yes, then I got a reply from another staff asking me to do more troubleshooting instead of taking down the instance to fix the problem.

Really wonder sometimes about their support. 


I am chatting with support now and this is the response I got:

Can we grab screenshots of this behavior? Unfortunately, this is a known issue that has started to occur after we updated Jamf Pro to 10.42At the moment, there is no PI for this issue since this issue is fairly new. We also do not have any information regarding a timeline but are aware that a fix is being worked on at the moment. At the moment we are unaware of a workaround. We can try enabling “Debug mode” within Jamf Pro Settings > Information > Jamf Pro Server Logs. We can try to navigate to the device record to see if it will load.

I am chatting with support now and this is the response I got:

Can we grab screenshots of this behavior? Unfortunately, this is a known issue that has started to occur after we updated Jamf Pro to 10.42At the moment, there is no PI for this issue since this issue is fairly new. We also do not have any information regarding a timeline but are aware that a fix is being worked on at the moment. At the moment we are unaware of a workaround. We can try enabling “Debug mode” within Jamf Pro Settings > Information > Jamf Pro Server Logs. We can try to navigate to the device record to see if it will load.


That is so lame and terrible service for a paid product. If the changes you introduced cause database issues, revert the changes, don't put everyone in limbo "until a fix is ready".

I did all that, debug mode, sent server logs, etc. 

That is so lame and terrible service for a paid product. If the changes you introduced cause database issues, revert the changes, don't put everyone in limbo "until a fix is ready".

I did all that, debug mode, sent server logs, etc. 


Support has given us a workaround for the issue we are seeing when some device records are viewed in Jamf Pro, they spin infinitely and never load. There is now a Product Issue PI110632 for this issue.  The workaround is running a MySQL query to update the "Priority" column for devices that do not have a priority.  Essentially the MySQL query will just update the affected table's priority to have a priority.

Rough update for us. First, package downloads broke with error -1200. Word from our onsite applications support group and a few calls with Jamf was that the cipher suite needed updating. We get that addressed after almost a week of trying to get the right assistance from Jamf and now we're seeing the problem of not being able to pull up device info on various iPads. Hoping 10.42.1 fixes this.

Terms & ConditionsCookie settingsAccessibility statement