How to use host IPs for folder type "Workstation" for RDP sessions?

Hello,

Thank you for contacting us on that matter!

In the latest versions of RDM, it is now possible to use inheritance to have sessions inherit their Host from their parent folder.

Any session that uses the "Inherited" option for its "Host" parameter will retrieve its host from the parent folder.



Let me know if that helps!

Best regards,

Thanks, I overlooked that dropdown! That's exactly what I searched for. Though, things don't seem to work for me:

The Workstation folder is able to maintain host name and IP. I have some configs for which only one of both is valid, namely the IP. Reason is VPN connections, SSH tunnels etc. which need to be established first, preventing name resolution in some setups. It seems that if I put host name and IP into Workstation folder, the host name is always used in case a RDP session inherits the host. OTOH, if I don't put a host name into the workstation folder, the RDP sessions errors out entirely. Would be great to have something like "Inherited (Host)" vs. "Inherited (IP)". RDP sessions can easily take either a host name or an IP on their own.

Hello,

Thank you for your response!

Although I understand that the Workstation folder type contains both a Host and an IP field, the Host inheritance feature was created as a more general option for all folder types, including most that do not have a separate IP address field.

Basically, to have anything inherited in the Host field of your sessions, you would need to enter it in the Host field of the parent folder, even if it is not strictly a Host in the proper sense.

Let me know if that can work for you!

Best regards,

That works perfectly for me, thanks! Should have simply tried it... :-)

I've just recognized one additional thing: When exporting a RDP session into a RDP file from Remote Desktop Manager, the inherited host IP is not embedded into the file. Is that by design or a bug or ...? Would be great if the RDP file would be usable, especially as the host IP is available in general.

Hello,

Thank you for your response!

Unfortunately, it is not possible to export a session using the Linked (Vault) credential mode and include the credentials directly in it. By design, it will be exported with that credential mode. To keep the link functional when exporting and importing, you would need to also include the Credential entry linked to your session in your export file.

Let me know if that helps!

Best regards,

I'm not exporting to import again, but instead am exporting to forward the RDP file to external people, so that those can access a system I have configured for me. Including the available host IP in those case would prevent me from additional manual customizations to the file.

Hello,

Thank you for your response. For the time being, the only two options to export your sessions with the credentials included would be to export both the session and credential entries, or to use the Custom credential mode to save your credentials directly in your session entry instead of using the Linked (Vault) credential mode.

If neither of these options really works for you, I could ask my supervisor to move this thread to the Feature Request section of our forum so you can request something that works better for your use case to our engineering team.

Best regards,

Just to make that clear: It's not about credentials, but an inherited host IP. I'm not using "Linked (Vault)", but "Inherited" instead. Making a feature request would be great, I can't see why the host IP/name should not be forwarded in my use case.

Hello,

First of all, I would like to apologize for mentioning credential inheritance in my last response. Since the option to inherit Hosts is pretty new, I'm still used to writing about inheritance relating to credentials. By automatism, that's what I did in my last reply, but I actually meant to write about Hosts. The same principle I mentioned when referring to credentials also applies to hosts.

With that said, since this thread has been going on for a while, to make sure that our engineering team receives the request properly, I have been authorized to open an internal ticket directly to request the feature instead of moving the thread.

We will keep you updated as progress is made on this feature request!

Best regards,