Skip to main content
Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. Join us in person at the ninth annual Jamf Nation User Conference (JNUC) this November for three days of learning, laughter and IT love.

Self Service Maintenance Mode

During any maintenance period for a Jamf upgrade to the server (On-Premises or Cloud), the Self Service.app still remains accessible to users.
If a user launches Self Service.app during this maintenance window they are just greeted with an error to saying it cant connect to the server.

I would like it to be possible to set a maintenance downtime window in Jamf Pro - All Settings - Self Service (ideally with the UI being able to be branded and a pre-defined timeframe)
So that during this planned downtime if the Self Service.app is launched by a user, they are greeted with a pleasant, Sorry we'll be back soon message instead of an communication error

A few examples attached of how the Apple do it for their website



Comment
Order by:

Posted: by Asifahmed

Good idea. It should not create any panic to end users during maintenance time.

Like

Posted: by Asifahmed

It is really very good idea.

Like

Posted: by garybidwell

A few UI mock-ups added


Like

Posted: by pete_c

Upvoted. This would be useful in setting end-user expectations, especially if there was a field that could indicate the expected time for the service to become available again. Instead of "IT told me to use Self Service and now I can't," it would become "oh I just have to wait however long and then I can do what I need."

Like

Posted: by brockwalters

I am little confused by this request because I think this feature already exists.

Like

Posted: by garybidwell

Hi, @brockwalters As far as im aware (and the Jamf engineers tell me when I asked about this) the maintenance pages introduced in Casper 9 still require tomcat to be running to serve out the pages.
That feature was meant to be used when the JSS was active but you didn't want users to use Self Service while your updating policies.
(apologies if I got this wrong, but thats the way it was explained to me)

If the tomcat is not running at all (i.e is completely shut down while your doing a version update to tomcat/java or migration etc...), if a user launches Self Service it just comes up with a connection error as it cant get these pages from the JSS.

My idea was to have these pages setup in the JSS, but store them within the actual Self Service.app in advance (like the app's custom branding icon) and made active client-side during the scheduled outage window (which you would set prior to the downtime in the JSS)

Like

Posted: by garybidwell

A few more mockups


Like