Should i create a child domain for new remote site?

[reynolwi]

ok im looking for input...

im going to be setting up a new remote site and since its 3.5 hours away from corporate im going to just go ahead and stick a domain controller in to manage the 2 or so workstations that will be there. would it be easier to create a child domain under the parent and seperate it like that or add it to the current domain and seperate it in sites and services and ensure thats replication is working?

we do run exchange 2003 on the parent domain and all servers are running windows 2003 r2. if i did go with setting up a child domain how is exchange going to work? am ii going to be able to issue an email account from the parent domain or am i going to have to do something different?

Wm. Reynolds
RRWDS | TxPSS

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -
Network Error:
Hit any user to continue

 

[pagy]

Add it to the current domain would be my suggestion. I don't see any need for another domain here, the only reason IMHO is to only have a child domain if you require seperate password polices.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[PU36]

I agree with pagy. I would add the site to the current domain and then create a new site with subnet to manage logon and replication traffic.

There are two reason to have a separate domain at that site.

1. Security (different users and different passwords) but then again unless you are also going to put an Exchange server there then you will have a trust relationship between the two domains which defeats the purpose of segrating based for security.

2. Replication (which can be assisted with sites).