should I setup new site or child domain

[m]

Hello,

I'm new setting up new site or child domain. Can someone
please help me with how and which option is the best?

My company have a corporate office and now they are going
to have a branch office in Texas.
We have a firewall over the corporate office with 2
segment one is connected inside the firewall and the other
is outside of the firewall.
The rang of ip address in side the firewall is xxx.xxx.4.x
and outside of the firewall is xxx.xxx.2.x. We have 2 DC
with active directory installed. and have intergrated DNS
and one dhcp server.
Now for the branch office we will not have any firewall,
all we have is a router, and we need to setup a domain
controller out there so the workstations can logon to this
domain. And we also want the workstations to have the
same policy as the corporate office.
We going to have the T1 connection between the branch
office and the corporate office.
Over this branch office should we have DNS server service,
DHCP server services, and print server services too.
The most important requirement is we got to have the
ability to manage the domain and these services over at
the corporate office "like users and computers accounts,
policy, dns, dhcp, and print server, etc.,,).
With these requirement should I have a new site or a new
child domain, and how can I have this setup? Please help,
this is very urgent!!!

Thanks a lot!!!

M.

 

[Herb Martin]

If you have to ask the answer is almost always "Site" but
let's work through it....

I'm new setting up new site or child domain. Can someone
please help me with how and which option is the best?

Default answer is SITE.

My company have a corporate office and now they are going
to have a branch office in Texas.
We have a firewall over the corporate office with 2
segment one is connected inside the firewall and the other
is outside of the firewall.

In an EXTREME case (unlikely here) a "firewall" can be
an argument for "different domains."

The rang of ip address in side the firewall is xxx.xxx.4.x
and outside of the firewall is xxx.xxx.2.x. We have 2 DC
with active directory installed. and have intergrated DNS
and one dhcp server.

IP ranges are irrelevant.

Now for the branch office we will not have any firewall,
all we have is a router, and we need to setup a domain
controller out there so the workstations can logon to this
domain. And we also want the workstations to have the
same policy as the corporate office.

This (same policy) is an argument for a single domain.

We going to have the T1 connection between the branch
office and the corporate office.

No reason here to pick "domain."

Over this branch office should we have DNS server service,
DHCP server services, and print server services too.
The most important requirement is we got to have the
ability to manage the domain and these services over at
the corporate office "like users and computers accounts,
policy, dns, dhcp, and print server, etc.,,).

Slight argument for "same domain" but it can go either way.
And if you are going to "manage the other location" anyway then
the firewall is not going to be a "different domain" case.

With these requirement should I have a new site or a new
child domain, and how can I have this setup? Please help,
this is very urgent!!!

New site.

Same domain; easier Group Policy and Administration.

 

[m]

Herb,

Thanks for your respond. I'm kinda comfuse on your
respond. So is the firewall going to be a problem for
managing the branch office by the corporate office? Do I
need to setup a separate AD on the branch office with new
new policies?

Thanks Herb,

M

 

[Herb Martin]

Thanks for your respond. I'm kinda comfuse on your

respond. So is the firewall going to be a problem for
managing the branch office by the corporate office?

Assuming the firewall is tightly closed then it is not going
to be a "problem" but you will need to deal with it as an
issue.

Management workstations should probably VPN into
the branch office.

Do I
need to setup a separate AD on the branch office with new
new policies?

No.