There’s a Windows-specific script called FastPush I just found that allows you to install VNC server onto a large number of computers remotely and silently. These target computers must be running NT, 2000 or XP, and you need admin rights to do this, but if you’re looking for the best way to install VNC into your whole LAN, this is it.
It should be quite easy and straight forward to deploy VNC server remotely using DOS command line but somehow I got stuck for nearly an hour on the password section. I was able to install VNC server on my computer on the same LAN and also able to connect to the VNC server. However, when it asked for password, there’s where I got stuck. After trying and re-reading again and again on FastPush website, I finally managed to get it working.
To save your time from chances of getting stuck at any problem, I will provide you with step-by-step information on how to install VNC server on a computer remotely and silently.
1. Download the latest version of FastPush at http://www.darkage.co.uk/downloads/
There’s 2 version of FastPush. Lite and Full. The difference between the 2 versions is the Lite version only comes with RealVNC and Full version comes with latest and older versions of RealVNC, TightVNC, UltraVNC and Zvnc.
2. Extract the downloaded files and it’s best you put everything in a folder called “FastPush” and place the folder FastPush in your C:\ drive.

3. You will need to do a little configurations such as setting the VNC server’s password before you can start.
Check the “common” folder inside FastPush folder, you will see machine.ini and vnc4.ini. Open it up and you’ll see a line which says “Password = REG_BINARY YOUR PASSWORD HERE”

Important Note: You can’t just type in any password you like because it will insert the password in Binary data and not value data into registry. Binary data are like hex codes. Think of a password you want to use, then download and install RealVNC on YOUR computer. Set a password for the VNC server that’s installed on your computer.
3. Now you need to extract the RealVNC password Binary Data from your registry. Go to Start -> Run -> type CMD and press OK. You will now see a black coloured dialog box. Type “CD \fastpush\utils” and it should bring you to C:\fastpush\utils
Type this command “REGDIR \registry\machine\software\realvnc\winvnc4″ and you should see something like the screen below.

If you get a message saying “REGDIR: Unable to open key ‘\registry\machine\software\realvnc\winvnc4′ (2), then try to run the command “REGDIR \registry\machine\software\orl\winvnc3\default”
4. Notice the part where it says Password = REG_BINARY 0×00000008 0xfd3cd8db 0x58147a72
That’s the VNC server password you just set on your own computer. Open machine.ini and vnc4.ini, and replace the text YOUR PASSWORD HERE with 0×00000008 0xfd3cd8db 0x58147a72 and save the files.
5. You can now start to FastPush VNC Server to another computer anywhere on a LAN.
From your command prompt, Go to C:\fastpush and type “fp82 COMPUTERNAME“.
6. Try using VNC Viewer to connect to the computer you just fastpush’ed.
For more advanced features, you can edit the fp82.cmd script. Right click on fp82.cmd and select Edit.

You can configure whether you want to install viewer on the remote computer, to have VNC shortcuts on remote computer, VNC service to be started in automatic or manual mode and etc…
To remotely uninstall or remove the VNC Server that you’ve just fastpush, just use the command “fp82 COMPUTERNAME /uninstall“.
Related posts:
is there a way to port this to linux (to push out to windows machines)
Nice info man! I will use it for my LAN :D
Hi, I can get to the stage of keying in the VNC password but then it fails saying VNC is not configured with a password, any ideas.
Help!!! I can’t get past the password part? When i run the regdir the password section does’nt look like your example. i’ve set everything per these instructions and i’m using ultravnc which uses an ini file for the password. So i’m not sure why i need the Password from the registry. Any info would be appreciated….
hi is there anybody has fastpush.exe setup please i just need it on my computers for my net cafe please help thanks
Nice article! A while ago I actually made a simple to use package that automatically installs VNC on a remote computer. Please have a look at it on jar.yosephine.com
Ok so I promised to re-do my manual so its a bit more clear and easier to understand.
My appologies in advance to the blog master.
But this will be my last post on this probably. If you follow this manual, you cant go wrong with Ultra and fast push. I woudl also like to thank the creator of fastpush as this is a mighty fine script. So here is my updated manual (AGAIN):
Ok so I finally got this baby to work as I wanted it to with the latest Fastpush and Ultra VNC versions available.
Fast Push Version: 8.2
Ultra VNC Version: 1.0.5.3
(These can also be found on the Resources Share)
Most editing was done using Notepad++ (Very nice program so you can actually see the line numbering in your batch files, scripts and so on)
OK, ready to rock!!
Administrative PC
1. Extract Fastpush 8.2 to the administrative PC it will be used on (First PC) to the local drive, in my case c:\fastpush.
2. Download the latest binaries version of Ultra VNC (1.0.5.3 current) from source forge.net
3. Create a new folder inside c:\fastpush and call it ultra (c:\fastpush\ultra) and copy the binary files for Ultra VNC to this folder.
4. Create a new batch file script inside c:\fastpush and call it push.bat
5. Edit the push.bat so the contents of the script has this line: fp82 %1 /ultra
6. Save and close the newly created batch file.
7. Create another batch file script inside the c:\fastpush directory and call it kill.bat
8. Edit the kill.bat so the contents of the script has this line: call fp82 %1 /uninstall /ultra (The reason I create these two extra batch files will make it easier when deploying and removing VNC when needed. It is however not necessary to create these. I just did this for administrative ease)
9. Save and close the newly created batch files
10. Next edit fp82.cmd and change variable on line 23 to: set flav=ultra
11. I also like to set line 34 to: set shortcut=no (because later on we will be pushing this to machines and this will not make start menu shortcuts on the destination machine) But if you want this on the administrative machine you are working on for the first push then leave it set to yes)
12. Also change variable on line 31 to where your fastpush directory is located. In my case: set fplocation=c:\fastpush
13. The first initial run we want to set up and create the install on the local machine (Administrative PC) and also configure it with everything we need such as passwords authentication and so on. So next you open up the CMD and go to the root of c:\fastpush; type in: push ‘computer name’ (In this case it will be the local host since we want to deploy VNC on my workstation first)
14. Once the script completes it will pop up with the VNC server settings where we set the password and all the configurations (Almost like a new install of VNC) This screen always pops up for config. Set the password and all other configurations as you want it to be. This is important because this step creates the ‘ultravnc.ini’ file which will be located on LocalHost\Program Files\Orl\VNC\ultravnc.ini This file is vital!!! (Most important file) It will also act as the master ini file for the deployment of VNC to other computers
15. Copy this ultravnc.ini file to the c:\fastpush\ultra\ directory we created in step #3 replacing the current standard one.
16. Ok now we will tweak some other settings before we move on to actually rolling out VNC to client workstations.
17. If you wish to disable the tray icon of the VNC server when you push it next open your master ultravnc.ini file we just spoke about in the previous step and on the line that says: DisableTrayIcon=0 change it to DisableTrayIcon=1
18. Next open up the ‘machine.ini’ file in the following location: c:\fastpush\common\machine.ini and on line 8 you will see Password. This line will be replaced by the password you set in step #14 of this manual, but needs to be in HEX format. It is quite easy to get the HEX as shown in the next step.
19. Open up cmd and go to the directory c:\fastpush\utils
20. Next type regdir \registry\machine\software\orl\winvnc3\default
21. This will throw out the Password you set in step #14 but will show it in HEX, it looks almost similar to what is written in the ‘machine.INI’ file; copy the line that starts with ‘Password’ and replace it with the line in ‘machine.ini’ (Its important that you keep the line and spacing exactly the same; Just replace the contents of the line)
22. The ‘machine.ini’ file should look something like:
****Selection from ini file******************************************
\registry\machine\software\orl\winvnc3\default
AllowProperties = REG_DWORD 0×00000000
AllowShutdown = REG_DWORD 0×00000000
AutoPortSelect = REG_DWORD 0×00000001
InputsEnabled = REG_DWORD 0×00000001
OnlyPollConsole = REG_DWORD 0×00000001
OnlyPollOnEvent = REG_DWORD 0×00000000
Password = REG_BINARY 0×580008 0xc55e8454 0x1578197e
PollForeground = REG_DWORD 0×00000001
PollFullScreen = REG_DWORD 0×00000001
PollUnderCursor = REG_DWORD 0×00000000
SocketConnect = REG_DWORD 0×00000001
*****************************************************************
23. This step is the most important one. Now that we have our configuration/master ‘ultra.ini’ file as described in steps #14 and #15 we will tweak fp82.cmd a bit more. So once again open up fp82.cmd in edit mode and add in a line of code just below line 755: xcopy “%currentpath%\%flav%\ultravnc.ini” %targetpath% /r /v
24. By adding this line the next time you push to a client machine, it will copy this config INI file with the password and all the nice settings we gave it in one shot.
This is done silently and if you disabled the tray icon as explained in step #17 the client wont even notice VNC being installed as it is silent, no password popups, nothing…(I am not sure why the script didn’t do this in the first place. But by adding this line, it saved me a hell of a lot of administrative overhead to walk to that client machine and configure it with a password and hide the tray icon.)
I must say however, I have been using Ultra VNC v1.0.4 without having to add this line with no issues. So its only necessary with version 1.0.5 up.
25. We’re almost done. For best practises you can read on or if you are happy with the manual so far just ignore. But to test this all open up cmd in the root of fast push and type: kill ‘localhost’ (LocalPC) This will remove everything silently, repeat the step by running: push ‘localhost’ again to install VNC again.
Deploy to client
1. Since this is now installed and deployed on the administrative PC and we are all ready and set to go, we will make one more slight change to fp82.cmd for future use to deployment to our client machines.
2. These steps are not really as critical but its good to keep in mind.
3. Edit fp82.cmd and change the line that says set viewer=yes to set viewer=no The only reason I want to do this is to prevent the client VNC viewer to be installed on the machines I push to. (If you are scared your employees may crack the password and use the viewer to spy on others) Otherwise leave it to yes.
4. So finally start up CMD, command or if you have a nifty script or database on the root directory of c:\fastpush and type: ‘push COMPUTERNAME/IP’ to install VNC to the target client. Or type: ‘kill COMPUTERNAME/IP’ to remove VNC from the target machine.
One final note: I used to use a nifty tool called vncpwd.exe to remotely set or change an Ultra VNC client password via another batch script. However, this only works for versions 1.0.4 and prior. This is a no go for v.1.0.5. (At least as of yet) Maybe because most configs are now kept in the INI file.. So if anyone comes across a newer version of vncpwd.exe that works on 105. Let me know, my e-mail is magiconion_M@hotmail.com
Ninja Out!
Oh I am a noob!!
I have found an easier way to diable the tray icon on a push.
Another way to disable the tray icon if you don’t want to add lines 15 and 16 as shown in step #19 you can configure your master ultravnc.ini file on the line that says: DisableTrayIcon=0 and change it to DisableTrayIcon=1
This is much easier.
Sorry blog master for all the posts.
I will re-create my manual and post it a last time tomorrow as it is quite late now. But I hope the info is beneficial to everyone.
Hi there,
I forgot to say. Step #19 in my manual.
Lines 15 and 16 are lines you have to put in under \’SocketConnect\’
here they are.
\\registry\\machine\\software\\orl\\winvnc3
DisableTrayIcon = REG_DWORD 0×00000001
Thanks.
Ok so I finally got this baby to work as I wanted it to with the latest Fastpush and Ultra VNC versions available.
Fast Push Version: 8.2
Ultra VNC Version: 1.0.5.3
OK, ready to rock!!
1. Extract Fastpush to the administrative PC it will be used on (First PC) to the local drive, in my case c:\fastpush
2. Download the latest binaries version (1.0.5.3 current) from source forge.net
3. Create a new folder inside c:\fastpush and call it ultra (c:\fastpush\ultra) and copy the binary files to this folder.
4. Create a new batch file script inside c:\fastpush and call it puch.bat
5. Contents of c:\fastpush\puch.bat script: fp82 %1 /ultra
6. Save and close the newly created batch file
7. Create another batch file script inside c:\fastpush and call it kill.bat
8. Contents of c:\fastpush\kill.bat script: call fp82 %1 /uninstall /ultra
9. Save and close the newly created batch file
10. Next edit fp82.cmd and change variable to set flav=ultra
11. I also like to set set shortcut=no (because later on we will be pushing this to machines and this will not make start menu shortcuts) But if you want this on the administrative machine then leave it set to yes)
12. Also change variable set fplocation=c:\fastpush
13. First initial run we want to set up and create the install on the local machine and also configure it with everything we need. So next you open up the CMD in the fastpush directory and type in: push ‘computer name’ (In this case it will be the local host)
14. Once the script completes it will pop up with the uvnc server settings where we set the password. Set the password and all other configurations as you want it to be. This is important because this step creates the LocalHost\Program Files\Orl\VNC\ultravnc.ini file which is vital!!! (Most important file)
15. Copy the ultravnc.ini file to the c:\fastpush\ultra\ directory replacing the current standard one
16. Ok now we will tweak some other settings before we move on to actually rolling out VNC to client workstations. Next open up the ini file in the following location: c:\fastpush\common\machine.ini and on line 8 you will see Password. This line will be replaced by the password you set in step #14 of this manual, but needs to be in HEX format. This is quite easy to get as in the next step.
17. Open up cmd and go to the directory c:\fastpush\utils
18. Next type regdir \registry\machine\software\orl\winvnc3\default
19. This will throw out the Password you set in HEX, it looks almost similar to what is written in the INI file; copy the line that starts with ‘Password’ and add it in the ini file. Also add lines 15 and 16 in the ini file
20. Now that we have our configuration ini file as described in steps #14 and #15 we will tweak fp82.cmd a bit more. So once again open up fp82.cmd in edit mode and change add in a line of code just below line 755: xcopy “%currentpath%\%flav%\ultravnc.ini” %targetpath% /r /v
21. By adding this line the next time you push to a client machine, it will copy this config file with the password and all the nice settings we gave it in one shot. (I am not sure why the script didn’t do this in the first place. But by adding this line, it saved me a hell of a lot of administrative overhead to walk to that client machine and configure it with a password and hide the tray icon.
22. We’re almost done. For best practises you can read on or if you are happy with the manual so far just ignore. But to test this all open up cmd in the root of fast push and type: kill ‘localhost’ (LocalPC) This will remove everything and to test that it all works ok, repeat the step by running: push ‘localhost’ again.
Deploy to client
1. Since this is now installed and deployed on the administrative PC, we will make one more slight change to fp82.cmd for future use.
2. Edit fp82.cmd and change the line that says set viewer=yes to set viewer=no The only reason I want to do this is to prevent the client VNC viewer to be installed on the machines I push to. (If you are scared your employees may crack the password and use the viewer to spy on others) Otherwise leave it to yes.
C:\\\\>cd fastpush
C:\\\\Fastpush>cd utils
C:\\\\Fastpush\\\\utils>regdir \\\\registry\\\\machine\\\\software\\\\realvnc\\\\winvnc4
\\\\registry\\\\machine\\\\software\\\\realvnc\\\\winvnc4
UpdateMethod = REG_DWORD 0×00000002
RSA_Private_Key = REG_BINARY 0×00000584 \\\\…
The final choice will be real412.
Script is version 8.2
—————————————————————
You want to install : real412
Log on as : Adhiegan
Log output to results.txt : no
Install warning box : no
Install method : Overwrite files and registry
Install Vncviewer program : yes
\\\’My Details\\\’ desktop icon : yes
Use specified VNC password : no
Open port on XP firewall : no
—————————————————————
R2 – VNC found in c:\\\\fastpush
Changing current directory to c:\\\\fastpush\\\\utils
All utilities present. Please wait.
Target pc will be \\\’asimaroham\\\’.
Machine name \\\”asimaroham\\\” is valid.
Checking to see if the source VNC files can be found in \\\”c:\\\\fastpush\\\\real412\\\”
All required VNC files are present in c:\\\\fastpush\\\\real412
*** USING PING TO FIND TARGET STATUS ***
Please wait while a TCP/IP connection to asimaroham is made.
Machine \\\”asimaroham\\\” is alive, script continuing
*** LOGGING ON TO THE TARGET PC ***
Local name
Remote name \\\\\\\\ASIMAROHAM\\\\ipc$
Resource type IPC
Status OK
# Opens 0
# Connections 1
The command completed successfully.
*** CHECKING SHARE ACCESS ***
Error: Access is denied.
Remote system drive found okay [].
Error: Access is denied.
Windows location found okay [].
Error: Access is denied.
Program files location found okay [].
*** CHECK REMOTE PROGRAM FILES FOLDER ***
*** WARNING! ***
Access could to the remote Program Files location could not be confirmed.
Please check that the folder below exists:
\\\”\\\\\\\\asimaroham\\\\$\\\\\\\”
\\\’C:\\\\Program\\\’ is not recognized as an internal or external command,
operable program or batch file.
please help me to resolve this problem…
The final choice will be real412.
Script is version 8.2
—————————————————————
You want to install : real412
Log on as : AXXXXXM\administrador
Use this password : XXXXXX
Log output to results.txt : yes
Install warning box : no
Install method : Overwrite files and registry
Install Vncviewer program : yes
‘My Details’ desktop icon : yes
Use specified VNC password : no
Open port on XP firewall : yes
—————————————————————
Presione una tecla para continuar . . .
R2 – VNC found in c:\push
Changing current directory to c:\push\utils
All utilities present. Please wait.
Target pc will be ‘aesis04′.
Machine name “aesis04″ is valid.
Checking to see if the source VNC files can be found in “c:\push\real412″
All required VNC files are present in c:\push\real412
*** USING PING TO FIND TARGET STATUS ***
Please wait while a TCP/IP connection to aesis04 is made.
Presione una tecla para continuar . . .
Machine “aesis04″ is alive, script continuing
*** LOGGING ON TO THE TARGET PC ***
Using provided login information
Se ha completado el comando correctamente.
Presione una tecla para continuar . . .
Fail under IPCSTATUS
PLEASE, any help will be appreciated.>
Don’t work on vista, says connection closed. Read that it has to do with something called session 0. No way around it?
I answered my own question. Just add to the end of the fp82.cmd file:
“C:\Program Files\RealVNC\VNC4\vncviewer.exe” %targetpc%”
Change the path to the vncviewer.exe if you have installed it in a different location.
Don’t forget to add your command options!! If you want a list of available command options, simply go to command prompt and change directory to where vncviewer.exe is located and type “vncviewer.exe /?”.
Cheers!
excellent post and instructions, worked flawlessly. Is there a way to make this command spawn a connection to the targeted workstation. This would save a LOT of clicks! :)
Server password did not work :(
no sirve
Very usefull, thanks
Nice info dude. Shall try it in my LAN ;)