[SOLVED] Make viewer catch the windwos key

[Prisma]

Hello,

would it be possible to achieve it, the viewer catches the Windows key? E.g. in full screen mode? Since windows 8 this strikes me as being essential for a efficient workflow. Technologically this should be possible, shouldn't it?

I think, on the viewer-side a full installation of uvnc is common. For this reason, there is no need for a single-click capability and the viewer usually runs within a secure location. Elevated or system rights could be passed by a service. If they would be needed. What are the technological requirements to get this managed?

Is this already planned for a later version of the viewer?

[Rudi De Vos]

Isn't this working ?

*UAC need to be on before install of
-ultravnc setup.
-ultravnc addons

-winvnc.exe installed as service
-viewer scroll-lock on to send special keys remote

It isn't a viewer issue, but a server issue. win8 protect the win key by UAC
( this is new for win8). To fix this we install a seperate exe ( addons) that
can inject the winkey on win8.

[Prisma]

OK, I see the problem. The scroll-lock must be on. Sorry, I missed this elementary info.
Wouldn't it be a good idea to activate the sending of special keys automatically while full screen (and e.g. mouse over viewer windows) ? RDP behaves this way, so it couldn't be that wrong.

We don't ship the special exe (name?) with our "single click" package. If I send Windows Key through a keystroke or the button at the top of the viewer, the ModernUI screen appears on server side anyway. This should not work. How do you explain this? Is it enough to have the special exe (installed) somewhere on the computer or is it expected in the same folder with winvnc.exe?

Further questions, just for my understanding:
- This exe must be modified during installation by the OS and while UAC enabled?
- This exe must be modified on the target system and cannot be pre-modified?
- Is it possible to let the OS patch/sign/modify the special exe "manually" triggered? The setup-function you use is a Windows-API-Call for sure.

[Prisma]

Oh, I've forgotten to write: Sending the Windows Key works in application mode. This should not be possible also. Now I'm totally confused....

[Rudi De Vos]

OK, I see the problem. The scroll-lock must be on. Sorry, I missed this elementary info.
Wouldn't it be a good idea to activate the sending of special keys automatically while full screen (and e.g. mouse over viewer windows) ? RDP behaves this way, so it couldn't be that wrong.

Yes and no
Multiple monitors ? full screen is only on one monitor
In the past i used "If viewer is foreground or mouse is over viewer" but this was changed as other people didn't liked it.
Scroll lock is simple, if you know it.

SC isn't running as service.
SC doesn't allow to inject keys nor does it allow to start the special exe with the correct permission.
Using SC you never can inject ctrl-alt-del or any protected key combination.

To be able to use it
-running as service
-installed in protected folder ( like program files)
-UAC on
-UAC on during install ( else security bit is never set)
-exe need to be singned
-exe need to have the manifest with uiaccess=true
uiaccess=true, is forbitten for a service. That's the reason we need to use a seperate exe
and start this from tghe service...

Simple; just a hell to....

The exe is not modified, but UAC add a special bit when you copy it, this bit
declare the exe save. When you copy the file to a unsecure folder (like a usb stick/temp)
the bit is not set. I guess the OS put it somewere in the filesystem, not on the exe himself.

exe:uvnckeyboardhelper.exe

[Prisma]

First of all, thank you for this very good explanation. Now the plain theory it's much more clear. But:

SC isn't running as service.
SC doesn't allow to inject keys nor does it allow to start the special exe with the correct permission.
Using SC you never can inject ctrl-alt-del or any protected key combination.

Excuse my unclear diction. When I write Single-Click I don't mean a special SC exe. I'm mean the normal winvnc.exe used in a single-click-scenario, single-click-like. We package the normal winvnc.exe with an own wrapper.

Within my test today I noticed that the windows key works (scroll lock active) with a normal winvnc, although the executable runs from temp folder, although no uvnckeyboardhelper.exe is shipped with our package, although winvnc doesn't run as service. That makes me wonder. Following and understanding your explanation, this isn't able to work. But it does. Therefore my question, wheter the uvnckeyboardhelper.exe must be in the same folder with winvnc.exe or somewhere else on the system would be enough. This would have been the only explanation for me why it works.

Tomorrow I'll do further research. Good night

[Rudi De Vos]

Indeed, all not UAC protected keys works.

The problem is for special keys like
winkey+x
alt-tab

[Prisma]

aaaaaaaaaaaaaaaahh. A misunderstanding. I meant only the behaviour of opening a local or the remote modernUI screen when pressing the windows key. And that's solvable with scroll-lock.
Thanks, you saved me a lot of time of senseless research.

Du sprichst nicht zufällig Deutsch? Vielleicht sogar besser wie Englisch? Das würde manchmal so manches Missverständnis umgehen...