NoMachine seems the only one (that worked well?) I've tried a few years back that could be used to access remotely a local session and viceversa. Which is my use case.
Sadly the local session must be logged in, as you said. The black screen feature sometime would fail and any passer by would then be able to use the machine locally. Also if there was a problem with the connection or you forgot to disconnect remotely there was no way to take over the session locally. Complete dealbreaker for me
Sarah from NoMachine here. Would you be able to reach out to us so we can investigate the blank screen not working properly? I understand that you are not using NoMachine anymore, but it would be useful for us to know more details about your setup at the time. You can use the contact us link in the footer of our website. Thank you!
I've only really used it for a VM, and using it "locally" via the hypervisor console works fine - in fact, I can operate both at the same time (NoMachine plus hypervisor console view) and you can see actions on one occurring on the other (since it's using the same desktop).
NoMachine seems the only one (that worked well?) I've tried a few years back that could be used to access remotely a local session and viceversa. Which is my use case. Sadly the local session must be logged in, as you said. The black screen feature sometime would fail and any passer by would then be able to use the machine locally. Also if there was a problem with the connection or you forgot to disconnect remotely there was no way to take over the session locally. Complete dealbreaker for me