Skip to main content

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):

Device count exceeded

Purchase additional licenses.

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.


That makes sense. UDID was already in my app configuration so I left it there. MANAGEMENT_ID was not in the app configuration; adding it was the only change i made.

That makes sense. UDID was already in my app configuration so I left it there. MANAGEMENT_ID was not in the app configuration; adding it was the only change i made.


I took it out thinking that the Jamf Documentation knew what it was talking about...LOL

Maybe you can try  the force update and see if that will help.


Just took a minute to start queueing up (6k iPads)

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


Verify the self service app config matches this:


<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>UDID</key>
<string>$UDID</string>
<key>JSS_URL</key>
<string>$JPS_URL</string>
</dict>


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.

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


Verify the self service app config matches this:


<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>UDID</key>
<string>$UDID</string>
<key>JSS_URL</key>
<string>$JPS_URL</string>
</dict>


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.


The fix for me was defining the JSS_URL key and not relying on the variable.

Looks like they released another update to self-service yesterday (11.2.1). Has anyone been able to confirm if the UDID and Management ID are required since the Jamf documentation removed the UDID and added the Management ID in the app config settings? 

Looks like they released another update to self-service yesterday (11.2.1). Has anyone been able to confirm if the UDID and Management ID are required since the Jamf documentation removed the UDID and added the Management ID in the app config settings? 


For us it works since we added the UDID and Management ID.
Also the Jamf support answered me, that both attributes are required.

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 

 

<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>UDID</key>
<string>$UDID</string>
<key>JSS_URL</key>
<string>$JSS_URL/</string>
</dict>


This worked for me. The user needed to restart the app for this to work (or restart iPad).

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


Verify the self service app config matches this:


<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>UDID</key>
<string>$UDID</string>
<key>JSS_URL</key>
<string>$JPS_URL</string>
</dict>


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.


What's the difference between $JSS_URL and $JPS_URL?

 

What's the difference between $JSS_URL and $JPS_URL?

 


I could be wrong:

JSS = Jamf Self Service

JPS = Jamf Pro Server

https://xxxx.jamfcloud.com

Above is what I have in the $JPS_URL section you do not need to make changes to the JSS_URL string section, just replace the $JPS_URL variable with whatever this is for you https://xxxx.jamfcloud.com

 

Example:

<key>JSS_URL</key>
<string>https://xxxx.jamfcloud.com/</string>

 

Terms & ConditionsCookie settings