Message boards : BOINC Manager : Home Domain with Roaming Profiles
Message board moderation
Author | Message |
---|---|
Send message Joined: 20 May 06 Posts: 7 |
I need help with, or found a bug in, how BOINC works with roaming profiles. I have a home domain, running W2K3 server on one computer, and four other computers running W2K Pro in various rooms. Over the past few days I installed BOINC on my office server under the domain admin account, my office desktop under my personal account, and my wife's kitchen desktop under her personal account. Since all our usual accounts were up and running, I then installed on my wife's travel laptop under the local admin account as a service. So far so good. The problem came up when I went to my travel laptop. I decided to logon here under my personal account even though I was already logged on on my office desktop. To my surprise, BOINC showed up in the tray even though I had never installed it on the laptop. When I opened the manager on both computers, it showed an exact one-for-one match with the tasks, with a close match on seconds each had progressed so far. But the laptop version was not running. In a bit of panic, I logged off the laptop, and installed BOINC as a service under the laptop local admin account. My concern is that BOINC will get corrupted if I log into the laptop again under my personal account. I can see my roaming profile on the laptop conflicting with the service, and/or conflicting with either open or closed logins on any other computer. I know there are users out there running BOINC on many computers. Please advise. How are you dealing with this? V/R, Walt |
Send message Joined: 20 May 06 Posts: 7 |
Hmmmm .... a lot of people looked at my question but nobody answered me. Oh well ... I eventually got bored with the graphics and decided I don't need them. So I converted all computers to use service mode. Problem solved. This has the additional benefit that I don't care if Windows Update boots my machines at 3:00 AM. All compurers start computing again after reboot with nobody logged on. |
Copyright © 2024 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.