![\"\"](\"https:\/\/wonghoi.humgar.com\/blog\/wp-content\/uploads\/2021\/06\/image-1024x496.png\")
The two session modules we are interested in here is <\/p>\n\n\n\n
- Xorg (libxup.so): Xorgxrdp is the MS-RDP-like mode that starts a new X session without first attaching to a screen.<\/li>
- Xvnc (libvnc.so): basically a VNC client. You start a VNC server (like X11vnc) with a display\/screen (can be started in any X session you logged in, or the local user screen if you set the VNC server as a service<\/a>) and connect to it in this RDP intermediary (welcome interface) without installing VNC client software.<\/li><\/ul>\n\n\n\n
In Windows, RDP do not distinguish between local and remote users and sessions with the same login account will take over other existing sessions. If you want each session to start fresh and leave other sessions alone, disable this in Group Policy Object editor under
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections -> \"Restrict Remote Desktop Services user to a single Remote Desktop Services session<\/code>“. <\/p>\n\n\n\nI am usually fine with this arrangement as well, but often prefer to connect to my remote sessions work in the background leaving the local user alone (i.e. if I want things to show up on the local monitor screen, I’ll use VNC instead). I’d also like to resume my remote<\/strong> sessions if I log in from another computer instead of starting from scratch with each new RDP connection. Turns out given a bunch of quirks of xrdp, this is much easier to do so than reproducing MS-RDP’s default behavior.<\/p>\n\n\n\n
\n\n\n\nAllow overtaking of locally logged-in session<\/h2>\n\n\n\n
First of all, out of the box, the same remote user cannot overtake locally<\/strong> logged-in<\/a> desktops nor be simultaneously logged in! It’s either one way or the other! I got bumped out immediately after logging in through sesman, or if I logged in remotely first, I get bumped out when I try to log in locally.<\/p>\n\n\n\n
Found somebody suggested<\/a> that certain desktop environment might have added code to prevent the second session from opening. And this blog<\/a> suggested you edit the windows manager launch script<\/p>\n\n\n\n
sudo nano \/etc\/xrdp\/startwm.sh<\/pre>\n\n\n\n
to add EITHER <\/p>\n\n\n\n
unset DBUS_SESSION_BUS_ADDRESS\nunset XDG_RUNTIME_DIR<\/pre>\n\n\n\n
OR<\/p>\n\n\n\n
export $(dbus-launch)<\/pre>\n\n\n\n
RIGHT BEFORE the last lines which checks and calls the Xsession<\/p>\n\n\n\n
test -x \/etc\/X11\/Xsession && exec \/etc\/X11\/Xsession
exec \/bin\/sh \/etc\/X11\/Xsession<\/code><\/pre>\n\n\n\nThis only solves the part of simultaneous local & remote logons<\/p>\n\n\n\n
\n\n\n\nIn the newer version as of writing, the default behavior is that locally logged in sessions are independent of remotely logged in sessions, yet the remotely logged in sessions resumes by default (if you log in as the same user). <\/p>\n\n\n\n
Turns out this is what I preferred as the local sessions should be reached with VNC instead and I’d prefer my remote sessions happen at the background without showing it on the local screen.<\/p>\n\n\n\n
![\"\"](\"https:\/\/wonghoi.humgar.com\/blog\/wp-content\/uploads\/2022\/03\/image-18-1024x471.png\")
<\/figure>\n\n\n\n