Skip to main content

Installation, Rollout & Uninstallation

Before you begin​

  • Requirements reviewed — see Requirements
  • Account / license available
warning

For now, the application must be installed per user to work correctly. This is likely to change in the future, but it's important to keep in mind today.

It is possible to install system-wide on macOS using the provided .app file. It should work completely fine but support is currently not extensively tested.

Rolling out to many users at once?

If you want to install and activate the sensor for a whole company without any user interaction, see Anonymous Mass Rollout.

Installation methods​

Manual installation​

  1. Download the installer here.
  2. Run the installer.
  3. Verify the installation.

Rollout via Microsoft Intune​

Rollout via Intune can be done using the .intunewin package, which is created automatically from the NSIS installer. You can download it here. To avoid confusing users, pass the /S parameter to the installer to suppress the progress window during installation. Use /S --force-run rather than /S alone: in silent mode the one-click installer never shows its finish page, so without --force-run the sensor is installed but not started afterwards. The --force-run flag makes the installer launch the sensor once the silent install completes.

Add --hidden if the installation should leave no Start Menu entry — see Anonymous Mass Rollout.

Clean-install wrapper (Desk.ly Connect)​

On devices where the Windows process mitigation Heap.TerminateOnError is enforced (common on hardened, managed fleets), the NSIS installer/uninstaller can hit STATUS_HEAP_CORRUPTION (exit code -1073740940 / 0xC0000374) at two points, because a late heap operation deep inside the NSIS runtime trips the mitigation:

  1. The uninstaller crashes while removing the previous version during an upgrade, aborting the install with the message "Die alten Anwendungsdateien konnten nicht deinstalliert werden".
  2. The installer itself crashes at the very end — after it has already copied all files, written the registry and started the sensor. The installation is complete and working, but the process still returns 0xC0000374, so Intune treats the deployment as failed.

For those fleets, deploy the following wrapper instead of calling the installer directly. It (a) removes any existing installation directly so the crash-prone uninstaller is never invoked, and (b) reports success based on the actual installation result rather than trusting the installer's exit code:

# Desk.ly Connect - clean install for Intune (per-user).
$ErrorActionPreference = 'SilentlyContinue'
$setup = "$PSScriptRoot\deskly-Connect.exe"
$key   = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\a2c22559-86a1-44c9-8683-d949e6de9bbb'

# 1) Stop the app
Get-Process shigoto.sensor | Stop-Process -Force
Start-Sleep -Milliseconds 500

# 2) Remove an existing installation directly (folder + uninstall key) - no NSIS uninstaller
$dir = Split-Path ((Get-ItemProperty $key).UninstallString -replace '^\s*"([^"]+)".*$', '$1') -Parent
if ($dir -and (Test-Path $dir)) { Remove-Item $dir -Recurse -Force }
Remove-Item $key -Recurse -Force

# 3) Install silently (--force-run also starts the sensor in /S mode).
#    Under the mitigation the installer can exit with 0xC0000374 *after* it has fully
#    installed and started the sensor. Ignore its exit code and report success from the
#    actual result: a successful install (re)creates the uninstall key.
Start-Process $setup -ArgumentList '/S', '--force-run' -Wait
if (Test-Path $key) { exit 0 } else { exit 1 }

Variant note: This script targets Desk.ly Connect (setup file deskly_connect.exe). For the Shigoto build or other whitelabel partner builds, only adjust the setup filename (e.g. shigotoSetup.exe). The process name (shigoto.sensor) and the NSIS GUID (a2c22559-86a1-44c9-8683-d949e6de9bbb) are identical across all variants.

The wrapper touches the installation directory and the uninstall registry key only. The configuration folder %APPDATA%\Shigoto\ is left alone, so a config.json deployed beforehand — for example for an anonymous mass rollout — stays in place.

Intune rollout on macOS is more manual than the automated .pkg install. For this we provide a .app bundle on our Download page. Stop the running application, then copy the .app file to /Applications. If a previous version is already installed, replace the existing .app when prompted (or remove it first to avoid leaving stale files behind). Once copied, start the application again.

Uninstallation​

On Windows, use the uninstaller included with the installer or remove the application via the Programs and Features menu.

On macOS, deleting the application from the Applications folder is enough. To also remove user data and logs, manually delete ~/Library/Application Support/Shigoto.