The consultant may have been referring to the number of GPOs that you are
attaching to the OUs. The more GPOs that have to be processed, the longer the
login time.
OU design is really a matter or preferences, IMO.
Sincerely,
_____
(, / | /) /) /)
/---| (/_ ______ ___// _ // _
) / |_/(__(_) // (_(_)(/_(_(_/(__(/_
(_/ /)
(/
Microsoft MVP - Directory Services
www.readymaids.com <http://www.readymaids.com> - we know IT
www.akomolafe.com <http://www.akomolafe.com>
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
________________________________
From: [EMAIL PROTECTED] on behalf of Milton Sancho
Sent: Wed 4/12/2006 1:53 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OU's Structure
Hello,
I got a discussion with a consultant who was hired to deploy a new corporate
domain(Win2003) structure.
We have right now a domain running on Windows 2000 (Active Directory 2000), I
created a logical OU structure in the domain controller according all the
departments we have in the network. For instance sales,customer service, IT ,
marketing, Facilities, so on. With this structure I have all the users and
objects organized by OU, then if we need to apply GPO or customized security
polices we apply it by department (OU) wihout affect others OU (Departments).
However in the other hand, the consultant told us we have not to use this "OU
structure" , because it decrease login time at client level. ???
Not sure about his comment. Because I have seen how end users loggin on their
different departments without the behaviour that he argumented.
Now, we have a Win2003 domain , without the "OU Structure" that we have in
the win2000 domain, I have not found yet the difference he mentioned. Besides
to keep all users just into one OU looks to be more complex to apply GPO and
other policies.
Thanks comments
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
