Discussion Locked

Active Directory Design

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are in the design stage of deploying Win2K and Active Directory. We are in 8 states with multiply sites in each state. Some of the people on the design team want to setup a root domain with only 2 child domains under it and setup OU's for all of the locations, while the others think we should have more child domains. Maybe in each state or support area. Can anyone help me out with the pros and cons to each of these plans. We have a apporx. 5000 users spread out over these areas. Security is an issue and the ones wanting to use the limited domain setup suggest it would be more secure.

All suggestion need.

14 replies

by ntoz

I hate to say it but, there is no one right way to do things, I guess thats the beauty of it. Its going to depend on how your organization is shaped, admin, circuts, etc. People are going to try and tell you one way or another how it should be, honestly, if your asking anyone with the amount of information you have given and they give you a straight answer, dont listen. While security might be an issue, Microsoft and Compaq both went with a single domain modle. Thats what OU's, Delegation and Group Pol's are all about. I think having an empty root domain keeping things flexable at the root sounds like a good idea, perhaps even having two child domains in which perhaps two diverse areas make sense, again guessing from what little I have. The more you add to the mix though, the more planing you should be doing, if done right AD makes your life a dream, poor planing and its going to be no better then most peoples NT domains that were out there. Keep it simple! Make sure your getting people from all departments involved with the design phase, getting buy in. MOST important, your designing AD around the business, not the business around AD. AD is nothing more then a database, the yellow pages and if you make it too difficult, people wont use it to its potential and in effect you will end up with nothing more then a fancy User Manager For Domains. Nuff

Pete

by ntoz

PS, not being smart but 5,000 users is small change. When your putting 50,000 or 60,000 users in one domain and joy, then you have a mid to large size domain. AD has not been tested to its limits yet, they are still trying to find it. Good Luck, email me if I can help anymore...

Pete

by erikdr

For security, the less domains the better.
This is because all settings are per domain,
and it is harder to enforce a policy if you have to apply all changes manually to x domains.
However, the consequence of being in a domain means that the whole ADS tree is replicated to EACH site in the domain sooner or later. No way to 'partition' that, and e.g. have only pw changes to your own users replicated to a site.
Hence, in ADS one is sometimes forced to choose for multiple domains in order to limit the costs of the WAN links. This 'issue' (I'd rather call it a major design limitation/flaw, NDS and iPlanet are a lot better in this) will be resolved in Whistler Server. This will allow (and recommend) one large domain with replication partitions in it.

Hope this helps,

- The Netherlands

by duskos

I really don't have much to add to what previous posters said. I agree with them.
It is really better to have less domains.
So challenge people in your design team to justify creation of a domain. Finance Department and Top Secret Projects Department might be candidates for their own domain, but generally, create large domain and create OU's.

by erikbutler

i agree the fewer the domains the better for security reasons ans so forth; however, if some of your organization require different password policies you will have to set up more domains because password policy is a domain level setting. Also take into consideration what type of wan links do you have if your on anything less than a T-1 i would recommend separate Domains due to logon times. Also with separate domains you do not replicate the whole configuration such as Global catalog. i alsosaw that you are planning several site. A site means you need very good bandwidth inside the site. One last thing to rant on is do you have make sure you have the hardware available at each site for bridgehead servers and so forth so you can tune the replication when the time comes. If you have and ? email me

by erikbutler

i agree the fewer the domains the better for security reasons ans so forth; however, if some of your organization require different password policies you will have to set up more domains because password policy is a domain level setting. Also take into consideration what type of wan links do you have if your on anything less than a T-1 i would recommend separate Domains due to logon times. Also with separate domains you do not replicate the whole configuration such as Global catalog. i alsosaw that you are planning several site. A site means you need very good bandwidth inside the site. One last thing to rant on is do you have make sure you have the hardware available at each site for bridgehead servers and so forth so you can tune the replication when the time comes. If you have and ? email me

by erikbutler

i agree the fewer the domains the better for security reasons ans so forth; however, if some of your organization require different password policies you will have to set up more domains because password policy is a domain level setting. Also take into consideration what type of wan links do you have if your on anything less than a T-1 i would recommend separate Domains due to logon times. Also with separate domains you do not replicate the whole configuration such as Global catalog. i alsosaw that you are planning several site. A site means you need very good bandwidth inside the site. One last thing to rant on is do you have make sure you have the hardware available at each site for bridgehead servers and so forth so you can tune the replication when the time comes. If you have and ? email me

This discussion is closed to new replies.