Mass rollout of client software

Message boards : BOINC client : Mass rollout of client software
Message board moderation

To post messages, you must log in.

AuthorMessage
NELLIE1

Send message
Joined: 9 May 06
Posts: 7
United Kingdom
Message 4267 - Posted: 9 May 2006, 9:07:18 UTC

I am new to this and please advise

We are currently proofing a requirement with our Company 'Serco'. The requirement from Serco is to design a custom screen saver using VB6 and
be able to allow configure / mass installation of BOINC client through our screensaver . The proper questions to our requirements as follows

1) What is the best option of installing BOINC clients on about 4000 pc's accross a Company internet.
2) We would like a single logon which the clients uses to access a defined project which we control.Is this possible for many clients to use one account to a certain project ?
3) Do you have API'S for visual Basic 6 which we can use to configure the client, e.g cpu usage,memory usage and others.
4) We do not want Boinc interfering with our custom screensaver but only to activate on low pc usage.
5) Could we embed the BOINC client in our screensaver with out the need of a full client installation (e.g have only necessary components of BOINC and embed this on our screensaver code)

Many kind thanks

ID: 4267 · Report as offensive
mmciastro
Avatar

Send message
Joined: 30 Aug 05
Posts: 98
Message 4270 - Posted: 9 May 2006, 9:29:40 UTC
Last modified: 9 May 2006, 9:32:01 UTC

wooa nellie, that's alot of puters. Just so you know, most people answering questions here are just regular users that volunteer time to do so. The actual devs are few and don't necessarily read these boards regularly. This might be best asked directly to them. I'm not willing to give out personal email addresses, but you could sign up for the "Boinc Developers" mail list, and ask this question there. I know it'll get seen by the right people.

tony
ID: 4270 · Report as offensive
Keck_Komputers
Avatar

Send message
Joined: 29 Aug 05
Posts: 304
United States
Message 4272 - Posted: 9 May 2006, 12:23:23 UTC
Last modified: 9 May 2006, 12:24:52 UTC

1. Assuming they are windows machines you can use active directories to customise and deploy the BOINC client.

2. Using one account for all these computers is not a problem. In fact the easiest way to attach them is to manually attach one then copy the account*.xml file from that host to all the new hosts.

3. The preferences are all web based. Percent of CPU is not currently an option. However BOINC launches apps at a very low priority so they normally get out of the way when anything else runs.

4. BOINC can be set up independantly from the screensaver and can be set to run only when idle.

5. This should be possible but since BOINC can be set up independantly it is probably not worth the effort.

The wiki has a wealth of information that may help you, see the link in my sig.
BOINC WIKI

BOINCing since 2002/12/8
ID: 4272 · Report as offensive
NELLIE1

Send message
Joined: 9 May 06
Posts: 7
United Kingdom
Message 4273 - Posted: 9 May 2006, 14:11:00 UTC

Many kind thanks on this....
I am new to this so please accept my apologies for not understanding

What do you mean

(2. Using one account for all these computers is not a problem. In fact the easiest way to attach them is to manually attach one then copy the account*.xml file from that host to all the new hosts.)

So in my senerio... the company decides to do a research hookup.I contact the research and create an account and get id file and a site. The company decides now we need to rollout the account to all pc's . Would you say that the XML be kept centrally and the clients will pick up the changes.

We want to take this serious and of course be helpful to alot of researches


ID: 4273 · Report as offensive
Aurora Borealis
Avatar

Send message
Joined: 8 Jan 06
Posts: 448
Canada
Message 4275 - Posted: 9 May 2006, 17:44:22 UTC - in response to Message 4273.  

Many kind thanks on this....
I am new to this so please accept my apologies for not understanding

What do you mean

(2. Using one account for all these computers is not a problem. In fact the easiest way to attach them is to manually attach one then copy the account*.xml file from that host to all the new hosts.)

So in my senerio... the company decides to do a research hookup.I contact the research and create an account and get id file and a site. The company decides now we need to rollout the account to all pc's . Would you say that the XML be kept centrally and the clients will pick up the changes.

We want to take this serious and of course be helpful to alot of researches


At the moment, as I understand it, Boinc as certain requirement.
Boinc needs to be install on each PC and operate independently with access to the internet.

There is no mass deployment option at the moment, but it is on the todo list.

To bypass the need for each computer to attach to a project, you can create a base system that attaches to the project then copy the Boinc folder to all the other systems with all the needed files. A Boinc install will still need to be done on top of this folder at each computer, but it would be ready to start downloading work immediately.

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470
ID: 4275 · Report as offensive
Rom Walton
Project developer
Avatar

Send message
Joined: 26 Aug 05
Posts: 164
Message 4277 - Posted: 9 May 2006, 18:02:02 UTC

Here is a pretty good write up of doing a mass deployment of the client software:
http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=5792

I should check back with him, he was changing the script around to make it generic and work for multiple project.

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog
ID: 4277 · Report as offensive
NELLIE1

Send message
Joined: 9 May 06
Posts: 7
United Kingdom
Message 4424 - Posted: 22 May 2006, 13:33:07 UTC

I have managed to get things working now by copying the account*.xml and restarting the service. Question

The issue I have is to package it up using msiexec using the paramters of

msiexec /i boinc.msi /qn /l c:\\boinc.log setuptype='Service' ALLUSERS=0
ENABLESCREENSAVER=0 ENABLELAUNCHATLOGON=0
LAUNCHPROGRAM=0 SERVICE_DOMAINUSERNAME='%COMPUTERNAME%\\%USERNAME%'
SERVICE_PASSWORD='%PASSWORD%'
SERVICE_GRANTEXECUTIONRIGHT=1

I expect it to load it as a service . But going into Windows services I cant see , My logon allows it to start services and i have admin rights. Therefore
USERNAME is me ... what is happening ?

ID: 4424 · Report as offensive
NELLIE1

Send message
Joined: 9 May 06
Posts: 7
United Kingdom
Message 4427 - Posted: 22 May 2006, 15:27:41 UTC

also I need to roll this out on windows 95 any ideas ?
ID: 4427 · Report as offensive
Aurora Borealis
Avatar

Send message
Joined: 8 Jan 06
Posts: 448
Canada
Message 4429 - Posted: 22 May 2006, 16:42:25 UTC - in response to Message 4427.  

also I need to roll this out on windows 95 any ideas ?

Win 95 presents its own challenges since it's not directly supported by Boinc. I've seen posts of work arounds on the Seti and Seti-Beta forum. I'll see if I can locate those posts.

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470
ID: 4429 · Report as offensive
NELLIE1

Send message
Joined: 9 May 06
Posts: 7
United Kingdom
Message 4441 - Posted: 23 May 2006, 8:05:37 UTC

ALSO this is important ... and all of you I really appreciate this help very much


I have managed to get things working now by copying the account*.xml and restarting the service. Question

The issue I have is to package it up using msiexec using the paramters of

msiexec /i boinc.msi /qn /l c:\\boinc.log setuptype='Service' ALLUSERS=0
ENABLESCREENSAVER=0 ENABLELAUNCHATLOGON=0
LAUNCHPROGRAM=0 SERVICE_DOMAINUSERNAME='%COMPUTERNAME%\\%USERNAME%'
SERVICE_PASSWORD='%PASSWORD%'
SERVICE_GRANTEXECUTIONRIGHT=1

I expect it to load it as a service . But going into Windows services I cant see it , My logon allows it to start services and i have admin rights. Therefore
USERNAME is me ... what is happening ?

ID: 4441 · Report as offensive

Message boards : BOINC client : Mass rollout of client software

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.