Skip to main content

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?

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. 

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.

Terms & ConditionsCookie settingsAccessibility statement