Guia De Server 2008
Páginas: 10 (2374 palabras)
Publicado: 20 de abril de 2012
Chapter 1: Getting Started with Windows Server 2008 Active Directory
Beginning with Windows 2000, Microsoft completely revolutionized its concept of Windows domains. Gone was the limited size, flat namespace of Windows NT domains, and in its place was the hierarchical Active Directory domain structure built upon the concepts of X.500 and Lightweight Directory Access Protocol (LDAP). ActiveDirectory has matured since its beginnings with Windows Server 2003 and now Windows Server 2008’s new features, improved functionality, and ease of configuration and management. Those of you who have worked with Active Directory in Windows 2000 or Windows Server 2003 will be familiar with much of the content of this book. For those of you who are new to server and network management or who haveworked with only Windows NT networks, this book begins with a brief introduction to the concepts that Microsoft used to put Active Directory together.
The Building Blocks of Active Directory
In creating the hierarchical database structure of Active Directory, Microsoft facilitated locating resources such as folders and printers by name rather than by physical location. These logical building blocksinclude domains, trees, forests, and organizational units (OU). The physical location of objects within Active Directory is represented by including all objects in a given location in its own site.
Domains
Similar to the case in Windows NT, the domain represents the core unit of the network structure. As in Windows NT, the domain is a logical grouping of computers that shares a commondirectory database and security. However, whereas in Windows NT each domain was a unit unto itself with no default trust relationship with other domains, in Active Directory you can have a series of domains organized into larger units called trees and forests, with inherent trust relationships already built into them. Individuals can be designated with administrative powers over a single domain or acrossan entire forest, and you can even configure trust relationships to external forests. Furthermore, Active Directory domains can hold millions of objects, as opposed to the Windows NT domain structure, which was limited to approximately 40,000 objects.
25
The Building Blocks of Active Directory
Trees
A tree is a group of domains that shares a contiguous namespace. In other words, a treeconsists of a parent domain plus one or more sets of child domains whose name reflects that of a parent. For example, a parent domain named examcram.com can include child domains with names such as products. examcram.com, sales.examcram.com, and manufacturing.examcram.com. Furthermore, the tree structure can contain grandchild domains such as america.sales.examcram.com oreurope.sales.examcram.com, and so on, as shown in Figure 1.1. All domains in a tree are linked with two-way, transitive trust relationships; in other words, accounts in any one domain can access resources in another domain and vice versa. See Chapter 5, “Active Directory Objects and Trusts,” for more information on trust relationships.
examcram.com
que.com
products.examcram.com
sales.examcram.commanufacturing.examcram.com
sales.que.com
america.sales.examcram.com
europe.sales.examcram.com
FIGURE 1.1
A forest can contain multiple trees, and trees can contain multiple levels of child
domains.
Forests
A forest consists of a group of domain trees that do not share a contiguous namespace. For example, you can have two trees with parent domains named examcram.com and que.com, asshown in Figure 1.1. Each tree can contain its own child domains within its namespace. Again, two-way transitive trust relationships exist between domains in the trees of a single forest. When you create a new Active Directory structure, the first domain created is the forest root domain.
26
Chapter 1: Getting Started with Windows Server 2008 Active Directory
Organizational Units
An...
Beginning with Windows 2000, Microsoft completely revolutionized its concept of Windows domains. Gone was the limited size, flat namespace of Windows NT domains, and in its place was the hierarchical Active Directory domain structure built upon the concepts of X.500 and Lightweight Directory Access Protocol (LDAP). ActiveDirectory has matured since its beginnings with Windows Server 2003 and now Windows Server 2008’s new features, improved functionality, and ease of configuration and management. Those of you who have worked with Active Directory in Windows 2000 or Windows Server 2003 will be familiar with much of the content of this book. For those of you who are new to server and network management or who haveworked with only Windows NT networks, this book begins with a brief introduction to the concepts that Microsoft used to put Active Directory together.
The Building Blocks of Active Directory
In creating the hierarchical database structure of Active Directory, Microsoft facilitated locating resources such as folders and printers by name rather than by physical location. These logical building blocksinclude domains, trees, forests, and organizational units (OU). The physical location of objects within Active Directory is represented by including all objects in a given location in its own site.
Domains
Similar to the case in Windows NT, the domain represents the core unit of the network structure. As in Windows NT, the domain is a logical grouping of computers that shares a commondirectory database and security. However, whereas in Windows NT each domain was a unit unto itself with no default trust relationship with other domains, in Active Directory you can have a series of domains organized into larger units called trees and forests, with inherent trust relationships already built into them. Individuals can be designated with administrative powers over a single domain or acrossan entire forest, and you can even configure trust relationships to external forests. Furthermore, Active Directory domains can hold millions of objects, as opposed to the Windows NT domain structure, which was limited to approximately 40,000 objects.
25
The Building Blocks of Active Directory
Trees
A tree is a group of domains that shares a contiguous namespace. In other words, a treeconsists of a parent domain plus one or more sets of child domains whose name reflects that of a parent. For example, a parent domain named examcram.com can include child domains with names such as products. examcram.com, sales.examcram.com, and manufacturing.examcram.com. Furthermore, the tree structure can contain grandchild domains such as america.sales.examcram.com oreurope.sales.examcram.com, and so on, as shown in Figure 1.1. All domains in a tree are linked with two-way, transitive trust relationships; in other words, accounts in any one domain can access resources in another domain and vice versa. See Chapter 5, “Active Directory Objects and Trusts,” for more information on trust relationships.
examcram.com
que.com
products.examcram.com
sales.examcram.commanufacturing.examcram.com
sales.que.com
america.sales.examcram.com
europe.sales.examcram.com
FIGURE 1.1
A forest can contain multiple trees, and trees can contain multiple levels of child
domains.
Forests
A forest consists of a group of domain trees that do not share a contiguous namespace. For example, you can have two trees with parent domains named examcram.com and que.com, asshown in Figure 1.1. Each tree can contain its own child domains within its namespace. Again, two-way transitive trust relationships exist between domains in the trees of a single forest. When you create a new Active Directory structure, the first domain created is the forest root domain.
26
Chapter 1: Getting Started with Windows Server 2008 Active Directory
Organizational Units
An...
Leer documento completo
Regístrate para leer el documento completo.