Jamf Pro 10.28 Now Available

@kaylee.carlson There's a problem with the URL. You'll want to link to the release notes here:
https://docs.jamf.com/10.28.0/jamf-pro/release-notes/What's_New.html
The current URL is pointing to 10.28 (no good) vs 10.28.0 (good)

Jamf Pro 10.28.0 Additional Reporting Capabilities for Computers: Supports iOS and iPadOS App Installations

When viewing an individual computer record, "Inventory > General > Supports iOS and iPadOS App Installations" displays "Not Supported."

After enabling "Settings > Computer Management > Inventory Display > Computer > Supports iOS and iPadOS App Installations," the "Supports iOS and iPadOS App Installations" field for multiple computers displays "No."

Why am I not able to see the Known Issues? Any time I go to the page, I get a 403 access denied. It feels like a real slap in the face when jamf tells me they are providing me with "greater transparency", when it is in fact the complete opposite.

@TeamOC Click on your avatar > My Asssets > Known Issues link
Or https://www.jamf.com/jamf-nation/my/assets/jamf-pro/known-issues

If neither works, the issue may be with your Jamf Nation account in which case you want to probably contact your Jamf Customer Success Manager or Jamf Support.

I run the update and it seems not really good on my side. I have multiple problems and all my Computer Configuration Profiles changed from System to User based. Some Profiles are broken or without any payload. Upgrade from 10.26.1 - 10.28 MySQL8.0

Update. Second update from 10.26.1. -> 10.27 -> 10.28 works for me.

We had a bunch of Notification MDM profiles which were created outside of Jamf. Upon upgrading to 10.28.0 (from 10.26.0) the 'Notifications' payload (previously not visible in the Web UI) was removed from all of them. Existing clients kept their config but new installs failed with a "This profile is missing some required information" error.

Jamf Pro 10.27.0 introduced full support for the 'Notifications' payload but nothing in the release notes suggested that profiles created out of the UI would lose their content post-upgrade. Just a heads up for anyone upgrading where there are Notifications profiles created outside of Jamf.

@jtrant Were the profiles that had their Notifications payload removed signed prior to being uploaded to Jamf Pro?

@sdagley No, I try to avoid signing unless I really need to. I wouldn't expect Jamf to take any action (or be able to) on a signed profile.

@jtrant Jamf Pro has a long history of mangling profiles when they're uploaded if they're not signed, especially if any part of the payload is something the Jamf Pro GUI can't handle. The usual practice is to sign those profiles to prevent damage. It sounds like you've found a new way for a profile to be damaged.

@sdagley yes, it seems that way. However, the mangling normally happens with things that are in the UI but we don't want to set 30 things to configure one preference, and sign the profile as a workaround. Wiping payloads that weren't in the UI but now are certainly seems to be a new behavior.

I'm being pointed to PI-009430 on this one.

Hi, is there an update to this technical paper about the automatic package deployment of Jamf Protect? It seems the information still includes manual package upload and policy deployment if you want to track installation feedback - is that correct? I note the initial lines about Jamf Protect being auto-magically installed if the feature is enabled, but I am curious if there's more info here, such as "how" and logging etc.

https://docs.jamf.com/technical-papers/jamf-pro/deploying-jamf-products/10.28.0/Jamf_Protect_Deployment_and_Updates.html

hooray to more Jamf BUGS!!!!