Runas Credentials formatting for Macros/Scripts/Tools

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

@Stephan Haupt


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

Unless I am doing something wrong it looks to be actually parsing the username for the domain.

I wasn't expecting that at all. I have included screenshots below.

What I will also do is create all an all new cred and server to make sure nothing is being retained somehow.

No, same thing. I created "Another Example" credential "johndoe2@adr.mydomain.org" and left everything alone so it should be passed just as typed.

Forgive me for all the screenshots, I wanted to make sure I was doing as you are asking. :-)



and the test.....

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

@Stephan Haupt
Is there anything else I can test regarding this?

Hi,

Thank you for the detailed testing — that's really helpful, and it points us toward the documented approach for this scenario.

The built-in RUN AS DIFFERENT USER option resolves the credentials for you at launch (https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/run-as-another-user/built-in-runas). Since the UPN form is the one that works in your environment and it isn't what's reaching RUNAS, the documented alternative for this is the MANUAL RUNAS method (https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/run-as-another-user/manual-runas), where you specify the RUNAS command yourself so the username is passed exactly as you write it.

For your case, that would be a Command Line (Macros/Scripts/Tools) entry with the command set to:

runas.exe /netonly /user:username.admin@ad.example.com "mmc compmgmt.msc /Computer=COMPUTERNAME"

(substituting your real UPN and host). With RUN AS DIFFERENT USER left OFF on that entry, RDM runs the command exactly as written and you'll get the password prompt — the same result as your manual test.

If there are still issues, please let me know your exact RDM Version, the Workspace you use and Windows Version.

Best regards,
Stephan

Hi,

Thank you for the detailed testing — that's really helpful, and it points us toward the documented approach for this scenario.

The built-in RUN AS DIFFERENT USER option resolves the credentials for you at launch (https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/run-as-another-user/built-in-runas). Since the UPN form is the one that works in your environment and it isn't what's reaching RUNAS, the documented alternative for this is the MANUAL RUNAS method (https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/run-as-another-user/manual-runas), where you specify the RUNAS command yourself so the username is passed exactly as you write it.

For your case, that would be a Command Line (Macros/Scripts/Tools) entry with the command set to:

runas.exe /netonly /user:username.admin@ad.example.com "mmc compmgmt.msc /Computer=COMPUTERNAME"

(substituting your real UPN and host). With RUN AS DIFFERENT USER left OFF on that entry, RDM runs the command exactly as written and you'll get the password prompt — the same result as your manual test.

If there are still issues, please let me know your exact RDM Version, the Workspace you use and Windows Version.

Best regards,
Stephan

@Stephan Haupt


So, if I am hearing you correctly, I have to manually duplicate the built-in tools rather than being able to just edit them? This seems needlessly cumbersome. Why is the credential formatting able to be altered in most all other areas but we cannot change the formatting passed to the RUNAS command?


Also, when I create a new tool, it just puts it under "Template" .... I do not find a place to sort created tools into categories.


I created a new example "tool/script" as shown below. This does appear like it will work, but again, seems messy long-term to re-create duplicate built-in entries. Also, when I create a new tool, it just puts it under "Template" .... I do not find a place to sort created tools into categories.

I did see where I could "turn off" the specific items... but this again just seems like the process would be

1. Duplicate manually (since I can't seem to copy) the built-in tools
2. Turn off the tools in Settings > Tools > Available Tools
3. Have multiple re-created tools unsorted in a list under "Templates"

I very much appreciate your help in finding a workaround, however, I feel like this is something that needs a bit more attention for user experience.

Can this be looked at for a better solution as either a feature request or enhancement? Thank you again. :-)

Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8655
Experience Windows Feature Experience Pack 1000.26100.315.0

RDM Version - 2026.2.11.0 64-bit (PreJIT)
Data source type: SQLite

I guess this is all I'll hear about this.... I really wish something could be done about this as it's been really cumbersome to create the SAME tools for every machine just because we can't have a formatting change like most other places.

Hi,
My apologies for the delayed follow-up and for leaving you without an update. You are absolutely right to raise the usability concern.
I have now reached out internally to our development team for clarification on whether this behavior is expected and whether there is room to improve UPN formatting support for the built-in Run As Different User workflow.
I will update this thread once I have more information from the team.
Thank you for your patience, and for all the detailed testing and feedback you have provided.
Best regards,
Stephan

Hi,
My apologies for the delayed follow-up and for leaving you without an update. You are absolutely right to raise the usability concern.
I have now reached out internally to our development team for clarification on whether this behavior is expected and whether there is room to improve UPN formatting support for the built-in Run As Different User workflow.
I will update this thread once I have more information from the team.
Thank you for your patience, and for all the detailed testing and feedback you have provided.
Best regards,
Stephan

@Stephan Haupt
Thank you so much for looking into this further! :-)