Branch Office Domain Change

Branch Office Domain Change

Post by kunundru » Sun, 11 Jun 2006 16:21:16

I have a question regarding what is the best choice for a remote office

Network Overview
My network consists of three sites all connect via internal 512Kbps
VSAT system. All routable we can ping each site via IP.

HQ = 1DC Win2k3, 1 Exchange Win2k3, 25-30 users (192.168.1.x)
Remote Office A = 1DC Win2k, 25-30 users (192.168.2.x)
Remote Office B = WinXP Pro, 4-8 users (192.168.3.x)

The Problem
Remote Office A was setup a few years back by a different network
administrator who setup this location as a separate domain from HQ
(totally separate). So now, we want to migrate to one domain so that we
may utilize Exchange network wide.

The Question
What would be my best course of action?

Should try and utilize the existing (production) Win2k DC and simply
change domains?

Should I configure a separate DC and bring it to the site and demote
the existing Win2k DC? I still want to use the existing Win2k DC for
DNS and file sharing.

I guess I am looking for the path of least impact to the end users as
well as the most functional option.

Branch Office Domain Change

Post by v-xuwe » Tue, 13 Jun 2006 11:54:03


I think the best way is migrate resources into one domain. To do this, we
have a tool called ADMT.

326480 How to use Active Directory Migration Tool version 2 to migrate from
Windows 2000 to Windows Server 2003;EN-US;326480

Restructuring Active Directory Domains Between Forests

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! -
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
This posting is provided "AS IS" with no warranties,and confers no rights.

07:21:20 GMT)
AppleWebKit/418 (KHTML, like Gecko) Safari/417.9.2,gzip(gfe),gzip(gfe)