Tight VNC MSI and ADM File
I have just finalized a custom VNC MSI File and a ADM file.
Firstly the ADM is not fully managed – so beware if you add it then remove it.
I have not changed any Tight VNC source. Just streamlined the installation.
Notes:
The typical installation – installs VNC server as a service. No viewer is installed – this is perfect for workstations.
So a quiet install would achieve this.
Customization the installation allows you to add the viewer, as well as the ADM template. (%Windows%/Inf) directory. Plus some other ancillary vnc stuff. Check the Adm for a description of the settings
FINALLY – THIS INSTALLER SETS THE DEFAULT PASSWORD TO BE BLANK (not empty) and sets the Autherization required to disabled…meaning no password is required to connect to the workstations it is installed on! The Authhosts settings restricts connection to the localsubnet only. As does the installed firewall entry for the server. THESE SETTING MAY NOT SUITE YOUR ENVIRONMENT – USE ORCA TO TRANSFORM THE INSTALLATION IF NEEDED.
Check the Tight VNC site for an explanation of settings.
This file was created with WIX.
VNC Network Installation File (updated 18/4/09)
If you find this useful please let me know – I am debating whether to learn enough C to reverse engineer Tight VNC to allow it to be fully managed under Group Policy.
I’m currently doing a desktop deployment and came across your post here and on Nabble (http://www.nabble.com/(no-subject)-td23109717.html).
Taking a quick look through the source the following line seems to control where the VNCServer config is stored in the registry:
winvnc/WinVNC.h:51:#define WINVNC_REGISTRY_KEY “Software\\ORL\\WinVNC3″
Once I get back to my office I’ll take a look at recompiling the source and running the server to see if it truly is that simple.
- Malcolm
@Malcolm
Sure – that part I had sort of worked out – the real issue I didnt seem to be able to surmount was extracting the des encryption to allow a password to be set at installation – I just need an exportable dll function call that I can call on a custom action….
Cheers
B
Hi,
Can you post instructions how to create the MSI and add the service password?
The latest version of TightVNC has 2 passwords. The MSI is very useful.
I created the MSI using WIX. Basically I just used the ZIP file that you can download from the TightVNC site and added in the registry entries. The instructions for using WIX are quite long winded…so you will need to read them yourself.. I will try and update this to the latest version of tight vnc as soon as possible..possibly releasing a patch if i can
Best article, lots of intersting things to digest. Very informative