La relación poder y prensa escrita: gobierno de Rafael Correa y los diarios El Comercio y El

Creating an OU structure can be a difficult task. Fortunately, there are a number of standard models on which you can base your design. Each model describes the cate­ gories of OUs and the relationships the OUs share with one another.

You can base an OU design on the following five OU models: ■ Location-based

■ Organization-based ■ Function-based

■ Hybrid of location, then organization ■ Hybrid of organization, then location

See Also The OU models described in this section should cover most situations and are those you are likely to see on the exam. However, these models certainly do not represent the only way to design an OU structure. Consult the Microsoft Windows Server 2003 Deployment Kit, part of the Microsoft Resource Kit collection (Microsoft Press, 2003), or check out the var­ ious articles on Active Directory deployment available at http://www.microsoft.com/technet.

Location-Based

In the location-based OU model, shown in Figure 4-5, network administration is dis­ tributed among a number of geographic areas. This model is useful if each location has its own administrative requirements that differ from other locations.

Builtin Computers Domain Controllers Users Dallas Memphis Domain User Accounts Computer Accounts

Figure 4-5 The location-based OU model distributes network administration geographically. The location-based model provides a number of advantages, including the following:

■ OUs are resistant to changes. Companies may reorganize their resources or departments, but geographic locations tend to remain more static.

■ A centralized administrative staff can easily implement domain-wide policies. ■ It is easier to figure out where resources are located.

■ It is easy to create new OUs if a merger or expansion takes place.

There are also certain disadvantages to the location-based model, including the following: ■ Because you are creating a structure based on geography, this suggests you will

need network administrators at each location.

Note Assigning Group Policy Objects to sites (which are typically based on location) can provide many of the same benefits as the location-based OU model, without the disadvan­ tages. You’ll learn more about designing sites in Chapter 5.

Organization-Based

In the organization-based OU model, shown in Figure 4-6, network administration is divided into departments or business units so that each has its own administrator. This model is useful if the company has a strong division structure.

Domain

Builtin

Computers

Domain Controllers

Users

Research & Development

Marketing

Sales

Figure 4-6 The organization-based OU model divides network administration according to depart­ ments or business units.

The organization-based model provides a number of advantages, including the following: ■ This structure helps maintain a certain level of autonomy for each department or

business unit.

■ It accommodates mergers and expansions.

■ This structure is friendly to administrators because the structure can be understood by anyone in the company.

There is also a major disadvantage to the organization-based model. This structure is vulnerable to reorganization. A change in department may require a change in top- level OU structure.

Function-Based

In the function-based OU model, shown in Figure 4-7, the administrative staff is decen­ tralized but bases its administrative model on business functions within the organiza­ tion. This is an ideal choice for small organizations that have job functions that span several departments. Builtin Computers Domain Controllers Users Engineering Transportation Domain Purchasing Research

Figure 4-7 The function-based OU model bases its administrative model on business functions.

The function-based model provides the significant advantage of being relatively immune to reorganizations.

However, there is also a significant disadvantage to the function-based model. You will likely have to create additional levels of OUs to delegate administrative control of user accounts, computers, printers, and network shares.

Hybrid of Location, then Organization

In this model, shown in Figure 4-8, you create top-level OUs that represent the geo­ graphic locations of the company and then create lower-level OUs by organization.

Domain Builtin Computers Domain Controllers Users Dallas Memphis Sales Marketing

Figure 4-8 This hybrid OU model is based first on location, then organization.

The hybrid of location, then organization model provides two advantages, as follows: ■ It allows for additional departmental and divisional growth.

■ It allows for distinct security boundaries.

There are also certain disadvantages to this hybrid model, including the following: ■ You would likely have to redesign the structure if the administrative staff becomes

reorganized.

■ This model requires cooperation among administrators if they are in the same location but different departments.

Hybrid of Organization, then Location

In this model, shown in Figure 4-9, you create top-level OUs that represent the orga­ nization of the company, and then create lower-level OUs by location.

Builtin

Computers

Domain Controllers

Users

Research & Development

Marketing

Domain

San Francisco

Fort Worth

Figure 4-9 This hybrid OU model is based first on organization, then location.

This hybrid model provides the single big advantage of allowing for strong security between departments or divisions while still letting you delegate administrative control based on location.

However, the disadvantage of this model is that it is vulnerable to reorganization—just like the organization-based model.