Dwarfguard version 1.9.0 "Keeper RC1"
- status: available
- released at: 2026-02-28
- supported modes of operation:
- production: Yes, but RC is not fully tested release
- free usage: Yes but primarily to BETA partners
- 1.9.0 RC1 build:
- MD5sum: b3a87b54fd7eec3d0c79eb7625962f19
- SHA1sum: 9329d79841ba4834750366bdcebb3958e447a3cb
- supported deployment modes:
- DT SAAS / DT Cloud / DT Server Managed: No / No / Yes
- Partner SAAS / Partner Cloud / Partner Server Managed: No / No / Yes
- Customer self-managed: Yes
- Private network: Yes
- support planned: till next RC/full release
- upgrade supported from:
- target audience: BETA partners, DEMO deployments
- showcase video: N/A
Release notes - known issues, changes since last release
- Version 1.9.0 RC1 is a first release candidate of Dwarfguard 2.0.0.
- Version 1.9.0 RC1 supports following Debian GNU/Linux versions:
- Debian GNU/Linux 13 - recommended for all new installs as the support for Debian GNU/Linux 12 may be dropped during the 2.x version line.
- Debian GNU/Linux 12 - support kept because of upgrades from oldstable versions (1.0.x). You will be able to upgrade the OS to version 13 later on, introducing a short Dwarfguard service downtime during OS upgrade and reboot. Instructions will be provided after release of Dwarfguard 2.0.0.
- Release Candidate usually contains all the release features and the primary difference to the future release is in the amount of testing done. Once all testing successfully passes, the Dwarfguard 2.0.0 wil be release. NOTE that RC1 step may be skipped in the upgrade chain (the 2.0.0 release will support upgrades from all of 1.4.3 BETA4, 1.9.0 RC1 and partial upgrade from 1.0.6).
- 1.9.0 supports full upgrade from 1.4.0 BETA 4 (build 1.4.3)
- As the major version 2.0.0 contains substantial changes from the previous oldstable (1.0.x), a seamless upgrade is not possible and a reinstall is required.
- 1.9.0 supports PARTIAL upgrade from 1.0.6, meaning:
- There is automated upgrade script from 106 to 190 bundled in the release
- The script performs these steps:
- Fully backs up the 106 deployment
- Stores the user table
- Wipes out the 106 deployment including ANY data including devices data, historic data, groups, profiles and notes
- Installs Dwarfguard 2.0.0 RC1 with defaults overridden by the actual 106 options (domain, server ID, Apache config, potentially the
SSL certificate and other)
- Restores the users and their passwords
- Once the Dwarfguard 2.0.0 RC1 starts up, it requests any reporting device to re-register, allowing keeping the device its old DevID
- It is possible, as a custom action, to import the device notes, profiles and other connected data, as the device IDs will be kept. NOTE that you need to wait until the devices re-register themselves before you run the DB import. This data import can be done manually by administrator or as a custom support action (covered by Advanced and Premium support levels). Please note that this operation is technically sophisticated and should be performed while Dwarfguard service is stopped. Also, if performed improperly, the DB could get broken, requiring removing the 2.0.0 deployment, restoring the 1.0.6 from backup and redeploying the 2.0.0 RC in the partial upgrade mode to get to the starting point again.
Featured changes
- Please refer to the in-application Release Notes
Known issues (updates with bugs being reported)
- There are no known issues at the moment.