Remote Office Win2k DC Migration
Posted on 2006-07-12
I am having a difficult time deciding what to do in a remote office. This remote office has the following:
1 Windows 2000 Server Domain Controller (which does all DNS and file/print sharing)
20 Client computers
For a long time this remote office operated independently, but we have recently connected the site via 512kbps VSAT, so the site is now a subnet in our cooperate network. This is important as we are rolling-out Exchange 2003 and resolution to our corporate domain is pre-requisite.
The problem now is this Windows 2000 DC is on a different domain then the cooperate network. I am not sure of the best method to migrate this remote site into the corporate Windows Server 2003 domain is.
Should I change domains on the Win2k Server and use ADMTv2 to migrate the accounts?
(Note: b/c there are so few accounts at the remote site….migrating them is not that big of a deal. Their permissions are all going to change anyway, I can simply recreate them on the corporate DC if that is easer).
Should I bring in a new Win2k3 DC and demote the existing Win2k Server?
What’s the best solution with the least impact to the users? Also what effect will this migration have on the 512kbps connection back to corporate?
Thanks for the help in advanced