Scalability demands flexibility, which is why the NT
domain model??™s lack of flexibility resulted in its subsequent lack of scalability.
In a Windows NT domain, users, groups, and computers are all stored in a flat structure.
There is no way to split up users into a more logical hierarchy that follows your own
organization??™s structure other than through NT groups or, in some cases, multiple domains.
Delegating authority over computers, users, and groups was difficult to achieve.
Many large companies wound up managing several thousand, or even tens of thousands,
of NT groups for each of their domains. In addition, large companies had to manage multiple
domains, mostly due to political reasons rather than technical ones (for example, one
part of an organization didn??™t trust or allow the other part to manage its user accounts).
Although I could talk volumes more about the shortcomings of Windows NT, I??™ll fast-forward
a few years to the development of Windows 2000 and Active Directory.
When Microsoft developers went back to the drawing board for Windows 2000, they
realized that the NT domain model was nowhere near where it needed to be in terms of
an enterprise directory service. What came out of this development process was Active
Directory, which addressed many of the weaknesses in the NT domain model. It was
hierarchical, extensible, more secure, and easier to administer.
Pages:
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135