Re: huge user OU

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 06/09/04 

Date: Wed, 09 Jun 2004 16:10:47 -0400

I will say the same thing Jimmy did but remove the thought that it sounds like a
bad idea...

It completely depends on the support model and doesn't become a bad idea and
difficult until the support model is known.

I had several domains with each domain > 45k users (one had 100k) in a single OU
for a long time and it worked great, however we weren't doing GPOs for users.
Once you do GPOs for users unless they are all taking on the same GPO, then you
probably want to break them up. Ditto if you want to delegate different rights
over different sets of users natively. Say HR can only be managed by the HR
support group natively. However if you used someone management tool, it may not
be necessary or desired to split them up.

All by itself, there is nothing wrong putting them all in one place. The
question comes down to what else is being done and how are they being managed.
That is what will drive the organizational structure in AD. 

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Jimmy Andersson [MVP] wrote:
> From an administrative point of view it sounds like a bad idea, the question
> you must ask is if it's going to be easy to administrate. I don't think it
> will in the long run.
> 
> See this link for more info:
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dpgDSS_overview.asp
> 
> Regards,
> /Jimmy