Network Architecture Question

I have a quick question about network architecture for the group.

Here's the senario.

I have a single domain for Company A with 150+ users running a VB front-end app hitting a SQL DB.

We recently acquired Company B with 50+ users.

Company A wants to keep the SQL DB in the local office and the users in Company B should be accessing the DB over a point-to-point T1 line (or multiple).

My question is do I create Single Domain for the 2 companies and use OUs for control
OR,
Do I create a child domain with a 2-way trust for the child domain.

Personally I want to create a child domain, to minimize network traffic, localize administration at Company B, etc.
BUT am I creating more administrative work?

I'd like to know what anyone thinks?

More domains = more work.

look into setting them up as either an OU or a site.
See:
How to create and configure an Active Directory Site in Windows 2000

http://support.microsoft.com/default...b;en-us;318480

hth
DDS W 2k MVP MCSE

"Jonsey" <(E-Mail Removed)> wrote in message
news:94F6E561-42BC-4059-AABE-(E-Mail Removed)...
> I have a quick question about network architecture for the group.
>
> Here's the senario.
>
> I have a single domain for Company A with 150+ users running a VB
front-end app hitting a SQL DB.
>
> We recently acquired Company B with 50+ users.
>
> Company A wants to keep the SQL DB in the local office and the users in
Company B should be accessing the DB over a point-to-point T1 line (or
multiple).
>
> My question is do I create Single Domain for the 2 companies and use OUs
for control
> OR,
> Do I create a child domain with a 2-way trust for the child domain.
>
> Personally I want to create a child domain, to minimize network traffic,
localize administration at Company B, etc.
> BUT am I creating more administrative work?
>
> I'd like to know what anyone thinks?
>
>