Deploying clients over network?

[DarkShadows]

Hello,

I don't post here very much as my distributed.net output is quite meagre 😱

However, that could change 😀

I recently talked with my father about assimilating his office computers (~20-30). They aren't bleeding edge, but i'm sure that their output will be decent. They computers consist of anything from p166mmx's to ppro200's to PIII's etc. I have received permission to run distributed.net on the computers. I prefer running distributed.net as it seems to be quite network / user friendly and it's presence is not noticable by the user.

The question is, how can i install the client on all computers on the network without physically having to go from workstation to workstation.

Is there anything such as a NT script or something like that which would automatically install the client on all computers connected to the server? (And also any computers that are added later as well)

Maybe this is just wishful thinking 🙂

Any help would be greatly appreciated 🙂

 

[SaX0N]

i've never really mucked around with deploying dnetc via scripts, although i had it running on a fair few winnt machines at one stage... all i did was use the RemoteCows program and a proxyer, although i think remotecows would be getting fairly old now and might not work with the newer clients

anyways your best bet it so to go the distributed.net downloads page and have a look in the 3rd party client/proxy add on's section, there is alot of usefull programs

edit - in having a look around atm i found this program that looks very promising in doing what you need. Remote Service Control Center

 

[BurntKooshie]

You could set it up so that all the clients point towards a Pproxy, and I believe there are other programs such as remote cows, but others have more experience than me (ie, they have experience, I don't 😉 )

 

[IJump]

I have about 450 computers in my network. I initially installed the client using an NT Login script. I used a UNC to copy the files down. That section looked something like this:

if exist c:\rc5\dnetc.exe goto skip
md c:\rc5
copy \\server\rc5\*.* c:\rc5
c:\rc5\dnetc -install
c:\rc5\dnetc -svcstart
:skip

I had a share on the server named rc5 tht help my dnetc.exe and dnetc.ini files. The first line would skip loading the client if it already existed. After that, if the client did not exist, it would make the directory, copy the files, install dnetc as a service, and start it. The only problem with this is that the user will have to click an "OK" button when the service is installed.

 

[DarkShadows]

Thanks for all the replies!

Does anyone know if it's possible to supress any output to screen from the client when installing as a service on win9x/ME machines?

In otherwords, is it possible to disable the popup confirming that the service has been installed?

 

[SlangNRox]

Can't you just install using a tacube floppy disk with a edited ini file with your info on it. This shouldn't take that much time if its 20-30 computers.