Re: Users container
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 19 Jul 2006 15:43:19 -0500
That's how it is normally done. "OU" isn't a valid child of "container"
(which is what Users is), so you really don't have a choice. :)
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"dfw63" <dfw63@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7AEDFBC6-5419-4185-96A6-E63AF19A668C@xxxxxxxxxxxxxxxx
Why is it that you cannot create an OU within the Users container? I know
technically why but I'm wondering why Microsoft designed it this way.
That
seems like a logical place to segregate users for group policy
application.
Are there best practices someone can refer me to for AD orgainzation? It
just seems a bit sloppy to add a bunch of user OU's right off the root,
but
I'm wondering if this is how it's normally done.
.
- Prev by Date: Re: ADAM Authentication
- Next by Date: Re: Migrating a Child Domain to a Parent Domain
- Previous by thread: IE Settings in GPO
- Next by thread: Re: Users container
- Index(es):
Relevant Pages
|
