Now if something does not work right, then can I not simply delete them while logged in as admin and then restart and be all good?
What circumstance needs going into safe mode?
Yes... correct. It is just a matter of finding which of those folders it is launching from and deleting it. There is a nice, free app called Etrecheck that will create a report for you that shows all those items and where they are located.
You would use safe mode as a diagnostic tool. Say you are having crashes... so what you do is start in safe mode to see if the crashes go away. If safe mode stops the crashes, then that is proof it is one of those launch/startup items causing the crash, because safe mode bypasses all those items.
Since 2006, I have regularly upgraded the OS and used Migration Assistant with every upgrade. Currently using the previous OS version. Now on to a 2016 MB Pro.
Any thoughts as to why I should not use Migration assistant? So much time wasted if I do not use it.
Possible option:
1. Use Migration assistant.
2. Then on new computer cleanup auto start apps. CPU cycles restored, SSD still used by "useless" apps.
I do have a lot of Apps installed that I do not use now, including I think I installed something once which allowed me to install Unix apps etc. But my 2009 MB Pro works fine - I am sure it runs some extra CPU cycles.
Thanks for weighing in!
If you do the migration as part of system setup, it will not cause any permissions issues. What sometimes happens is people will complete system setup and create an account, then AFTER that run Migration Assistant. That scenario can cause permissions problems if the account to be imported is also using userID 501. You can read more about it here.I would advise against using Migration Assistant. I work in tech support at a third party company and have seen too many people with problems with the software I support due to messed up user permissions when they use it. 10.12 makes fixing user permissions. Building a new user profile is just the safer route.
If you do the migration as part of system setup, it will not cause any permissions issues. What sometimes happens is people will complete system setup and create an account, then AFTER that run Migration Assistant. That scenario can cause permissions problems if the account to be imported is also using userID 501. You can read more about it here.
I would advise against using Migration Assistant. I work in tech support at a third party company and have seen too many people with problems with the software I support due to messed up user permissions when they use it. 10.12 makes fixing user permissions. Building a new user profile is just the safer route.
can someone recommend the best way to get back to FROM THE FACTORY setup after create an account, to test a machine?If you do the migration as part of system setup, it will not cause any permissions issues. What sometimes happens is people will complete system setup and create an account, then AFTER that run Migration Assistant. That scenario can cause permissions problems if the account to be imported is also using userID 501. You can read more about it here.
can someone recommend the best way to get back to FROM THE FACTORY setup after create an account, to test a machine?
I'll often setup a simple account to test the machine, screen, HD, dGPU etc, but want to get back to that state and then do a migration assistant backup direct as "first time"
hi guys - migration assistant did not quite work for me
Can you explain step by step exactly what you started with in the way of accounts on both machines and exactly what you did?
So I am thinking there can be two causes of the error:
- Source machine was a different OS.
- CCC backup did not have *.caches and /Library/Logs and Library/Caches. (This one makes less sense - why would iTunes be skipped then?)
I dunno what went wrong. That should work fine. I don't see how excluding the apps would matter. If you are up for it, might be worth another shot.Yes - 2009 MBP on El Capitan to 2016 MBP on Sierra.
Yes - data source was CCC clone (without caches and logs). Wifi earlier - not relevant.
Have made a CCC clone with all files - nothing left out. Reset the 2016 MBP by Disk Utility erase, and reinstall OS.
Wondering if I should try to migrate one more time, or whether to only try to migrate the User folder - and not the Apps.
Good idea. I will boot into the clone on the 2009 MBP and then try the migration one more time. Will update.I dunno what went wrong. That should work fine. I don't see how excluding the apps would matter. If you are up for it, might be worth another shot.
Can you boot to the clone and login to the accounts there? That would prove at least the clone is good.
I'm a bit confused. Why are you running migration assistant against the backup, rather than against the actual original machine?
Migration Assistant can restore from backups, but it can also talk to a Migration Assistant running on the source machine. That's what I used last time I did this, and it seemed to work fine. I've never tried to use a CCC backup, although I can't see why it should matter; I thought the whole point of CCC was to be identical.
And I've definitely done migrations from 10.10 to 10.12 without any difficulties. Did you get a log file, possibly with some diagnostics or errors?
Hmm. I don't mind doing a direct computer to computer transfer - now I have a ethernet dongle for 2016 MBP.
When you moved from 10.10 to 10.12, did you do a computer to computer transfer?
---
Also, creating a Time Machine backup on a separate external drive thinking that may be a Time Machine backup of 10.11.6 will work.
I started it with Ethernet. And the transfer is still going on after 7 hours. Showed about 5 hours when it started, but 7 hours later still says 3 hours and 20 min. About to give upYeah, I just did computer to computer. I actually used thunderbolt for it; I have a TB3<->TB2 adapter. Did it a couple of times, actually. Only annoyance was that since the 10.10 machine had more recent iTunes, it had to update iTunes during the migration process to import the library.
I may have to give up on this transfer business. Need to start looking at the bright side - the (forced) clean start!I didn't use the migration assistant, as I wanted to start with a clean machine. Instead, my 2016 Macbook SSD is larger than all data on my previous Macbook. I created a folder 'DumpedFilesFromOldMacbook' in my homefolder, attached a Thunderbolt cable between the two MacBooks (with a USB-C/Thunderbolt adapter) and transferred all files between them. The transfer reached speeds around 500 MB/s. So I was done in about 10-15 minutes, copying every data I had.
I installed all apps from the App Store and the respective website and reconfigured everything again.
Like you said, I also had a lot of unused apps, so it gave me a clean machine again![]()
I started it with Ethernet. And the transfer is still going on after 7 hours. Showed about 5 hours when it started, but 7 hours later still says 3 hours and 20 min. About to give up