On Jan 13, 2011, at 10:26 AM, Brian White - WebHostingSolutions.com wrote:
> IAfter the migration completed I realized that I ended up with 2 admin users
> instead of 1 (merged) admin user. Of course I can't access my migrated data
> and apps unless I log out of the "new" Mac admin user and then log in as the
> admin user from the old Mac (that user's admin privileges apparently
> transferred over).
I can't count the number of clients I've had who called me with this problem.
BY the time they call me, they've already set up a new user account on the new
machine -- often with exactly the same name, making it even rougher -- and want
to know how to get out of it. Despite the "ka-ching!$" nature of these
incidents, they annoy my sense of good engineering.
I wish the initial screen you see when setting up a new Mac that asks you if
you have any data to transfer from an old Mac contained a warning like, "DO IT
NOW, or explore Permissions Hell when you do it later!!"
> I have not yet transferred to the new Mac for my day to day work, so if
> necessary I could erase the drive and start from scratch, although it would
> be great to avoid that. Either way though, because I'm still using the old
> Mac for a few tasks until I can transition 100% to the new one, I'll
> eventually have to transfer some files over manually (I'm trying to keep that
> in mind to hopefully avoid permissions issues when I have to move those
> files).
>
> On an Apple support discussion regarding this topic, I found this comment:
>
> "Or, if the new account has nothing of interest to you on it yet, just make
> sure the old account already transferred over is an admin one, log into it,
> and delete the new account."
>
> That almost seems too simple (therefore an attractive option), and I assume
> there must be a few more recommended or necessary steps in that process that
> are being overlooked or unstated.
No. If you haven't created anything on the new machine yet that you would
regret abandoning, do this.
> BUT, if I did do that, are there some bad consequences that I'll eventually
> come across (i.e. permissions issues)?
There's a really, really minor issue: in all probability, the old user was
"number 501," and the new user will be "number 502." To a well-written
application this should make absolutely zero difference. But I have heard that
there are a rare couple of porkers out there who trip over this, and sorry, I
don't recall who they are. None of them are Apple products, and none of them
are "must-have" third-party apps.
> Now that I think about it, if I did delete the "new" admin account that was
> created, would I simply be able to open iTunes, iPhoto, etc... while logged
> in as the "old" migrated user and import my music and photos into the new
> versions of these apps that came pre-installed?
Well, wrong question. If you log in as the old (migrated) user, you won't have
to import anything, because presumably all your photos and tunes have ALREADY
been populated there for you.
> What about everything associated with my iPhone syncing? I'm sure I could go
> on with all the possible questions... sigh.
All syncing cares about is what your user ID is and what your store account is.
That is, modulo the raft of problems syncing has every day, all on its own,
which is going to be entirely independent of this.
--
Macs R We -- Personal Macintosh Service and Support
in the Wickenburg and far Northwest Valley Areas.
http://macsrwe.com
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
