Exclusive LG phones only from AT&T
Late-2008 MacBooks: Migration Assistant fails
Users who have just purchased new MacBooks may run into an issue in which the Migration Assistant fails to properly transfer data.
Apple Discussions poster fghia writes:
"I just bought the new aluminum MacBook and I am trying to move my files and settings across from my IMac. I set up the DVD / CD share software on both machines. I tried connecting both via direct Ethernet cable and wireless. Both machines are stuck on 'Preparing Information' for a long time, then i get a "Network Connection Failed" error message on the MacBook."
Being first-run hardware, the new MacBooks have had some glitches that have been addressed by software updates from Apple. Before running Migration Assistant on the new MacBooks directly out of the box, connect them to the Internet and run Software Update. Apple recently released software updates for the new MacBooks as well as for Migration Assistant. The standalone installers for these updates are available here:
It is recommended that users apply the Migration Assistant update to all computers, to ensure they are running the same version of the driver and utility software before transferring data from one Mac to another. Doing so has solved the Migration Assistant issues for users.
Resources
This creates a problem for novice users. In order to apply any updates to a brand-new computer, one must first create an account. This means you skip the Migration Assistant, create an account, install an update, then run MI manually.
It's probably best to create that temporary account with some "temporary" name to avoid conflict during the MI transfer of the old account. The old account's UID would also get changed by MI, because the temp account uses 501.
Sounds dicey to me. My recommendation: 1. Update the old computer. 2. Try letting the new computer automatically run MI at startup.
When setting up a new Mac that will receive user data from another, I create the primary user's account (501) - same short name as the old Mac, and a temporary admin account (502). I then run ALL software updates, and finally the Migration assistant - from the temporary account. Migrarion assistant will allow the primary account to be replaced with the old account, and the userID (501) is preserved. Once all he dust settles, the temporary account can be deleted.
This ensures that the new Mac has ALL the proper updates, which is even more critical as the migration tools themselves are invited to that party.
- Marc
Thanks, Marc; your procedure a good idea for me to follow when setting up systems for clients.
Those who set up their own will probably use the automatic Migration.
(I don't know why I had abbreviated it MI rather than MA...)
Good suggestion, Mark, thanks. I saved a copy for future reference.
The fact Apple released the new MacBooks with a flaw in so vital a function is reprehensible. That they patched it quickly is little comfort to those who have to jump through hoops to apply it. This adds substantially to the perception the new MacBooks were poorly thought out from the get go. No FireWire plus a buggy alternative procedure for migration. Thanks for nothing.
In any case, I prefer to migrate user data manually when I'm setting up a new computer. Auto migration can import old problems from the old computer. Better to get a clean start. The trick is to have the old computer running while you're setting up the new one so you can easily access necessary user information - particularly those tidbits like forgotten dot Mac account information locked away in old keychains.
Speaking of which, keychains are among the most problematic items to be migrated from old user accounts to new ones. Again, in my opinion, it's better to start fresh.
Meanwhile, the loss of Target Disk Mode in the new MacBooks makes the whole procedure more complex. Sure, you can set up a direct Ethernet connection, but it's nowhere near as convenient - though, on the up side, it is substantially faster than FireWire 400.
---
Don't anthropomorphize computers.
They hate that.
Thanks for the suggestion.
I tried to transfer data from an older G3 to a new MacBook Pro and failed. I tried the using Migration Assistant later and had more trouble with the user info. I then erased the MacBook and reinstalled all software. From what I read, I?ll try updating the Migration Assistant G3 and try again. If that works, I?m home free. If not, it erase, reinstall, temp user and then Migration Assistant.
I just got a new MacPro 3 GHz 8 Core machine and I had the same issue. I found success by reinstalling OS on new machine and the Migration assistant worked flawlessly. Didn't try updating Migration Assistant on old machine because I thought it was up to date with all of the system updates that have come down the pipe?
- by tonysilva October 24, 2008 8:52 PM PDT
- I also am having consistent hangs when using MIgration Assistant on a new MacBook (13"). Post-MigAsst update. Whether via Ethernet to an older 13" MacBook or via USB to external drive (clone of old MacBook), system hangs after about 5-10 minutes. Console reports "npvhash=4095"
- Like this Reply to this comment
-
(9 Comments)---
tonyinosaka