With the old seti@home OS-X client, when I wanted to create a disk image which was to be cloned to all my workstations containing SETI@home (using the excellent NetRestore utility from www.bombich.com), I installed and launched seti@home, registered with my account, and then deleted the "workunit.sah" file immediately prior to creation of the disk image. This had the result of ensuring that on each newly cloned workstation (iMacs, eMacs, etc), when the screensaver kicked in, the program was properly configured and proceeded to download a new workunit.

So, under the new system, is it merely sufficient to start and attach a project to BOINC and then remove the workunit files from the "projects/setiathome.berkeley.edu" directory prior to the creation of my disk image to ensure my cloned workstations will run BOINC properly (and I suppose the answer to this depends on the answer to a previous question I wrote about whether BOINC can run as a background process independant of any user- ie at the login screen).

Still no answer on this question. Forgive me for bumping the thread.