To not constantly get a new CPID as users joins new projects, the oldest CPID should propagate to all projects, as long as there's a connection to all projects. The easiest is to just keep one computer attached to all projects, and as long as they're making regular scheduler-requests to all projects, the CPID should "synch-up" in a couple days.

To speed-up things, you can manually issue an update to all the projects.

NekdDrgn,

No need to wait for daily stats updates, in fact at project level it's irrelevant. Some projects have long time spans set before a client will follow the "talk to me and tell me you're still alive and interested to do more work for me", particular if they haven't got any work. Just do a manual update in the BOINC manager's project tab with any of your older/oldest projects and WCG to have My Grid > My Profile to pick up that oldest CPID. The client compares them and then forces the older CPID to be uploaded to the project with the newer. When e.g. BOINCstats completes it's update cycle your various contributions will consolidate.

I just looked in the WCG profile (the oldest BOINC project for me) and in the Docking@home account (the newest BOINC project for me) and both showed the same CPID, so think that all the later ones are discarded. Never tried to find out, but I've been for weeks detached from WCG and never observed at any 3rd party stats generator that things went out of sync i.e. WCG suddenly not being rolled up into my totals.

For BAM to work with WCG on a device you first need to manually attach / detach to WCG on that client. Also the WCG and BAM passwords must be the same, and of course, you need to tick the box at BAM to always attach WCG to any new hosts **. That's this page.

http://boincstats.com/bam/resources.php

Don't think the member name is relevant. At least mine is here and there different.

Edit: ** Just tried with a brand new system, clean 6.10.18 client and WCG already and still attached to the client. It happily registered with BAM and communicated without throwing fits such as detaching from WCG as first action. The message log of the client:

20-11-2009 18:13:31 Fetching configuration file from http://bam.boincstats.com/get_project_config.php
20-11-2009 18:13:32 Resuming network activity
20-11-2009 18:13:53 Contacting account manager at http://bam.boincstats.com/
20-11-2009 18:13:55 Account manager: BAM! User-ID: 4xxx
20-11-2009 18:13:55 Account manager: BAM! Host-ID: 1xxxxx
20-11-2009 18:13:55 Account manager: This host connected 1 times to BAM!
20-11-2009 18:13:55 Account manager contact succeeded
20-11-2009 18:14:14 Contacting account manager at http://bam.boincstats.com/
20-11-2009 18:14:15 Account manager: BAM! User-ID: 4xxx
20-11-2009 18:14:15 Account manager: BAM! Host-ID: 1xxxxx
20-11-2009 18:14:15 Account manager: This host connected 2 times to BAM!
20-11-2009 18:14:15 Account manager contact succeeded

No error messages, not on WCG side, not in client, not on BAM side observed.

I have had the same problem since I joined WCG almost 3 years ago.
My other projects, many of which I joined earlier, use one CPID and WCG uses a different one. This is despite having one system attached to all my existing projects, including older live projects and using the same email address, and usually the same name and team.

I would even detatch and creat a new account if I knew it would make give me the same CPID as on other projects, but I would not be able to use the same name or email address, otherwise I would just get my existing WCG CPID.

Does anyone KNOW how to fix this?
No random speculations please, this is one for the experts.

Thanks,