davidyates

HI @Luc Fauvel Do you know if there's any update on this, this would be a really convenient feature to extend a check out without having to check in and then back out again.

Hello @davidyates ,

Thanks for reaching out.

The system seems to snag on reading 'netbiosName' from the currently configured group.

I could not replicate in my environment; the check box does the trick.

I'm using DVLS 2026.1.12.

Maybe you have a different version? Thanks for confirming

Given that this was an admin group, is it safe to assume it doesn't have specific permissions on Vault/Folders/entries?

If that's the case, I think we could try deleting and re-importing it.

Thoughts?

Best regards,

@Alexandre Bélisle

Hi Alexandre

Yep, that seemed to have done it (deleteing and re-importing)

Thanks for the suggestion!

Dave

Hello Everyone!

I wonder if someone could help, or has come across this issue before. We are currently evaluating the Devolutions Team Starter Pack and trying to get Gateway to work with Devolutions Server via an Azure/Entra Reverse Proxy/ Application Proxy.

Current Setup:

We have a Windows 2025 server installed on prem running Devolutions Server with a side-by-side installation of Gateway server. We have existing Azure connectors on the LAN for other applications, so we have created a Enterprise Application in Azure to access the Devolutions Server via web and RDM with MFA SSO Enabled. This is all working fine and we can access our estate on RDM and Devolutions server using this setup.

Issue:

When trying to configure the Gateway server using the same reverse Proxy address within Devolutions server, it fails on the ping test and therfore marks it as "down". If we specify the internal address for the Gateway server it finds it and works without issue, however when connecting to sessions via the Gateway server, this only works when on the internal network, externally it fails (even though if we go into a RDP entry within the vault and test the Gateway connection, it passes)

Reading the forum post here (Best practices for Devolutions Server & Gateway deployment) it sounds like the Gateway server should be accessible via the same URL as the Devolutions server because the IIS handles the redirects. Has anyone got this to work using the same entra reverse proxy address?

Thanks!

Dave

We currently have 2 Entra-synced groups into DVLS, one for Administrators and one for Users. We since then found out that Administrators have access to all entries in PAM vault, so I tried moving myself from Administrators to Users, but doesn't seem to have made a difference. So my next step was to de-select "Is administrator" tickbox within the group and then specifically assign permissions to the group. However when deselcting and trying to save settings we get the following errors:

TypeError: Cannot read properties of undefined (reading 'netbiosName') at i.onSave (https://<SERVERNAME>/dvls/chunk-YGRHIQBO.js:1:91037) at https://<SERVERNAME>/dvls/chunk-YGRHIQBO.js:1:83874 at Tf (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:7:74231) at Object.o [as next] (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:7:74400) at Ui.next (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:3484) at be._next (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:3208) at be.next (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:2935) at https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:5944 at zt (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:2326) at ya.next (https://<SERVERNAME>/dvls/chunk-4HFZZ7HS.js:3:5783)

I've replaced our server URL with <SERVERNAME> just to clarify that it's now actually saying that/using that variable