Re: Child Domain
- From: "Laura E. Hunter \(MVP\)" <laura(nospamplease)>
- Date: Fri, 13 May 2005 14:09:00 -0400
Generally speaking, you'll create a child domain (or a new domain tree) if
you need to create security settings for one group of clients that are
different from the rest of your clients. There are certain AD settings like
password length/complexity and account lockout settings that can only be set
at the domain level. So if your ASP clients need different security settings
than your company computers, a child domain might be the way to go.
Some companies will use a child domain to segregate the administration
process as well, but you can do that just as easily by placing your NT 4.0
clients in a single Organizational Unit.
--
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Consultant's Field Guide_
(http://tinyurl.com/7f8ll)
All information provided "AS-IS", no warranties expressed or implied.
Replies to newsgroup only.
"Jobe Gates" <jgates@xxxxxxxxxxx> wrote in message
news:O3oe1B9VFHA.3140@xxxxxxxxxxxxxxxxxxxxxxx
> We have 2 domains currently one for our company and one for our ASP
> customers. We've decided to add all of our NT 4.0 clients to the domain
> and are unsure of where to put them. We aren't sure if we should either
> do a child of the ASP domain or put it in the top level ASP domain.
>
> Any thoughts?
>
.
- References:
- Child Domain
- From: Jobe Gates
- Child Domain
- Prev by Date: Re: Login Scripts
- Next by Date: Re: security descriptor
- Previous by thread: Child Domain
- Next by thread: Child Domain
- Index(es):
Relevant Pages
|
