Credentials issue in 6.0

Hi,
You are not the first person to tell about this. I'm investigating.

Can you send me a rdm file (clone and change the server) that you have a problem. I will look at it. Does it work in embedded or external mode? Can you try?
edited by dhervieux on 3/8/2011

Example connection attached. I run all connections embedded, but I tried external, and got the same result. Oh, and just to clarify, this was not an issue on 5.9.

I found a workaround for this. For some reason, the Windows Credentials saved in the Credential Manager are never retained on my PC after a reboot, but those saved under Generic Credentials are. I decided to manually save my TS Gateway credentials in the Generic section, and now I am no longer prompted for them by RDM, so it appears that's what it was reading.

However, on a co-worker's PC, also running Windows 7, his Windows credentials are retained in the Credential Manager after reboot, and RDM is successfully reading those, no Generic credentials necessary. Looking online, the issue of Windows credentials not being retained after reboot seems to be a somewhat common issue for Windows 7 PCs, and I can't help but think that issue is related to this somehow.

Anyway, the workaround works good enough for me, so I'm happy for now. I hope the above information is useful for you to track down the root cause.

Hi,
I can add an option to save it in the Generic credential, it's very easy, will you try it ?

Sure, I can try that. In the meantime, I'm going to continue trying to figure out why the Windows credentials aren't saving after reboot.

Hi,
I verified and it's already a generic credential, I don't know what might be the problem. I will keep an eyes and see if there is something else I can do.

Oh, so RDM 6.0 is already set to use the generic credentials? That actually might explain why it's now refusing to read the Windows credentials from the credential manager now. Did this change from previous versions of RDM?

No,
it's was this way for a long time, I verified.

It's not possible for an application to read the Domain credential from the vault. It's by design by Microsoft for security reason. It's possible to enter a domain credential that can be read, but not from the Microsoft tools, only by programmings.

Hmm, very strange, because I've never had anything stored in the generic credentials before, so if RDM never read the generic credentials, the MS RDP client itself must have been pulling those credentials from the vault. What's strange is that if I didn't have anything at all stored in the Windows or generic credentials, and when prompted for TS Gateway credentials, I chose to save them, they would save to the Windows credentials in Credential Manager, as they always have. However, the first time I tried any connections in RDM that use TS Gateway, the first time after saving them, I get a TS Gateway credential prompt with an error message stating that the login failed, as if RDM or the RDP client was passing through incorrect credentials, and every subsequent attempt to use a TS Gateway session from RDM just gives an ordinary prompt for TS Gateway credentials, no error message.

Here's where it gets even stranger. On my Windows 7 Pro PC, and also on a co-worker's Vista Business PC, we had to switch to generic credentials for this to work. But on another co-worker's Windows 7 Pro PC, it continues to pass-through the stored Windows credentials for TS Gateway as it always has, just like in previous versions of RDM. I thought the issue for me might be caused by whatever is causing my stored Windows credentials to be wiped out after every reboot, but the co-worker with Vista Business does not lose his Windows credentials after reboot, and still has this problem with TS Gateway credential pass-through, so that seems to rule out that theory.

Is there any kind of verbose logging I can enable to see exactly what RDM is doing when it tries to launch a TS Gateway connection?

I just discovered something. If I manually save a set of Windows domain credentials in the vault, and try to connect to a TS Gateway session in RDM, I will get a prompt for credentials with an error stating "The login attempt failed." At that point, the stored domain credentials in the vault get deleted. It almost seems as if it sees that their are credentials there, but they get deleted first, and then it attempts to read them, and then ends up passing blank credentials through to the remote server, which of course fails. I have no idea what's causing this, but if it's not something in RDM, I don't know what else. The standalone RDP client on my PC has no problem reading the saved credentials and passing them through.

RDM is only invoking mstsc, so we don't do anything special, we just set the credential. We can try to do the reverse, let RDM set it as a domain credential instead of a generic, do you think that it could help ?

If you want to make an option for that, that's fine. Really, setting the generic credentials manually works okay, so I can live with that. I'm just the kind of guy that hates it when there's a problem I can't figure out, especially when it's on my own computer. ;)
edited by ivorycruncher on 3/15/2011

Hi,
Can you try this version, in the application Option, Advanced tab page, you will find a RDP gateway credential setting:

http://remotedesktopmanager.com/download/Setup.RemoteDesktopManager.6.0.0.0d.exe

Okay, I finally got some time to try that. Now here's what's funny. With the "Use RDP Gateway generic credential" option enabled, now when I get prompted for credentials, and choose to save them, they get saved in the Windows Credentials section of the credential manager, just like they used to. Also, RDM is ignoring anything stored in the Generic Credentials section of the credential manager.

I would say go ahead and roll this option into the next main release. It will be nice for people to have the option, especially if they have a messed up PC like me. :)

I've same problem. After some searches it found out that problem is with RDP 7.0. Yoy can read more here:
http://blogs.msdn.com/b/rds/archive/2007/07/31/problems-using-saved-credentials-with-vista-rdp-clients-and-above.aspx