That's not a valid reason to run a second domain ;)

There's seriously no difference, other than the obvious DNS differences,
between those two options. We run two domains, empty root and one with
everything else in it, in a discontiguous namespace (we use a both the .com
and .net versions of the domain name for the two). Works flawlessly.

--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.


> -----Original Message-----
> From: Weatherly, Rob [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, August 12, 2003 4:19 PM
> To: NT 2000 Discussions
> Subject: RE: Difference Between Child and New Domain
> 
> 
> I completely agree with trying to keep everything in one 
> domain. In this
> case we actually have to have a second domain. They want to 
> be set up as
> a second domain in the same forest. We want to set them up as a child
> domain. The problem is we are having trouble finding documentation to
> support either or. The reason they want a second domain is 
> because they
> want to maintain the internet namespace internally (company.co.uk).
> 
> --------------------------------
> Rob Weatherly
> --------------------------------
> 
> -----Original Message-----
> From: Roger Seielstad [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, August 12, 2003 4:01 PM
> To: NT 2000 Discussions
> Subject: RE: Difference Between Child and New Domain
> 
> My personal belief is that it doesn't matter either way, although I
> prefer
> to keep it as a single domain rather than two.
> 
> 
> --------------------------------------------------------------
> Roger D. Seielstad - MTS MCSE MS-MVP
> Sr. Systems Administrator
> Inovis Inc.
> 
> 
> > -----Original Message-----
> > From: Weatherly, Rob [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, August 12, 2003 3:31 PM
> > To: NT 2000 Discussions
> > Subject: RE: Difference Between Child and New Domain
> > 
> > 
> > Wow!! I guess this question was too tuff for everyone
> > 
> > --------------------------------
> > Rob Weatherly
> > --------------------------------
> > 
> > -----Original Message-----
> > From: Gonzalez, Alex 
> > Sent: Tuesday, August 12, 2003 8:58 AM
> > To: NT 2000 Discussions
> > Subject: Difference Between Child and New Domain
> > 
> > 
> > 
> > I was wondering if anyone could tell me some of the 
> > differences between
> > setting up a child domain and setting up a new domain in the 
> > same forest
> > in Windows 2000 Active Directory.  We have a company that 
> we own that
> > wants to finally implement Windows 2000 and join our forest 
> > but it is up
> > in the air as to whether we should have them become a child 
> domain or
> > become a new domain in the same forest.  If they become a 
> child domain
> > they would become them.us.com.  If they become a new domain 
> > in the same
> > forest they become them.co.uk.  The reason they want to do 
> this is to
> > stay current with their Internet name space which I told them is not
> > necessary.  Any help would be appreciated. 
> > 
> > Thanks!!
> > 
> > 
> > ------
> > You are subscribed as [EMAIL PROTECTED]
> > Web Interface:
> > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&tex
> t_mode=&la
> ng=english
> To unsubscribe send a blank email to %%email.unsub%%
> 
> ------
> You are subscribed as [EMAIL PROTECTED]
> Web Interface:
> http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&tex
t_mode=&la
ng=e
nglish
To unsubscribe send a blank email to %%email.unsub%%

------
You are subscribed as [EMAIL PROTECTED]
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&la
ng=english
To unsubscribe send a blank email to %%email.unsub%%

------
You are subscribed as [EMAIL PROTECTED]
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=e
nglish
To unsubscribe send a blank email to %%email.unsub%%

------
You are subscribed as [EMAIL PROTECTED]
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=english
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to