Migration Assistant Causing Access on New MBP to Impersonate Other Mac

TresyK said:
Ok, I did as instructed. I even uninstalled and reinstalled Access on both machines per your KB article for the second time, just to make sure both systems were "pristine." The problem persists. The report IDs are 177150246 and 177149861.
Click to expand...
I really appreciate all your patience and co-operation. We'll now investigate the issue internally and get back to you on this as soon as possible. Please stand by.
 
Hemnath@Parallels said:
Thanks for waiting. Is one of your Mac machines a result of drive cloning of the other? If so, then please perform these steps.
Click to expand...
I never got the email that presumably went out to alert me to the above question. As I said in the title to this thread, the MBP used Migration Assistant to set itself up from my older Mac Pro. You tell me if that's "cloning".
 
TresyK said:
As I said in the title to this thread, the MBP used Migration Assistant to set itself up from my older Mac Pro. You tell me if that's "cloning".
Click to expand...
Before we discuss this, please confirm whether you have actually performed the steps suggested earlier. Please do those steps (assuming they are related to your case) if you haven't already and revert with the results.
 
You asked me to do those steps IF I had cloned my Mac, and I said asked you whether Migration Assistant constituted "cloning." If you wanted me to do those steps regardless of the answer, you should have skipped the "IF" part. Follow these steps, brought up for the first time months into this thread, fixed it. Seems in retrospect that it could have been solved in 5 minutes (which is what I expected when I asked), but I'm glad it's finally resolved.
 
TresyK said:
You asked me to do those steps IF I had cloned my Mac, and I said asked you whether Migration Assistant constituted "cloning." If you wanted me to do those steps regardless of the answer, you should have skipped the "IF" part. Follow these steps, brought up for the first time months into this thread, fixed it. Seems in retrospect that it could have been solved in 5 minutes (which is what I expected when I asked), but I'm glad it's finally resolved.
Click to expand...
There's no need to make pointless presumptions, thinking that I asked you to perform the said steps regardless of whether or not you had cloned your Mac. After you indicated that you didn't know if Migration Assistant was the same as drive cloning, I asked you again to perform the said steps merely under a rational assumption that those steps might be related to your scenario, as Migration Assistant and drive cloning might have technical similarities although they are different processes. Anyways, good to know that the issue has been resolved. Pls get back to us for any further queries.
 
Last edited:
TresyK said:
Was wondering what had happened to my response. I will not rely on email replies going forward.
Click to expand...
How do I get rid of this? I tried reinstalling over the migrated copy of Access, but that didn't fix it. I've tried logging in and out turning Access off and on. So far, nothing. I assume there's some cookie somewhere in the bowels of my Mac that needs to be deleted but I have no idea what it would be.
 
ZIMZ said:
How do I get rid of this? I tried reinstalling over the migrated copy of Access, but that didn't fix it. I've tried logging in and out turning Access off and on. So Dafont Showbox Adam4adam far, nothing. I assume there's some cookie somewhere in the bowels of my Mac that needs to be deleted but I have no idea what it would be.
Click to expand...
 
You must log in or register to reply here.
Back
Top