• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 825
  • Last Modified:

Migrate user profile between Domains

I currently have a domainA with W2K, I am going to create another domainB with W2k3. I would like to move the user profile from DomainA to DomainB so that all the files and settings are remains after the clients join DomainB.

Is there any way I can do that?

Thanks.
0
leoshiu
Asked:
leoshiu
  • 6
  • 5
1 Solution
 
Chris DentPowerShell DeveloperCommented:

It depends a bit.

How are you migrating the user account?

If you're using Active Directory Migration Tool then it can be made to rewrite the profile when you migrate the computer account to the new domain.

Chris
0
 
leoshiuAuthor Commented:
Dear Chris,

I prefer USMT than ADMT but I do not know how to use it.

Thanks
0
 
leoshiuAuthor Commented:
All the user settings and files must be kept after they join the domain including print queue and IE settings.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Chris DentPowerShell DeveloperCommented:

Fair enough. Ultimately you're just copying the profile to a new one with USMT. It probably tidies it up a bit, but there's not much to it.

Configuration such as printers, IE settings, etc are stored in the users registry hive which loads as HKEY_CURRENT_USER when they log in. That runs from %UserProfile%\ntuser.dat, and is why you can copy the contents of a profile to preserve settings.

Will the user be moving onto a new computer? Or are you using the existing system?

Chris
0
 
leoshiuAuthor Commented:
Dear Chris

I have over 200 computers to upgrade, so I rather joining them to the new domain than moving them onto a new computer.

I found some solutions on the web about using USMT, but it doesn't work in my case, I dunno why
0
 
Chris DentPowerShell DeveloperCommented:

How are you getting the user accounts onto the new domain?

For that number of users and computers I'd seriously consider using ADMT, it can take all this hassle out of your hands.

Chris
0
 
leoshiuAuthor Commented:
Dear Chris,

I created user accounts on the new DC, I wanna their user profile remains unchange after they logon to the new domain

Thanks
0
 
Chris DentPowerShell DeveloperCommented:

Ahh, that's a shame.

I'm not sure USMT will work for you here, you really need to something to translate the profile, to rewrite the security rather than just pick it up and drop it as USMT seems inclined to do.

The difficulty is, without ADMT it's not easy to perform the translation, bear in mind that access to the profile is defined by the users Security Identifier rather than a simple user name. With ADMT it writes the old security ID into the new account (into an attribute called sidHistory).

On the simplest level you can just copy the profile contents from one to another. That's quite a big job for that many users.

Chris
0
 
leoshiuAuthor Commented:
Dear Chris,

Workload and time are not the main issue, we are going to do it department by department, so I am looking for the simplest way to do it.

thanks
0
 
Chris DentPowerShell DeveloperCommented:

Then I would still recommend ADMT, even though it means deleting the accounts you've created in the new domain :)

Chris
0
 
lscapaCommented:
ADMT is the ONLY way to do what you are wanting to do. USMT was designed for moving user data between computers WITHIN the same domain. Besides it sounds as if you are truely doing a domain migration and guess what? ADMT = Active Directory Migration Toolkit. Ahhh the solution as Chris-Dent has already pointed out is to use ADMT. Take the 2 hours read, understand, use...
Another benifit of ADMT is sid history. Instead of having to reconfigure all your permissions on shares and the like, ADMt will carry the old domain sid with it and voila!! your users have access to all the same information. Plus it will migrate PC and server accounts as well. 200 users would take only about 2-4 hours to migrate over. You're trying to backward enginner a process that Microsoft already has. Probebly wasted more time than if you would have begun with ADMT in the first place?
Again Chis is right USE ADMT...
0
 
leoshiuAuthor Commented:
Thanks, but I found a third party tools called Forensit works perfectly for me.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now