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!

Jamf Self Service Not Associated with Jamf Pro Server

Same issue.

Now Fixed with new config:

This is a known Product Issue, PI115080 for your reference. With the upgrade to Self Service 11.2, we will need to replace the App Configuration for the Self Service App which contains additional keys.

We can go to the Self Service App Record > App Configuration > Edit > Remove the old App Configuration > Add the new App Configuration > Save.Once this is done, we should see Devices get sent an MDM Command (Settings - Managed App Configuration). After around 5-10 minutes we should see this command complete and Self Service should begin to work.

Here is the new App Configuration we will want to add:

<dict>

<key>INVITATION_STRING</key>

<string>$MOBILEDEVICEAPPINVITE</string>

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

</dict>

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

That solution worked for us so far. Immediate fix, no need to exclude/reinstall the app.

The MANAGEMENT_ID fix worked for me. A heads up from Jamf would have been nice. It caused a little stress around here!

Now Fixed with new config:

This is a known Product Issue, PI115080 for your reference. With the upgrade to Self Service 11.2, we will need to replace the App Configuration for the Self Service App which contains additional keys.

We can go to the Self Service App Record > App Configuration > Edit > Remove the old App Configuration > Add the new App Configuration > Save.Once this is done, we should see Devices get sent an MDM Command (Settings - Managed App Configuration). After around 5-10 minutes we should see this command complete and Self Service should begin to work.

Here is the new App Configuration we will want to add:

<dict>

<key>INVITATION_STRING</key>

<string>$MOBILEDEVICEAPPINVITE</string>

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

</dict>

Thank you, that worked for me.

Where do you find your MANAGEMENT_ID?

There's no need, the only line that you have to customize is...

...which is the URL to your Jamf server.

Thanks so much for this, this worked. However, Self Service is now taking a good bit of time to download on wiped devices, I am currently have been waiting 18 minutes for it to come down on an iPad. Anyone else seeing this?

It's only been 4 minutes for me so far waiting for Self Service to install on a fresh iPad.

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

We tried the above Jamf-URL string with no success but found this worked.

Adding these 2 lines below to our (now broken) prod app config resolved the issue:

<key>MANAGEMENT_ID</key>

<string>$MANAGEMENTID</string>

Also, make sure the below lines are not removed from the app config as suggested in Jamf documentation as the 16/11/23:

How our app config now looks:

<dict>

<key>INVITATION_STRING</key>

<string>$MOBILEDEVICEAPPINVITE</string>

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

</dict>

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

I can confirm adding the management id fixed my issue. I left the UDID in place.

It looks like 11.2.1 has fixed the issue. The iPads that have that version (released today, I believe) have started working again with no changes to the app config.

Just wanted to add to this to keep it alive a little longer since I'm annoyed from being out sick and coming back to this mess. Adding the management ID lines between UDID and JSS URL fixed it up for me too. Really unacceptable to make a change like this without testing how it affects current instances of the app already installed. Thankfully everyone here is looking out for each other and we don't have to go by just the documentation since going by that also apparently didn't work.

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.

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.

Is this still not fixed?

Arek

Is this still not fixed?

Arek

I guess not. We also have the same issue.

I will attempt the fix/workaround, which was posted above, this week.

I guess not. We also have the same issue.

I will attempt the fix/workaround, which was posted above, this week.

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

Now Fixed with new config:

This is a known Product Issue, PI115080 for your reference. With the upgrade to Self Service 11.2, we will need to replace the App Configuration for the Self Service App which contains additional keys.

We can go to the Self Service App Record > App Configuration > Edit > Remove the old App Configuration > Add the new App Configuration > Save.Once this is done, we should see Devices get sent an MDM Command (Settings - Managed App Configuration). After around 5-10 minutes we should see this command complete and Self Service should begin to work.

Here is the new App Configuration we will want to add:

<dict>

<key>INVITATION_STRING</key>

<string>$MOBILEDEVICEAPPINVITE</string>

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

</dict>

The above is working for us. Thank you.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded