Skip to main content
Solved

Jamf Self Service Not Associated with Jamf Pro Server

  • November 14, 2023
  • 44 replies
  • 434 views
B
Forum|alt.badge.img+2

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!

Best answer by m_ruehl

m_ruehl

can you expand on that please, may be an example?


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

    44 replies

    J
    Forum|alt.badge.img+14
    • jtrant
    • Honored Contributor
    • November 14, 2023

    Self Service is normally licensed via AxM and deployed automatically using Jamf. As long as you have VPP licenses for Self Service there should be no need for Apple ID login.

     

    M
    Forum|alt.badge.img+4
    • mecklind
    • Contributor
    • November 14, 2023

    Seeing the same exact thing. No changes to the environment and suddenly 2 new ipads set up not working.

     

    it appears to only be affecting newly enrolled iPads and not devices that are already enrolled.

    whiteb
    Forum|alt.badge.img+9
    • whiteb
    • Valued Contributor
    • November 14, 2023

    I think this is a bug relating to the new version of Self Service (11.2).

    https://www.reddit.com/r/k12sysadmin/comments/17vd7h8/psa_new_version_of_jamf_selfservice_released_wont/

      B
      Forum|alt.badge.img+2
      • bembry
      • Author
      • New Contributor
      • November 14, 2023

      I think this is a bug relating to the new version of Self Service (11.2).

      https://www.reddit.com/r/k12sysadmin/comments/17vd7h8/psa_new_version_of_jamf_selfservice_released_wont/


      Thank you for supplying this link. Hopefully this bug is fixed soon!!

      BlakeR-NZ
      Forum|alt.badge.img+4
      • BlakeR-NZ
      • Contributor
      • November 15, 2023

      Having this exact same issue, testing iOS devices in Jamf Pro for the first time after managing Mac's using Jamf for years and thought I was doing something stupid but glad to hear its most likely a software bug. 

      FYI I'm using the cloud hosted of Jamf Pro.

        F
        Forum|alt.badge.img+7
        • foobarfoo
        • Valued Contributor
        • November 15, 2023

        We have an on-prem instance, and we have the same issue as well. Great, 60k devices affected, going to be a huuuuge poop sandwich today. Thanks for the abysmal QA, Jamf!

          F
          Forum|alt.badge.img+7
          • foobarfoo
          • Valued Contributor
          • November 15, 2023

          We have an on-prem instance, and we have the same issue as well. Great, 60k devices affected, going to be a huuuuge poop sandwich today. Thanks for the abysmal QA, Jamf!


          FYI, the config has been silently changed in the JAMF Pro documentation (UDID is now MANAGEMENTID), but it seems like updating the managed app config makes no difference. Anyway, insight into cause and fix (including ETA on an app update, if one is required) would be greatly appreciated, JAMF!

          m_ruehl
          Forum|alt.badge.img+3
          • m_ruehl
          • New Contributor
          • November 15, 2023

          FYI, the config has been silently changed in the JAMF Pro documentation (UDID is now MANAGEMENTID), but it seems like updating the managed app config makes no difference. Anyway, insight into cause and fix (including ETA on an app update, if one is required) would be greatly appreciated, JAMF!


          Both UDID and MANAGEMENTID must be entered. Then it works.

            M
            Forum|alt.badge.img+3
            • Mountain_Man
            • New Contributor
            • November 15, 2023

            Both UDID and MANAGEMENTID must be entered. Then it works.


            m_ruehl

            can you expand on that please, may be an example?

              M
              Forum|alt.badge.img+3
              • Mountain_Man
              • New Contributor
              • November 15, 2023

              m_ruehl

              can you expand on that please, may be an example?


              Tried adding the MANAGEMENTID made no difference

                D
                Forum|alt.badge.img+11
                • dlevendo
                • Contributor
                • November 15, 2023

                Never had anything in the app config for Self Service but the URL of our JAMF.  Not even sure what my UDID is for this configuration.  If anyone can shed some light on this for me, I’d appreciate it.  Thanks in advance.

                m_ruehl
                Forum|alt.badge.img+3
                • m_ruehl
                • New Contributor
                • Answer
                • November 15, 2023

                m_ruehl

                can you expand on that please, may be an example?


                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

                  S
                  Forum|alt.badge.img+3
                  • schiemsk
                  • New Contributor
                  • November 15, 2023

                  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


                  Thanks, this config works for us too.

                  That's immed : No need to re-deploy the App.

                  jr139
                  Forum|alt.badge.img+6
                  • jr139
                  • New Contributor
                  • November 15, 2023

                  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


                  Thanks @m_ruehl - Confirmed we were having the same issue and the configuration you provided with both management ID and UDID fixed our issue on newly enrolled devices. 

                  For those copying and pasting this make sure to change the last string to your jamf pro URL or use $JPS_URL

                  It's worth noting that the Jamf Pro documentation only calls for management ID and not both management ID and UDID, we tried copying directly from jamf documentation and it did NOT work. 

                    M
                    Forum|alt.badge.img+3
                    • Mountain_Man
                    • New Contributor
                    • November 15, 2023

                    Thanks, this config works for us too.

                    That's immed : No need to re-deploy the App.


                    Does Self Service get the new config automatically or do we need to remove and reinstall self service?

                    M
                    Forum|alt.badge.img
                    • mdecola
                    • New Contributor
                    • November 15, 2023

                    It's an 11.2 bug.  I had an ipad with 11.1 and did a blank push.  Soon as Self-Service updated to 11.2 it blew up.     

                    M
                    Forum|alt.badge.img+3
                    • Mountain_Man
                    • New Contributor
                    • November 15, 2023

                    Thanks @m_ruehl - Confirmed we were having the same issue and the configuration you provided with both management ID and UDID fixed our issue on newly enrolled devices. 

                    For those copying and pasting this make sure to change the last string to your jamf pro URL or use $JPS_URL

                    It's worth noting that the Jamf Pro documentation only calls for management ID and not both management ID and UDID, we tried copying directly from jamf documentation and it did NOT work. 


                    I tried leaving it as $JPS_URL it didn't work used the URL for the server but where i had a / at the end of the URL which worked before i had to remove it. Now all ok.

                    M
                    Forum|alt.badge.img+3
                    • Mountain_Man
                    • New Contributor
                    • November 15, 2023

                    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


                    Many thanks All good now. Its ridiculers that in the Jamf documentation it doesn't have the UUID key. 

                    V
                    Forum|alt.badge.img+1
                    • viorel
                    • New Contributor
                    • November 15, 2023

                    Manually Installing Self Service with Volume Purchasing
                    https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Jamf_Self_Service_for_iOS.html#ariaid-title3

                    Please ensure you add the key between the opening (<dict) and closing (</dict>) tags. Also, ensure it does not go in between another key and value pair. If you are unsure where to add this exactly, please share a copy of your app config.

                    How to fix:
                    -Go to VPP app and paste App Config:
                    <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>JSS_URL</key>
                    <string>$JPS_URL</string>
                    </dict>

                    -Once the changes are saved, we will see ‘Settings - Managed App Configuration’ MDM command sent with plist
                    -Kill Self Service(Might need to restart the device)
                    -Re-open

                    1. Manually delete the Self Service application from the device.
                    2. Find this device in Jamf Pro. Click on the device, then go to the management tab for this device.
                    3. Let's click on the update inventory button for this device.
                    4. After the inventory completes, it should realise that Self Service is not installed and try to install again.

                    Best regards,

                    S
                    Forum|alt.badge.img+3
                    • schiemsk
                    • New Contributor
                    • November 15, 2023

                    Manually Installing Self Service with Volume Purchasing
                    https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Jamf_Self_Service_for_iOS.html#ariaid-title3

                    Please ensure you add the key between the opening (<dict) and closing (</dict>) tags. Also, ensure it does not go in between another key and value pair. If you are unsure where to add this exactly, please share a copy of your app config.

                    How to fix:
                    -Go to VPP app and paste App Config:
                    <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>JSS_URL</key>
                    <string>$JPS_URL</string>
                    </dict>

                    -Once the changes are saved, we will see ‘Settings - Managed App Configuration’ MDM command sent with plist
                    -Kill Self Service(Might need to restart the device)
                    -Re-open

                    1. Manually delete the Self Service application from the device.
                    2. Find this device in Jamf Pro. Click on the device, then go to the management tab for this device.
                    3. Let's click on the update inventory button for this device.
                    4. After the inventory completes, it should realise that Self Service is not installed and try to install again.

                    Best regards,


                    Please, that's not the point here.

                    L
                    Forum|alt.badge.img+5
                    • lstrehlau
                    • New Contributor
                    • November 15, 2023

                    We are having the same issue happening today. Submitting a Jamf support ticket. 

                    M
                    Forum|alt.badge.img+1
                    • MJan
                    • New Contributor
                    • November 15, 2023

                    It's an 11.2 bug.  I had an ipad with 11.1 and did a blank push.  Soon as Self-Service updated to 11.2 it blew up.     


                    We experienced this before 11.2, with iPads still running 11.1.1. It was always on newly enrolled devices. However, now that 11.2 is starting to deploy, it's probably going to break existing devices.

                    M
                    Forum|alt.badge.img+1
                    • MJan
                    • New Contributor
                    • November 15, 2023

                    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 this works as well. I talked to support yesterday, they had me try a different config profile but clearly it wasn't this.

                    sjuarez
                    Forum|alt.badge.img+3
                    • sjuarez
                    • New Contributor
                    • November 15, 2023

                    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


                    This also worked for us! Thank you!

                    jr139
                    Forum|alt.badge.img+6
                    • jr139
                    • New Contributor
                    • November 15, 2023

                    I reached out to our customer success manager and they said they are aware of the issue and working on a hotfix. Not sure if we will need to adjust the App config after the hotfix is applied (hoping not) since things are now working with @m_ruehl 's app config. 

                      Terms & ConditionsCookie settingsAccessibility statement