Overview:

This how to covers how to put a working setup.exe into a login script so the program can be installed to Windows 9x systems. This technique will not work on Windows NT, 2000 or XP as they have specialist user rights to prevent Tom, Dick or Harriet from loading any old cack to the PC. If you want to roll out VNC to those OS' - use fastpush.

If you did want to use the login script to roll VNC out to NT, 2000 and XP then you'll need to use the joewrae CPUA tool. Try google for a link.

Requirements:

A network (doh!)
Basic command line knowledge

Steps

1. Upload the file

After you've tested the setup.exe that you built, you might be wanting to roll this out to all your old Windows machines.

You need to put the file in a folder that everyone can read. If it's Novell - stick it in f:\public. With NT I'd make up a share or use Samba to host the file.

2. Modify the script

The core command to install VNC is as below and it runs with only one request needed by the user. That's when VNC installs the service and I've not found a way of getting around that.

\\server\share\\vnc_333_r3.exe.exe /silent 

Where server is the host server and share... is well - the share name! For NT you can put this in the netlogon.cmd file. Netware 3 users will need to put a # (hash) in front... and Netware 5 or 6 bods - shame on you, why aren't you using ZEN to roll this out? :-)

Obviously this will install VNC each time the setup is executed. What you need to add in is a line that says:

REM Check to see if VNC is installed.
if not exist c:\program files\orl\vnc\winvnc.exe goto install
Goto END


:install
REM If not NT, then map a drive, install and remove drive.
if "%OS%"=="Windows_NT" echo Cannot install to NT &    goto end
net use q: \\server\vncshare
q:\vnc_333_r3.exe.exe /silent 
net use q: /del

:END
Echo Script has finished.

That should make things a bit better.

3. Trial it

Best give it a whirl before you make the change to the entire network.