All products

Toolbelt Connect icon: a wrench in a gray circle with two orange signal arcsToolbelt Connect

Help an Intune-managed PC without walking over.

From the browser, your service desk sees how a device is doing, starts a repair, fetches the support package or looks at the screen. By default only after the user's consent.

Not for sale yet. The licenses are being prepared. A demo is available on request.

Toolbelt Connect by SoulBit. Works with Microsoft Intune.

Sketch. The labels are the product's own.

Where your service desk gets stuck today

  • Walking over or taking over the screen

    A known repair needs admin rights, so someone has to be there.

  • Logs arrive the long way round

    A log file comes by mail, through a share, or not at all.

  • The ticket lacks the evidence

    What happened on the device is nowhere in the ticket.

How it works

One support case, from ticket to fixed.

  1. Step 1 of 4

    Open the device from the ticket

    A link in your ticket system opens the device in the console, with the ticket number attached.

  2. Step 2 of 4

    The user gives consent

    With the default setting Ask, nothing happens until the user clicks Allow.

  3. Step 3 of 4

    Repair remotely

    Start Retry apps & policies or another Endpoint Toolbelt action, or fetch the support package.

  4. Step 4 of 4

    The result in the ticket

    Success only when the effect shows. Copy for ticket gets a summary ready, and everything is in the audit trail.

What your service desk does with it

  • Status next to Intune

    Endpoint Toolbelt next to compliance, Windows version and last sync from Intune.

  • Repair actions remotely

    With the same confirmations and limits as on the device.

  • Support package in one click

    Logs and diagnostics straight in the browser.

  • Files both ways

    Send, request or fetch, also through a file browser within the file rules. Placing files in a folder is off by default. Up to 200 MB.

  • Read the event log and registry

    Events and registry keys, from the console.

  • Registry changes under control

    Through signed templates. One-off changes are off by default and need a second approval. Always with backup and rollback.

  • From your ticket system

    When your technician comes in through the ticket, the ticket number is on every action, in the audit trail and in the name of every download.

  • View and take over the screen

    With the Remote Control add-on, in the same console. With a banner, a time box and a recording.

Trust is part of the design

  • Consent by default

    Four settings, also for unattended devices.

  • An audit trail that shows tampering

    Each line holds a check value of the one before.

  • No shared platform

    An environment per organization, normally in your own Azure subscription.

  • No free command line

    Only fixed, signed commands.

Common tasks

One task from start to finish: first what Intune itself offers, then what this product adds.

All the details

Remote Control: view and take over the screen

With the Toolbelt Connect Remote Control add-on, a technician sees the signed-in user’s screen in the console, and takes it over when that was asked for and allowed at the start. The picture travels over the same outbound connection on port 443 as the rest of Toolbelt Connect.

  • Consent and visibility. With the setting Attended, the device always asks the user first, and the question says whether it is about viewing or taking over. With Unattended, the session starts without a question. Either way, a signed-in user sees a banner on top of every window with the technician, the ticket and the end time, and can end the session. A session with control can be turned back to view only.
  • A time box. The technician picks a length of 5 to 240 minutes at the start, and the session then ends by itself. One session runs per device at a time.
  • A recording. By default a session is recorded in your organization’s environment and kept for 90 days; you set that period yourself. An administrator can download the recording. Sessions under Unattended are always recorded.
  • The audit trail. Start and end, the consent, taking over, and turning back to view only.

The add-on has a license of its own and an installation package of its own, and stays off until the administrator turns it on per device with a policy. It does not yet show or operate the sign-in screen or UAC prompts.

Next to Remote Help and the Intune admin center

Toolbelt Connect adds to Intune’s tools. It adds the repair of the Intune Management Extension, consent and audit per action, and evidence of the effect. For the screen you choose: Remote Help from the Intune admin center, or the Remote Control add-on in the same console as everything else. What each one does is on Toolbelt Connect next to Remote Help and Intune’s device actions.

How the user is involved

The organization chooses how the user is involved in actions, packages and files:

Setting What the user notices
Ask (default) Nothing happens until the user gives consent. No answer within two minutes means no.
Ask, or run without a user As Ask. When nobody is signed in, the command runs without a question, and the audit trail records that.
Notify The session starts at once, and the user sees a notice with the technician’s name.
Silent Meant for unattended devices: no notice and no question, also when someone is signed in. The actions are still listed in the recent activity on the device and in the audit trail.

For the screen, the setting of the Remote Control add-on applies.

How it works technically

The devices make an outbound connection over port 443 themselves and sign in with a certificate whose key is in the TPM. Technicians sign in with their Microsoft Entra ID account. A command goes to the device signed. There, a service without network access checks the signature and runs only a fixed set of commands.

What you need
  • Windows 10 22H2 or Windows 11, 64-bit, managed with Microsoft Intune.
  • Endpoint Toolbelt on every device.
  • An Azure subscription for your organization’s environment, and Microsoft Entra ID for the technicians’ sign-in.
  • For the screen: the installation package of the Remote Control add-on, and the policy RemoteControl set to Attended or Unattended.
What Toolbelt Connect needs Version
Endpoint Toolbelt on the device 1.1.0 or later
Protocol between the two (trusted service caller) Version 1

The Toolbelt Connect installation stops with a message when Endpoint Toolbelt 1.1.0 or later is missing.

License

Toolbelt Connect will be a paid product with a license per organization. There are no prices here yet. What is fixed:

  • When the license stops, Endpoint Toolbelt keeps working on the devices.
  • The updates and the removal of the agent on the devices keep working, and you can keep exporting your data.
  • An expired license only stops new remote sessions and the enrollment of new devices. It never starts anything that affects devices or data.
  • The Remote Control add-on has a license of its own. When it expires, only new screen sessions stop.

Want to see how it works?

Request a demo, or mail your questions.

Request a demo

Also from SoulBit