Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
General Discussions
Switcher Hangout (Windows to Mac)
iMac M1 Monterey running slowly.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MacInWin" data-source="post: 1900343" data-attributes="member: 396914"><p>OK, an update. Spent two hours playing "Stump the Apple Tech Rep," and I won! Totally stumped 5 of them in one call!</p><p></p><p>At the end I offered to do a Nuke'n'pave reinstall and they agreed that might be the only way to sort it out.</p><p></p><p>So, EACAS, here we go.</p><p></p><p>You find Erase All Content And Settings in System Preferences by opening the SysPrefs pane, then on the top bar, click on the System Prefences and the second menu item is "Erase All Content And Settings." Click on that and you get started down the trail to nuke-land. You get warnings of impending doom, pleas to back up with Time Machine, warnings that this will also erase other accounts, etc. Just keep plowing on and eventually it asks for your AppleID to log out of there and finally, it kicks off the EACAS process.</p><p></p><p>Surprisingly, that doesn't take long at all. After all, it's not really erasing anything, just resetting a lot of flags and setting back to factory standards. In a lot less time than I thought, the system boots to the "hello" screen and the setup begins.</p><p></p><p>Ok, now cue the sinister music...</p><p></p><p>At Eclectic Light website, Howard had suggested that it was no longer necessary to execute the Migration Assistant before creating a user on the new system. In fact, for a new system that may need immediate updates, he suggests creating an account with exactly the same name and password as on the old Mac from which you are migrating. So, that is what I did this time.</p><p></p><p>Part of that setup was to activate Apple Pay, and enter a credit card into the Wallet. Given that it knew about what I already had because it had asked for my AppleID and password to log into that account, I let it enter all of the cards it knew about. All I had to provide were the CVC numbers on the cards and agree to the terms. No problem, we're all good.</p><p></p><p>So, account is created, system boots into the login screen, I log in and launch Migration Assistant. First problem is that it wanted either the old Mac (gone) or a Time Machine backup (no recent one available because TM has not worked in three weeks, remember). The only option was to restore from a December 15 TM that was the last backup that worked.</p><p></p><p>First thing that popped up was that it saw two accounts on the TM backup (Logical, I had two accounts on the system) and it wanted to know if I wanted to merge the old data into my new account or keep them separate (ominous music gets louder). I picked the merge option for no particular reason. Restoration starts, all goes well. At the end of migration, the system reboots to the login screen, I log into my account. Everything seems to be there, but I do have to log into iCloud to get my Messages up to date, and I needed to import my Mail to get to my messages there. While Mail is importing, I look at the Wallet in System Preferences. Uh, oh, no cards. (Music gets really ominous here.) I clicked on Add card and in a couple of seconds, the same error message pops up! Dang!</p><p></p><p>I have a couple of minutes, so I ponder it while I am recovering Mail. It dawns on me that the reason to create an account first on a new machine is to be able to get the latest update in system software before you recover from the old machine or time machine. Maybe I don't need to do that. More thinking and I realize that maybe the "Security issue" that Wallet is finding is not really any security issue, but is the fact that the account that entered cards to Wallet has been change/merged/overwritten by the Migration and it no longer trusts that user. Seems to me that Apple could have considered this possibility, but whatever...</p><p></p><p>Ok, back to EACAS again, lather, rinse, repeat. But this time I don't create a new account, I just restored from back in December. Once the migration is complete, I still have to log into AppleID, iCloud and get that going, Mail still imports my mail, but now everything is catching up. And I can enter my cards to Wallet and they are still there!</p><p></p><p>So, lesson learnt after all this is that while creating a new account and updating the system software for a brand new machine is a good idea, you need to be aware that if you use Apple Pay on the Mac, you don't want to enter anything into Wallet until all migrations are done. Another way to avoid the problem is to create an account, update the OS and firmware, then use EACAS to get back to "naked" and use Migration Assistant at first offer.</p><p></p><p>OK, Wallet sorted. Off to test Time Machine to see if it works now.</p></blockquote><p></p>
[QUOTE="MacInWin, post: 1900343, member: 396914"] OK, an update. Spent two hours playing "Stump the Apple Tech Rep," and I won! Totally stumped 5 of them in one call! At the end I offered to do a Nuke'n'pave reinstall and they agreed that might be the only way to sort it out. So, EACAS, here we go. You find Erase All Content And Settings in System Preferences by opening the SysPrefs pane, then on the top bar, click on the System Prefences and the second menu item is "Erase All Content And Settings." Click on that and you get started down the trail to nuke-land. You get warnings of impending doom, pleas to back up with Time Machine, warnings that this will also erase other accounts, etc. Just keep plowing on and eventually it asks for your AppleID to log out of there and finally, it kicks off the EACAS process. Surprisingly, that doesn't take long at all. After all, it's not really erasing anything, just resetting a lot of flags and setting back to factory standards. In a lot less time than I thought, the system boots to the "hello" screen and the setup begins. Ok, now cue the sinister music... At Eclectic Light website, Howard had suggested that it was no longer necessary to execute the Migration Assistant before creating a user on the new system. In fact, for a new system that may need immediate updates, he suggests creating an account with exactly the same name and password as on the old Mac from which you are migrating. So, that is what I did this time. Part of that setup was to activate Apple Pay, and enter a credit card into the Wallet. Given that it knew about what I already had because it had asked for my AppleID and password to log into that account, I let it enter all of the cards it knew about. All I had to provide were the CVC numbers on the cards and agree to the terms. No problem, we're all good. So, account is created, system boots into the login screen, I log in and launch Migration Assistant. First problem is that it wanted either the old Mac (gone) or a Time Machine backup (no recent one available because TM has not worked in three weeks, remember). The only option was to restore from a December 15 TM that was the last backup that worked. First thing that popped up was that it saw two accounts on the TM backup (Logical, I had two accounts on the system) and it wanted to know if I wanted to merge the old data into my new account or keep them separate (ominous music gets louder). I picked the merge option for no particular reason. Restoration starts, all goes well. At the end of migration, the system reboots to the login screen, I log into my account. Everything seems to be there, but I do have to log into iCloud to get my Messages up to date, and I needed to import my Mail to get to my messages there. While Mail is importing, I look at the Wallet in System Preferences. Uh, oh, no cards. (Music gets really ominous here.) I clicked on Add card and in a couple of seconds, the same error message pops up! Dang! I have a couple of minutes, so I ponder it while I am recovering Mail. It dawns on me that the reason to create an account first on a new machine is to be able to get the latest update in system software before you recover from the old machine or time machine. Maybe I don't need to do that. More thinking and I realize that maybe the "Security issue" that Wallet is finding is not really any security issue, but is the fact that the account that entered cards to Wallet has been change/merged/overwritten by the Migration and it no longer trusts that user. Seems to me that Apple could have considered this possibility, but whatever... Ok, back to EACAS again, lather, rinse, repeat. But this time I don't create a new account, I just restored from back in December. Once the migration is complete, I still have to log into AppleID, iCloud and get that going, Mail still imports my mail, but now everything is catching up. And I can enter my cards to Wallet and they are still there! So, lesson learnt after all this is that while creating a new account and updating the system software for a brand new machine is a good idea, you need to be aware that if you use Apple Pay on the Mac, you don't want to enter anything into Wallet until all migrations are done. Another way to avoid the problem is to create an account, update the OS and firmware, then use EACAS to get back to "naked" and use Migration Assistant at first offer. OK, Wallet sorted. Off to test Time Machine to see if it works now. [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
General Discussions
Switcher Hangout (Windows to Mac)
iMac M1 Monterey running slowly.
Top
