Devolutions Server - Devolutions Forum

Ctrl + k

Devolutions Server

Devolutions Server

Current Releases

Announcements of new versions for the Current releases

Extended Maintenance Releases

Announcements of new versions for the Extended Maintenance releases

Support

Support forum for Devolutions Server

Support (français)

Forum de support dédié aux demandes en français sur Devolutions Server.

Support (Deutsch)

Supportforum für deutschsprachige Benutzer

Feature Request

Feature request forum for Devolutions Server

Beta

Bugs, comments or suggestions; anything related to Devolutions Server Beta releases

API and SDKs

All about our REST API and the SDKs that we provide to our community. Suggestions / Bug reports / Feature requests

Linux

All about Linux deployment of Devolutions Server. Suggestions / Bug reports / Feature request

Recent Posts

devolutions-automation

Published 6 hours ago

Devolutions Server Version 2026.2.16.0 (August 24, 2026)

If you are using a client (RDM, PowerShell, etc.), version 2026.2 is required for this DVLS version FIXES Core - Fixed an invalid license error when connecting from Remote Desktop Manager or the Launcher to servers using PAM package licenses with auto-assign enabled Core - Fixed an issue where System Settings couldn't be saved from Remote Desktop Manager when a ticketing system was configured Core - Fixed an issue where User Vault credentials couldn't be set in user-specific settings when entry creation was restricted to templates only PAM - Fixed an issue where the Get-DSPamVault PowerShell cmdlet returned errors or no results when listing accessible PAM vaults Web - Fixed an issue where spaces couldn't be entered when renaming an entry or folder from the right-click menu Web - Fixed an issue where the "User vault" label wasn't displayed in the configured language until the page was refreshed Web - Multiple UI fixes ** CONSOLE RELEASE NOTES ** IMPROVEMENTS Minor update

Current Releases

timsilasherrmann

Published 2 days ago

Can't upload Images in Image management / RDM System Images

Hi everyone, I’m running a Devolutions Server with Docker behind a reverse proxy, which works well overall and was straightforward to set up thanks to the excellent documentation. When I try to upload custom images via RDM, it works; however, when I try to upload them persistently, this isn’t possible either via RDM or through the Devolutions Server’s web interface, and the error message “The type initializer for 'Windows.Win32.PInvokeGdiPlus' threw an exception.” is displayed. I also checked the stack's logs using `docker compose logs` in the stack directory—but unfortunately, there weren't any further details there. Unfortunately, I haven't found any other variables or workarounds (such as a bind mount for images to mount the images). I would really appreciate any suggestions for a solution.

Published 3 days ago

Generic SAML/OIDC SSO provider

Hi lbeaudry , This was requested previously in https://forum.devolutions.net/topics/55460/generic-oidcsaml-client-for-sso-login I will close this request as duplicate. I recommend commenting and voting for the thread I mentioned above.

Feature Request

William Alphonso

Published 3 days ago

Database retention policies don't work

Hello, Thank you for checking this. Would it be possible to configure a log path for the scheduler under? Administration > Server Settings > Logging and also enable the Log debug information (note that this setting should only be enabled temporarily as it can create numerous logs in the DB). Then wait for the automatic cleanup to run and retrieve the Scheduler logs as well as the Server logs (Data source logs if you are on an older version of DVLS) from the reports tab of Devolutions Server. The Log debug information allows us to log more information for troubleshooting, so the error messages from the Server logs (Data source logs) might change or you might have more information available there. Once you have those files you can either send them through a ZIP file in direct messages from the forum or email them at service@devolutions.net with FO-55873 in the subject of your email. Best regards,

Daniel Albrecht

Published 3 days ago

Database retention policies don't work

Hi! I checked the logs but they still were not moved/deleted automatically. [image] How to troubleshoot further? Thank you! Best regards, Daniel

Published 4 days ago

Using non-admin account for report purposes

Hi pgeorgiev, Glad that did it, and thank you for coming back to close the loop. One thing worth knowing: an application identity can be put in a user group, but only a group created in Devolutions Server itself. Groups that come from your directory are read only there, which is why the checkmark would not take. It is not specific to application identities. Before you do the other fifteen, one caution. Where a folder's Permission reads Inherited, what it gives comes from above it, and setting a View row to Custom replaces that instead of adding to it: a folder whose View list does not name you is refused outright. So everyone not on that list loses the folder, and everything under it. In the same dialog, in this order: set the folder's Permission to Custom, then set the View row to "Custom + Inherited" rather than "Custom" - that one keeps what is inherited and adds the identity on top. It is offered only on those individual rows, not in the Permission dropdown above them. Two exceptions. On a folder nested below another it will not help you, since there View follows what is granted above. And where a folder's Permission reads Allowed or Disallowed rather than Inherited, moving it to Custom changes the other rights on that folder, so leave those ones until you have looked at them. Best regards, Michel

Published 4 days ago

Kubernetes Deployment Documentation

Just curious if there was any movement on this? Would be great to have this deployment as an option. Thanks

Feature Request

William Alphonso

Published 4 days ago

Database retention policies don't work

Hello, Thank you for the confirmation. Now we just need to keep an eye out to see if the automatic cleanup runs normally. I would suggest capturing the number of rows in the Archived tables and see if the number changes in a couple of days. Best regards,

Daniel Albrecht

Published 4 days ago

Database retention policies don't work

OK, good to know! Thank you! btw I also completed Step 3 from the script (Shrinkfile + Index rebuild)

William Alphonso

Published 4 days ago

Database retention policies don't work

Hello, Thank you for the confirmation. For the Archived logs, I would suggest archiving earlier than 2 years. Archived logs are still accessible but they will only be loaded when required instead of being loaded when you open a vault. When you open a vault, you are loading the entries and all logs attached to these entries that are not archived. By archiving these logs (let's say older than 1 month as an example), we can accelerate the process of opening vaults. Then when you open the log tab on an entry and select a filter that contains logs older than 1 month, then archived logs will be loaded for that specific entry only. Best regards,

Daniel Albrecht

Published 4 days ago

Database retention policies don't work

It worked! Your new script's output from Step 2: ARCHIVE LogMessage -> LogMessage_Archive : 0 rows moved PURGE LogMessage_Archive : 0 rows deleted (older than 36 months) ARCHIVE LogMessage_Old -> LogMessage_Old_Archive : 696062 rows moved PURGE LogMessage_Old_Archive : 654813 rows deleted (older than 36 months) ARCHIVE BackupLog -> BackupLog_Archive : 0 rows moved PURGE BackupLog_Archive : 0 rows deleted (older than 36 months) ARCHIVE ConnectionLog -> ConnectionLog_Archive : 222 rows moved PURGE ConnectionLog_Archive : 0 rows deleted (older than 36 months) ARCHIVE ConnectionHistory -> ConnectionHistory_Archive : 81781 rows moved PURGE ConnectionHistory_Archive : 76883 rows deleted (older than 36 months) ARCHIVE LoginAttempt -> LoginAttempt_Archive : 0 rows moved PURGE LoginAttempt_Archive : 0 rows deleted (older than 36 months) ARCHIVE LoginHistory -> LoginHistory_Archive : 1 rows moved PURGE LoginHistory_Archive : 0 rows deleted (older than 36 months) ARCHIVE UserInfoHistory -> UserInfoHistory_Archive : 0 rows moved PURGE UserInfoHistory_Archive : 0 rows deleted (older than 36 months) ARCHIVE PamLog -> PamLog_Archive : 0 rows moved PURGE PamLog_Archive : 0 rows deleted (older than 36 months) ARCHIVE PamHeartbeat -> PamHeartbeat_Archive : 0 rows moved PURGE PamHeartbeat_Archive : 0 rows deleted (older than 36 months) Archive + purge done. It ran for about 6 minutes. Here's my summary after the manual cleanup: [image] Entries older than 2 years were moved to _Archive tables, Entries older than 3 years were permanently deleted. I'll check tomorrow if the automatic cleanup works now. Thank you!

elaineberenguer

Published 4 days ago

Domain attribute of PAM accounts not retrieved after updating to 2025.3.7

Hi! There were any updates about this? When trying to open an RDP session to one of our domain TS Servers, the JIT PAM account credential (domain user) doesn't work because of the missing DOMAIN information... As I don't know the password, it's pretty impossible to authenticate... :P [image] I tried to add the domain suffix in username field new entry, but it's not supported. Can you help me how to achieve this or if I'm doing anything wrong (I'm trying Devolution's PAM solution). Thank you in advance. Regards, Elaine Berenguer

William Alphonso

Published 4 days ago

Database retention policies don't work

Hello, I sent you a revised script with everything needed to run a test and the full cleanup. Please let me know if this new version helps. Best regards,

Daniel Albrecht

Published 4 days ago

Database retention policies don't work

Thank you! I have built a list of database table names based off the existing _Archive tables and the Log categories listed in the settings UI: Logs Backup Logs BackupLog BackupLog_Archive Connection logs ConnectionLog ConnectionLog_Archive Login attempt LoginAttempt LoginAttempt_Archive Login history LoginHistory LoginHistory_Archive Message Logs (Log messages?) LogMessage LogMessage_Archive LogMessage_Old LogMessage_Old_Archive PAM logs PamLog PamLog_Archive User info history UserInfoHistory UserInfoHistory_Archive PAM Checkout PamCheckout PamCheckout_Archive Heartbeat PamHeartbeat PamHeartbeat_Archive Connections Connection history ConnectionHistory ConnectionHistory_Archive Privileged sessions monitoring Remote sessions RemoteSession RemoteSession_Archive Traffic events TrafficEvent TrafficEvent_Archive But with some tables (most importantly ConnectionHistory) I'm not sure which field to use to compare the "DeleteBefore" timestamps Currently I'm looking at the following fields, but I'm not sure they are the correct ones: BackupLog.StartDate, BackupLog_Archive.StartDate, ConnectionLog.CreationDate, ConnectionLog_Archive.CreationDate, LoginAttempt.CreationDate, LoginAttempt_Archive.CreationDate, LoginHistory.CreationDate, LoginHistory_Archive.CreationDate, LogMessage.CreationDate, LogMessage_Archive.CreationDate, LogMessage_Old.CreationDate, LogMessage_Old_Archive.CreationDate, PamLog.DateTime, PamLog_Archive.DateTime, UserInfoHistory.ModifiedDate, UserInfoHistory_Archive.ModifiedDate, PamCheckout.CheckoutDateTime, PamCheckout_Archive.CheckoutDateTime, PamHeartbeat.HeartbeatDateTime, PamHeartbeat_Archive.HeartbeatDateTime, ConnectionHistory.ModifiedDate, ConnectionHistory_Archive.ModifiedDate, RemoteSession.StartDateTime, RemoteSession_Archive.StartDateTime, TrafficEvent.ConnectedAt, TrafficEvent_Archive.ConnectedAt These tables have multiple datetime fields for example: BackupLog.StartDate, BackupLog.EndDate ConnectionHistory.ModifiedDate, ConnectionHistory.CreationDate, TrafficEvent.ConnectedAt, TrafficEvent.DisconnectedAt, TrafficEvent.CreatedAt By the way, I think "Message Logs" should be changed to "Log messages" in the UI Here's an overview of our log table usage currently: [image] Best regards, Daniel

William Alphonso

Published 4 days ago

Database retention policies don't work

Hello, Sorry about the issue with the script. Yes, I would suggest cleaning any table that has an _Archive version. My script was done some time ago and new tables were added to logs so it is possible that some might be missing from my original script. I will look at cleaning it up. Best regards,

Published 4 days ago

Passkey Support for Devolutions Server

Hi gernoth , A YubiKey should work with the Passkey MFA option that we’ve added in DVLS 2026.1. We left the YubiKey option there as to not lock out users relying on it, but I would recommend using the Passkey option over the YubiKey OTP option. Cheers,

Feature Request

fritzzzzzzzzzzzzzzt

Published 4 days ago

Multiple passkey support per user

I completely agree with this. We are facing the same issue in our environment. We deliberately do not use an external identity provider such as Microsoft Entra ID/Azure AD, because we want to keep our password management infrastructure as isolated as possible from the rest of our corporate identity environment. For us, being able to register multiple passkeys per user is therefore really important. Users need to be able to use separate passkeys on different devices while still keeping the password vault protected with a strong, phishing-resistant MFA method. Hopefully this will be included in one of the upcoming updates soon. We would definitely appreciate this feature as well!

Feature Request

Published 4 days ago

Passkey Support for Devolutions Server

Hi Luc Fauvel thank you very much, real passwordless sign in would be nice too. But at the moment Yubikey is only supported as TOTP, not as a physical safe for passkey. Would be nice if Yubikey woul also get real Passkey support, not only TOTP. Thank you!

Feature Request

Published 4 days ago

Multiple passkey support per user

Thank you very much. We are not using external identity providers like Microsoft Azure on purpose (because we do not want that our password safe gets exposed when a user in Azure gets hacked). So the devolution internal passkey is the only really secure way to separate password safe from working environment, and a second passkey is really missing here. Great when it's on the roadmap, hopefully more on the short term than too long :-). Looking forward to it!

Feature Request

Daniel Albrecht

Published 4 days ago

Database retention policies don't work

Hi William! I ran the manual cleanup for a longer retention period (2 years archive, 3 years delete instead of 1 year archive, 2 years delete) The script you sent me had a problem though: It adds the retention time rather than subtracting it from the current date, so it would move/delete all the logs, not just old logs. -- Define variables for retention periods DECLARE @NumberOfMonthToArchive INT = 12 DECLARE @NumberOfYearToDelete INT = 10 DECLARE @ArchiveBefore DATETIME = DATEADD(MONTH, @NumberOfMonthToArchive, GETDATE()); DECLARE @DeleteBefore DATETIME = DATEADD(YEAR, @NumberOfYearToDelete, GETDATE()); -- For testing SELECT @ArchiveBefore, @DeleteBefore -- Output (executed on 2026-08-20): -- 2036-08-20 09:45:53.923 -- 2027-08-20 09:45:53.923 I fixed the script before running it by adding minus signs I also ran this query to get an overview before and after the manual cleanup: Before: [image] After: [image] I will wait some time and check if the automatic cleanup works now. Do you think I should also manually clean up the LogMessage_Old table? It has the most (and oldest) records here. There's also the ConnectionHistory table, which I forgot to include in the overview query. It also has over 89k entries, and should be included in the cleanup according to the settings GUI. Thank you! Best regards, Daniel

External resources

Devolutions Documentation

Technical SupportEmail : service@devolutions.netPhone : + 1 844 463.0419