Is it best to migrate from PC or drag drop iTunes?

Hi everyone..
I just set up my iMac abd am moving over from Windows.
Regarding iTunes, all I did was copy my complete iTunes folder complete with movies, books, whatever else to my network drive and then
simply move it to the music folder in the finder on the Mac.
Although this works, would I have been better doing it some other way??
-Frankie

normally not. I've done that in the same way. It's good to use the same iTunes version and disable the registration on the 'old' windows system.

Similar Messages

  • How best to migrate from MacPro to iMac w/ SSD and extrenal drives

    Currently I have a MacPro with 4 drives - 3 1TB and 1 2Tb, the 2TB drive is my main hard drive, so it has system, apps, documents, itunes etc....and it has been upgraded and migrated from one computer to the next as long as apple has had the ability to do so (and before that by moving over targeted drive manually). I currently am running 10.6.8 on the machine. I have ordered a new iMac w/ an internal 512gb SSD drive, and after speaking with an Apple rep, I got a THunderbolt enclosure to house my current 4 hard drives. Now my question is how best to get my preferences etc into the new computer w/o dragging along all the old stuff...(ie old apps not compatible w/ Mountain Lion, old system folders, etc). Here is what I would like to do:
    1. setup SSD with OS, fresh installs of Apps, and my fonts (i am a designer and i have a gazillion fonts and they always take way to long to load into my font app).
    2. I would like my 2TB drive to eventually just include my home directory where all my files, and such will be stored. But I would like to keep the drive as is to make sure everything is working just in case, I dont want to have any down time during the upgrade process (ie if a client calls me and needs something while I am still setting up I could boot off the 2tb drive and work). But after all is working properly then I would like to make it just the home directory and main place for all files etc
    3. My remaining 3 drives are broken up for manual backups of my work on 2 of the drives, and then photos and mp3s on one, and movies and tv shows from itunes on the other. I dont currently run Time Machine or Retrospect or RAID....
    I see most people saying to create 2 admin accounts, one that would stay on the SSD drive and the other which could be mapped to the 2TB drive and have its home directory there...but what do I do about moving preferences etc? is there a way when setting up that will let me import my current account and let me keep it on the external drive as is? should i move the files that i want to keep off the 2tb drive, wipe it to get rid of the old apps and system and then put back the home directory??I don't want to run into trouble with permissions, and I really dont even want to create 2 accounts because I hate having to close everything and log out for simple installs and updates...i have 2 on my macbook pro now and i run into errors all the time of i cant update this or that because of admin account...even though both accounts are set as admin.
    I want to keep the whole upgrade simple, but I would like to keep this fresh system clean as  am sure there is way to much left over garbage from upgrades past. So just not sure how best to do any of it.....

    I purchased the DataTale RS-M4t SMART 4-Bay Thunderbolt RAID storage enclosure. But it can do both RAID if you get their data manager software download, or it can just mount the drives and be used normally. So basically I can plug all 4 of my current drives into it...and it into my iMac and it will be same as if I had it in my tower....so really not moving over a ton of stuff. I will load all apps fresh onto the brand new iMac - so the SSD will be a clean install...my worries are trying to get access to home directories etc on the current main drive and have things get setup correctly, keychains, bookmarks, etc...as well as my iTunes which has iPad and iPhone backups, etc. I am just not sure as how to best setup the SSD to get the most of its speed while being able to get my current account working but on the second external drive.

  • Best practice - Migrate from WLC4404 to WLC5508

    Hello everyone,
    I would like to have pointers how to migrate from WLC4404 to WLC5508. I want to know your propositions.
    I could replicate the configuration manually but there is a lot of confirugation menus and all. If both could be online and migrate the AP to the new one until there is none on the old one, it would be great.
    I'm waiting your replies.
    Best regards

    1.  Upgrade the 4400 to the "highest" firmware, 7.0.235.3.  Make sure the 5500 also have the same firmware (7.0.235.3).
    2.  Copy the config from the 4400 to your TFTP server. 
    3.  Copy the config from the TFTP to the 5500.
    4.  All done.

  • Difference between importing images from iphoto via drag & drop vs 'media' button

    Hi (long time reader of this community, but my first post),
    i'm creating a huge document (approximately 200 pages) in Pages (5.0.1, Using Maverick on a 27 inch iMac).
    In the new version of Pages the "Media" button only produces small images that makes it difficult for me to choose which photo i want.
    Is there a difference between importing images from iphoto drag & drop vs 'media' button.
    Or is it better to just drag and drop the original jpegs (which i also have in a folder).
    Is Pages the best program to use for this type of project? it is a profolio with about 4 photos, text, text boxes etc on each of the 200+ pages.
    any help much appreciated.

    Pages 4.3 might be up to the job. I very much doubt Page 5.0.1 is.  It lacks more than 90 features of its predecessor and is very buggy to boot. You probably have an iwork09 folder in your Applications folder. I suggest you trash Pages 5.0.1 and use Pages 4.3 until Apple makestheir new "Eddie Cue" ready for prime time (if, that is, they ever do).

  • Best practices: migrating from Aperture 2 to Aperture 3

    What are the best practices for moving from Aperture 2 to Aperture 3. One thing I do know from reading the discussions board is to turn off Faces recognition until everything is working. What else?

    Make sure you do a full backup and rebuild on the aperture 2 library before you migrate. (opt-cmd when you open Aperture 2)
    Aperture 3 may slow down on you don't be scared it will finish. Mine took 1 1-/2 days, about 30,000 raw photos / 800GB.
    Don't reprocess masters until Aperture is done with everything it needs to do, keep an eye on the activity window.
    After you reprocess masters it will take a long time to generate thumbnails, again don't worry.
    Bill Debevc
    sshaphotos.com

  • Just migrated from macbook. can't open iTunes on iMac. ''The file itunes library.itl" cannot be read because was created by a newer version of iTunes. Would you like to download itunes now." Tried downloading.

    Hi. I've just migrated 750GB worth of data from an old MacBook unto iMac but now itunes won't open and i've downloaded the latest itunes with no effect on the error message received. Please help.

    Hey,
    Thanks for your response. I've checked in the about itunes and it says the MacBook's itunes details are as follows
    11.05.5 (5)
    64 bit
    copyright 2000-2013
    I imagine the iMac has the lates itunes on it although I cannot check because it brings up the error message as described above. Any help will be appreciated.
    AJ

  • Migrated from PowerMac to iMac but iTunes library did not come over

    How do I get my iTunes Library over from my PowerMac to my iMac?

    Is it only the iTunes library that didn't transfer? It is possible that it transferred but into a new account.
    When you run a migration it will transfer even the user accounts.
    So go to  menu -> System Preferences -> Accounts and check how many accounts you have there. If you only have the one (your current one) then you can run the transfer again, or just transfer the Music library with FireWire, ethernet or airport (or a USB stick etc)
    If there is another account there, then logout of the one you are in, and login to the other account to see if things are as they should be
    Cheers

  • Upgrade and migration from Netware to Linux best practice

    Hi folks,
    We've been running NSM 2.5 for a few years on Netware and have been very satisfied with the product and performance. We are planning to migrating to SLES11 with OES11 very soon to finally move away from Netware and I have some issues I can't seem to find answers to. Of course I want to use NSM to move my home directories from my Netware to my SLES so I want this working well when we migrate.
    I've searched but not found a good resource to show how to move the NSM engine from a Netware server to a Linux server with best practices. Anyone have experience with this and any gottchas?
    The other question is of course is to upgrade NSM to a new version before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want to move to the latest version. Upgrade procedure and best practices would be handy.
    The last of course is NSM compatible with SLES/OES11? I presume it is and certainly hope so because we want to move all of our users to SLES11 NSS.

    On 5/9/2012 11:06 AM, jlauzon wrote:
    >
    > Hi folks,
    > We've been running NSM 2.5 for a few years on Netware and have been
    > very satisfied with the product and performance. We are planning to
    > migrating to SLES11 with OES11 very soon to finally move away from
    > Netware and I have some issues I can't seem to find answers to. Of
    > course I want to use NSM to move my home directories from my Netware to
    > my SLES so I want this working well when we migrate.
    > I've searched but not found a good resource to show how to move the NSM
    > engine from a Netware server to a Linux server with best practices.
    > Anyone have experience with this and any gottchas?
    The NSM 3.0.x Engine setup process actually handles the migration from
    NSM 2.5 fairly easily. Our 3.0 Installation Guide (available at
    http://www.novell.com/documentation/storagemanager3 ) includes all the
    information you should need regarding migration, including the
    suggestions I'll list here.
    You'll want to leave NSM 2.5 running during the migration so that the
    NSM 3.0 setup wizard can connect to that Engine and import its policies
    and pending events. You'll also want to have as few pending events as
    possible in NSM 2.5 -- deferred deletes are fine, but all pending events
    will slow down the migration process, since they'll have to be
    transferred over.
    > The other question is of course is to upgrade NSM to a new version
    > before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want
    > to move to the latest version. Upgrade procedure and best practices
    > would be handy.
    Again, this information is available in the 3.0 Installation Guide. To
    migrate from 2.5 to 3.0.x, you'll have to have at least one OES11 server
    in your tree to install it on; but you'll also have to leave the NSM 2.5
    Engine running on its Netware host long enough to migrate from it.
    > The last of course is NSM compatible with SLES/OES11? I presume it is
    > and certainly hope so because we want to move all of our users to SLES11
    > NSS.
    We are about to release version 3.0.4 of NSM, which provides full
    support for OES11 on SLES11. The NFMS Support Team can also provide you
    with builds of NSM 3.0.3 which support OES11; if you need those for
    early testing, please send an email to storagemanager[at]novell[dot]com.
    Hope this helps!
    - NFMS Support Team

  • Which one is the best way in migration from sap bpc ms 5.1 to nw7.5

    Hi,
    I am doing Migration project from SAP BPC MS to NW.
    In this which one is the best way migrating By manually or By using SAP Migration tool.
    What are the merits and demarits migrating by manually.
    The data is moving from MS to NW as it is by using sap migration tool.
    Could you please answer my questions as early as possible.

    Hi,
    You would need manual effort anyways. Some of the objects are not either migrated or you need to update manually after the migration. Example, reports have to be modifed and as they may not work due to some of the options.
    Also your packages, script logic etc have to recreated. So its upto you as the migration toosl takes across your appset, applications, dimensions and the master data etc. The manual involvement is inevitable. You need to probably take what the tool allows you to do and make manual corrections for the objects that are not supported.
    Thanks,
    Sreeni

  • What is the best solution for migrating from Maverick to Yosemite?

    What is the best solution for migrating from Maverick to Yosemite? Anyone have suggestions?

    Back up all data. Update all third-party software to the latest version and remove any you don't need. Download the Yosemite installer from the App Store. Run it.

  • What's the best way to migrate from an old iMac to a new iMac?

    What's the best way to migrate from a 2010 iMac running Yosemite to a new 2014 iMac?

    Hello jonfromnorth caldwell,
    The article linked below details how to utilize target disk mode to transfer files. This can also be used in conjuction with Migration assistant to transfer your information quickly (the 2010 iMac will appear as a storage device to the new iMac).
    OS X Yosemite: Transfer files between two computers using target disk mode
    http://support.apple.com/kb/PH19021
    OS X Yosemite: Transfer your info from a computer or storage device
    http://support.apple.com/kb/PH18870
    Cheers,
    Allen

  • What's the best way to migrate from Macbook to Macbook Pro with renting?

    Having trouble migrating from old Macbook to new Macbook Pro with Retina Display.  It seems I skipped some steps and it looked like it was working over wifi but there were password problems I didn't find out until I quit the process after about 5 hours.  How long should it take over wireless?  Should I skip that altogether?

    Hi,
    In addition, please review the link below and hopefully it will help you.
    Migrating Hierarchies in System Center 2012 Configuration Manager
    http://technet.microsoft.com/en-us/library/gg682006.aspx
    Migration to System Center 2012 Configuration Manager
    http://blogs.technet.com/b/server-cloud/archive/2012/03/27/migration-to-system-center-2012-configuration-manager.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

    We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
    a great guide which has been a big help,
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
    Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
    everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
    At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
    certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
    Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
    Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
    I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
    WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
    connectivity.
    Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
    credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
    the user exists on Mailbox server EX02.DOMAIN.COM
    I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
    I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
    I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
    of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
    If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
    Thanks.

    Hi,
    In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
    Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
    public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
    there’s no coexistence between versions.
    For this reason, it’s recommended that prior to migrating your public folders, you should
    first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    (Please note the What do you need to know before you begin part in this link)
    Regards,
    Winnie Liang
    TechNet Community Support

  • Migrating from Exchange 2007 to exchange 2013 ( special case )

    Hello , 
    what is the BEST scenario ( fastest , most efficient , most secure in terms of data loss )  , to migrate from exchange 2007 ( one server , all exchange roles installed on this server , 1200 mailbox ) , to exchange 2013 ? 
    knowing my environment needs to be connected to their mailboxes , 24/7 ! 
    it's very frustrating . 
    and i have no clue even if this is the right place to post about this , if not please refer me as to where to post . 
    Also , All my domain controllers are 2008 .

    It's fine to post your question here, and you are fine with Server 2008 Domain Controllers - that is a supported scenario.
    If you haven't performed such an upgrade and you need to have 24/7 mailbox availability, I would seriously recommend you to duplicate the production environment on a test network and run through the upgrade at least once.
    Most people neglect the Outlook clients requirements - they need to be updated and include several specific updates, which allow the automatic reconfiguration of internal clients. If you are preparing for this upgrade, you should be aware that all internal
    Outlook clients switch to Outlook Anywhere. Clients that miss these updates will get connectivity problems.
    Another common problem is the configuration of the Exchange URL - I mean the Exchange 2013 URL and the modified Exchange 2007 URL that will allow the co-existence. In your case, you definitely need to plan for co-existence - that includes requesting and
    installing a new Exchange UCC (Multiple Domain Certificate) on both Exchange servers, configuring Split DNS (or preferably PinPoint DNS zones), and correct timing when replacing the existing Certificate on the Exchange 2007 server. Failure to configure the
    correct URL (and it's quite easy to miss one, so triple check them) will get you in trouble.
    Once you get through the switchover (switching the mail flow and Client Access through the Exchange 2013 server), move just a couple of test mailboxes and check the result.
    Finally, if you are moving the Public Folders, make sure that the lock is really applied before you complete the process. Most people proceed right away and that get's the process stuck. If you can afford it (the mailboxes are already on the Exchange 2013
    server at that point), just restart the Exchange 2007 server (after locking the Public Folders) and then complete the Public Folder migration.
    Good Luck with the project!
    Step by Step Screencasts and Video Tutorials

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for