|
|
|
|
This document covers the output you can expect to see with beta version 7.2g (fp72g)
A configured copy of the script
Your host system is Windows NT, 2000 or XP
I've started the script up with:
fp72g testpc1 /user administrator password /wait
Just take a moment to review the details of the boilerplate. If the settings are not okay, quit the script with CTRL C and amend as necessary. Press the space bar when you're ready to continue.
The next step is the path processing segment. Fastpush checks the current path and if the fplocation variable has been set, it changes the current working directory to this value.
After the path procedue, the target PC name is checked to make sure it's a valid computer name (no leading "\\") or an IP address. If so, the script continues.
Next the script uses the flavour variable to find which version of VNC you want to install. It then checks that the necessary files are present.
Finally, fastpush prepares to PING the remote workstation. This is to check that the system is online.
Once the space bar is pressed, fastpush attempts to PING the remote workstation. If the PC can be pinged the script moves on to the next stage.
After the PING the script attempts to log on to the remote computer. This isn't normally a problem but again, non-english Windows installations may throw up an odd error. I know that english, german and spanish all work okay.
Once the script has logged on to the remote Windows computer the next thing it does is read the remote registry for some key pieces of information. These are where Windows is installed, what drive does the system live on and where is the program files directory.
Next the system checks that the registry read has been done correctly by using an IF EXIST check. This helps trap an error with REG as the program doesn't always handle umlauts. If the program files directory can be accessed, the script continues.
The script then reads the remote computer's registry for the Start Menu settings. Again this can be an issue for german based Windows installs. I've added some extra error checking here and if the folder can be accessed the script continues.
Now the script produces a quick report saying where Windows is and where the program files can be found on the remote computer.
The next section deals with any existing VNC installation. If a previous version of VNC is detected then it will be removed. This deletes the service, any start menu shortcuts, registry settings and files on the remote computer. If a service is found the script waits for a few seconds to give older computers time to stop the service properly.
The last part is a boilerplate that shows you who the target PC is, where you're copying the VNC files from and where they're being copied to.
The top section shows the files being copied from the fastpush folder to the remote computer.
The next section checks to see that the critical files have been uploaded. For VNC3 versions the script checks for vnchooks.dll and winvnc.exe. That's enough to start the service. For RealVNC4 or greater it checks for logmessages.dll, winvnc4.exe, vncconfig.exe and wm_hooks.dll. Again, those are the necessary files to start a VNC4 service up. If all the necessary files are present, the script continues.
The registry procedure pushes the password from machine.ini (VNC3) or vnc4.ini (VNC4) to the remote computer.
The service configuration routine installs the service and sets it to run automatically. If you don't want to wait for the script to finish, as soon as the service is up and running you can connect to the remote computer's VNC installation.
The next section deals with the Start Menu. Basically the script uses the settings it's read from the remote registry and creates a cmd file that will create new shortcuts on the target PC. This icons.cmd file is executed by PSEXEC or XMD to run the program remotely. Icons.cmd uses the SHORTCUT program to generate the actual links. In the example above you can see the script has been set to use XCMD.
In the window above you can see that the icons.cmd file has been executed sucessfully. Although having start menu icons is very useful, it is not critical to the installation of VNC. This is one section (of many? <wink>) that needs work within Fastpush.
Finally the script tells you that the software has been installed and gives you a very brief review of what it's done.