Discussion Locked

Reasons to use a Single Master Domain

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

Hello,

I need the technical reasons why (or why not) we should change from a Complete Trust Domain model to that of a Single Master Domain Model, other than to simplify migration to W2K, the centralisation of user accounts and the simplificationof trusts.

We have 6 domains at present all running NT 4, SP5 in a Complete Trust Model.

13 replies

by noraann

By having the Master Domain Model, you would have all user accounts in the Master Domain and then all resources in the other domains. This allows for organizational grouping of your network resources, but still allows the central administration. Other words, different departments could have the ability to manage their own resources (printers, etc.) while allowing central administration of accounts. Since you already have the 6 domains the resources could be grouped according to 5 of the local domains and then 1 domain would become the master. All of the local administrators would continue to administer the resources and the master domain admin would administer the user accounts. This way the decentralized management is not totally taken from the current domain admins and helps with the deparmental politics.. This type of domain model can handle approx. 30,000 users depending on the number of servers and type of hardware being used. This also will simplify the "trust" model which with 6 domains you would have 35 trusts built.

by nmoore

Thanks, but as I said I need some tech. reasons other than simplification of trusts and centralisation of user accounts.

by dennis rigdon

Your on the right track.
1]Central account management is one of the strongest benefits of the Single Master Domain. Users have a single username for the entire network. That's a great advantage. It may take some campaigning to convince "Resource Domain" administrators that this model does not take control away from them.
We have our resource domain admins in the master "Accounts Domain" Account Operators group. This allows them to create accounts or group and supply them with access to resource just as before the change.
2] You should notice a decrease in network traffic as the number of trust decrease. This can be significant. Eliminiating the management of the trust relationships, both in regard to personnel as well as the server processor time, should be enought reason.
If you organization expects growth, then the complete master will become increasingly more complex and more difficult/costly to manage.
Without Windows 2000, managing a WINNT4 network via complete trust candrive your administrators crazy. It is not recommended for large networks.
With the advantages of the Single Master Domain, I don't know of a strong enough reason to spend the additional time and money to support the multiple master model.
In most cases, the reason for using it are not related to networking but are political.

Some of our departments are desolving their domains into the the Master domain, now that they understand that they can still maintain control of their servers, but don't have to maintain domain controllers or user accounts. They just manage users access to their resources. This is more seems reliable to the end user, because they don't have to remember different user accounts, passwords or to which domain they should log on.

by gadawg

For the type of answer you are looking for I have to suggest going straight to the source...Microsoft.com. They have some great articles in Technet and other white papers and which discuss the pros and cons of the different domain models. "Technical" reasons are not necessarily the most compelling in this case (in my opinion) if you are referring to traffic and infrastructure issues. The ease of administration of a single master domain would be my main arguement but it sounds like you are possibly looking for fuel for a presentation to sway a customer or IT mgr. Check out Microsoft documentation for their insight.

by knudson

Well if you are looking for technical reasons, there really aren't any. The reasons for one versus the are almost a matter of opinion. Other than the issue of the number of Users, NT Machines ... in the domain if you are over several thousand start looking at some flavor of multiple domains, Master or Trusts. Or Geography, keeping some form of domain controller close to the users. Even here the decisions are not technical, more manageablity, and reliability.

by mpdcsup

Since centralization and manageability are not of concern, I'd have to go with reliability and performance. In a master domain model, you will centralize your point(s) of failure -- if one can't authenticate, no one authenticates. On a WAN, a userfrom a neighboring LAN will have to authenticate back to his or her home LAN (possibly to access a resource also across a slow WAN link. If you're moving to Win2K, I'd suggest spending the effort learning the new model and how best to fit it into your organization before taking any time to change or even think of changing the current model.

by rwscc

The teechnical reason for keeping separate domains is the limitation on size of the sam database. The technical reason for a single domain is the elimination of interdomain authentication traffic and thus one less failure point in the authentication process. In NT4 there is a problem authenticating without a local domain controller unless you are using WINS and IP.

The real reason multiple domains exist is usually management autonomy in each domain. If you are looking for the technical reason for a particular domain model to be compelling enough to overide strong management desires for autonomy or the reduction of autonomy, you won't find a real technical reson unless your organization has too many users for a single master domain.

This discussion is closed to new replies.