VERSION 2022.3.0.0 (October 17th 2022)

VERSION 2022.3.0.0 (October 17th 2022)

avatar

Hello everyone,

We are excited to release the beta version of Devolutions Server 2022.3.0. Please make a backup before performing the upgrade, and we strongly recommend you install in in a test environment first.

Console download(.exe):
https://cdn.devolutions.net/download/Setup.DVLS.Console.2022.3.0.0.exe
Offline package (.zip):
https://cdn.devolutions.net/download/RDMS/DVLS.2022.3.0.0.zip

Upgrade procedure: https://helpserver.devolutions.net/upgrade_rdms.html

The 2022.3.1 Gateway is also available from the console, and it is required to have the latest features (see below).

Database upgrade required
DVLS Console 2022.3 is required
RDM 2022.3 is required, if you use RDM: https://forum.devolutions.net/topics/38137/remote-desktop-manager-20223--beta

NEW FEATURES

  • Core - Added a way to migrate users from an authentication mode to another (from Active Directory to Azure AD for exemple)
  • Core - Added permission set to assign permission easily on users
  • Core - Added support to Okta authentication
  • Core - Added support to SMTP modern authentication with Azure
  • Core - Implemented attachment and documentation support for sub connections
  • Gateway - Added Kerberos authentication via KDC Proxy
  • Gateway - Added new reports to display Devolutions Gateway permission
  • Gateway - Added permissions on Devolutions Gateway
  • Gateway - Sessions launched via Devolutions Gateway can now be killed
  • PAM - Added description field on PAM account
  • PAM - Added support for generic providers
  • Web - Added markdown WYSIWYG documentation editor


IMPROVEMENTS

  • BREAKING CHANGE Core - RDM User license must be set in the data source
  • BREAKING CHANGE Core - RDM users need one license assigned for each user account
  • Core - Added one button in login page for each Active Directory configured
  • Core - Added support for multiple emails in email configuration
  • Core - Button label can now be configured in login page
  • Core - Improved RDM connection stability with Devolutions Server
  • Core - Improved security dashboard UI
  • Core - Renamed 'Custom User' by 'Devolutions Server User'
  • Gateway - Added a filter in the Devolutions Gateway list
  • PAM - Added log messages if PAM password propagation failed
  • PAM - Added possibility to include PAM vaults in search side bar
  • PAM - Changed the way PAM account are displayed: Removed tiles and display a tree
  • PAM - Improved PAM Heartbeat failed message to differentiate provider and account name


FIXES

  • Core - Fixed an issue where administrator received an exception about telemetry when internet was not available
  • Core - Fixed an issue where attachments were corrupted after download
  • Core - Fixed an issue where folder structure was visible in DWL even if user didn't have access to the folder
  • Core - Fixed an issue where importing Azure AD accounts didn't fill the first and last name
  • Core - Fixed an issue where license capacity could be exceeded
  • Core - Fixed an issue where password set on an attachment was not shown correctly
  • Core - Fixed an issue where read only users could add attachments or documentation
  • Core - Fixed an issue where username field could be missing in Emergency Login
  • Core - Fixed an issue where Website entry could not be saved with a Password Management license
  • Core - Fixed an issue where wrong RDM version was logged in reports
  • Core - Fixed issue in My Account Settings where Dashlane Password and KeePass Server Password were not obfuscated
  • Core - Removed sensitive information from public endpoint
  • Web - Several UI fixes


####

Console Release Notes

IMPROVEMENTS

  • Add read right to IIS_IUSRS on encryption.config file
  • Removed the Basic authentication and Digest authentication from the prerequisites
  • Set the Devolutions Gateway ID when Devolutions Gateway is installed side by side


FIXES

  • Fixed an issue where Devolutions Gateway side by side installation button was grayed out
  • Fixed an issue where semicolon was not accepted in SQL Server password

Richard Boisvert

All Comments (0)