Got my M3 Ultra Studio today. First thing to do is was duplicate the user setting and environment from an M4 Pro MacBook Pro. The MBP was purchased a few months ago. It's relatively new (after all, it's an M4 Pro). Only a few programs are installed. Everything is newly/cleanly installed, not migrated from any previous Macs. So it's relative clean and simple. The OS on the MBP is 15.5, the latest.
The M3 Ultra Studio came with 15.3 OS. I did not try to upgrade it to 15.5 nor try to use Migration Assistant during the initial setup. Only after the setup, I upgraded it to 15.5 and opened Migration Assistant. Then it came the trouble: the Migration Assistant did not see the MBP. Both are connected to the same wifi network, and both have firewalls disabled. The Migration Assistant just couldn't see the MBP.
I tried the following methods connecting the two computers:
1. Use a different wifi router (AirPort Extreme).
2. Use ethernet (through AirPort Extreme)
3. Directly connect the two with an ethernet cable (the MBP needs an adapter, of course)
4. Directly connect the two with a firewire cable
5. Connect the two to my cell phone's wifi hotspot
In all the above methods (wifi, ethernet, firewire), the Studio can see the MBP in finder. Can see the files on it, and can share screens. The two computers are aware about the existence of each other and can connect to each other without any problems. The only problem is in Migration Assistant. The Migration Assistant on the Studio just refuses to show the MBP for migration.
At the end, I backed up the system and user data of the MBP in an external disk with Time Machine. Then I can use the TM backup for migration. So the Studio is good to go now. But I just can't figure out why Migration Assistant refuses to show the MBP as a migration source. In the past with many generations of Macs, my experience with Migration Assistant was always pleasant. It made setting up a new computer super easy. This time, it's so frustrating. I have no idea what I did wrong.
Any insights on this? With this M3U Studio and M4P MBP, it will probably be a very long while later when I have a new Mac. But I still would like to know what went wrong with the Migration Assistant. I Googled around and check quite several articles. None is useful. So I appreciate any helps here.
The M3 Ultra Studio came with 15.3 OS. I did not try to upgrade it to 15.5 nor try to use Migration Assistant during the initial setup. Only after the setup, I upgraded it to 15.5 and opened Migration Assistant. Then it came the trouble: the Migration Assistant did not see the MBP. Both are connected to the same wifi network, and both have firewalls disabled. The Migration Assistant just couldn't see the MBP.
I tried the following methods connecting the two computers:
1. Use a different wifi router (AirPort Extreme).
2. Use ethernet (through AirPort Extreme)
3. Directly connect the two with an ethernet cable (the MBP needs an adapter, of course)
4. Directly connect the two with a firewire cable
5. Connect the two to my cell phone's wifi hotspot
In all the above methods (wifi, ethernet, firewire), the Studio can see the MBP in finder. Can see the files on it, and can share screens. The two computers are aware about the existence of each other and can connect to each other without any problems. The only problem is in Migration Assistant. The Migration Assistant on the Studio just refuses to show the MBP for migration.
At the end, I backed up the system and user data of the MBP in an external disk with Time Machine. Then I can use the TM backup for migration. So the Studio is good to go now. But I just can't figure out why Migration Assistant refuses to show the MBP as a migration source. In the past with many generations of Macs, my experience with Migration Assistant was always pleasant. It made setting up a new computer super easy. This time, it's so frustrating. I have no idea what I did wrong.
Any insights on this? With this M3U Studio and M4P MBP, it will probably be a very long while later when I have a new Mac. But I still would like to know what went wrong with the Migration Assistant. I Googled around and check quite several articles. None is useful. So I appreciate any helps here.