How to switch data source to online mode in RDM PowerShell?
Hi!
I'm trying to edit entries using a PowerShell command, but it seems the Devolutions PowerShell module is in Offline mode and changes are not being synced correctly. There's no Windows Hello verification or Entra authentication popup, which RDM UI will usually show. It just loads the data source in offline mode. There's the Cmdlet 'Get-RDMOnline'. Is that meant for switching to Online mode? It doesn't do anything. (Also 'Get' should not be used for Cmdlets that modify a state.)
How to I switch to Online mode in RDM using Devolutions PowerShell?
PowerShell 7.6.7
C:\Users\da
PS7› Get-RDMCurrentDataSource | select ID,Type,IsConnected,IsDefault,IsOffline
ID : 3101d1a9-8f87-4d62-85d8-20fa05ac1cad
Type : RDMS
IsConnected : True
IsDefault : True
IsOffline : True
C:\Users\da
PS7› Get-RDMOnline
C:\Users\da
PS7› Get-RDMCurrentDataSource | select ID,Type,IsConnected,IsDefault,IsOffline
ID : 3101d1a9-8f87-4d62-85d8-20fa05ac1cad
Type : RDMS
IsConnected : True
IsDefault : True
IsOffline : TrueThank you!
Cheers, Daniel
All Comments (4)
Hello @Daniel Albrecht,
We think this might be related to a problem we recently fixed for DVLS logins in PowerShell. If it is, the fix would go out with our next release. But to confirm, can you tell us:
The version of the module you're using
In your workspace's settings, in the Advanced tab, is "Auto-go offline" checked? Also, what's your authentication browser mode set to?
In File > Settings > Advanced > Authentication, is 'Use embedded browser for login' checked?
Until the fix ships, if the issue is what we think it is, it should be avoidable by connecting with an application identity, which avoids the normal sign-in flow.
(Agreed that we should change the verb for these cmdlets.)
Best regards,
Christian
Hi Christian!
The PowerShell module is version 2026.3.2.0. The installed RDM is still on 2026.2, because we use the Extended Maintenance version.
Auto-go offline is enabled
Embedded browser login is disabled
Thank you!
Hello @Daniel Albrecht,
That matches the failure we've investigated and fixed. The fix will be in the next release. Until then, as mentioned, using an application identity should avoid it. Another way to avoid it would be to set that workspace's Authentication browser mode to Embedded, in its Advanced settings.
Best regards,
Christian
Hello,
Thank you for your patience while our team looked into the issue you reported.
I'm happy to let you know that the latest version of the Devolutions.PowerShell module (2026.3.3) includes a fix for this problem. You can get it from the PowerShell Gallery here:
https://www.powershellgallery.com/packages/Devolutions.PowerShell
If the module is already installed, you can update it with the following command:
Update-Module -Name Devolutions.PowerShell
Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.
Thank you for your collaboration.
Best regards,
Maxim Robert