Migrating to new Mac. Best Practices?

I just ordered my first Mac Pro and will be migrating Aperture (and everything else) from my MacBook Pro in a few days.
Question is: Use Migration Assistant or not?
I've heard good stories and bad about people using Migration Assistant and I'm wondering if anyone has some good advice on whether I should trust it.
Some details about my particular situation:
My photography is the most critical content on my MBPro.
I use Aperture with a few plugins (Nik, and others)
All my images are referenced to an external drive.
Other critical apps include Adobe CS3 Photoshop, Illustrator, Dreamweaver
I also have 150+ other apps that can be installed (or not) easily and individually.
Thanks.

i would not recommend migrating applications ... ever ... at all ... especially the pro apps ...
things can go wrong ...
obviously the choice is yours to make, but me, never ... i have all my install disks and would just do it manually ... why take the chance on screwing up a new clean fresh computer ...
this is a topic that pops up now and again ... you can search this board for more opinions ...

Similar Messages

Unable to open indesign after migration to new mac all other programs open and work.

Unable to open indesign after migration to new mac all other programs open and work. Why? Running Yosemite 10.10.1 Indesign CS5

The keyword is "migration." Migrating or copying files for Adobe applications usually does not work. Not all of the necessary subsidiary files are copied to the right location.
You'll need to first clean up the mess with this tool:
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
Then download an installer from here:
Other downloads

After migrating to new Mac iCal pop-up screen is mostly off screen ...

After migrating to new Mac iCal pop-up screen is mostly off screen and I can't seem to find a way to get it so that it pops up in the middle of the screen or anywhere else where I can see the whole thing.

This is a known bug which began to occur with the 10.4.8 update. I suggest you file a bug report with Apple. Its quite annoying and hopefully, the more people who contact Apple about it, the more importance they will give to fixing the problem.

After migrating a new Mac Book Pro from Time Capsule, I noticed that I lost a group of Favorites on the older iMac. The puzzling thing is that the Favorites are on my iPhone--not the old iMac or the new Mac Book Pro. How do I get the Favorites back?

After migrating a new Mac Book Pro from Time Capsule, I noticed that I lost a group of Favorites on the older iMac. The puzzling thing is that the Favorites are on my iPhone--not the old iMac or the new Mac Book Pro. How do I get the Favorites back?

If you are syncing using iCloud, try going to System Preferences/iCloud (computers) and checking Safari. If it is checked, try deselecting it, wait 10-15 seconds, and then check it again.

2nd Mac - best practices using iPhoto on both?

Hi -
I just got a new MacBook and have an iMac that is still the "hub" of my photo library. It is, in fact, about a 180 GB iPhoto library. I know that I can't sync libraries between Macs (a shame - someone should come up with a way to that assuming they haven't already!) so I'm just looking for any best practices?
I got the MacBook to be able to work on some photos while on the road - I can at least work on post processing in Photoshop, etc. I'm thinking now that my best strategy is to possibly work with the images on my MacBook, importing them into the iPhoto library if desired. Then use my Photo sharing service - Phanfare - to "sync" them? It requires me to download them on the other side and pull them again into the iPhoto Library on the iMac?
I don't use the Mobile Me Gallery but I suppose that would be another way to have access to them on the alternate computer?
Any other best practices or suggestions?
Thx!

So, if there are times when I'm not home to access my external drive, then going with the two libraries is the best solution, yes?
Perhaps, but you can get very small and portable external HDs these days.
I'm not sure though if I should really make both a 180 GB iPhoto library, do you? It is a back up true, but seems like a chunk to move
But you only do it once. The first time. Thereafter you're simply updating the other with the changes.
At least maybe I could split into pictures from 2009 - 2010 and have that library for both my iMac and the MacBook. I very rarely access before then (only if I need something specific) so then I could access that via the iMac exclusively?
That would be viable.
I would maintain a +full Library+ on the Desktop, the mobile versions a Smaller subset.
I'm sort of ruling out the one library on the external solution because it eliminates the possibility of being remote -
As I said above you can get tiny portable drives...
unless there is some swanky Login to My Computer or something that works with a Mac that can go remotely to my computer and then to my external drive.
*_This_* might help.
Regards
TD

I want to migrate to new Mac. How do I also Restore the partition with old Snow Leopard?

I will install a second internal HD first, and use Time Machine Restore to it with the Migration Assistant on the new Mac's Mountain Lion.
Then I will erase the preinstalled Mountain Lion internal HD, and:
How do I now proceed to Restore to an internal partition on the new Mac, my (still) left Time Machine copy of Snow Leopard,( just a spare system partition, also for Power PC Apps)?
If I install a new Snow Leopard first from DVD and then tries the Migration Assistant in it, can it us a Mountain Lion Time Machine backup of the Snow Leopard partition? Or can Mountain Lion Migration Assistant be used for Restoring and Migrating Snow Leopard.
I do not have a Snow Leopard Time Machine backup copy of the partition left. Otherwise I could have taken that on a new installed Snow Leopard.
Thankful for all ideas, also I understand that HD Restore fully on the whole partition without using Migration Assistant will not work.
Another question:
I hope that I can use my new Mac with the old Mac OS X licenses and transfer the new preinstalled Mac OS Mountain Lion license to the old Mac, before giving it away?
Thanks,
/groundliner

Thanks!
I'm not familiar with the issue of what Mac OS new Macs manages. That puts things in another perspective. I have Lion on a fast 8 GB USB Stick, can I not boot from that either? Of Course, I may be able to put the Mountain Lion Installer on the stick, instead. It could not upgrade the stick to Mountain Lion due to not having enough space for that. But I maybe could fix that. Just wondering - I have several hard disks around, I could try to put the preinstalled Mountain Lion OS version on one of those. Best copying method?
I did not know that transfer of OS Mountain Lion was not allowed. Leopard license document mentions transfer of hardware and software to another person. So I thought the Mac App Store license was similar - bought for and on just this old iMac, that it also could be transferred to another person. Which would solve the problem for my friend who should have it!
I keep planning, but I think running old Power PC Apps maybe was no big deal.
/groundliner

OS X Server 3.0 new setup -- best practices?

Alright, here's what I'm after.
I'm setting up a completely new OS X Server 3.0 environment. It's on a fairly new (1.5 year old) Mac Mini, plenty of RAM and disk space, etc. This server will ONLY be used interally. It will have a private IP address such as 192.168.1.205 which will be outside of my DHCP server's range (192.168.1.10 to .199) to prevent any IP conflicts.
I am using Apple's Thuderbolt-to-Ethernet dongle for the primary network connection. The built-in NIC will be used strictly for a direct iSCSI connection to a brand new Drobo b800i storage device.
This machine will provide the following services, rougly in order of importance:
1. A Time Machine backup server for about 50 Macs running Maverics.
1a. Those networked Macs will authenticate individually to this computer for the Time Machine service
1b. This Server will get it's directory information from my primary server via LDAP/Open Directory
2. Caching server for the same network of computers
3. Serve a NetInstall image which is used to set up new computers when a new employee arrives
4. Maybe calendaring and contacts service, still considering that as a possibility
Can anyone tell me the recommended "best practices" for setting this up from scratch? I've done it twice so far and have faced problems each time. My most frequent problem, once it's set up and running, is with Time Machine Server. With nearly 100 percent consistency, when I get Time Machine Server set up and running, I can't administer it. After a few days, I'll try to look at it via the Server app. About half the time, there'll be the expected green dot by "Time Machine" indicating it is running and other times it won't be there. Regardless, when I click on Time Machine, I almost always get a blank screen simply saying "Loading." On rare occasion I'll get this:
Error Reading Settings
Service functionality and administration may be affected.
Click Continue to administer this service.
Code: 0
Either way, sometimes if I wait long enough, I'll be able to see the Time Machine server setup, but not every time. When I am able to see it, I'll have usability for a few minutes and then it kicks back to "Loading."
I do see this apparently relevant entry in the logs as seen by Console.app (happens every time I see the Loading screen):
servermgrd: [71811] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
servermgrd: [71811] process will force-quit to avoid deadlock
com.apple.launchd: (com.apple.servermgrd[72081]) Exited with code: 1
If I fire up Terminal and run "sudo serveradmin fullstatus timemachine" it'll take as long as a minute or more and finally come back with:
timemachine:command = "getState"
timemachine:state = "RUNNING"
I've tried to do some digging on these issues and have been greeted with almost nothing to go on. I've seen some rumblings about DNS settings, and here's what that looks like:
sudo changeip -checkhostname
Primary address = 192.168.1.205
Current HostName = Time-Machine-Server.local
The DNS hostname is not available, please repair DNS and re-run this tool.
dirserv:success = "success"
If DNS is a problem, I'm at a loss how to fix it. I'm not going to have a hostname because this isn't on a public network.
I have similar issues with Caching, NetInstall, etc.
So clearly I'm doing something wrong. I'm not upgrading, again, this is an entirely clean install. I'm about ready to blow it away and start fresh again, but before I do, I'd greatly appreciate any insight from others on some "best practices" or an ordered list on the best way to get this thing up and running smoothy and reliably.

Everything in OS X is dependant on proper DNS. You probably should start there. It is the first service you should be configuring and it is the most important to keep right. Don't configure any services until you have DNS straight. In OS X, DNS really stands for Do Not Skip.
This may be your toughest decision. Decide what name you want the machine to be. You have two choices.
1: Buy a valid domain name and use it on your LAN devices. You may not have a need now for use externally, but in the future when you use VPN, Profile Manager, or Web Services, at least you are prepared. This method is called split horizon DNS. Example would be apple.com. Internally you may name the server tm.apple.com. Then you may alias to it vpn.apple.com. Externally, users can access the service via vpn.apple.com but tm.apple.com remains a private address only.
2: Create an invalid private domain name. This will never route on the web so if you decide to host content for internal/external use, you may run into trouble, especially with services that require SSL certificates. Examples might be ringsmuth.int or andy.priv. These type of domains are non-routable and can result in issues of trust when communicating with other servers, but it is possible.
Once you have the name sorted out, you need to configure DNS. If you are on a network with other servers, just have the DNS admin create an A and PTR record for you. If this is your only server, then you need to configure and start the DNS service on Mavericks. The DNS service is the best Apple has ever created. A ton of power in a compact tool. For your needs, you likely need to just hit the + button and fill out the New Device record. Use a fully qualified host name in the first field and the IP address of your server (LAN address). You did use a fixed IP address and disabled the wireless card, right?
Once you have DNS working, then you can start configuring your other services. Time Machine should be pretty simple. A share point will be created automatically for you. But before you get here, I would encourage starting Open Directory. Don't do that until DNS is right and you pass the sudo changeip -checkhostname test.
R-
Apple Consultants Network
Apple Professional Services
Author, "Mavericks Server – Foundation Services" :: Exclusively in the iBooks Store

Migration to new mac and now compressor wont work

after a migration - new 6 core - my final cut studio (2) - doesn't all work. final cut works, but compressor tells me to restart or verify that my instillation is correct. DVD studio doesn't work either....
help!!!
thanks
MR C

David is spot on. Follow his advice.
You need to understand that if you were running a G5 - a PowerPC chip computer - and migrate to an Intel chipped computer, the binary code to run the program on the new computer will not be present. Your G5's FCS installation doesn't have any intel code on it. FCS requires intel specific code on intel machines.
Also, you will need FCP v5.1 or higher to run on the intel machine. v5.0 or lower is not supported.
Heck, even migrating pro apps between machines on the same processor can be problematic due to the specificity of the chips and how FCS stashes system files. Sometimes they are not copied over or the frameworks are the wrong one for the processor or version of OSX.
Best practice is to always do a fresh installation from the disks (or disk images) then use software updater to bring it up to the current update.
x

Aperture: Migration to new Mac (Referenced Library)

Apologies if this has been covered before but I've used numerous searches and don't seem to be hitting the right combination of terms to bring up what I want.
I currently have a flagging 2007 MacBook (OS 10.6.8; 2.16 GHz, 2MB RAM and only 7GB free of the 160 GB HDD). Aperture is struggling. Time to upgrade.
My Aperture Library is currently on the Mac and is 'Managed'. I have contemplated moving the 50GB or so of Aperture Library to an external HDD and going 'Referenced', mainly because I still have some images I need to work on (even though Aperture is for obvious reasons ponderously slow with frequent SBOD on this machine) until I decide what to upgrade to (Macbook 15" or iMac with more bangs for the buck) and wait for the latest refresh of the line that I choose.
Upon getting the new machine I plan to use the Migration Assistant to help with app/doc/settings transfer but what about Aperture? I am not sure if it's best to:
1) Get the new Mac now, migrate everything across (including Aperture and its Managed library) THEN move the Aperture library off the internal HDD to an external and going Referenced, or;
2) Go Referenced now. In which case when I eventually do then migrate Aperture to the new machine will it automatically 'point' to the correct location of the external HDD referenced library when what is left of Aperture copies across or is there and easier (or indeed more convoluted) process I will have to go through if I switch to Rferenced before getting the new Mac and migrating?
Accept of course with the new Mac the HDD will be so much bigger so there may actually be no need to go Referenced, at least yet. Try as I might, save for HDD space I don't see that many benefits to Referenced
On the new Mac front, while I like laptops, I find that the iPad and this Mac do most of what I want (e.g. surfing, mailing and running the odd few apps). While a new MBP would be appreciated part of me still thinks that the more bang for the buck iMac is the better investment. The only thing I MAY need to do is upload the occasional photo shoot on the move (by creating a new project) which, if stripped back to basics, this Mac miight still be OK for until I get back home and move the project to the iMac, reloacting to the masters to the referenced external HDD after.
Any help appreciated.

Hi,
some consederations you may want to keep in mind. There is no definitive answer for the perfect library setup - it will depend on the size of your Aperture Library, the amount of available disk space, on your workflow, and on your backup strategy.
I currently have a flagging 2007 MacBook (OS 10.6.8; 2.16 GHz, 2MB RAM and only 7GB free of the 160 GB HDD). Aperture is struggling. Time to upgrade.
On that machine you really need to relocate your master image files to an external drive or free disk space in a different way. With only for 4% of empty space on the system drive, even a newer Mac will be very slow. Try to keep 20% to 30% of your system volume free.
My Aperture Library is currently on the Mac and is 'Managed'. I have contemplated moving the 50GB or so of Aperture Library to an external HDD and going 'Referenced', mainly because I still have some images I need to work on (even though Aperture is for obvious reasons ponderously slow with frequent SBOD on this machine) until I decide what to upgrade to (Macbook 15" or iMac with more bangs for the buck) and wait for the latest refresh of the line that I choose.
For best performance the Aperture library should reside on your fastest drive, usually the System drive. If you want to go referenced, relocate the masters, but keep the library on the internal drive. Only if you have a very fast connection to your second drive, or two internal drives, it may be advantegous to move the whole library to the other volume.
Managed, referenced, or mixed?
Managed: A managed library is easier to handle, as long as it is reasonably small. With 50 GB Aperture Library you can continue with a managed library, as soon as you have more disk space available. The advantage of "Managed" is that you do not have to keep track of your masters on your own, and that they will be included in the vaults. You will need an incremental backup scheme that looks inside the library package however - like Time Machine, otherwise you will need to backup the whole library over and over again, even if you only changed one single image.
Referenced: If your Library gets larger, and you have several hundreds of GB, then a managed library becomes a nuisance and it is time to go referenced. Very large libraries are difficult to move or copy between disks; It will be wasteful to have several vaults, for each vault will include the same masters over and over again.
Mixed: The Aperture library on the system drive, most of the masters on an external (or second internal) volume. This setup is perfect for laptops with limited space on the internal drive, but it will require that you have a well ordered strategy where to keep your masters, since Aperture will not manage them for you. There are two pitfalls to avoid: Accidentally deleting or modifying masters from the Finder, or accidentally relocating them to a place where you store other images that are not your masters. When you have several similar images in the same folder, it can be very hard to tell which image is the master that you need to keep and which is a redundant copy.
The "mixed" setup is great, if you are on the road (bt will put mre strain on your memory or master management skills)- you still have your Aperture library with you and the master image files you are currently working on, but not the bulk of your masters. If you create high quality previews, you probably even will not notice, that most of your master image files are still at home.
Upon getting the new machine I plan to use the Migration Assistant to help with app/doc/settings transfer but what about Aperture? I am not sure if it's best to:
1) Get the new Mac now, migrate everything across (including Aperture and its Managed library) THEN move the Aperture library off the internal HDD to an external and going Referenced, or;
2) Go Referenced now. In which case when I eventually do then migrate Aperture to the new machine will it automatically 'point' to the correct location of the external HDD referenced library when what is left of Aperture copies across or is there and easier (or indeed more convoluted) process I will have to go through if I switch to Rferenced before getting the new Mac and migrating?
Accept of course with the new Mac the HDD will be so much bigger so there may actually be no need to go Referenced, at least yet. Try as I might, save for HDD space I don't see that many benefits to Referenced
From my experience, it is less troublesome to migrate a managed library with Migration Assistant. If parts of your Library are referenced, and you migrate the referenced masters as well, you may need to reconnect them, unless you only have to plug in the volume with referenced masters. Then Aperture should reference them correctly without extra trouble.
Try as I might, save for HDD space I don't see that many benefits to Referenced
Then stick to the managed setup until your library really becomes huge.
On the new Mac front, while I like laptops, I find that the iPad and this Mac do most of what I want (e.g. surfing, mailing and running the odd few apps). While a new MBP would be appreciated part of me still thinks that the more bang for the buck iMac is the better investment. The only thing I MAY need to do is upload the occasional photo shoot on the move (by creating a new project) which, if stripped back to basics, this Mac miight still be OK for until I get back home and move the project to the iMac, reloacting to the masters to the referenced external HDD after.
Any help appreciated.
I am still waiting for my iPad to be delivered - right now I take a MBP on the road. For the new shoots I create a new Aperture library, do most of the tagging while I still remember how the images have been taken, and when back home I import the new project into my main library.
Reagrds
Léonie

Migration to new Mac Pro

I am ready to transfer to my Mac Pro and know there are a lot of options...however, I have accumulated many apps & junk I don't want.
I do however want all my photos, music, email, Safari settings and accounts/documents and a lot of compatable Apps soooooo...is it better to do a total MIGRATION and then delete what I don't want or only transfer what I do want up front - and if the latter...what is the best way to do so??
thanks
eric

Migrating from a PPC Mac to an Intel Mac can be very problematical. I would definitely not migrate your entire system because you will end up replacing Intel specific software with PPC software, thus rendering your new Mac quite dysfunctional.
A safer solution is to only transfer your personal data files such as your Music, Movies, Pictures, Sites, and Documents folders located in your Home folder.
If you have third-party applications I recommend you reinstall them after upgrading them to universal binary versions wherever possible.
You can also copy the /Home/Library/Mail/ and /Home/Library/Safari/ folders to their respective locations on the new computer. You can do the same with your /Home/Library/Application Support/AddressBook/ and /Home/Library/Application Support/iCal/ folders.
The following has more information on migrating to Intel Macs:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3 or G4 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior (does not work), TechTool Pro (pre-4.5.1 versions do not work), SuperDuper (newest release works), and Drive Genius (untested) may not work properly on Intel-Macs. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Written by Kappy with additional contributions from a brody.

IPhoto Migration to new Mac--MAJOR ISSUES

We just got a new iMac to replace our previous 2006 iMac that was running Mountain Lion. It had already been determined by a Mac repair person that our old iPhoto library was corrupted and that we couldn't migrate that Library to the new Mac. Rather, we'd need to drag the "Originals" folder to the new Mac. Note: Due to the amount of photos we have, we store our photos on an external hard drive. (Also, nevermind that the 35K photos that were so carefully organized into folders and albums over the past 8 years would be lost). Fine. That's what we did. Major issues ensued:
1. Everytime I've imported photos from my iPhone over the past two years, random photos (mostly those that I edited in Apps like hipstogram) multiplied and were reimported EVERYTIME I plugged my phone in the Mac. There are, like 10 copies of certain photos.
2. Many photos are somehow duplicated, but in different "rolls." How do I even find the duplicates? They're dated when they were imported, not created. Grrr...
3. During the import to the new Mac, an error message let us know that 795 photos were not imported. Which ones? Don't know.
4. The WORST issue of all, a lot of the metadata on the photos is incorrect. Some is user error (Canon camera had the year as 2007 when it was really 2008), but a lot of photos imporated from the iphone over the years are saying 1/20/1980 or another nonsensical date. Or the photos are dated as the date of import, not when they're taken. So, not only did I lose the organization of the library, the metadata is incorrect. For many of the 35 thousand photos over 12 years.
The result? A jumbled nightmare of "Events" that aren't in chronological order in the new iPhoto.
Sidenote: Why can I navigate to the Originals photo files in the old Mac, but I cannot navigave via the finder to the Originals in the new Mac? The only way I can get there is to click "Go to original file" from iPhoto...and even then, its location is unclear.
I don't know what to do from here. The options as I see them:
1. Clean up the duplicates/metadata in the old Originals folder and re-import the folder to the new Mac.
2. Start with the current debacle on the new Mac and painstackingly reorganize all the folders (cleaning up, correcting dates).
Another sidenote: Is there a way to delete a photo in iPhoto and truly delete the file? I started deleting duplicates on the new iMac and I have to navigate to the original file (in its mysterious location), delete it, and then delete the thumbnail in iPhoto. This may take a year or two to complete. There has a be a better way. Help.....me.....

Our Mac person determined that our library was corrupted because various attempts to rebuild the cache/library were unsuccessful (spinning wheel and error messages).
try to reproduce this on your old computer nad report the exact error messages (and look at the iPhoto menu ==> about iPhoto to get the version)
So, from what I understand, the best path forward would be to fix/rebuild the old library to be able to migrate it to the new machine
Yes
I do have a question about deleting photos in iPhoto. How do I handle eliminating duplicate photos in an iPhoto library (new or old)? My understanding is that deleting an image in iPhoto does not delete the actual file (in originals or masters or where ever it is housed on the Mac). Does this matter? Why would deleting photos in iPhoto cause corruption of the library?
Duplicates - IPLM does them very well
And most certainly deleting using iPhoto properly does totally remove the photo form iPhoto and from th ehard drive
Deleting in iPhoto is trivial - select a photo in an event, press the delete key and empty the iPhoto trash (do not let the iPhoto trash get large since sometimes iPhoto does not handle large trash bins well) - on later versions then you need to empty the system trash too
Do that and the photo is gone from iPhoto and from the Mac (given that you have a corrupted library past deletes might not have worked - from a properly working library it will work)
Deleting using iPhoto will not corrupt anything
BUT you stated
I started deleting duplicates on the new iMac and I have to navigate to the original file (in its mysterious location), delete it,
That is NOT using iPhoto to delete photos - it is using the finder to go directly into the contents of the iPhoto library and makeing changes - that corrupts the database
LN

Migrating to new Mac

Hi
I am going to be getting a new mac soon, and wanted to use my backups as a source of data. Is this possible/the best way?
Do I need to by an external hard drive as well?
thanks
Arie

You can migrate your data from the TC..
See the instructions here.
Q14-17 http://pondini.org/TM/FAQ.html
But 14 is the main one.
Nevertheless.. I would also do a full disk image to USB drive.. you can download and do the disk image from superduper. Free to do that. Let me say it is only way to ensure all the files are actually available.
Obviously gets messy if you go from SL to ML in the new computer though. Same to same is ok.

User ID Not Recognized in App Store after Migrating to new Mac

I migrated to a new Mac using Migration Assistant being careful to create an identical user account on the new Mac. All went fine. When it came time to update apps through MAS, some apps updated and some would not (e.g. Pixelmator) and MAS tells me "You have updates available for other accounts" and asks me to log out and sign in as another user – but the user name is exactly the same as my current user name. There is definitely only one user account on the Mac, so what is going on?

Cracked it – thanks. The message that MAS displays is not clear and looks like it's referring to User Name. Also MAS does not have a Preferences dialog where you would normally enter Account/Apple ID details, but it's under the Store menu item – confusing.

Time Machine consistency after migrating to new Mac

I have just migrated my Macbook Black to my new MacBook Silver, and I am away from my Time Machine backup. I have a new account name on my new MacBook Silver, so as to not cause any kind of disambiguation error. How do I continue with my Time Machine backup with my new machine? Is there some way of connecting the data on this new machine with the backup that was generated on the old machine?
Thanks for your help.

goldfilm wrote:
Hi, I have a similar problem. I restored my new Mac with the Time Machine from the old Mac. Now I want to keep on using incremental. Why I can't?
Because it's a new and different Mac, and TM backs up Macs, not just drives, or files and folders. Besides, unless they're absolutely identical (same make & model of everything internal and external), there are different drivers, etc.
Also, I can't see that option of "Browse Other Time Machines".
From the TM icon in the menubar, where you normally see +Enter Time Machine+, if you press Option, you should see +Browse Other Time Machine Disks.+
My problem is, I didn't change any file since the old Mac in any file (except tiny changes), but now it tells me that in order to make a new back up it needs a lot more space than I have in the Time Machine. If I had the old Mac it would simply update an incremental...
If you'd done a complete restore on your old system, TM would make a complete, new, full backup. It may seem strange, but reloading a file is the same as changing it, as far as TM is concerned.
Here's the scoop: http://support.apple.com/kb/TS1338
Think of it this way: TM backs-up everything, not just your "raw" data. Any change you make to a file or folder, even just moving it, means something changed, so TM backs it up.

Uninstall problem in cc applications after time machine migration to new mac

Newbie to cc. Having problems with cc programs that were migrated across to new iMac via Time Machine back up when setting up new mac.
Attempting to open PS cc results in error message 86. I have now uninstalled Creative Cloud program and a PS cc program in Utilities via Adobe Installer in Ulilities however, (other copies?) of the programs PS cc and Bridge cc, the only 2 cc programs I have so far, are listed in my Applications folder.
I think I need to remove them both from the Applications folder but am unsure how to do this safely. There is no Abobe Uninstaller now in Utilities as it was empty after uninstall removal of duplicate? programs noted earlier so I deleted that too.
Should I send them to trash? And then perhaps I can start afresh with new installs of Creative Cloud and required cc programs.
Any advice gratefully received.
Thank, Barry

Hi Jakekira14,
We never suggest our customer's to move Adobe softwares using Timemachine because it causes launch/Licensing issues. I would request you to kindly delete all the Adobe folders and then install everything from scratch. To remove the left over's, please delete the following folders from your machine.
Click on Go>Go to
/Library/Application Support/Adobe
/Library/Preferences/Com.adobe.....
~/Library/Application Support/Adobe
~/Library/Preferences
Cheers,
Kartikay Sharma

Time Machine after migration to new Mac

So, I just got a new Mac, and used the option to copy settings and files from a Time Machine volume to the new machine. Now that everything's run, though, I can't use Time Machine to backup the new Mac -- it says "Volume not found". I've Googled a bit, but most of the troubleshooting seems to assume that the drive is missing or won't mount -- the drive is there, but the Time Machine software won't use it.
What are my options here?

Hi VK
A supplementray question:
I have one i-mac happily backing up with Time Machine to an external hard drive.
I have just bought a second i-mac (stops the fighting!) and propose to use migration assistant to move my [admin] account from the old to the new i-mac leaving two other accounts on the old one. I see from your posts that it seems as if Time Machine will start a new back up series for the new i-mac's back ups. But what about the old i-mac? Will that continue to extend the existing Time Machine back up files, albeit without my transferred account and its files? If so, should I partition the external drive and start the new back ups from the new i-mac on this new partition. I'd like to end up with the old i-mac continuing to build its Time Machine back ups (less my account and its files) and have a new back up series from the new i-mac building to a separate partition on the external drive.
Does this make sense? I can't see an answer in the forum to what must be a reasonably common issue in this expandin mac world.
MVBW
Mervyn

Migrating to new Mac. Best Practices?

Similar Messages

Maybe you are looking for