Windows - Software - Install DBeaver Community Edition

What the DBeaver deployment Worklet does

This Automox Worklet™ deploys DBeaver Community Edition, the open-source universal database client, to Windows endpoints. The Worklet checks the uninstall registry on the endpoint, downloads the matching 32-bit or 64-bit installer from the Automox cache API, and runs a silent install with system-wide scope. DBeaver Community Edition supports MySQL, PostgreSQL, Microsoft SQL Server, Oracle, SQLite, MariaDB, MongoDB, Redis, and roughly 80 other relational and NoSQL platforms through JDBC drivers.

Architecture detection runs through [System.Environment]::Is64BitOperatingSystem. The Worklet pulls the latest build from the Automox cache API at api.automox.com/api/cache, passing cmd=downloadLatestVersion, name=DBeaver, os=Windows, and an arch parameter of 64 on 64-bit operating systems or 32 on legacy 32-bit hosts. The installer lands in the script working directory, runs with the NSIS flags /S /allusers, and is deleted after the process exits. The default install path is %ProgramFiles%\DBeaver on 64-bit systems and %ProgramFiles(x86)%\DBeaver on 32-bit systems.

The evaluation phase is idempotent: an endpoint that already carries DBeaver in either the native or Wow6432Node uninstall hive exits zero and is skipped. New endpoints, freshly imaged hosts, and any workstation that has had DBeaver removed will be flagged on the next policy run, so the deployment baseline holds without an admin chasing individual machines.

Why deploy DBeaver across the fleet

Database administrators, application developers, data engineers, and tier-2 support staff all need direct query access during incident response and day-to-day work. Without a sanctioned client, those teams reach for whatever is on hand. Common substitutes include an aging copy of SQL Server Management Studio, a personal HeidiSQL install, a portable Navicat trial, or a browser-based admin console. The fleet ends up with several different SQL clients, each with its own driver versions, query history locations, and credential stores, and your incident-response playbook can no longer assume a common tool.

DBeaver Community Edition is free, open-source under Apache 2.0, and ships with bundled JDBC drivers for every major database engine. Standardizing on it removes the procurement back-and-forth around paid SQL clients and gives security review a single artifact to track for vulnerability advisories. The Worklet keeps the deployment cadence aligned with new-hire onboarding and re-imaging: the moment an endpoint shows up in your Automox console, the next policy run installs the same DBeaver build the rest of the fleet is on.

Apply this Worklet to the database administrator and developer workstation group so the DBeaver installer lands on every machine that needs the client. The policy re-applies the install on any machine where DBeaver has been removed since the previous evaluation.

How DBeaver deployment works

1. Evaluation phase: The Worklet opens the native 64-bit uninstall hive at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall using Microsoft.Win32.RegistryKey with the Registry64 view, then iterates every subkey and matches DisplayName against *DBeaver*. If no match is found, it falls back to the 32-bit hive at HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall. A match in either hive exits 0 with the message DBeaver is already installed. Now exiting. A miss exits 1 with the message DBeaver was not found. Flagging for remediation.

2. Remediation phase: The script reads [System.Environment]::Is64BitOperatingSystem to decide which architecture to pull. On 64-bit hosts, it calls (New-Object System.Net.WebClient).DownloadFile against the Automox cache URL with an arch value of 64 and writes DBeaver.exe into the script working directory. On 32-bit hosts, it pulls the arch=32 build. Either path then runs Start-Process "$scriptDir\DBeaver.exe" -ArgumentList ("/S", "/allusers") -Wait, which launches the NSIS installer with silent mode and the all-users flag so the binaries land under %ProgramFiles% and register in the machine-scope uninstall hive. Remove-Item deletes the installer after the process completes, and the script exits 0 on success or 1 on any Try/Catch failure.

DBeaver deployment requirements

• Windows 7, Windows 8.1, Windows 10, Windows 11, or Windows Server 2008 R2 and later; the Worklet targets both workstation and server endpoints

• Administrative privileges on the endpoint; the Automox agent default context already meets this for /allusers installation under %ProgramFiles%

• Outbound HTTPS to api.automox.com so the remediation script can reach the cache URL for downloadLatestVersion

• Approximately 250 MB of free disk space for the installer download, the unpacked Eclipse runtime, the bundled OpenJDK, and the JDBC drivers DBeaver downloads on first connection

• No prerequisite Java install; DBeaver Community Edition ships with its own OpenJDK runtime inside the program directory

• Compatible with the FixNow workflow for ad-hoc deployment to a single endpoint or a small target group outside the regular policy schedule

Expected state after DBeaver deployment

DBeaver Community Edition lands under %ProgramFiles%\DBeaver on 64-bit endpoints, with dbeaver.exe as the launcher and a Start menu shortcut under DBeaver Community. The NSIS installer registers an entry in HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall with a DisplayName beginning DBeaver, which is what the evaluation phase looks for on the next run. The installer used by this Worklet is wiped from the script directory; only the deployed binaries remain on disk.

Validate by opening an elevated PowerShell session and running Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object { $_.DisplayName -like '*DBeaver*' } | Select-Object DisplayName, DisplayVersion, InstallLocation. The output should show the deployed version and the install path. For an end user check, launch DBeaver from the Start menu and confirm the welcome window opens; no reboot is required. The Automox activity log records exit code 0 for successful deployments and exit code 1 for any failure, with the failure message Failed to install DBeaver 64-bit or Failed to install DBeaver 32-bit written to stdout so the cause surfaces in the run history.