I've never waited for them to clear, but the fact that they even pop up is
bad enough. This disturbs the users at the workstations and causes them to
call me and ask what it is. If there is anything out of the ordinary, they
get bent out of shape. I'm also making my script to update it periodically
as new versions come out or as I modify existing versions to suit a need.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Folder
Simon-ASL021
Sent: Wednesday, December 20, 2000 9:04 AM
To: '[EMAIL PROTECTED]'
Subject: RE: VNC Noise
I get the same boxes, but the clear after 5 seconds, and do not need to be
clicked for the installation or removal to continue unattended.
Simon
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 20 December, 2000 14:20
To: [EMAIL PROTECTED]
Subject: RE: VNC Noise
Well, my kix script is a little more automated than that and -install still
pops up a dialog that needs to be clicked.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian Cowley
Sent: Wednesday, December 20, 2000 7:12 AM
To: '[EMAIL PROTECTED]'
Subject: RE: VNC Noise
OK, here is the much-desired method that I developed for a silent network
install of VNC:
Install VNC on a test machine, and set it up with the right refesh
properties and password that you want. You also need to set up any
AuthHosts properties or the disabling of the 'Close VNC' and 'Properties'
menu options on the system tray icon (documentation available on VNC
website).
Then export the registry entries to .reg files (we had three, from
HKEY_LOCAL_MACHINE, HKEY_CURRENT_USER and HKEY_USERS/.DEFAULT).
Export the whole ORL/VNC branch.
Now, all you need to install VNC on any machine is to copy winvnc.exe,
vnchooks.dll to c:\program files\vnc (or wherever) and omnithread_rt.dll to
c;\winnt\system32 and install the .reg files.
I achieved this by the following method:
Use the NT4 Server resource kit command 'rsetup' to set up access to a
remote command prompt on the target machine.
Then use 'rclient' to connect to the remote comamnd prompt (thisa is a
command prompt that is actually running on the target machine, but operates
in the background, so the user sees nothing).
Inside this command prompt, run a batch file that copies the files and runs
the .reg files, then runs 'winvnc -install'.
This copies all the needed files, the settings (in the registry) and then
installs VNC as a service.
At the next reboot, VNC server is running as a service.
the bonus of this method is that there is no start menu entries, and the
viewer is not installed.
when the 'rclient' progam is used, you pass the administartor password to it
(giving a command prompt with admin access on the target machine) and
there's a switch to run a batch file and close.
Hence the whole lot can be automated from a batch file.
All that is needed is the NETBIOS name of the target machine, and if you
have loads of them, the passing of the names to the batch file can be
automated too.
I have included the contents of the batch files below.
Hope this all helps, if you have any more questions feel free to ask :)
--
Ian Cowley
Computer Services Dept.
National Farmers' Union
MAIN BATCH FILE:
please note the 'rclient.....\install.bat' is all on one line.
=============================================
@echo off
rsetup \\%1
rclient \\%1 /logon:<domain>\administrator <admin password here> \runbatch
\\<server>\<share>\install.bat
==============================================
INSTALL.BAT:
==============================================
@echo off
c:
cd \
cd "program files"
md orl
cd orl
md vnc
cd vnc
copy \\server\share\winvnc.exe c:
copy \\server\share\uninst.isu c:
copy \\server\share\vnchooks.dll c:
copy \\server\share\omnithread_rt.dll c:\winnt\system32
regedit /s \\server\share\1.reg
regedit /s \\server\share\2.reg
regedit /s \\server\share\3.reg
winvnc -install
This process is invisible at the user's end.
You just need to run "main_batch <NETBIOS name>" e.g. "main_batch PC205"
**********************************************************************
THIS EMAIL MESSAGE AND INFORMATION IT CONTAINS MAY BE PRIVILEGED AND/OR
CONFIDENTIAL, AND IS FOR THE USE OF THE ADDRESSEE ONLY.
UNAUTHORISED USE, DISCLOSURE OR PRINTING OF THE CONTENTS IS PROHIBITED.
IF YOU ARE IN POSSESSION OF THIS EMAIL AND ARE NOT THE ADDRESSEE PLEASE
NOTIFY THE SENDER IMMEDIATELY.
ALTHOUGH EVERY EFFORT HAS BEEN MADE TO ENSURE ACCURACY NEITHER THE NFU
NOR THE AUTHOR CAN ACCEPT LIABILITY FOR ERRORS AND OMISSIONS. (c) NFU
COMPANY REGISTRATION NO. 245E
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
