What's the recommended/preferred unattended remote access solution in Kaos?
I had been using XRDP in other Linux distros. The options that I've seen in Kaos so far has been Anydesk via Flatpak and Chrome Remote Desktop. I've tried Anydesk and it works but haven't tried Chrome Remote Desktop yet. Any other options that I'm unaware of? I'm pretty new to Kaos yet.

I'm looking for the server piece for KaOS. I do have KRDC installed already for RDP client access to work. I was unaware of Krfb's existence so thank you for that. It looks like it's only VNC based rather than RDP but it's still an option.

Freerdp does seem to have a server component with freerdp-shadow-cli. I'll have to see if this would be an option by SSH'ing into KaOS and starting the server on demand.

I still have to try Chrome Remote desktop too. It's nice to have options.

I tried KRFB and it seems like it would be a good solution but the problem is that I can't initiate control. The Security tab has "Allow remote connections to control your desktop" checked but it's behaving as if it is not checked. And Yes, I've unchecked it with the same result. Is this any type of known issue?

This helped. It turns out the actual issue is bug 438007. The screen being displayed is not the one being controlled. I brought up Anydesk which could show whichever monitor that I wanted and could see the clicks happening on another monitor that wasn't being displayed after I put some clickable content on it so KRFB isn't going to be a workable solution until that gets fixed.

I tried Chrome Remote Desktop. Everybody seems to say that this is easy to setup but it failed for me. Extension is in Chrome -- Chrome is obviously installed as is the chrome-remote-desktop-94.0.4606-27-1 package. Every time it gets to the point where you enter Pins and are prompted for authentication to run the /usr/bin/systemctl as superuser it fails. It simply comes back with "An unknown error has occurred" which isn't very helpful.

Running crd from the CLI shows:
CRD is not running; starting.
Deleting old pulse audio files
Failed to start chrome-remote-desktop@xxx.service: Unit chrome-remote-desktop@xxx.service not found.

I've also tried freerdp-shadow-cli and got close to making it work from a Windows client. I got it to authenticate and establish a session showing a desktop for a couple seconds but it would kill the connection immediately. I'll probably try this on a non Windows RDP client and see if it's just Microsoft trying to thwart me.

[edit] I just tried this with KRDC on another Linux machine and it worked without issue so I wasn't paranoid about Microsoft[/edit]

So far only Anydesk has worked without issue.

The freerdp-shadow-cli program does work with the wfreerdp.exe client. The wfreerdp.exe doesn't require any installation so is still an option on Windows clients where you don't have administrative privileges to install software.

wfreerdp.exe /v:<ip or server> /u:<userid> /p:<password> /gfx:AVC420

The /gfx parameter is required since AVC444 isn't working properly and seems to be the default. RFX and AVC420 seem to work.

Anydesk is slightly faster if I compared side by side on an Internet connection.