Fastpush - Best Practices?

dansajd · Post by **dansajd** » 2004-06-02 21:18

I'm rolling out UltraVNC to a number of machines on the network through the use of Fastpush.

What I can't seem to locate any information on is if there are any best practices for doing this.

Here are my concerns:

The "ultra" folder only has 6 files: auth.dll, authad.dll, omnithread2_rt.dll, vnchooks.dll, vncviewer.exe and winvnc.exe.

These, of course, are copied to the machines you're pushing out to. Common sense suggested replacing the files with the ones from the most recent release of UltraVNC - which worked wonderfully. However, my local install of UltraVNC has a total of 24 files. So this begs the question, "Are my client machines benefiting from UltraVNC's full functionality?" I'm betting the obvious answer is "No".

That being the case, what steps would I need to take to basically have a complete install of UltraVNC on my client workstations without having to manually install to each machine? Is this even possible? What about the UltraVNC Driver? Is there a way I can push that as well? Am I losing functionality I should even be worried about?

Any help and or advice on this would be appreciated.

Thanks!

Phil · Post by **Phil** » 2004-06-07 14:59

dansajd wrote:I'm rolling out UltraVNC to a number of machines on the network through the use of Fastpush.

What I can't seem to locate any information on is if there are any best practices for doing this.

Here are my concerns:

The "ultra" folder only has 6 files: auth.dll, authad.dll, omnithread2_rt.dll, vnchooks.dll, vncviewer.exe and winvnc.exe.

These, of course, are copied to the machines you're pushing out to. Common sense suggested replacing the files with the ones from the most recent release of UltraVNC - which worked wonderfully. However, my local install of UltraVNC has a total of 24 files. So this begs the question, "Are my client machines benefiting from UltraVNC's full functionality?" I'm betting the obvious answer is "No".

That being the case, what steps would I need to take to basically have a complete install of UltraVNC on my client workstations without having to manually install to each machine? Is this even possible? What about the UltraVNC Driver? Is there a way I can push that as well? Am I losing functionality I should even be worried about?

Any help and or advice on this would be appreciated.

Thanks!

The fastpush code is too clever for its own good, and copies files based on some hard-coded (in fastpush) file patterns. Why not just copy everything from your ultrravnc source directory?

You need:

auth.dll, authad.dll, authlogonuser.dll, ldapauth*.dll, logmessages.dll, unzip32.dll, vnchooks.dll, vncviewer.exe, winvnc.exe, zip32.dll, and zlib.dll.

(OK, maybe you don't need ALL of the above, but what the heck, copy them anyhow).

The zip/unzip stuff is used for file transfers, IIRC.

It should be possible to automatically install the Win 2000/XP/2003 display driver via Fastpush, but that may be more hassle than it is worth.

Guest · Post by **Guest** » 2004-06-08 11:39

I emailed the author of Fastpush a while ago, and he suggested some modifications to his code to make it install the latest versiono of Ultra.

Previously, there was an installation of vanilla VNC 3 on the target systems. For some reason, I found that I had to use fastpush to remove it a few times (weird, huh?), and then reboot, before installing Ultra (otherwise it wouldn't allow me to use Ctrl-Alt-Del).

Also, does anybody know if you can install the driver remotely, and if you can, whether you need to reboot afterwards?

Thanks,
Victor

Post by **Rudi De Vos** » 2004-06-08 12:13

Driver install can be done without reboot..
Uninstall and upgrade of driver require a reboot.

hemaroid · Post by **hemaroid** » 2004-06-08 12:40

Is "setupdrv.exe install" enough to install the RC17 driver both on fresh install and for upgrading? I'm making a fastpush equivalent for ultravnc and I sometimes get a message that the second part of the installation has failed. But also on some machines the drivers doesn't seem to be used even if I got no errors with the install.
Runnig the setup for the mirror driver seems to fix this so there seems to be a step in the setup process that I'm missing.

Post by **Rudi De Vos** » 2004-06-08 13:16

Setupdrv was updated on 7/6
Can you test if this fixed this issue.....

But reboot is needed before the driver can be used by vnc.
Perhaps i need to remove some extra messages boxes to make
it more suitable for remote install

Rdv

prandal · Post by **prandal** » 2004-06-08 15:32

You could add a /q or /s (quiet or silent) switch to setupdrv to suppress messages for those who want to do a remote install.

Guest · Post by **Guest** » 2004-07-16 11:44

Yes, it seems to have fixed the issue. Thank you very much

I agree with the silent command line option. That would enable me to create a much cleaner remote installation.

Fastpush - Best Practices?

Fastpush - Best Practices?

Re: Fastpush - Best Practices?