Version scheme
From now on the suite (controller, BMS, setup, ISO) uses the scheme YY.MM.Build. Modules keep their own versions.
New
- Trial version (7 days): signed key, shown in the controller as “Testversion: noch N Tage”.
- BMS web administration in the browser (
https://<server>:8443/admin): sign-in only with a one-time password (300 seconds, valid once). Controllers, pairing codes, profiles, groups, RDP and SSH connections, module store and events. Session ends after 15 minutes idle, protection against forged requests and throttling of failed attempts. - Installer as a module: You prepare your own programs (EXE, MSI, folder) in the controller and deliver them through the BMS to all paired controllers.
- SSH connections at the BMS (password and/or key, stored encrypted) and upload to the module store (default 100 MB, adjustable up to 4096 MB).
- The public update feed stays available even with a paired BMS and when the BMS is down. The ISO login banner mentions the web administration.
Known issues
- The RDP/SSH display in the controller (previously black) is not confirmed again after the fixes.
- A user reported that the one-time password login did not work. It could not be reproduced in testing; error messages and logging were improved.
- Not supported: MSIX/APPX and scripts as a module, Windows Hello requirement at local controller start, recovery after a lost key at the BMS.