[solved] How to mangage MS Windows Server via RDP

Latest response

Good morning folks,

It seems to be Monday and I got stuck while trying to access a MS Windows Server via RDP from a RHEL 7 host with GNOME Desktop.

The tool rdesktop which I'm familar with seems not to be available for RHEL 7. The RPM Package Search returned only sources for RHEL 6.

Althought vinagre claims to have RDP support in the GUI is not able to connect to a MS Windows host. In vinagre(1) I read that currently plugins exist for VNC and SSH, only.

What do you use to manage your Windows Server?

Best regards,
Joerg K.

Responses

Hi Jörg,

Although not being available from the official Red Hat repositories, you may want to check out Remmina.
It is a feature rich remote desktop application, which you can easily install on your system as a Flatpak. :)

sudo yum install flatpak
sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
sudo flatpak install flathub org.remmina.Remmina

Note : The flatpak commands don't explicitly have to be run with elevated privileges.
Start the application from the dash or execute flatpak run org.remmina.Remmina.

Regards,
Christian

Hello Christian,

At the end I've chosen the solution you provided, because Remmina fits my needs at best. Thank you for that recommendation.

Best regards,
Joerg

You're welcome, Jörg ! :)

I did a yum search "rdp" from a RHEL7 system and got the following hits.

freerdp-libs.i686 : Core libraries implementing the RDP protocol freerdp-libs.x86_64 : Core libraries implementing the RDP protocol freerdp-plugins.x86_64 : Plugins for handling the standard RDP channels libguac-client-rdp.x86_64 : RDP support for guacd xorgxrdp.x86_64 : Implementation of xrdp backend as Xorg modules xrdp.x86_64 : Open source remote desktop protocol (RDP) server xrdp-devel.x86_64 : Headers and pkg-config files needed to compile xrdp backends xrdp-selinux.x86_64 : SELinux policy module required tu run xrdp freerdp.x86_64 : Remote Desktop Protocol client

Freerdp is From repo : rhel-x86_64-server-7 and xrdp is from Repo : epel/x86_64

Freerdp is the the client and I included xrdp though it is a server if ever you need one. Hope this helps.

Hello Christian, Hello Joe,

Thank you both for your suggestions.

I will go with freerdp first because I would prefer a solution from the rhel standard repo over a flatpack package. I'm going to mark the answer as "Best Response" that I choose in the end.

Best regards,
Joerg

Hi Jörg,

Just to clarify ... the flatpak package is available and it is getting installed from the Red Hat repositories.
And the remmina application packaged as a flatpak brings along one big advantage : It is a "containerized"
solution which might be considered a safer option, especially when it comes to remote desktop engineering.
Of course it's up to you to choose what is best for your own convenience and what fits best to your needs. :)

Regards,
Christian

But with flatpack I would need two tools to keep my system up-to-date wouldn't I? Today I just need to run yum update and with flatpack it would be yum -y update && flatpack --refresh or something like that.

That are a lot more characters to type. ;-) (just kidding)

Yes Jörg, flatpak update ... but once RHEL provides GNOME 3.30, you will have the "automatic update feature" and then installed flatpaks get updated automatically (if you want it). Anyway, most important is that the application provides the features you want. :)

Regards,
Christian

Hi,

Reminder about one issue if you ever need to use xrdp on Linux. You cannot use digest MD5 when FIPS is enabled:

# xrdp-keygen xrdp auto 2048

Generating 2048 bit rsa key...
ssl_gen_key_xrdp1 ok
md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
Aborted (core dumped)

In any case, that same digest affects other products, like Subscription Asset Manage:

https://access.redhat.com/solutions/790793

Regards,

Dusan Baljevic (amateur radio VK2COT)

Heh... Ended up here after a google search for that exact error-string. Did you ever find a solution for this (or even just file a bug against the upstream project)?