New 8.3 beta causing a problem with a cloned machine
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 308
- Joined: Wed Feb 16, 2022 1:18 am
New 8.3 beta causing a problem with a cloned machine
The new beta is nice, I've logged all my machines into a newly created proper account, and they all can see each other.
Except one. I have two very similar machines, and one lost it's hard disk n an untimely manner. I cloned it form the other one to save time quite a while ago. Not a problem until I upgraded beat from 8.1 to 8.3. Now they both call themselves the same name. How do I split them?
Except one. I have two very similar machines, and one lost it's hard disk n an untimely manner. I cloned it form the other one to save time quite a while ago. Not a problem until I upgraded beat from 8.1 to 8.3. Now they both call themselves the same name. How do I split them?
-
- Site Admin
- Posts: 7937
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: New 8.3 beta causing a problem with a cloned machine
Uninstall the client completely and reinstall. Also make certain the OS install is renamed differently, a clone may have inherited the same naming and settings. The client can not be cloned, that causes problems by having the same ID as the system it was cloned from.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 308
- Joined: Wed Feb 16, 2022 1:18 am
Re: New 8.3 beta causing a problem with a cloned machine
I'll try that tomorrow, but I thought perhaps I could remove the setting and it would recreate it. In Boinc there's an ID it puts in a configuration file. If I delete it, it recreates one based on hardware serial numbers or something.
-
- Site Admin
- Posts: 7937
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: New 8.3 beta causing a problem with a cloned machine
When installed the client gets an ID assigned the first time it connects to the servers. I do not know where that ID is stored, and it is not based on your hardware.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 308
- Joined: Wed Feb 16, 2022 1:18 am
Re: New 8.3 beta causing a problem with a cloned machine
What do you mean by "make certain the OS install is renamed differently"? They're on the same network, they have to have different names under Windows. Do you mean the Windows network name or is there something else? Because other than the network name, they're pretty much identical. I just copied one then renamed it.Joe_H wrote: ↑Fri Feb 09, 2024 5:07 pm Uninstall the client completely and reinstall. Also make certain the OS install is renamed differently, a clone may have inherited the same naming and settings. The client can not be cloned, that causes problems by having the same ID as the system it was cloned from.
-
- Site Admin
- Posts: 7937
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: New 8.3 beta causing a problem with a cloned machine
The Windows network rename probably is enough. But I have seen cloned systems try to reuse the same network address and other settings that need to be changed.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 308
- Joined: Wed Feb 16, 2022 1:18 am
Re: New 8.3 beta causing a problem with a cloned machine
Uninstall (including ticking delete data - although it remembered my login?!) and reinstall seemed to work. Do you mean IP address? Those are obviously different or they couldn't operate on the same network. MAC address is hardware related so different.
-
- Site Moderator
- Posts: 1117
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: New 8.3 beta causing a problem with a cloned machine
You cloned the entire machine, or just fah?
-
- Posts: 308
- Joined: Wed Feb 16, 2022 1:18 am
Re: New 8.3 beta causing a problem with a cloned machine
The entire machine. I see no reason to clone a program.