Question Locked

Replicate user data across two domains

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I need to sync DCs that are in two different geographic locations. (Windows Server 2003) They currently do not communicate at all, but we can set up a VPN to allow them to communicate. How do I get the user from the PROD DC onto the DR DC? The domains share the same name, but are located on different networks.

17 replies

by matt.altman

If you are asking how to replicate an AD server then go to the Sites and Services snap in, expand sites, expand the site name if you have one, expand servers, click NTDS settings, right click on your DR server and replicate now. This assumes that you have already set up both sites in Sites and Services. If you have not set these up then right click on sites, select new site. You can then add your subnets and servers.

by dkhman26

So I have to set up both sites in the other sites' "sites and services", then connect them using our VPN, then tell it to replicate?

What happens if I have usernames that exist on both sites, but with different passwords?

by matt.altman

If you have a user on Main DC that has one pw and that same user on DR DC has a different pw then you might not want to replicate because these sites are completely different. The replication will allow you to keep your Prod DC and DR DC the same in case of a DR situation. Is this not what you are doing or am I misunderstanding something?

by dkhman26

Unfortunately we are trying to sync the users after having already done some work on the "DR" site. I'm not sure if there will be any conflicts. I could check manually.
I was asking the questions "just in case" we do have that scenario.

by dkhman26

Here's the reality of the situation. We were bought out by another company so we are building one of our clients a new environment at the new company's data canter. We've already started building the new environment, so some of the service accounts may be the same.
We need to get the user accounts from the current environment to the new environment because there are about 300 users. As far as I have been able to figure out, there is no way of exporting just the users along with their passwords, so we have to sync the DCs.
My only concern with conflicts are if the service accounts in the new environment have the same username, but a different password, because we cannot afford to have the service accounts' passwords reset.
However, this will be a one-time sync, so if that is the ONLY way to do it and the current environment does overwrite the passwords on the new environment, we can simply disconnect them after replication has taken place and reset the passwords for the service accounts.

by dkhman26

Also, if we do have conflicts, I need to make sure that the current environment overwrites the new environment and NOT vice-versa as the current environment is live 24x7.

by dkhman26

I appreciate the information, but none of that seems useful in my situation.
Unless there's something I'm missing...
DNS and AD aren't really my strengths.

by dkhman26

This utility looks awesome and looks like it will do what I need it to do. Now I just need to get our network guys to allow communication between the servers...

by dkhman26

Is it at all possible to migrate the users (along with their passwords) to a file, that can simply be imported into the new domain?

This would be the easiest solution, but I don't think Microsoft wants people to do that.

by matt.altman

The ADMT works great. We used it here when we rolled out our DR site and migrated everything over. To answer your earlier question about already having data on your DR site, that is not an issue. You will be replicating all current data so whether there is data there or not does not matter.

by dkhman26

From my understanding, this utility doesn't copy passwords, does it?

by dkhman26

But what if I have the same user on each domain, but because the second domain was built separately without communicating with the first domain, the user has two different passwords? What happens in the case of that kind of conflict?

by cg it

if you've been bought out by another company and want to bring in your users to their domain [or even vice versa], the best way we have found is to install XP or whatever flavor of O/S your using, on a VM with a script that launches it when the machine boots up.

Err this assumes you've done the survey of users and computer collecting user names, passwords, computer names, and created them in AD. [note: User preferences can be brought over without much problem.]

The problem inherent with migration between domains in different forests is AD schema, object identifiers, SIDs, that are different and unique to domains. Thus the user account joeuser@abc.com in the domain abc.com doesn't migrate to to the account joeuser@nbc.com in the domain nbc.com very well even with ADMT and Exmerge.

This discussion is closed to new replies.