Skip to main content

Important notice: Beginning with this version, Jamf is no longer sending maintenance release email messages. We will continue to send Jamf Pro release announcement email messages for major and minor releases (e.g., 12.0.0, 11.21.0, respectively).

 

Today we are releasing a maintenance version of Jamf Pro; highlights include:

Resolved Issues

Jamf Pro Server

  • "PI134363] Fixed: When configuring a computer configuration profile with a Network payload with "Any ethernet" selected, Jamf Pro incorrectly uses the string "AnyEthernet" instead of the required "GlobalEthernet" in the payload, preventing computers from successfully joining corporate 802.1x wired networks.
  • "PI139045] Fixed: Activation Lock status fails to display for eligible iOS devices in the Management > Activation Lock bypass category of a mobile device inventory record.
  • "PI140234] Fixed: Static groups fail to display in the Management > Mobile Device Groups category of a mobile device inventory record.
  • "PI140306] Fixed: Jamf Pro fails to display new, updated, and existing students imported from Apple School Manager.
  • "PI140403] Fixed: Jamf Pro requires Platform Single Sign-on (Platform SSO) configurations to include an Associated Domain payload, despite not being necessary for every identity provider.

 

For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.

To access new versions of Jamf Pro, log into Jamf Account with your Jamf ID. The latest version is located in the Solutions section under Jamf Pro.

 

Cloud Upgrade Schedule

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

To upgrade manually: Log in to Jamf Account, click View details on the Jamf Pro tile, and then click Upgrade on the appropriate instance. Note: This capability is not available for GovCloud environments and is disabled for all instances one day prior to when the scheduled standard upgrades begin.

Subscribe to product alerts to receive real-time updates.

 

Hosted Region Begins Ends
ap-southeast-2 19 September at 1400 UTC 19 September at 2000 UTC
ap-northeast-1 19 September at 1500 UTC 19 September at 2300 UTC
eu-central-1 19 September at 2200 UTC 20 September at 0900 UTC
eu-west-2 19 September at 2300 UTC 20 September at 0600 UTC
us-east-1 StateRAMP 20 September at 0400 UTC 20 September at 1400 UTC
us-east-2 20 September at 0400 UTC 20 September at 1400 UTC
central-us Azure 20 September at 0500 UTC 20 September at 0700 UTC
us-west-2 20 September at 0700 UTC 20 September at 1800 UTC

Important notice: Beginning with this version, Jamf is no longer sending maintenance release email messages. We will continue to send Jamf Pro release announcement email messages for major and minor releases (e.g., 12.0.0, 11.21.0, respectively).

 

 

This is very concerning, some organizations like mine have very strict change control procedures that require us to submit change requests for vendor initiated changes for governance and notification of outages. Jamf changing its posture to rely on us checking Jamf nation and hopefully seeing a community manager post about a minor upgrade’s is deeply concerning and a violation of fundamental change management and stakeholder notification practices. Organizations cannot use community message boards as notifications for official change events. 

Important notice: Beginning with this version, Jamf is no longer sending maintenance release email messages. We will continue to send Jamf Pro release announcement email messages for major and minor releases (e.g., 12.0.0, 11.21.0, respectively).

 

 

This is very concerning, some organizations like mine have very strict change control procedures that require us to submit change requests for vendor initiated changes for governance and notification of outages. Jamf changing its posture to rely on us checking Jamf nation and hopefully seeing a community manager post about a minor upgrade’s is deeply concerning and a violation of fundamental change management and stakeholder notification practices. Organizations cannot use community message boards as notifications for official change events. 

agreed. I’m not always watching the macadmins slack channel and these emails are usually how i know an update is available (hence me coming to this thread). 

If Jamf was a consumer oriented company, it’s understandable to a degree. In what world does this decision make any sense?

Couldn’t you have at least sent an email to let people know that this was coming? I don’t recall seeing one.

 

[PI134363] Fixed: When configuring a computer configuration profile with a Network payload with "Any ethernet" selected, Jamf Pro incorrectly uses the string "AnyEthernet" instead of the required "GlobalEthernet" in the payload, preventing computers from successfully joining corporate 802.1x wired networks.

Happy to see this one fixed! 

Oh joy! So I get notified by email that someone responded to this thread and our email security flags it saying that the following link is potentially malicious. I don’t see anything in this link that supposedly originated from Jamf that makes me believe it is Jamf other than I know that there is a us-west-2 server as listed in the schedule above.

pwreyz8k.r.us-west-2.awstrack.me

Reply


Terms & ConditionsCookie settings