Set up start buttons for your devices (Start Center)

What it is for

With the Start Center users trigger common tasks on their device themselves — without a technician and without admin rights: for example "allow USB storage", "repair printer" or "info for IT". In the console you decide which start buttons a device shows and what each button starts: an approved script with fixed values or a workflow. The user never types anything; they only click.

What you need

• Cloud or your own relay with the add-on module Start Center (A6). Free never has the Start Center.
• A console account with administrator rights: Administrator or Tenant administrator. Other roles do not see the menu item.
• For buttons that need system rights: the BrowserDesk service on the device.
• BrowserDesk for Windows, Mac or Linux on the device. The menu item Startcenter (Start Center) is below "Tickets" there.

How to do it

Buttons for the whole access

1. In the console open Deployment › Start Center. On the left is the tree Accesses & devices. Elsewhere the console calls the access a "tenant" — it is the same thing.
2. Choose your access on the left. On the right the preview shows This is how the Start Center looks on this device.
3. Quick start: choose Insert template …, pick a template (for example "Geräte und Schnittstellen", devices and ports), tick Release scripts and workflows for this access as well if needed, then Insert. Each template puts its buttons into a group of its own.
4. One by one: click Start button. In the dialog Edit start button: - Label and image: text (required), notice, Icon or an image of your own. - Action: choose Script or Workflow, then the target. If it is not approved yet, Approve for access appears below it — one click approves it. Then the Fixed values appear. - Behaviour: Operating systems, Ask before running, Needs system rights (service only), Active. - Save.
5. Change the order: drag a tile or use Alt+Left / Alt+Right.
6. Sort into groups: Group → name and icon, optionally Show collapsed. In the button dialog you pick the group in the field Group. Up to 12 groups and 128 buttons per list.

Let a single device differ

1. Expand the access in the tree and click the device — or use Choose device ….
2. Each tile carries a badge: - "from access" — clicking opens Adapt for this device …; the ⋮ menu also has Hide for this device. - "adapted for this device" — in the dialog, Reset at the bottom. - "hidden" — ⋮ menu → Show again. - "this device only" — a button of its own for this device only (Start button).
3. At the top choose whether the device keeps the access's buttons: Add to the access’s buttons (default) or Replace the access’s buttons (then it shows only its own).

How you know it worked

• The preview shows the tiles the way the device shows them. Grey tiles state their reason.
• On the device: open Startcenter (Start Center). The page loads when opened and then every minute; Aktualisieren (Refresh) loads at once.

What the other side sees

The user sees the page Startcenter with the sentence "Häufige Handgriffe mit einem Klick — eingerichtet von Ihrer IT." (common tasks with one click — set up by your IT) and your buttons, in groups that open and close. Hovering shows your notice. With "ask" a confirmation comes first (Ausführen (Run) / Abbrechen (Cancel)). The button then shows Läuft … (running), afterwards Erledigt (done) or "Fehlgeschlagen: …" (failed) with the reason. What it is like for the user: F8.

Good to know

• Seats: a device takes its Start Center seat the first time a button is started, not when the page is shown. The seat stays with the device (G24).
• Deliberately more rights: a button with system rights lets a user without admin rights run something as the system. The device only sends the button's ID; what runs is decided by you alone. Every run is in the log (G17) and in the script history.
• Approval reaches further: a script approved for the access may also be run by technicians on the devices. Withdraw it only under Scripts & packages or in the workflows (G6, G8).
• If a technician clicks a button during a session, the device asks the person in front of it — the technician's click does not count as consent.
• An adaptation for a device is a copy. If you later change the access's button, the adaptation stays as it is.
• Ready-made scripts, workflows and templates: 44 scripts, 4 workflows and 4 templates from the library, plus a second set. None of them has been measured on a device.

If it does not work