Is it possible to modify the lite version so that it does not install a tray icon so that you con monitor rogue employees?

Pete
 

Hi
also is it possible to get fastpush working on vista?

Pete
 

Hi Pete,

> modify the lite version

Currently the bug free version of VNC does not support this. I did have an older version that did, however I removed that because it had the vulnerability in it.

> vista

Vista isn't something I've investigated yet. I have been keeping track with what's going on and it seems that UltraVNC is the version to watch.

Given Vista's new security model, I'm not sure how Fastpush would work.
 

Thanks for the comments Richard.

We will have to wait and see it seems...
Pete
 

Hi Richard

I have been trying a few things with vista. Here is where I am so far.

I can get your script to install on my vista test machine if I make the following 2 changes:
1) Add LocalAccountTokenFilterPolicy to the registry as per this post:
http://www.paulspoerry.com/2007/05/09/how-to-access-administrative-shares-on-vista-c/

2) Set the "remote registry" service to automatic and reboot or just start it manually for that session.

What happens:
Fastpush seems to push out UltraVNC to the vista computer no problem, however when connecting from anouther machine, I am presented only with a black screen.

I believe this is because the service winvnc is running on session 0 (when i run qwinsta) while the user is logged in as session 1.

Here is a similar post with a similar issue being caused by the session ID being different...
http://forum.ultravnc.info/viewtopic.php?p=35044

Im not sure where to progress from here. I have searched around for some kind of fix but am battling.

Any ideas?

Pete
 

You've got a lot further than I have :-)

Did you replace contents of the UltraVNC folder with the latest Vista compatible version?

The Session0 bug is discussed here
 

Hi Richard

I was using 1.02 stable, which I now replaced with 1.04 RC16 per your recommendation.

This seems to have got me a little further, but the end result is still not desirable.

On completion of your script the winvnc.exe service runs and pops up on the remote computer with the default admin properties, asking theuser to type in a default password.
Trying to connect at this point from the machine where you pushed out the script does not work, complaining that there is no default password set...

If the user sets a default passord and hits ok, he gets UAC askin him to run the file winvnc.exe and then if he clicks run the icon appears in the system tray.

You still cannot connect at this point - it claims the password is still blank despite being set.

If the service is restarted however on the remote machine then you can connect fine...

Thanks for your help so far. Do you think that these problems are fixable?

Pete
 

Do you think that they changed the location that the password is stored in this version of UVNC?

Pete
 

Hi Peter,

Yes, the new version of uVNC doesn't use the registry. The settings are stored in an INI file.

You'd have to tweak the FastPush system to copy that file in and REM out the bits concerning REG.
 

Hello there.

This one is for you guys and girls who use Ultra VNC and fastPush.
I also posted this on raymonds blog.

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 0×1578197e
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!
 

hi, I am using your fp82 to push out vnc on about 20 PCs, it works great on XP. Now, here I have a issue pushing out vnc on Vista, it seems vnc service running but when I attempted to connect, it shows error. have you had this expereince before? any workaround?
 

Hello,

THANKS for your tool, and the explanations below !!!

I am using a French version of Windows and have problems with it. The point is that, when we read the "common program" variable, we get : Documents and Settings\All Users\Menu DÚmarrer\Programmes.
have you notices the accent ? Yes ... this is it, we get it wrong... We must have something like Documents and Settings\All Users\Menu Démarrer\Programmes ...

Does someone knows how to deal with it ?
 

Found ! The solution is to use the last REG... I change the one in utils by the one in Vista (in system32). The information given is correct ...
 

... and just another short line you'll need to push vnc on vista (and windows 7) target machines without any manual prequisites:

1) sarch for the line "echo *** CHECKING SHARE ACCESS ***" [somewhat around line 590]

2) add the line "sc \\%targetpc% start RemoteRegistry" after that to start the Remote-Registry service in order to enable the remote reg export needet by pushvnc.


As far as i can say, Richard Harris' way works perfect. I added another few tweaks for my domain environment, but the basics are just cools. Thanks a lot.
 

Hi,

Thanks for the tip about Remote Registry. It should be easy enough (!!) to use an IF EXIST to spot the "Users" folder and Program Data for Win7.

Hmm... There's a thought! :)