I login the remote desktop via VNC. In my client screen, clicks and keyboard input seems doesn't work. Whenever I press a key, it just disconnects.
Related
I am working on asp.net application which is used in one specific machine. On launching this website, the website will be opened in full screen. Now, I should restrict user to use only this window. I should not allow user to open any window, app, anything else by keyboard, mouse.
Please help me in designing this.
Thanks,
Fayaz
Some trial and error helped me. Posting here so that would be helpful for who are looking for same...
Quoting from http://www.pcmag.com/article2/0,2817,1858713,00.asp
You can lock down these subversive key combinations using restrictions in the Registry. Launch RegEdit from the Start menu's Run dialog; navigate to HKEY_LOCAL_MACHINE\SOFTWARE\
Policies\Microsoft Internet Explorer\Restrictions; and find or create each of the following DWORD values, setting its data to 1 to enable the restriction:
NoBrowserClose (disables closing the browser window)
NoBrowserContextMenu (disables right-click context menu)
NoFileOpen (disables use of Ctrl-O or Ctrl-L to launch an arbitrary URL)
NoOpenInNewWnd (disables opening a link in a new window via Ctrl-N or Shift-click)
And below url helps in blocking other functionality
http://blogs.technet.com/b/askpfeplat/archive/2013/10/28/how-to-setup-assigned-access-in-windows-8-1-kiosk-mode.aspx
I built a Linux distro using Yocto, for an ARM-based web-kiosk application.
The system works without any mouse or physical keyboard, but using only the touchscreen and a virtual keyboard, in particular the "matchbox-keyboard". The matchbox-keyboard runs as a daemons, as usually in these kind of application and appears automatically when the focus is on some text field.
Now, with a web browser (both Chromium and Firefox), entering in a typical "login" web page, all works good for the "username" field (the keyboard focus is correct and the matchbox-keyboard pops up automatically), but, after pressing TAB to fill the "password" field, the matchbox-keyboard disappears. And the keyboard doesn't appears even if you try to enter in the "password" text field directly, using the touchscreen.
Did anybody find a solution to solve this problem?
Thanks,
Flavio
I am building my first local Chrome App using this tutorial
My goal is to build an app that launches fullscreen when the PC is started.
The app can be closed by pressing a certain button (Q) but otherwise the user should not be able to close the app.
Is this possible using Google Chrome Apps? How do you launch fullscreen, and how do you prevent the user from closing the app?
Can you prevent the user right-clicking to inspect the page, or clicking on the top menu bar to close the app?
Sounds like you may want to use kiosk mode. Use this manifest permission for your app, as listed here.
You can enter kiosk mode from the chrome command line as well, with --kiosk.
Everything on my server works perfectly through ssh, using putty. However on both putty and even directly on the servers keyboard I cant page/scroll up using shift+page up. It goes up about half a page then automatically goes back to the bottom where the flashing text entry cursor is.
Using SSH, the system automatically scrolls down. To review the text view the server log in pico.
I'm using Guacamole VNC web client viewer and I want to hide the local browser cursor, because otherwise you see two cursors and it is confusing.
I can hide the browser mouse using simple style: cursor:none;
But this is not so good because when some connection exception occurs, I need the browser mouse in order to close the error window etc.
Any solution?
What you want is to hide the remote cursor not the local one. The VNC protocol allows you to hide the remote cursor. Most VNC clients support this. For example, in noVNC (a HTML5 VNC client) there is a "Local Cursor" option to hide the remote cursor so that you only see one cursor.
Unfortunatley, you can't do this right now in Guacamole. There is a long standing bug in Guacamole to add this support: http://guac-dev.org/trac/ticket/33
Update: the option has been fixed in Guacamole.