Connect to Devolution Server via Application identities
Hello,
I updated to Devolution Server 2025.1.4.0 from 2024.3.x and the Devolutions.Powershell Update to 2025.1.2.
Since the update I can't connect to my Devolution Server via Powershell.
This is my script to connect:
$key=(Get-Content -Path D:\PS_API\appkey.txt | ConvertTo-SecureString -Key (Get-Content -Path D:\PS_API\appkeyEncryptedPass.reg))
$appkeytmp = new-object -typename System.Management.Automation.PSCredential -argumentlist "Username",$key
$appkey=$appkeytmp.GetNetworkCredential().password
$secret=(Get-Content -Path D:\PS_API\appsecret.txt | ConvertTo-SecureString -Key (Get-Content -Path D:\PS_API\appsecretEncryptedPass.reg))
$appsecrettmp = new-object -typename System.Management.Automation.PSCredential -argumentlist "Username",$secret
$appsecret=$appsecrettmp.GetNetworkCredential().password
$dsname = "XXX"
$dsurl = "https://XXX/dvls"
$ds= New-RDMDataSource -DVLS -Name $dsname -Server $dsurl -ScriptingTenantID $appkey -ScriptingApplicationPassword $appsecret -SetDatasource
Set-RDMDataSource $ds
The command Get-RDMDataSource XXX return IsConnected False
What I am doing wrong or what has changed after the update?
All Comments (7)
Hello lukas06,
Thank you for reaching out to the Devolutions support team.
This is a known issue, and an internal ticket has been raised.
I have also added your forum information to this ticket.
With 2025.1 and the new RDM engine, we cannot connect to the database using this method for now.
Since it's related to the version, trying to connect on a 2024.3 version might be possible.
If you already have a portable version of RDM, I suggest this method:
https://docs.devolutions.net/powershell/rdm-powershell/rdm-powershell-core-module/#use-an-override-configuration-portable
Best regards,
Patrick Ouimet
Hello Patrick,
thank you for your response.
Do you mean I can connect to my 2025.1.4.0 Devolution Server with a Devolutions Powershell Version 2024.3?
Can you please write to this Ticket, if there are any new informations or the problem was fixed?
Hello Lukas,
As a workaround for now, even if it is 2025.1 DVLS, you can create a portable version of RDM 2024.3 and use this method to connect.
It is not the best way to do it, but its the only workaround I can provide for now.
To do so, you will need to do the following:
(Close RDM)
1- Download the .zip file below:
https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2024.3.31.0.zip
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe
5- Connect to your data source
6-Run the override script I have sent (both files are in the new folder)
7-Connect with the same method
Note that you will also have to uninstall module 2025.1 and install 2024.3.11.0
https://www.powershellgallery.com/packages/Devolutions.PowerShell/2024.3.11
And yes, I will post here when this will be fixed.
Best regards,
Patrick Ouimet
Hello Patrick,
could you post that override script you mentioned above?
We recently had to do an update to DVLS 2025, and i'm trying to get everything running again...
Right now when i set up a connection in RDM with TenantId und Secret, it redirects me to the browser to log on
(Authentication modes Domain and Devolutions Server, with domain as primary method)
Hello Hoppe,
Sure, this is the script to run.
$override = Get-RDMPowerShellOverride $override.OptionFilePath = "PathToCfg" # C:\RemoteDesktopManager\2023.1\config\RemoteDesktopManager.cfg $override.RemoteDesktopManagerExecutablePath = "Path to desired Remote Desktop Manager version" # C:\RemoteDesktopManager\2023.1\Devolutions.RemoteDesktopManager.Bin.2023.1.11.0\RemoteDesktopManager64.exe Set-RDMPowerShellOverride # Restart Powershell
Both paths will be on the portable version folder of RDM.
Best regards,
Patrick Ouimet
Hello,
This issue should be fixed on the module 2025.1.4.0.
Best regards,
Patrick Ouimet
Hello Patrick,
thanks for your reply. Now it is working fine.