Posted on 07-28-2015 01:35 PM
Is it possible to scope Self Service Plug-ins to specific groups? For example, I want to have a link to "QuickStart" guides for applications that are installed on specific Macs. Then scope a smart group with those apps installed, so those who do not have these apps installed won't see the link to the "QuickStart" guides
Solved! Go to Solution.
Posted on 07-28-2015 04:57 PM
Or, you can take a look at the more automated/scripted process I put together back in January for this, which you can find on this thread - https://jamfnation.jamfsoftware.com/discussion.html?id=12987
Long story short, you can quickly create Self Service URL plug-ins directly on your Mac with a script, test them in Self Service.app, then package them up for deployment (or use them with a companion Self Service installer script, also mentioned on that thread), rather than needing to create them on the JSS, or edit them by hand.
Posted on 07-28-2015 01:42 PM
Self service plugins can't be scoped AFAIK. There is a feature request that is currently under review here https://jamfnation.jamfsoftware.com/featureRequest.html?id=392
Posted on 07-28-2015 04:30 PM
There is a manual way to accomplish what you want. Self Service plugins that the JSS handles get stored on the client as plist files locally at /Library/Application Support/JAMF/Self Service/Managed Plug-ins/
If you make a folder at /Library/Application Support/JAMF/Self Service/Plug-ins/, and then copy a working plist from the other folder and modify it to suit your needs, you can package it up and then scope it as a policy based install manually since valid plists at that location will show up in Self Service as well.
Posted on 07-28-2015 04:57 PM
Or, you can take a look at the more automated/scripted process I put together back in January for this, which you can find on this thread - https://jamfnation.jamfsoftware.com/discussion.html?id=12987
Long story short, you can quickly create Self Service URL plug-ins directly on your Mac with a script, test them in Self Service.app, then package them up for deployment (or use them with a companion Self Service installer script, also mentioned on that thread), rather than needing to create them on the JSS, or edit them by hand.