Vista - Registering a new computer in account

I recently got a new Mac (let's call it "Mac 2") and migrated all my
applications from my old one ("Mac 1") to the new one, including foldershare.
However, when I launched foldershare on the new mac, Foldershare thinks "Mac
2" is my original computer "Mac 1". I can't figure out how to tell it to
register as a new computer under my foldershare account.

I've tried reinstalling the app and also going into settings and renaming my
computer, but Foldershare keeps changing the name back to my old computer's
name, "Mac 1". How do I get foldershare to see my new computer as a new
computer, not my old computer?

Figured it out. I had to delete the Foldershare folder in the Application
Support directory and it cleared everything up.

"random1destiny" wrote:

I spoke too soon. Changing the name of my new Mac computer on Foldershare
somehow changed the name of my old Mac to be the same name. Foldershare
still sees the two as the same computer. When I launch Foldershare on both
computers, it even crashes the Foldershare running on the first computer!!
What the heck is going on?? Why is Foldershare seeing my two computers as
the same exact computer and how to I fix this?


"random1destiny" wrote:

Btw, this problem seems to be occuring with other users who have migrated to
a new Mac. Here's another post with a better explanation of the problem than
mine:

two machines appear as one in foldershare

I have used FolderShare for some time successfully on several machines. I
recently bought a new macbook air, and used the Mac Migration Assistant to
transfer my settings from my mac desktop to the new machine. Foldershare was
also transferred. Now both machines appear as the same identity in
FolderShare. This persists even after I uninstalled FolderShare on the
laptop (including deleting the corresponding directory in my Library folder),
and did a fresh install. When I renamed the laptop during the install
process, the FolderShare name of my old machine was also renamed. How do I
establish independent identities for the two machines?


"random1destiny" wrote:

> How do I establish independent identities for the two machines?

I've never used the Mac client, but couldn't you go to the Web site and
handle the profiles there? Uninstall the client software, delete the
computer relationship via the Web, then re-install and re-establish the
relationship.

Just did exactly what you said but getting the same result. Full uninstall
of foldershare and settings files on both computers, deleted profiles in
online account.

After reinstalling, as soon as I connect the foldershare program to my
account, somehow the computer name from earlier is prepopulated in the
program. Somewhere this computer identity name is still lingering. Then
when install on the second computer it assumes the same identity and crashes
the first.

The only explanation is that there is some file or fingerprint on both of my
computers that Foldershare is seeing and is interpreting as both computers
being the same computer. Any ideas as to what this could be?

"Jason Dunn" wrote:

> The only explanation is that there is some file or fingerprint on both ofI know nothing about Macs, so I can't be of much help...but you're right,
there's got to be SOME file somewhere that's telling FolderShare "Hi, I'm
Mac #1" even when it's Mac #2. Hopefully someone here knows more about
Macs...

Jason Dunn
Executive Editor, Digital Home Thoughts
www.digitalhomethoughts.com

Man, still can't figure this one out. Does anyone have a complete list of
files that Foldershare uses to store its settings? I've delete the
Application Support file, but it still won't forget its old identity.

Since the last post I've changed the name of my computer in my network
Sharing preference pane. It does work if I create a new user profile on my
new mac, though. Unfortunately, doing that would defeat the purpose of
migrating all my old settings to my new mac.

"Jason Dunn" wrote:

Hey, just fixed the problem. I ended up registering a new Foldershare
account and synced my computers to that new account and it now works. So it
seems this issue has something to do on the server side of things, not the
local computers.

"random1destiny" wrote:

I 'm in exactly the same situation as random1destiny however have libraries
shared across 4 windows machines (some VM's) and 2 Macs using my primary live
account, so starting again is not so appealing. Does anyone know of an
alternative solution?

"random1destiny" wrote: