I tried using several different tools, including: Microsoft's Active Directory Migration Tool version 3.2 (which is probably best for Server 2003 -> Server 2008 and above migrations in larger enterprises, where both AD servers are functioning normally and the old one still is online), evaluated the built in Easy Transfer or the Files and Settings Transfer Wizards, and ended up with the User State Migration Tool (USMT).
USMT can basically copy the files from one profile to another, to a local disk or to a network share. This had to be done in order to change the association of the profile, unfortunately, from the old domain to the new one.
Here are some useful download links:
- USMT 3.01 - for Windows XP and Vista migrations
- USMT 4 (part of the Automated Installation Kit - AIK for Windows 7) - by the way, this one is an annoying 1.7 GB ISO file. There is a repackaged version provided from wintools.com.au, but it may not be always up-to-date. If you download the ISO, you then have to install it (or maybe you can extract directly from a CAB file? I didn't try that).
- Hotfix for USMT 4 which migrates Outlook 2010 settings (oops, they left that part out of the RTM version!). Also, USMT DOES migrate Outlook files - but it screwed up a lot of user settings, including email rules and Outlook Address books which required manual reconfiguration.
I don't know how the heck a large organization would use any of these tools to successfully migrate like I did without some degree of manual intervention. What a headache!
Also, quick tip - for small Active Directory domains that might grow up into larger ones some day, the best internal Active Directory domain naming scheme is an unused corporate public domain or subdomain that you own and will keep for a very long time. For example, I might own mycompany.com and mycompany.net. Therefore, you might use corp.mycompany.com for your internal domain name, or mycompany.net if you are not using it for anything else. I DO NOT recommend using anything else, including .lan or .local.