Re: Possible Administration Issue.
From: Frater (None_at_legioobscurantis.com)
Date: 07/26/04
- Next message: Sergio Fonseca [MVP]: "Re: Confused"
- Previous message: Enkidu: "Re: Anyone Done a Disaster Recovery of AD?"
- In reply to: Laura E. Hunter \(MVP\): "Re: Possible Administration Issue."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 26 Jul 2004 09:18:04 +0200
Thanks a lot Laura.
On Fri, 23 Jul 2004 10:54:00 -0400, "Laura E. Hunter \(MVP\)"
<hunter(nospamplease)@sfs.upenn.edu> wrote:
>Typically you'll want to create a separate or child domain if your branch
>has differing security requirements from the parent company, especially in
>terms of password length or complexity requirements. Organizational Units
>are a valid choice for delegating administration without creating the added
>overhead and complexity of a separate domain. Within Active Directory, you
>can address your logical network design (domain vs. OU) as a separate entity
>from your physical design. Sites and domains do not need to exist in a
>one-to-one relationship: you can have a single site that contains multiple
>domains or a single domain that spans multiple sites. As long as you define
>your subnets correctly withing AD Sites & Services, any AD-aware
>applications and resources will attempt to use servers & services within the
>local site before attempting to traverse a WAN link.
- Next message: Sergio Fonseca [MVP]: "Re: Confused"
- Previous message: Enkidu: "Re: Anyone Done a Disaster Recovery of AD?"
- In reply to: Laura E. Hunter \(MVP\): "Re: Possible Administration Issue."
- Messages sorted by: [ date ] [ thread ]