|
|
Windows Server 2003 is designed to take into account both logical and physical structural parameters. The logical structure can be described as the conceptual way an organization breaks down into a hierarchy of units and subunits. These units may be business groups, product lines, geographic locations, and the like. As discussed in Chapters 5 and 6, the Windows Server 2003 enterprise model relies on the concepts of forests, domain trees, domains, and organizational units to formulate the logical structure. These divisions are based on an assortment of criteria, including domain names, security boundaries, resource availability, and administrative authority. Users, computers, devices, applications, and other system objects are grouped into organizational units where function and responsibility are logically assembled. The logical structure of most organizations is very dynamic, and the Windows Server's logical structure can effectively accommodate change.
The physical structure is defined in Windows Server 2003 primarily by network connectivity. Windows Server assumes that reliable and cost-effective connectivity achieves optimal performance. A site is the Windows Server base unit of the physical structure and is defined by well-connected TCP/IP subnets. The planning process will determine how sites are linked to best facilitate directory service replication, user logons, and data flow.
Independent accounting for both logical and physical structural paradigms adds levels of complexity. However, through careful planning and deployment, administration of the enterprise can be greatly enhanced. The demands of the logical organizational structure coupled with the potential limitations of the physical structure require careful review. When planning a Windows Server 2003 enterprise, both sides of the equation require attention.
In this chapter, we look at the logical and physical structures from a more homogeneous vantage point. That is, we do not distinguish between them at this stage of this discussion for a reason that can be classically defined as the "chicken and the egg" dilemma. To appreciate the distinction between Windows Server's treatment of logical and physical structures, it is necessary to understand the topics covered in the next several chapters (specifically those dealing with the Active Directory and networking). Unfortunately, to get to those topics, it is vital that foundations of information be laid. In the real world, attention must be paid to both the logical and the physical enterprise. While the two can be independently administered, their interplay is vital to effective Windows Server deployment. For this reason, we recommend that you use the information outlined in this chapter after at least a minimal review of the Active Directory (Chapters 5 and 6), user management (Chapter 7), group policies (Chapter 8), and networking (Chapters 12 and 13).
 |
|
|
| Top |