Windows - Software - Install DBeaver Community Edition

What the DBeaver installer does

This Automox Worklet™ deploys DBeaver Community Edition, a universal SQL client and database administration tool, to Windows endpoints. The Worklet automatically detects endpoint architecture and installs the appropriate 32-bit or 64-bit version.

DBeaver Community Edition provides database connectivity, SQL query execution, data exploration, and reporting capabilities across multiple database platforms. The Worklet uses the Automox cache API to download the latest stable version, verifying endpoints receive current releases without manual version management.

The installation runs silently in the background with the /S and /allusers parameters, making it suitable for large-scale deployments. After successful installation, the Worklet automatically removes the installer executable.

Why deploy DBeaver across your endpoints

Database administrators, developers, and system engineers frequently require direct database access to troubleshoot issues, execute queries, manage schemas, and perform administrative tasks. Without standardized tools, teams resort to ad-hoc solutions that lack audit trails and create security gaps.

DBeaver Community Edition offers a free, open-source alternative that supports MySQL, PostgreSQL, Oracle, SQL Server, SQLite, and dozens of other databases. Deploying it through Automox keeps all qualified staff have immediate access to a supported, consistent tool without manual installation requests.

This Worklet reduces deployment friction, improves productivity by eliminating installation delays, and maintains audit compliance by using a single standardized version across endpoints.

How DBeaver installation works

1. Evaluation phase: The Worklet checks the Windows registry (HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) for DBeaver entries in both the 64-bit registry hive and 32-bit Wow6432Node registry hive. If DBeaver is already installed in either location, the evaluation exits with success status. If DBeaver is not found on the endpoint, the evaluation flags the endpoint for remediation.

2. Remediation phase: The Worklet downloads the appropriate DBeaver installer (64-bit or 32-bit) from the Automox cache API using the endpoint's system architecture. The installer runs silently with system-wide installation parameters (/S /allusers). After successful installation, the Worklet deletes the temporary installer file and exits with success status.

DBeaver installation requirements

• Windows 7, Windows 10, Windows 11, or Windows Server 2008 R2 and later

• At least 100 MB of free disk space

• Java Runtime Environment (JRE) is bundled with DBeaver installer

• Administrative privileges required for system-wide installation

• Active internet connection during remediation for downloading the installer

Expected state after DBeaver installation

After remediation completes successfully, DBeaver Community Edition is installed and available in the Start menu under the application name. The Worklet registers the software in the Windows registry, allowing the evaluation phase to recognize the installation on subsequent runs.

Users can launch DBeaver immediately without rebooting. All database connection functionality is available, including SQL editing, query execution, data browsing, and administrative tasks. The installation is system-wide, making DBeaver accessible to all user accounts on the endpoint.

How to validate install dbeaver community edition changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install dbeaver community edition.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as New-Object, Start-Process, Remove-Item, then rerun evaluation for compliance.