Self Service doesn't activate

[Yu-64]

After installing Self Service (ver11.2.0-588) to managed iPad device, the app requests log in to JAMF Software Server.

This happens iOS 16.6.1 and 17.1.1, then it's possible to access internet.

Even after reseting iPad, reinstall App, it occurs.

I have no idea to solve it.

Help me.

[Yu-64]

I can't continue and use the app.

On Jamf Pro Console, the system doesn't request user login.

[foobarfoo]

We have the same problem and it's a HUUUUGE issue for us! Any insights?

[naominix]

In my environment, I was able to work around this by adding the following to the app configuration of the Self Service Moblie App. 

<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>

[m_ruehl]

---

@naominix  schrieb:

In my environment, I was able to work around this by adding the following to the app configuration of the Self Service Moblie App. 

<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>

---

This Workaround also works in our Environment 👍

[Kaiserma]

This also worked for our environment! :D

[Myhr]

Chipping in that this worked for us too!
Initially we replaced UDID with MANAGEMENTID which didn't work, needed to have them both in the config.
Jamf told me that they have an open case for this: #PI115080

[vickih]

I will try adding the UDID back as well.

Thank You. 

[vickih]

So yes adding the UDID worked for me.  Thank you.

[vickih]

I had hoped this would work for us, because I saw this from another post but my gut says iPadOS 17.1.1 compatibility issue.  LOL

[Myhr]

Worked on our 17.1.1 devices! Couldn't be bothered with waiting for the Managed App Configuration to queue so I just reinstalled the Self Service app instead and voila!

[vickih]

Yes, I'm having the exact same issue.  I have enough licenses because that was the first thing I thought of.  And then I just updated the App Configuration under the app as we deploy it using the VPP.  And there is apparently a string missing.

So I updated the App Configuration per Jamf manual 

https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Jamf_Self_Service_for_iOS.html

Then after I updated our iPad to 17.1.1 this is when my issue's started. 

VickiH

[viorel]

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

[vickih]

I have also done what you mention above and copied the App Configuration from the Jamf online Admin Manual and it still does not work.  I know this workaround works for some but there are others that it does not fix. I read somewhere Jamf has an open case for this.

[cdenesha]

THANK YOU for documenting the fix. It is working in my district.

[Shearbec]

Thank you - this worked for our district as well!  Out of curiosity, since I'm not the normal JAMF Admin, how long for the devices to pick up the parameter change?  I forced an update to inventory and that did not update on the device.  I had to remove the Self Service app and reinstall it.  

[Matt]

Depends, MDM is pretty hit or miss. Could be instantly, could take a few minutes.

[Matt]

Im still getting the error after adding this to the Self Service App Config. This issue is so annoying.

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

---

[vickih]

Matt this is what worked for me the UDID string needs to be added back which is not in the Jamf Admin Documentation.

change the $JSS_URL string to match your https://xxxx.jamfcloud.com instance.

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

[shawn_spence]

Will this work even with cloud hosted Jamf environments?  Just checking as I know some things work differently in configuration for us cloud vs on prem instances.

[Matt]

I'm on prem and it fixed one of my phones, verifying with some clients right now.

[vickih]

Yes I am cloud based. I've never been on-prem :-) We also don't require a user to log into Self-Service that's why we have it setup for volume purchase install.

[Matt]

So it fixed our issues. We are on-prem with no login required and it fixed it right away.

[vickih]

Excellent news !

[Matt]

We have been going back and forth with JAMF about this for over a month, doing DB edits, repairs, etc. So nice to know that the issue is finally fixed.

[vickih]

That is unfortunate, my issue just started yesterday.  I'm glad you were able to get your fix from the Jamf Nation world.  It's where I come to first because there are a lot of smart people in these forums. 

[Matt]

Yeah I've been a part of this community since it was an email list but was away from the JAMF world for a few years. Nice to see its still the defacto place to go.

[Matt]

May have a winner!!!! If this works thank you everyone. I have been going back and forth with JAMF about this for over a month! This community to the rescue again.

[CoryCooper]

Hi All,

This seems to have worked for us as well.

Thanks for the discussion and let us know if anyone hears from Jamf directly on their fix.

[Matt]

Yeah im wonder if this is a JAMF thing or an iOS thing. Defining a variable doesn't seem to be a long term solution IMHO.

[foobarfoo]

So, new managed app config has been pushed and verified installed on my device. We already know that reinstalling self service will fix it. But what about if you DON'T reinstall self service? What needs to happen then for the new managed app configuration to take effect? Or is the only solution to unscope and re-scope self service?

[Matt]

For my environment it updated when the check in process happened.

[vickih]

I was just able to confirm with what Matt said, I turned on a device it checked in (its been awhile) and it updated to the new self-service app and then the app configuration deployed out.

You can force them to check inventory automatically

VickiH

[Matt]

I just did a mass command too and had a ton of messages of people saying "Self Service works!"

[vickih]

WooHoo!

[bfrench]

Just read this post and not 1 minute later a student came down with this issue.  Oddly on the device Self Service and Settings were both listed twice.  I was able to delete and redeploy SS and that fixed the issue.  Are others also seeing Self Service duplicates if you search for it on the iPad before this "fix"?

[bfrench]

Jamf is now posting this message

https://jamf.service-now.com/kb_view.do?sysparm_article=KB0035429

[vickih]

I don't have access to view that.. :-( 

[bfrench]

You must be able to log into the Jamf Service portal.  It basically states what others have posted about - adding the management id key

[bfrench]

Also that it is an issue with Self Service 11.2 and was effecting iOS 16 and 17