I am looking at an issue selecting a suitable tool for Remote Access to our "Things", historically we have used a re-packaged VNC application but have come up against these issues:
Does anyone have any advice/solution?
These links describe a solution to this issue, but poses it's own problems. It's a modification of Local/Group Security Policy settings that eliminates the secure desktop for UAC prompts.
Your end users may not wish to disable this functionality - in which case there is no workaround to UAC.
For the first item, I do not currently have an answer.
Oh dear! Is there a prize of any kind for the first unanswerable question?
Thanks for looking at this Chris, it's useful to know that we haven't missed anything,
I don't know about a prize, but I'm not sure it's unanswerable. Assuming you're talking about Windows Server products and the Terminal Services feature built-in, there's the Console session, and up to two remote users connecting over RDP to the server (unless you spring for the upgraded Terminal Services licensing). I seem to remember there being a capability for a remote user to connect to the console in the TSADMIN utility. If the user has Administrator rights on the machine, it should be able to "Connect to Console" and then share the desktop that VNC is running on.
I'm not sure if the reverse - connect to the remote users RDP session - is possible to do without disconnecting them.