search

ArcticaProject / lightdm-remote-session-freerdp2

Arctica Greeter: Remote Logon Support for RDP Servers
GNU General Public License v3.0
7 stars 120 forks source link

How do you specify RDP server(s)? #2

Open jphein opened 4 years ago

jphein commented 4 years ago

Installed using sudo apt install lightdm-remote-session-freerdp2. On Ubuntu 19.10.

You need to install the entire Arctica Greeter. sudo apt-get install arctica-greeter Configure the greeter using sudo nano /etc/lightdm/lightdm.conf.d/90-arctica-greeter.conf. Remote login does now show up in LightDM. However, I could not find out how to add my server info. Read this doc: https://github.com/ArcticaProject/ArcticaDocs/blob/master/ArcticaGreeter/ArcticaGreeter_RemoteLogon-HowTo.md, but is old.

kgleason commented 4 years ago

Similar issue here, except I can't get remote login as an option in LightDM. I suspect it has something to do with remote-logon-config-agent not being installed by default

I'm pretty sure that it will go in /etc/remote-logon-service.conf but I can't find any indication of what the URI should look like.

fitzmorrispr commented 2 years ago

I struggled with the same issue, but in hopes that someone will find it: basically don't change remote-logon-service.conf You will need to install x2gobroker-daemon.

you will need to specify a server in its conf file, /etc/x2go/broker/x2gobroker-sessionprofiles.conf (if, like me, you have only one RDP server, comment out everything except the lines in the [DEFAULT] section, add a new section something like:

[WINDOWS] #section name is up to you, only used behind the scenes
host=<address of RDP server>
name=Windows #what appears in the greeter as a label, doesn't really matter
command=xfreerdp #probably doesn't need to be set

you will need to either: Install x2gobroker-authservice or set default-auth-mech = none in /etc/x2go/x2gobroker.conf

you will need to make sure that enable-uccs-output = true is set in your x2gobroker.conf

and you'll need to put the key into the authorized keys file as mentioned in the readme

After this you'll get a remote login prompt that either: requires a local username and password, then displays a RDP login prompt with the username prefiled from the first prompt, where you enter the windows credentials, and then it starts a session

or, takes an arbitrary username and arbitrary or blank password, then displays an rdp prompt with the username prefilled, etc.