Skip to main content
Question

Experiences Deploying Self Service Plus with Jamf Connect 3.x

  • October 20, 2025
  • 4 replies
  • 111 views

Person
Forum|alt.badge.img+9

I’m curious about your experiences deploying Self Service Plus alongside a Jamf Connect 3.x update. I’m currently testing this and have a policy set up to install both Jamf Connect 3.x and Self Service Plus via policy.

However, I’m wondering if it’s better to just upgrade Jamf Connect and use the “Use Self Service+ as the default end user application option directly from the Jamf Pro server instead.

Has anyone tested or noticed any issues in the app’s behavior or reliability during deployment with each approach?

4 replies

Chris_Hafner
Forum|alt.badge.img+25
  • Jamf Heroes
  • October 20, 2025

I’ve had good luck both ways. Though, I only used the policy installation for testing. When we were ready for production we flipped the switch to use Self-Serivce+ by default and let Jamf manage it. It worked very well in the two instances I managed. 


Person
Forum|alt.badge.img+9
  • Author
  • Jamf Heroes
  • October 20, 2025

That’s helpful to hear as I’m leaning the turn it on via Jamf direction. I may keep my current policy route for initial testing, then switch to letting Jamf Pro handle the deployment once everything looks good. I am also looking to just install Jamf Connect 3.x when Self Service Plus is installed.


AJPinto
Forum|alt.badge.img+26
  • Legendary Contributor
  • October 21, 2025

I have done both as well with no issue, the only problems I have is how poorly Jamf has documented any of this and that Jamfs own documentation makes conflicting statements on workflows and capabilities.


garybidwell
Forum|alt.badge.img+15
  • Jamf Heroes
  • October 22, 2025

We just moved to using Self Service+ as default last weekend, by activating it in Settings - Jamf Apps - Self Service+ and it was all pretty painless.

Only thing that was needed was a policy to remove the old Self Service icon from the dock and add the new Self Service+ once it detected its had been installed

The only other gotcha we found was with older computers that were still bound to AD, is upon very first launch it requires the user to enter their UPN even though they were configure to also use SSOe.
Anyone that was Entra ID based didn't even notice the change over until they used it and noticed the new layout