Corcoran Smith wrote: now we just need uvnc 1.02 in there and we're good as gold.

Well, Corcoran, all you need to do is replace the current contents of the UltraVNC folder (in Fastpush) with the new files and you're done.


David Litchman wrote: I LOOOOVE Fastpush, thank you so much! It's made my admin duties so much easier on countless occasions. One question though, is it possible to use a username with a space in it? I've tried:

fp82 /user "user name" password

(other switches omitted) but it doesn't like that.

Thanks very much David. Glad you found the tool useful. The spaces issue is a bit of a pain and I'd have to put a wodge of new code in to detect the spaces and handle that. This is because of the NET USE command:


As mylogon is being piped from the command line using the %1 %2 variables (put simply), spaces are always going to be a problem. Have you tried using the UPN instead?


Christian wrote: Nevertheless we are stuck at the point, where the fp-script (tested 8.a and 8.1) checks for the startmenu on the target machine. As we are using a german installation for our clients, the script stops and outputs the following message:
The Start Menu variable has been read from the remote registry

This is because the REG command does not read non-US (or non-English) special characters. I understand that the German for start menu has a special character rather than just a 'u'. It is possible to fix this, but I have not put this into the main script. The fix is to use VBscript to read the registry values and pipe them back to Fastpush.


Todor Hristov wrote: How can I have fastpush not install that "My Details" shortcut?

It's been a while since I've check this, but I have a feeling that there's a variable at the start of the Fastpush script (mydeatails I think) that is set to 'yes'. Change that to 'no' and the shortcut and program will not be installed.

Alternatively, search through the script for the mention of 'MyDetails.exe' and put a REM at the start of the line. That will make the script skip that line.

Steven Wallace wrote: I need to change the password for VNC on all the machines on my network at work that have VNC.

There's a couple of ways you could do that:

1. You could create a file called machines.cmd and on each line put:
   
   call fastpush mymachine1 /pwd newfastpushpassword
   call fastpush my2ndmachine /pwd newfastpushpassword
   
   That's quite a lengthly task!
   
   
2. You could also dump the contents of 'domain computers' - if the machines are in a domain. The NT resource kit tool 'global' will do that for you. You could pipe that to a text file (global > "domain computers" > mylist.txt) but I would recommend you remove your key servers from the text file. Then you'd do something like this:
   
   for /f %g IN ('mylist.txt') do @call fastpush %g /pwd newVNCpassword
   
   or
   
   for /f %g IN ('mylist.txt') do @vncpwd /h:%g /v:VNCpassword
   
   
3. If you are feeling very clever, you could also write a VBscript to push the value into the target computer's registry. However, you would need to do that in the 'start up' scripts section of the Group Policy. It's a bit of a faff, but it does work!
   

I've been meaning to do some work on this site for a while now. The Fastpush stuff has pretty much dried up because of other things I'm working on. I've got a raft of poorly written (!!) VBscripts that may be of use to other admins. Watch this space.