"Run us" for Macro / script does not work as intended.
Hi there,
first, all the best for the New Year.
Have here the latest Windows RDM.
I would like to start the RSAT tools with a another user, this only works to a limited extent.
As a base that these instructions.
https://help.remotedesktopmanager.com/index.html?tipsandtricks_mmc.htm
and
https://help.remotedesktopmanager.com/index.html?tipsandtricks_runas_builtinrunas.htm
"Run as different user" was activated under Advanced Options.
With the "default" execution mode, the program does not start.
If you select "Keep Command-Line opened" as execution mode, the program starts with a cmd session,
but after the program has ended, this cmd session remains open.
This is not helpful, because if you e.g. opens five RSAT tools, you also have five cmd sessions that must be closed.
What is the correct way, to use the built-in "run us" in this case?
thx for any help here.
Stefan
All Comments (9)
Hello,
Thank you for your kind wishes for the New Year! All the best for the New Year!
From what I understand, you are using the Macro/Script/Tool Command Line entry type. Could you please try with the Command Line Session entry type? It offers more RunAs possibilities that the Macro/Script/Tool. Moreover, there is no need to switch the Execution mode from Default to Keep Command-Line opened. So when you close RSAT, the tab in RDM will also be closed.
Best regards,
Érica Poirier
Hi Erica,
you guess right, currently i'm using Macro / Script / Tool Command Line entry type.
I am trying to do this with "Command Line Session entry type", but without success.
Although i selected the correct entry from the "Credential option" under "Run as" option,
RDM starts the RSAT Tool with the current session / login user and not as "run as".
Can you, if possible, show an example with an RSAT tool that starts with "run as" and Command Line Session entry type?
thx
Stefan
Erica,
found it out, "Keep Command-Line opened" is necessary, otherwise this error message.
Error.png
Hi Team,
Is there a solution here?
And what about the error message "The specified executable is not a valid application for this paltform",
regardless of whether "run in a 64bit mode" is selected or not.
thx for any help here.
Stefan
Hello,
I can reproduce the same exact behaviour on our environment as what you get with the RunAs configuration. I haven't found yet any other method to launch any RSAT tools as another user.
Because we are using the RunAs section of the Command Line Session entry type, RDM will automatically launch the session externally and it requires that the Execution mode needs to be set with Keep Command-Line opened. RDM will not be able to launch it in embedded mode and this will result having a tab that will not automatically close in RDM once you close any of the RSAT tools.
I will ask an engineer to have a quick look on this next week. I will keep you posted once I will get any information about if it's possible or not.
Best regards,
Érica Poirier
Thanks Erica for the quick reply, we wait until next week.
Your engineer may find a quick solution.
Best regards,
Hi Team,
any news here ?
Hello,
The issue hasn't been fixed yet. The engineer is working to try to find a solution to fix the "The specified executable is not a valid application for this platform" error message. Once an update will be available, I will keep you posted.
Best regards,
Érica Poirier
Hello Stefan,
Could you please try the latest RDM version 2020.1.16 and let us know if it's now working properly? This version contains a fix for the RunAs feature and you should not have to use the Keep command-line opened option anymore.
Best regards,
Érica Poirier