Using Self Service for basic troubleshooting/maintenance.

[jgwatson]

Currently, we are under utilizing Self Service in many ways. One of the ways we want to expand on is to have our users use Self Service as their first option for troubleshooting/maintaining their machines. E.g. my computer is running slow, I'll go to Self Service first. Does anybody out there use Self Service for basic/advanced maintenance tasks? Or does anyone know of any examples out there? Screenshots would be fantastic, or a list would be great. Thanks in advance for sharing.

[Taylor_Armstron]

A few. We don't have a lot, and some of them are honestly probably more "placebo" than anything, but we have SS policies for repairing permissions, "install all cached software", running software update (pointed at a Reposado instance, so they only get what we've approved), one to flush the cache and re-apply our policy settings, one to update the JSS inventory, etc. Nothing destructive, and most things run on a regular schedule regardless, but it gives users a feeling of a bit more control, and occasionally does prevent the helpdesk from dealing with something that could be solved by a permissions repair/ etc.

[bvrooman]

I have a "Maintenance" category with a dozen or so policies named after the problems users might see, rather than the solution. Most (as @Taylor.Armstrong mentioned above) are likely placebo, but they're effective. Some actually make changes, though.

For example:
- Computer Running Slowly: Fix permissions, flush caches, reboot
- Internal Network Issues: Re-run network/proxy config script, reboot
- Keychain Password Prompts: Clear all "Local Items" keychains, reboot
- Printers Not Working: Remove all print queues, re-run scoped policies to re-map printers

[dpertschi]

Do a search here. Here's one thread... Show off your Self Service