Silent install for TightVNCis one example of a VNC Server and Client, a standard means of remote access. Running [http://en.wikipedia.org/wiki/Virtual_Network_Computing VNC] server software on Windows allows you to connect to the Windows graphical environment using VNC client software on a remote computer. There are various VNC client and server softwares, such as TightVNC and UltraVNC. There are VNC clients for probably every operating system, so you don't need to be running Windows to connect to and use Windows. VNC uses the [http://en.wikipedia.org/wiki/RFB_protocol RFB protocol], a defined standard method for remote access, so generally speaking any VNC client will connect to any VNC server, however occasionally some VNC implementations have added non-standard features that other clients may not support, examples of this are UltraVNC's remote login and file transfer features. VNC clients connect into the session currently running on Windows, so the remote user and the person who might be sat at the computer see the same thing; the client doesn't get a separate login prompt, if someone is already logged into the computer then you see that, otherwise you get to login. For remote administration or remote staff working, for security reasons you are strongly advised not to enable remote access to desktop computers directly over the Internet, instead you should have a firewall in place (for example [http://www.pfsense.com/ pfSense]), running a VPN server, which clients are required to securely VPN into before they have unfettered access to connect to VNC on desktop computers running Windows (or other operating systems). =Version 2.0.2x=TightVNC v2.x version 2 is a complete rewrite. It over version 1; it doesn't need the Mirage driver. The Reg ; the registry settings are in a different location. The ; the command -line switches are different too.
==Preconfiguration Steps==
* download the new software and place it in your wpkg WPKG software folder.
* on a PC install TightVNC and configure it with your password settings, etc.
* using regedit export HKEY_LOCAL_MACHINE\SOFTWARE\TightVNC\Server and save it as settings.reg in your wpkg software folder. '''WARNING: as others can read this file it is possible that they could decrypt the VNC passwords!'''
==WPKG Package file==
<source lang="xml">
</source>
=Version 1.3.0x=
See also silent installation for [[DFMirage hook display driver]].
I prefer TightVNC over UltraVNC, essentially because they have viewers also for other operating systems and I'm not stuck on browser/java viewer under my preferred OS.
I install and manage TightVNC with the following XML package description:
</source>
tightvnc.bat is a simple batch script that to setup TightVNC server and restart it:
<source lang="dos">
</source>
tightvnc.reg contains the VNC server setup of the server, most notably the access password, i.e. I can use as a registry patch:
<source lang="reg">
</source>
'''NOTE''' that passwords are cryptedencrypted, but this is no a paranoid setup, not considered secure as someone can easily have access to the registry patch and try to decrypt the password.
[[Category:Silent Installers]]