Using lightdm/xrdp in a headless single board computer for remote connection

I have installed Armbian (uname -a result: Linux orangepi2g 3.10.62-rda8810 #1 PREEMPT Tue May 29 13:37:31 +03 2018 armv7l armv7l armv7l GNU/Linux) on an orangepi 2g-IoT board (http://www.orangepi.org/OrangePi2GIOT/). This board does not have a display output, but has a pins for communicating with a PC through the serial port. This is the OS version shown in Putty when the board boots up:

Welcome to ARMBIAN 5.46 user-built Ubuntu 16.04.4 LTS 3.10.62-rda8810

I have used the built in configuration tool (armbian-config) to install a light desktop. I believe what it installed is called lightdm. When the board is reset I get messages saying Light Display Manger could not start. (Something similar to this: https://www.debugpoint.com/2021/03/f...start-lightdm/). systemctl status lightdm.service gives me this output:

Code:orangepi@orangepi2g:~$ sudo systemctl status lightdm.service
lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset:
Active: inactive (dead) (Result: exit-code) since Wed 2021-10-27 11:22:47 UTC
Docs: man:lightdm(1)
Process: 2385 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
Process: 2382 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-dis
Main PID: 2385 (code=exited, status=1/FAILURE)

Oct 27 11:22:47 orangepi2g systemd[1]: Failed to start Light Display Manager.
Oct 27 11:22:47 orangepi2g systemd[1]: lightdm.service: Unit entered failed stat
Oct 27 11:22:47 orangepi2g systemd[1]: lightdm.service: Failed with result 'exit
Oct 27 11:22:47 orangepi2g systemd[1]: lightdm.service: Service hold-off time ov
Oct 27 11:22:47 orangepi2g systemd[1]: Stopped Light Display Manager.
Oct 27 11:22:47 orangepi2g systemd[1]: lightdm.service: Start request repeated t
Oct 27 11:22:47 orangepi2g systemd[1]: Failed to start Light Display Manager.I have also installed xrdp in this board

Code:orangepi@orangepi2g:~$ sudo systemctl status xrdp
xrdp.service - LSB: Start xrdp and sesman daemons
Loaded: loaded (/etc/init.d/xrdp; bad; vendor preset: enabled)
Active: active (running) since Wed 2021-10-27 11:07:37 UTC; 18min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/xrdp.service
935 /usr/sbin/xrdp
946 /usr/sbin/xrdp-sesman

Oct 27 11:07:36 orangepi2g systemd[1]: Starting LSB: Start xrdp and sesman daemo
Oct 27 11:07:36 orangepi2g xrdp[907]: * Starting Remote Desktop Protocol server
Oct 27 11:07:37 orangepi2g xrdp[907]: ...done.
Oct 27 11:07:37 orangepi2g systemd[1]: Started LSB: Start xrdp and sesman daemon
Oct 27 11:13:05 orangepi2g xrdp-sesman[1875]: pam_unix(xrdp-sesman:session): sesHowever, on my windows machine when I try to connect to this board using Remote desktop, I get the error shows in the attached picture.

I want the GUI desktop to run in the background while I use this board though it's serial port, so that I can view it's GUI using windows remote desktop. What should I do to achieve this? I can provide more details if necessary.

I am also ok with viewing the GUI through the ssh connection using some other software on the Windows PC, if it's something possible and if that is an easier way to do this. I am just assuming xrdp is what I need here, as I have used it before to remotely view desktop of a different PC version of linux.
Attached Thumbnails