Home > Articles > Certification > Microsoft Certification

This chapter is from the book

Gathering and Analyzing Technical Requirements

When you're gathering and analyzing information about a business, you must consider the business requirements as well as the technical, security, and performance requirements. These three requirements have a major impact on the design of the Active Directory structure and must be carefully considered.

These factors are covered in the next three sections: "Determining the Technical Environment," "Assessing Security Requirements," and "Determining Performance Requirements." Keep in mind that these topics are equally as important as the previous ones discussed and are crucial in designing an effective Active Directory structure.

Determining the Technical Environment

To get a good overall picture of the technical environment in an organization, you need to look at the following aspects:

  • LAN/WAN connectivity

  • Available bandwidth

  • Server and workstation distribution

LAN/WAN Connectivity

Begin the assessment of LAN/WAN connectivity by determining the topology of the network; document the network topology and the size of the network. After the layout of the network has been established, you can assess the connectivity between the physical networks. Documenting the connectivity in a business helps you in designing an Active Directory structure that complements the physical layout. Not doing a thorough assessment of the connectivity between and in the various locations can result in such things as regular replication occurring over a slow network connection.

The easiest thing to do to get an overall picture of the network structure is to draw a diagram representing the physical structure of the network. An example of this type of diagram is shown in Figure 3.4 (this will help give you an overall picture of the physical layout). After you've documented the physical layout, you can determine the type and speed of connections in the locations as well as the speed of the links between them.

Figure 3.4Figure 3.4 An example of how the physical WAN structure of the XYZ Corporation might look. The design team can choose to document the physical structure in a similar way to get a better overall idea of the structure. In your diagram, be sure to also include the LAN structure.

Determining the appropriate speeds of the links in an organization depends on the amount of network traffic generated. Further analysis of the amount of network traffic generated throughout the business must be done to determine available bandwidth.

NOTE

Completing these assessments helps the design team determine the best replication routes in the business and the optimum location for its servers.

Available Bandwidth

Assessing the amount of bandwidth available is necessary in determining the location of Active Directory sites. A connection between two locations might be high-speed and reliable, but if it is already heavily utilized, it might not have enough bandwidth available to support regular replication. This information can lead the design team to create sites on either side of the connection. Only a thorough analysis of the network traffic generated in an organization will give you a good picture of the available bandwidth, and using a network analyzer such as Network Monitor will help you determine the amount of traffic currently being generated.

CAUTION

The physical LAN and WAN infrastructure influences not only site design, but also domain design and server placement in a domain.

Figure 3.5 shows the speed of the WAN connections between the various locations in the XYZ Corporation (when doing an actual assessment of connectivity, be sure to include LAN connectivity as well as WAN). Creating a diagram similar to this one will help the design team establish an overall picture of the links available. After the type of connectivity has been established, the next step is to determine how much bandwidth is available over each link.

Figure 3.5Figure 3.5 This figure shows the design team the exact speeds of the connections between the locations. The team would then have to assess the usage of each link to determine whether it would be capable of handling traffic generated by Active Directory replication.

When determining the amount of traffic generated on the network and the available bandwidth, consider some of the following traffic-generating events and how often they occur:

  • How often are users required to change their passwords?

  • How many users log on to the network?

  • When do the bulk of the logons occur?

  • How many DNS queries are performed throughout the day?

Server and Workstation Distribution

The design team is responsible for assessing how the servers and workstations are currently distributed throughout the organization. After the physical setup of the network has been documented, the design team needs to determine how many workstations are in each location, the number of servers in the business, and their current placements. The design of Active Directory sites is dependent on the number of workstations in each location. Therefore, the decision as to where domain controllers should be placed is partially dependent on the number of workstations in the various business locations.

For example, the design team working for the XYZ Corporation might determine during its assessment that one of the locations has a small number of workstations. Information such as this can help the design team later in determining whether a domain controller should be placed in this location.

NOTE

It can be beneficial to add this information into your diagram of the physical network so you can get an overall picture of how the servers and workstations are distributed throughout the network.

Assessing Security Requirements

The security requirementsof a business have a major impact on the design of the Active Directory structure. The security plan developed by the design team should be based on the security requirements of the business. Security has become a hot issue when designing a network infrastructure. As the need for enterprise networks increases and the distribution of internal data among employees becomes a necessity, businesses are implementing strict security policies to secure their network resources. When assessing the security requirements of a business, you must consider user security needs and local (geographical) security requirements.

User Security Needs

Most businesses implement some form of security for their users to protect network resources and reduce the total cost of ownership (TCO). The security requirements a business implements for its users, such as data encryption for mobile users, application restrictions, and account restrictions, need to be considered when designing the Active Directory structure.

For example, the XYZ Corporation might have some of the following security requirements for its users:

  • Preconfigured desktop for all users

  • Limited capability for users to modify the configurations assigned to them

  • Secure logon

  • Application restrictions

  • Sensitive data available to select groups

  • Encrypted data for mobile users

The design team needs to be aware of these security requirements so the Active Directory structure can support them.

Local (Geographical) Security Requirements

The security of the users needs to be assessed, but consideration also must be given to the security needs of the various locations. Instances often occur in which one location in an organization has different security needs from another location. If this is the case, the design of the Active Directory infrastructure must reflect this.

For example, the XYZ Corporation has several locations throughout the world. After completing an assessment of the local security needs, the design team might determine that the offices in L.A. and the offices in Paris have different security requirements. Figure 3.6 shows a few of the security requirements for each of the geographical locations.

Figure 3.6Figure 3.6 A list of some of the different security requirements that two of the locations in the XYZ Corporation might have.

The design of the Active Directory infrastructure for the XYZ Corporation needs to reflect the individual security needs of the locations in the business. To meet the different security needs of Paris and L.A., the design team might decide to create separate domains for each location. This would allow each of them to implement its own security. The point is that a company's security requirements have a major impact on the creation of forests, trees, domains, and OUs. Therefore, it's an aspect that deserves attention.

CAUTION

In particular, a critical aspect of domain design is understanding all the security requirements of an organization. Almost all security policy decisions are made at the domain level, so if part of an organization requires specialized security, the creation of multiple domains might be required.

Determining Performance Requirements

The performance requirements define the business and employee expectations for the network. The information gathered during this assessment assists you in creating a design that meets the expectations that have been expressed. Your goal should be to understand the performance requirements a business has and ensure that they are incorporated into the Active Directory design plans. Assess the performance requirements of both those in management positions as well as the end users.

For example, one of the expectations that the XYZ Corporation has expressed is that it does not want the WAN link between Paris and N.Y. to become saturated with replication traffic (refer to Figure 3.5). Being aware of this performance expectation, the design team could create two separate Active Directory sites between the two locations to enable the XYZ Corporation to schedule when replication traffic can occur over the WAN connection.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020