Trying to work out how I can change these settings back to default
Get-RDMUser appears to have boolean settings (true/false) - is there somewhere else it can be set?
CreateSQLServerLogin : True
HasPrivateVault : False
IntegratedSecurity : True
Password :
ServerUserType : 8
UserType : User
CanAdd : True
CanDelete : True
CanEdit : True
CanMove : True
ConnectionOverrides :
CreationDate : 1/1/0001 12:00:00 AM
CustomSecurity : <?xml version="1.0" encoding="utf-8"?>
<CustomSecurity>
<IntegratedSecurity>true</IntegratedSecurity>
<ContainedDatabaseUser>true</ContainedDatabaseUser>
</CustomSecurity>
DataSourceID : 00000000-0000-0000-0000-000000000000
GroupInfos :
HasAccessLauncher : True
HasAccessRDM : True
HasAccessWeb : False
HasAccessWebLogin : True
IsAdministrator : False
IsEnabled : False
IsLockedOut : False
IsNew : False
IsOwner : False
IsTemplate : False
LastLockoutDate :
LoginEmail :
78e00f0f-822f-4f67-8451-96727ed11b66.png
Hello sjames,
Thank you for contacting the Devolutions support team.
In theory, by setting it to "default" with this script, it should use the default configuration.
However, I found an issue with the PowerShell script on version 2025.3.
It looks like the change executed in PowerShell is not applied to your users in DVLS.
I will report this and let you know when it is fixed.
In the meantime, this is the script I use for one user:
$ds = Get-RDMDataSource | Where-Object { $_.name -eq "your data source name" }
Set-RDMCurrentDataSource $ds
$user = Get-RDMUser | Where-Object { $_.name -eq "user account" }
$user.HasAccessRDM = "Default"
Set-RDMUser $user
Best regards,
Patrick Ouimet