When a user with a managed iPad starts Self Service, the app complaints it should be linked to a Jamf Pro-server. And you can't do anything with the app. See screenshot (Dutch localization):
This is weird, because the iPad is listed between the devices in Jamf Pro.
I do notice two pending commands from yesterday and the day before yesterday (inventory update and a time zone settings update).
I tried to quit self service and relaunch: did not work. I also switched the iPad off and back on.
What could be wrong?
Edit: could it have to do with the license? I get this notification now (I'll ask my boss about this):
Just an update on this to regroup thoughts. Starting with Self Service 11.2 (released 14 November) both MANAGEMENT_ID and UDID key in the app config are required
Once saved a "Settings - Managed App Configuration" command will be sent to all devices in scope. This may take some time since it relies on MDM communication.
@doekman check for Self Service app > App Config > in the plist if the below key pair is missing: <key>MANAGEMENT_ID</key> <string>$MANAGEMENTID</string>
If it's not present, add it and save. Then quit and re-open Self Service.
I'd recommend to check the same. Editing the app with the key pair should be all what's needed. Upon saving, you should see MDM commands called "Settings - Managed App Configuration" starting to be sent to devices that will pull down the new config and let Self Service re-connect (needs to be quit/re-open).
I'd recommend to check the same. Editing the app with the key pair should be all what's needed. Upon saving, you should see MDM commands called "Settings - Managed App Configuration" starting to be sent to devices that will pull down the new config and let Self Service re-connect (needs to be quit/re-open).
Is this requirement new? The self-service app entries in my MDM only have the UDID entered and not the MANAGEMENT_ID. In the product documentation for Jamf Pro, only the MANAGEMENT_ID is entered and not the UDID.
@doekman check for Self Service app > App Config > in the plist if the below key pair is missing: <key>MANAGEMENT_ID</key> <string>$MANAGEMENTID</string>
If it's not present, add it and save. Then quit and re-open Self Service.
The Preferences-textarea is empty. Is this a new thing, since in the past Jamf Self Service worked.
Also: because it's empty do I need to enclose the xml in a dict-tag? So like:
Is this requirement new? The self-service app entries in my MDM only have the UDID entered and not the MANAGEMENT_ID. In the product documentation for Jamf Pro, only the MANAGEMENT_ID is entered and not the UDID.
I haven't had that MANAGEMENT_ID key in my App Configuration ever and our Self Service broke with this 11.2 update. Not sure if I missed something but adding it in seems to resolve the issue.
@doekman check for Self Service app > App Config > in the plist if the below key pair is missing: <key>MANAGEMENT_ID</key> <string>$MANAGEMENTID</string>
If it's not present, add it and save. Then quit and re-open Self Service.
I started having the issue when the iPadOS updated to version 17.1.1. Prior to this everything was happy.
VickiH
The issue is not iPadOS 17.1.1. I have iPads with earlier iPadOS versions that are having this issue this morning. The issue comes with the update to Self Service version 11.2.0. Adding the MANAGEMENT_ID key in the Self Service app configuration fixed it for me as it did for others.
Hello, any ideas when the MANAGEMENT_ID does not solve the problem?
Did your devices receive the new updated management configuration command after you added the key? In our environment we force push Self Service so we can delete it and run an inventory update to install it again. This makes sure it has the new App Configuration settings with it.
The issue is not iPadOS 17.1.1. I have iPads with earlier iPadOS versions that are having this issue this morning. The issue comes with the update to Self Service version 11.2.0. Adding the MANAGEMENT_ID key in the Self Service app configuration fixed it for me as it did for others.
It may have worked for you and others but it is not working for me and some others after adding the key. The only time I started to have the issue was after I updated to 17.1.1, prior to that it was working.
Did your devices receive the new updated management configuration command after you added the key? In our environment we force push Self Service so we can delete it and run an inventory update to install it again. This makes sure it has the new App Configuration settings with it.
I did that as well and I'm still receiving the same message about it being a component of Jamf Pro and it must be associated with a Jamf Pro Server. :-(
Currently the config is without UDID. But I tested it too. Same like before...
So I was just able to get this working, I read another post where management_id and UDID still needs to be there...I've just tested on another iPad and it works as well. After adding the App configuration, save it and then I deleted the app from device. Went to that device and ran an update inventory so it will push out the Jamf Self-Service.
Note please make sure you update the $JSS_URL with your jamfcloud URL
The issue is not iPadOS 17.1.1. I have iPads with earlier iPadOS versions that are having this issue this morning. The issue comes with the update to Self Service version 11.2.0. Adding the MANAGEMENT_ID key in the Self Service app configuration fixed it for me as it did for others.
Also what helped was adding UDID back. Not just management_id that seems to be working for me. I hope you have a great day.
I'd recommend to check the same. Editing the app with the key pair should be all what's needed. Upon saving, you should see MDM commands called "Settings - Managed App Configuration" starting to be sent to devices that will pull down the new config and let Self Service re-connect (needs to be quit/re-open).
I've made the change, and new installs are working, but I'm not seeing the "Settings - Managed App Configuration" command going out to the existing devices. Is there an API command to force that?
I've made the change, and new installs are working, but I'm not seeing the "Settings - Managed App Configuration" command going out to the existing devices. Is there an API command to force that?
Maybe you can try the force update and see if that will help.
