gbbiv

We tried numerous permutations of the advanced tab options within RunAs without success, then we ran into another user on our team who was working and noticed that the Advanced Tab on his PVWA credential was Field/Address and he was working... ours was Field/Domain and worked for RD connections but not RunAs connections... he switched and his also failed, we switched an ours also worked. So that seems to be the solution for both to work you need to be set as Field/Address on the credential. Thanks for your help.

Outside of RDM I can do a Run As and use the credentials and it works.

Under the Run As tab, if I choose Credentials = None... then the app opens but it has the credentials of the current windows user rather than the Privileged Account I am trying to use.

I'm not sure where you are suggesting that I copy/paste the Privileged Account info... can you clarify please?

We have successfully been using PVWA Credentials to launch SSMS (and other applications like Chrome), we were using the RADIUS authentication method without any problems. Now we have a use case where we need to use PVWA Credentials to do the same thing but using LDAP authentication and it is failing. There error message says Unable to execute the command line, "The stub received bad data".

Only other changes are to set Run As to Current Session and the launch the entry with the PVWA credentials. The same credential entry works fine to launch Remote Desktop session.

Seems like it might be nice to add Microsoft Remote Assistance Connections...

Also I wonder if it would be a good idea to refresh the config from the server before allowing someone to edit. Right now if you don't refresh your session and you edit you'll stomp on anyone else's edits.

_Great_ product by the way!!! ;)