Posted on 11-14-2023 01:48 PM
I am getting the message saying "Self Service is a component of Jamf Pro, developed by Jamf. This app must be associated with a Jamf Pro Server. Contact your IT administrator for more information."
We use automated device enrollment and the iPads experiencing this issue are enrolled into our Jamf instance. Our Self Service app is set to be installed manually to avoid Apple IDs. I have already set up the app configuration as seen on the Jamf Pro documentation. Is there anything else that I am missing? Thank you!
Solved! Go to Solution.
Posted on 11-15-2023 05:03 AM
This Config-Dictionary works for us:
<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>UDID</key>
<string>$UDID</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>JSS_URL</key>
<string>*Jamf-URL*</string>
</dict>
*Jamf-URL* must be replaced with the URL of the MDM server
Posted on 11-16-2023 02:40 PM
Came back from PTO to see this. Deleting Self Service and reinstalling it from the App Store pulled down version 11.2.1. Trying the plist key App Configuration update.
11.2.1 does work, but some are still stuck on 11.2.0.
Posted on 11-16-2023 03:07 PM
We made the fix and it does work. Jamf support called me back and said this was a work around, not the fix and that they will be fixing it in the next jamf release.
Posted on 04-08-2024 01:13 PM
Is this still not fixed?
Arek
Posted on 04-16-2024 02:11 AM
I guess not. We also have the same issue.
I will attempt the fix/workaround, which was posted above, this week.
Posted on 04-16-2024 11:19 PM
Did that yesterday. Worked.
It was enough to simply add the App Config and wait a bit. No need to remove or push out the portal again.
I did use a placeholder though for the Jamf-URL: $JPS_URL