Is this the best solution?

I am helping a client setup a new branch office. They want to setup the new
branch with one domain controller which will be a member of the domain that
is the main HQ instead of creating a child domain for the branch office.
Replication will be via an ISA2004 box on each location using the
site-to-site VPN option. Each site has a 2mb broadband connection.

My plan is to create the new DC on the HQ sites LAN, make it a Global
catalogue server, install DNS and then force replication. I would then
create a new site for the branch office and its subnet. Change the branch DC
IP information to the new information and then ship the DC to the new site.
I then plan on joining the branch ISA server to the domain and configuring
for site-to-site VPN connectivity to allow replication(I know that was a bit
vague but you know what I mean).

Does this solution sound fine, does anyone foresee any problems? Will there
not be issues with the fact that FSMO roles will be split over physical
connections over what is probably not classed as a good connection? Would it
be better to set the new site up as a child domain?

It sounds fine,...just remember to create the "Site" in Active Directory and
move the effected DC's "object" to be under that Site. AD uses the "Sites"
object to control replication over slow WAN links (which VPN certainly
qualifies as).

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"HDZ" <(E-Mail Removed)> wrote in message
news:F8E7B270-927B-4F5C-9C0C-(E-Mail Removed)...
> I am helping a client setup a new branch office. They want to setup the
new
> branch with one domain controller which will be a member of the domain
that
> is the main HQ instead of creating a child domain for the branch office.
> Replication will be via an ISA2004 box on each location using the
> site-to-site VPN option. Each site has a 2mb broadband connection.
>
> My plan is to create the new DC on the HQ sites LAN, make it a Global
> catalogue server, install DNS and then force replication. I would then
> create a new site for the branch office and its subnet. Change the branch
DC
> IP information to the new information and then ship the DC to the new
site.
> I then plan on joining the branch ISA server to the domain and configuring
> for site-to-site VPN connectivity to allow replication(I know that was a
bit
> vague but you know what I mean).
>
> Does this solution sound fine, does anyone foresee any problems? Will
there
> not be issues with the fact that FSMO roles will be split over physical
> connections over what is probably not classed as a good connection? Would
it
> be better to set the new site up as a child domain?
>