Apologies if this is solved somewhere else and I haven't found it.
TLDR: Trying to change the format used in Macros/scripts/tools" from domain\user to user@domain and I am not able to find where this is specifically set.
Have changed it in Credentials and on the machine specifically.
I'm trying to run from "Macros/Scripts/Tools" and I'm not able to. When I look at the command called in Process Explorer it is
PS C:\Users\EXAMPLE> runas.exe /user:ad.example.com\username.admin /netonly "mmc compmgmt.msc /Computer=COMPUTERNAME"
Replicating this in terminal I get....
Enter the password for ad.example.com\username.admin:
Attempting to start mmc compmgmt.msc /Computer=COMPUTERNAME as user "ad.example.com\username.admin" ...
RUNAS ERROR: Unable to run - mmc compmgmt.msc /Computer=COMPUTERNAME
1348: The validation information class requested was invalid.
Which gives the below from Google.
The Windows System Error 1348 (ERROR_BAD_VALIDATION_CLASS) occurs when your local computer passes an authentication format that the target identity provider or network resource does not recognize. This frequently happens on Microsoft Entra ID (Azure AD) joined devices or Intune-managed machines when a user attempts to use a legacy NetBIOS domain format (DOMAIN\username) to authenticate against an on-premises or cloud resource.
And I can confirm this works for me..... Although, it does require a elevated shell.
PS C:\Users\EXAMPLE> runas.exe /user:username.admin@ad.example.com /netonly "mmc compmgmt.msc /Computer=COMPUTERNAME"
Enter the password for username.admin@ad.example.com:
Attempting to start mmc compmgmt.msc /Computer=COMPUTERNAME as user "username.admin@ad.example.com" ...
PS C:\Users\EXAMPLE>MMC starts as expected.
Recommended Answer
Hello,
Thank you for being so patient!
I'm pleased to inform you that a new version of RDM (2026.2.14.0) has been released, featuring the fix for your issue.
Latest Version: Download RDM
Please let us know if this works or if you encounter any issues.
Best regards,
Maxim Robert
Hi jwoodard1,
Thanks for the detailed write-up!
There is a setting that may do precisely what you are after, without rebuilding the command. In the entry's properties, under the Advanced section, there is a USERNAME FORMAT dropdown. Setting it to {User}@{Domain} (or UPN) is worth a try here.

To confirm we're adjusting it in the right place, could you let me know:
- Your exact RDM version and Workspace you are using.
https://docs.devolutions.net/rdm/getting-started/workspaces#startup-workspace-1
Best regards,
Stephan
Hi jwoodard1,
Thanks for the detailed write-up!
There is a setting that may do precisely what you are after, without rebuilding the command. In the entry's properties, under the Advanced section, there is a USERNAME FORMAT dropdown. Setting it to {User}@{Domain} (or UPN) is worth a try here.

To confirm we're adjusting it in the right place, could you let me know:
- Your exact RDM version and Workspace you are using.
https://docs.devolutions.net/rdm/getting-started/workspaces#startup-workspace-1
Best regards,
Stephan
Thank you for the response. I have had to do this before so I did try to change this setting in both the entry and even created a new credential just for testing.
I filled in the UPN setting in the credential and re-tested. Nothing changed.
I'm away from things at the moment but I will make a note to try again.
I'm using the latest version of windows RDM as of the original posting and SQL Lite workspace in Windows 11.
Happy to do any further testing to help resolve the issue. 😊
Hi jwoodard1,
Thanks for the additional details — that's helpful context!
One more thing worth trying: rather than relying on the dedicated Domain field combined with the Username Format setting, could you try entering the credentials directly in the username field in UPN format (username.admin@ad.example.com), leaving the Domain field empty? This bypasses the formatting logic entirely and lets RDM pass the value through as-is.
Give that a go and let us know how it behaves!
Best regards,
Stephan