admindin

Starting with the new beta version of RDM 2026 it's no longer possible to simply press enter when entering a search in the filter box to open a session.

This worked with all versions before and it would be nice, if that could be solved.

Hello,

Thank you for reaching out!

My name is William, and I'm here to assist you in any way I can.

This error is related to the certificate attached to your Devolutions Server. It looks like RDM sees that the URL used by the Devolutions Server doesn’t match the certificate’s CN/SAN issuer. Could you confirm that the URL used by the Devolutions Server matches the Hostname listed in the certificate?

Best regards,

@William Alphonso

Hi William

Meanwhile I guess I figured out what the issue is. Our access URI has uppercase and lowercase letters but not within the domain, only after the domain.

Changing the Access URI to all lowercase letters seems to fix the issue, but that's not a solution, since I would have to update all the configurations on our RDM user installations.

And to be honest, it does not make any sense to check for the part behind the FQDN if it's "matching" the certificate, since the certificate only contains the FQDN (in lowercase) of the server, nothing behind.

It seems that RDM 2025.3 has changed something in certificate checks, because RDM 2025.2 does not complain about this uppercase/lowercase issue.

Hello,

Thank you for reaching out!

My name is William, and I'm here to assist you in any way I can.

This error is related to the certificate attached to your Devolutions Server. It looks like RDM sees that the URL used by the Devolutions Server doesn’t match the certificate’s CN/SAN issuer. Could you confirm that the URL used by the Devolutions Server matches the Hostname listed in the certificate?

Best regards,

@William Alphonso

Hi William

Yes, I can confirm that the URL used for our Devolutions Server matches the hostname within the certificate. The Edge Browser or any other browser does not complain about the certificate not being valid.

It's a certificate of our internal Certification authority, the root Certificate is available on the machine.

And as I told, all 2025.2 version do not show any error.

Best regards

Just tested the new beta version of RDM (2025.3.10.0). While RDM tries to connect to our Devolutions Server, we receive the following error message. RDM 2025.2 versions work fine.

Any news on this issue? The newest build .32 still has this issue

Great news, thank you for the update.

Yes, please. Thank you in advance.

There must have been a change in code, since the older versions are still correctly working with $USER_PRINCIPAL_NAME$

Unfortunately, we cannot use both. $USER_PRINCIPAL_NAME$ gives us the authentication loop and %username%@ourdomain.com reports back the sAMAccount Name in our case, not the UPN. Although the device is Azure AD only.

Using the full e-mail address, it's working, but that's not a solution to deploy the new version to all our users.

Hi Richard

Any news regarding the Azure AD only authentication issue?

Best regards

René

That's exactly what I do to test new versions on my device. I have installed the msi version for daily use and the bin version for testing.

It's happening with the bin version as well on another computer with a msi version installed.

I will send an email on Monday, so we can have a remote session to analyze.

Thanks in advance for your help.

Hi Richard

Yes, it's hapening to all users, I've tested with it. Luckily I have not yet rolled out the new version to all users.

I have even added a new Microsoft 365 account on the Devolutions Server and logged into a computer with that account, where this user have never logged on before.

Same behaviour. The browser pops up again and again, asking to authenticate.

Best regards

René

Hi Devolutions Team

Starting with version 2022.3.26.0 we are facing a logon loop when using Microsoft authentication.

This does not happen with version 2022.3.24.0 and older, but still in version 2022.3.27.0.

What happens when starting RDM is, the browser is opening up, I click on the "Microsoft" button, it authenticates and the same browser windows opens again and again.

Could you please have a look at this issue?

Our Devolutions server is up to date with version 2022.3.7.0.

Best regards

René

Hi Richard

Thank you for your quick response. I know about the shortcuts, but it's not what we would like to see.

It would just be "nicer" if multiple vaults could be shown.

We the legacy permissions you could see all your folders at once, where you're permitted to. With the vaults it's kind a tricky, when permanently working on servers on different locations (would be different vaults) and sometimes slow to switch between them.

We would have around 40 different vaults. But I guess I will simply go with showing all entries to everyone to no longer use the legacy security groups.

Thank you anyway.

Hi everyone

Previously we used the legacy Security Groups on our Devolutions Server to only show our worldwide administrators the folder they belong to.

With a new installation of Devolutions Server we would like to switch to Vaults, but the handling wo permanently switch vaults with the drop down list is quite annoying.

So, is there probably a way, to show all vaults within the navigation pane one below the other without having to switch between vaults?

Can confirm, it's fixed. Thank you very much.

Unfortunately, the custom installer for 2021.1.20 produces 0 KB msi and exe files at the moment.

Hello Rene,

You will need to upgrade both Devolutions Server and RDM at the same time. If one is at version 2020.x and the other 2021.1, you will receive a prompt saying you need to upgrade to be able to connect.

Best regards,

Hi Richard

Thanks for the info. Then we have to wait, until RDM 2021 is released for Custom Installers, since we have around 40 clients using RDM and we need to deploy it using our internal software deployment tool with custom msi.

Best regards

Since Server 2016 it's difficult to see, if a server has been rebooted with the "Check is online" function.

That's not a bug of RDM, it's more an "issue" of newer Windows versions, where RDP is still available, while starting the reboot of a server.

Maybe you'll be able to find a way to improve the "Check is online" function within RDM, to "really" check if the server is back online after a Windows Update has been installed.

Maybe some kind of function, that check is online will only reconnect to the server, if at least one or two pings have been missed, since starting "Check is online".

I often use this function to reconnect to a server after doing Windows Updates.