Enable the Software Kiosk

Turn on the Software Kiosk so the people using your managed devices can self-install approved software from the octoja agent in their system tray.

Written By Stefan Steuer

Last updated 8 days ago

Enable the Software Kiosk

The Software Kiosk lets the people using your managed devices install approved software themselves. It lives in the octoja agent's self-service app, which sits in the device's system tray. A user opens the app, browses or searches the list of apps you've approved for that device, and installs one with a single click β€” so routine software requests never have to reach you. Each entry shows whether the app is already installed or has an update available.

This guide walks an administrator through switching the kiosk on and choosing which software appears in it.

Before you start

  • You need the Software Deployment Management permission to add and edit software in a config package, and the Monitoring Check Management permission to open and edit config packages. Both are granted per group under Administration β†’ Groups.
  • To change agent settings on a single device, you need permission to manage that device. Device permissions are also granted per group under Administration β†’ Groups.
  • A config package must already exist (or you need permission to create one), and it should match the devices you want the kiosk on.
  • The octoja agent must be installed on the target devices.

Step 1 β€” Show the agent and turn on the kiosk

The kiosk only appears once two agent settings are on for the device: Show agent in system tray (so the self-service app is reachable) and Software kiosk enabled. You can set these for a whole group of devices through a config package, or for one device on its own.

For matched devices, via a config package

  1. Go to Configuration β†’ Config Packages and open the package that matches the devices you want.
  2. Find the Agent settings section.
  3. Turn on Show agent in system tray.
  4. Turn on Software kiosk enabled.
  5. Save the config package.

Every device the package matches gets these settings. A device ends up with a setting switched on if any of its config packages turns it on, so you set the rule once and it follows your fleet.

For a single device

  1. Open the device from Devices.
  2. From the device's action menu, choose Agent settings.
  3. For Show agent in system tray, pick On to override it for this device.
  4. For Software kiosk enabled, pick On as well.
  5. Click Save.

Each setting shows Default (the value it inherits from the device's config packages) or an Override you set here. Leave a setting on Default to keep following the packages, or set it to On or Off to fix it for this one device.

Step 2 β€” Publish software to the kiosk

Turning the kiosk on gives the user an empty shelf. You decide what goes on it per software item in a config package's Software tab.

  1. Go to Configuration β†’ Config Packages and open the package.
  2. On the Software tab, add a software deployment (or open one you've already added). See Deploy Software to Devices for how to add software.
  3. Turn on Show in Software Kiosk for that item. Its hint reads: "Display this software on the Software Kiosk page so users can self-service it."
  4. Save the config package.

Repeat for each app you want available in the kiosk. Only the items you switch on appear there; everything else in the package still deploys the way it normally would.

What the user sees

On a device where the kiosk is on, the person using it opens the octoja agent from the system tray and finds the Software Kiosk. There they can:

  • Browse or search the list of apps you approved for that device.
  • Install an app with one click.
  • See, for each app, whether it's already installed or has an update available β€” and update it from the same place.

The octoja agent on the device carries out the install, so users can install approved software without local administrator rights.

Tips

  • Use a config package's Agent settings to switch the kiosk on across a group of devices at once, and reserve the per-device override for one-off exceptions.
  • Keep the kiosk list short and relevant to each device group β€” approve the everyday apps your users actually request, and leave specialised tools to a scheduled deployment.
  • An app only reaches the kiosk when both its config package matches the device and Show in Software Kiosk is on for that item.
  • Installed and update states are detected machine-wide. Software a user installed only under their own account may not be reflected.