Tài liệu Module 13: Planning a Metadirectory Implementation doc

Contents
Overview 1
Overview of the Metadirectory Planning
Process 2
Assessing the Existing Information
Infrastructure 5
Identifying the Functional Goals of the
Metadirectory 9
Determining the Information Requirements 10
Determining Management and Security
Requirements 14
Lab A: Determining the Functional
Requirements for a Metadirectory
Implementation 16
Review 17

Module 13: Planning a
Metadirectory
Implementation
BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Information in this document is subject to change without notice. The names of companies,
products, people, characters, and/or data mentioned herein are fictitious and are in no way intended
to represent any real individual, company, product, or event, unless otherwise noted. Complying
with all applicable copyright laws is the responsibility of the user. No part of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any

purpose, without the express written permission of Microsoft Corporation. If, however, your only
means of access is electronic, permission to print one copy is hereby granted.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.

 2000 Microsoft Corporation. All rights reserved.

Microsoft, BackOffice, MS-DOS, Windows, Windows NT, <plus other appropriate product
names or titles. The publications specialist replaces this example list with the list of trademarks
provided by the copy editor. Microsoft is listed first, followed by all other Microsoft trademarks
in alphabetical order. > are either registered trademarks or trademarks of Microsoft Corporation
in the U.S.A. and/or other countries.

<The publications specialist inserts mention of specific, contractually obligated to, third-party
trademarks, provided by the copy editor>

Other product and company names mentioned herein may be the trademarks of their respective
owners.


Module 13: Planning a Metadirectory Implementation iii

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Instructor Notes
Instructor_notes.doc

Module 13: Planning a Metadirectory Implementation 1

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Overview
!
Overview of the Metadirectory Planning Process
!
Assessing the Existing Information Infrastructure
!
Identifying the Functional Goals of the Metadirectory
!
Determining the Information Requirements
!
Determining Management and Security Requirements


When planning a Microsoft Metadirectory Services (MMS) version 2.2
implementation, you must determine a set of functional objectives for the
metadirectory that will meet the information management needs of an
organization. To determine these functional objectives, you must take a current
directory inventory, develop the metadirectory content requirements, determine
the information flow behavior of the metadirectory, and determine management
and security issues. The planning process results in a functional specification
that is used to guide the design and development of the MMS implementation.
The results of the planning process include a list of directories to be integrated
in the metadirectory, a list of the type of entries and the attribute for information
for each, and a specification of which connected directory is authoritative for
each attribute.

At the end of this module, you will be able to:
!
Describe the metadirectory planning process.
!
Assess the organization’s current information management systems and
gather the information necessary to determine metadirectory requirements.
!
Identify the functional goals that a metadirectory will provide that meet the
identity management needs of the organization.
!
Determine the metadirectory information requirements.
!
Determine the metadirectory management and security requirements.

Topic Objective
To provide an overview of
the module topics and
objectives.
Lead-in
In this module, we will
discuss how to plan an
MMS implementation that
meets an organization’s
functional requirements for a
metadirectory.
Emphasize that throughout
this module, the deliverables
that are developed during
the planning process
provide the input into the

design and development
process, which is discussed
in module 14, “Designing
and Developing a
Metadirectory,” in course
2062A, Implementing
Microsoft Metadirectory
Services 2.2.
2 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

#
##
#

Overview of the Metadirectory Planning Process
Assemble
Planning and
Design Teams
Assemble
Planning and
Design Teams
Assess Current
Directories and
Applications
Assess Current
Directories and
Applications
Determine

Functional Goals
Determine
Functional Goals
Determine
Information
Requirements
Determine
Information
Requirements
Determine
Management and
Security Requirements
Determine
Management and
Security Requirements
The Functional Requirements
of the Metadirectory


The goal of the metadirectory planning process is to define a set of functional
requirements. These functional requirements will then be used to guide the
design and development of an MMS implementation that meets the identity
information needs of an organization. The metadirectory planning process
consists of the following steps:
!
Assemble the metadirectory planning and implementation teams. Because
implementing the metadirectory will affect the entire organization, the key
stakeholders must be identified and organized into the following teams:
• Planning team. This team consists of staff from the information
technology (IT) support groups, the business groups that own the

identity information contained in the directories and the applications that
use this information, the human resource group, and the person(s) who
will be leading the design and development of MMS.
The planning team works towards joining the information they own into
a common metadirectory and defining the rules for how information
flows between the metadirectory and the connected directories. The
primary goal of this team is to develop a basic vision for a directory-
enabled computing environment and to determine the functional
objectives for the metadirectory.
• Implementation team. This team includes the developers, administrators,
and support personnel who will design, implement, and manage MMS
according to the goals outlined in the functional specifications.
!
Assess the current information flow for the organization. The planning team
assesses the existing flow of identity information through the organization
and identifies the current business processes and rules that determine this
information flow. Assessing the current information flow also includes
gathering information about the existing directories and the applications that
use those directories.
Topic Objective
To describe the
metadirectory planning
process.
Lead-in

Module 13: Planning a Metadirectory Implementation 3

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

!

Determine the functional goals of the metadirectory. This step results in a
list of specific and achievable goals that describe how identify information
should flows throughout the organization, what information should be
integrated, and how the organization will then use this integrated
information. These functional goals will guide the development of the
metadirectory’s information, management, and security requirements.
!
Determine the metadirectory information requirements. After defining the
objectives of the metadirectory and taking inventory of the existing
directories, you need to determine a specific set of information flow
requirements that outlines the behavior of the metadirectory. These
requirements include identifying what information the metadirectory will
contain, what directories this information originates from, and the basic
model for how attributes flow among the connected directories.
!
Determine the metadirectory management and security requirements. The
final step in the planning process is to define who will manage the
connected directories and who will manage the MMS product itself, as well
as managing the MMS Server service. Additionally, you will have to specify
the security and access requirements for the group that will manage and
maintain MMS.

4 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

The Metadirectory Functional Requirements
A List of Directories to Be Integrated in the Metadirectory
A List of Directories to Be Integrated in the Metadirectory
The Naming Convention for Metadirectory Entries

The Naming Convention for Metadirectory Entries
The Metadirectory Entry Types
The Metadirectory Entry Types
The Attributes Stored in Each Metadirectory Entry
The Attributes Stored in Each Metadirectory Entry
The Directory From Where Each Attribute Initially Originates
The Directory From Where Each Attribute Initially Originates
The Directory That Will Be Authoritative for Each Attribute
The Directory That Will Be Authoritative for Each Attribute
The Metadirectory Management Method
The Metadirectory Management Method
The Metadirectory Security Policy
The Metadirectory Security Policy


The result of the planning process is a specification that outlines the functional
requirements for the metadirectory. These requirements describe the content
and behavior for the proposed metadirectory, and will guide the MMS design
and development process, during which the implementation team will develop
join and attribute flow strategies, and develop and test the management agents.
The following list identifies the information that makes up the functional
requirements:
!
A list of directories to be integrated in the metadirectory.
!
The naming convention for metadirectory entries.
!
The metadirectory entry types.
!
The attributes stored in each metadirectory entry.

!
The directory from where each attribute initially originates.
!
The directory that will be authoritative for each attribute.
!
The metadirectory management method.
!
The metadirectory security policy.

Topic Objective
To identify the items in the
list of functional
requirements.
Lead-in
The result of the planning
process is a functional
specification that outlines
the functional requirements
for the metadirectory.
Module 13: Planning a Metadirectory Implementation 5

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

#
##
#

Assessing the Existing Information Infrastructure
!
Assess the Current Directories

!
Assess Directory-Enabled Applications
!
Document Current Business Processes and Rules
$
Determine business rules that define the current
environment
$
Integrating directories in the metadirectory may require
changes to existing business processes


MMS joins together information from various directories in an organization.
Therefore, it is important to develop a good understanding of the current
directory environment, which includes taking an inventory of the existing
directories and assessing the applications that use those directories.
Assessing Current Directories
You will need to systematically assess each current directory that will be
integrated with the metadirectory. During this inventory, you will need to
document the kind of information each directory currently contains, how the
information is organized, and whether identical information is contained in
other directories.
Assessing Current Directory Applications
You will need to take inventory of the current applications that will use the
metadirectory, as well as determine the need for additional applications in the
future.
Documenting Current Business Processes
Directory systems and the applications that use them usually exist in the larger
scope of a set of business processes. These business processes often determine
what information is contained in each directory and how this information is

collected and used. Because implementing a metadirectory may require
modifying business processes, you need to document the organization’s current
business process and rules.
Topic Objective
To describe why it is
necessary to gather
information about the
existing directory
environment to determine
metadirectory requirements.
Lead-in
The first step in the planning
process is to assess the
current directory
environments. You will
analyze the current
environment within the
scope of how the
metadirectory can provide
potential solutions to the
organization’s information
flow requirements.
6 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

For example, you could document the processes that occur when a person is
hired. What are the processes for getting the new employee a telephone number,
a mailbox, and a user account? What directory systems and application are
utilized during this process?

When determining the functional goals for the metadirectory, an organization
may also need to consider ways to improve how they manage identify
information. Improving identity information management may require
modifying current business processes.
Module 13: Planning a Metadirectory Implementation 7

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Collecting Directory Information
Identify Directory, Function, and Protocols Used to Access It
Identify Directory, Function, and Protocols Used to Access It
Identify Entry Types and Structural Containers
Identify Entry Types and Structural Containers
Identify the Attributes for Each Entry Type
Identify the Attributes for Each Entry Type
Identify Whether Entry Types Contain Attributes That Are Unique
Identify Whether Entry Types Contain Attributes That Are Unique
Identify the Authoritative Source for Duplicate Data
Identify the Authoritative Source for Duplicate Data
Identify the Directory Topology and Whether It is Distributed
Identify the Directory Topology and Whether It is Distributed
Identify How Clean the Data Is and How Often It is Updated
Identify How Clean the Data Is and How Often It is Updated
Determine How Much It Costs to Maintain the Directory
Determine How Much It Costs to Maintain the Directory


The following is a list of guidelines that need to be followed to systematically
collect information about each directory that is a candidate for integration with
the metadirectory:

!
Identify the name of the directory, the type of directory in terms of its
function in the organization, and the protocols that are used to access the
directory. Additionally, identify the person(s) or department who owns and
manages the directory.
!
Identify what type of entries (such as employee records, user accounts, and
lists) the directory contains, and determine how these entries are used.
Additionally, identify how the entries are organized and identify the
structural containers (such as organizational units) that are used to organize
the entries.Identify the attributes for each entry type. Additionally,
document whether other directories may also include duplicate attributes.
!
Determine whether entries listed in multiple existing directories contain
identifying information that is likely to be unique throughout the
organization. For example, unique information can include payroll numbers
or employee numbers.
!
Identify the authoritative source for data that is duplicated in multiple
directories.
!
Identify the topology of the directory and whether it is distributed across
multiple servers. If the directory is distributed, identify the location of the
master node that contains a full copy of all the information in the directory.
!
Identify how clean the data is in the directory. Data is considered clean
when entries are unique across multiple directories throughout the
organization. For example, data is considered when there is no uncertainty
that the employee Suzan Fine in the e-mail directory is the same Suzan Fine
who is in the human resources directory.

Topic Objective
To describe the type of
information that needs to be
collected about the current
directory environment.
Lead-in

For each guideline, ask the
students to speculate on
how the collected
information will be used
during the design and
development phase.
8 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

!
Determine, if possible, the total cost of ownership to maintain and
administer the directory. When determining the functional goals of the
metadirectory, you should have an idea of how much it costs to maintain all
the existing directories, because the cost of maintaining existing directories
can factor into the metadirectory design.

Module 13: Planning a Metadirectory Implementation 9

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Identifying the Functional Goals of the Metadirectory
!

Identify the Following:
$
Which CDs to integrate in the metadirectory
$
High level information flow based on business processes
!
Identify how to improve information flow
$
Identify what currently does and does not work
$
Prioritize changes/enhancements
$
Business processes and rules may have to change
$
Possible metadirectory solutions


After accessing the current directories and the business processes that drive how
information flows through the organization, the next step in the planning
process is to identify the functional goals of the metadirectory. Begin this
process by thinking about how the organization wants to use the metadirectory
to integrate identity information. The result of specifying the functional goals is
a set of high level, but specific goals for integrating directories and managing
information flow throughout the organization.
Use the following guidelines to help you develop the functional goals for the
metadirectory implementation:
!
Identify what currently does and does not work in the existing environment.
After assessing this, determine whether or not there is a better method for
managing identity information.

!
Prioritize the changes and enhancements that the metadirectory will address.
Identify the specific, achievable goals for integrating directories and then
prioritize those goals by what can be achieved immediately and what may
have to be implemented over time.
!
Consider modifying business processes and rules, if necessary, to achieve
the functional goals of the metadirectory.
!
Identity possible metadirectory scenarios, such as hire/fire solutions and
interforest synchronization, which can meet the organization’s information
flow goals.

Topic Objective
To describe the planning
step of identifying the
functional goals for the
metadirectory.
Lead-in

10 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

#
##
#

Determining the Information Requirements
!

Information Requirements from the Planning Phase
Guide the Design and Development of the Metadirectory
!
Metadirectory Information Requirements Include:
$
Naming conventions
$
Metadirectory entries types and attributes
$
Information flow


After you gather information about the existing environment and define the
functional goals of the metadirectory, the next step in the planning process is to
create a preliminary set of information requirements that satisfy each functional
goal. These requirements define the basic content and behavioral requirements
for the information that will go into the metadirectory. More importantly, these
requirements guide the design and development phase where the
implementation team will design join and attribute flow strategies and then
configure the management agents in a way that implement the requirements
identified during the planning phase.
The information requirements that define the basic content and behavior of the
metadirectory need to address the following issues:
!
The naming convention used for metadirectory entries.
!
The metadirectory entry types and attributes.
!
The basic data model for how attributes flow between connected directories.

Topic Objective
To introduce the information
requirements to be
determined that satisfy the
functional goals of the
metadirectory.
Lead-in

Module 13: Planning a Metadirectory Implementation 11

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Determining Naming Requirements
!
Determine a Naming Convention for Metadirectory
Entries
$
Examples include first name/last name or
first initial/last name
$
Adopt naming convention from the first connected
directory integrated in the metadirectory
!
Identify the Attribute(s) That Will Ensure Entries Are
Unique Within the Metadirectory
$
Use attributes with numeric or alphanumeric values
$
These attributes ensure that entries are unique across
all connected directories

All entries in the metadirectory should be named according to an enterprise-
wide naming convention and be identified by an attribute that uniquely
identifies an entry from every other entry in the metadirectory.
Naming Conventions for Metadirectory Entries
Names for person entries in the metadirectory are normally held in the Common
Name (CN) attribute. In preparation for importing entries into the
metadirectory, it is important that entry names be created according to a
consistent enterprise naming convention, such as first name/last name or first
initial/last name. Because you will initially create metadirectory entries by
importing the CN attribute from the first connected directory integrated in the
metadirectory (called the prime directory), consider adopting this directory’s
naming convention for the metadirectory.
Unique Attributes for Metadirectory Entries
All entries in the metadirectory require a unique attribute to distinguish
themselves from other metadirectory entries. You will need to identify the
attribute to use when joining entries in the connected directory to the entry in
the metadirectory.
If your organization has a large base of users, common names or logon names
made up of initials or parts of the first/last names are not good unique
identifiers. While these types of identifies may be unique within the context of a
single connected directory, they may not be unique in the context of the
metadirectory.
An attribute that is effective in defining uniqueness among entries is usually a
numeric or alphanumeric (such as an employee number or payroll number)
attribute that is unique across all connected directories. It is strongly
recommended that you make use of unique attributes if they already exist in
your organization. If such an attribute does not exist, consider adding an
attribute to entries in all connected directories once you have joined them in the

metadirectory.
Topic Objective
To explain that the naming
requirements must be
determined for the
metadirectory.
Lead-in

12 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Determining Metadirectory Entries and Attributes
!
To Identify the Content of the Metadirectory:
$
Determine the type of entries that will reside in the
metadirectory
$
Determine which directory will initially populate the
metadirectory for each entry type
$
Determine the attributes for each entry type
$
Identify the directories that will be authoritative for each
attribute


When setting the functional goals for the metadirectory, you identified which
directories will be integrated in the metadirectory. Now you must identify what

content from each of those directories will be contained in the metadirectory.
This directory content specifies the types of entries in the metadirectory and the
attribute information that each entry type holds.
To identify the content of the metadirectory:
!
Determine the metadirectory entry types. In addition to metadirectory
entries that represent people, you may also want to store information about
departments, lists, network resources, and network applications or other data
such as geographic, organizational, and system data.
!
Determine the connected directory that you will use to initially populate the
metadirectory with each of the entry types that you have identified. The
directory you will use depends on how clean and accurate the data is for
each specific entry type. You will use this information when you design the
join strategy.
!
Determine the attributes that each entry type will hold. Also, determine
whether users can update any specific attribute. You will use this
information when you design the attribute flow strategy.
!
Identify the directory that is authoritative for each attribute. This
information is required to help you determine the flow of information
through the organization. You will use this information when you design the
attribute flow strategy.


When identifying what types of entries will reside in the metadirectory,
you may also need to determine whether to allow new metadirectory entries to
created manually in the metadirectory by using MMS Compass.

Topic Objective
To identify what needs to be
determined to define the
metadirectory content.
Lead-in

Note
Module 13: Planning a Metadirectory Implementation 13

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Determining Information Flow
!
To Define the Flow of Information Between the
Metadirectory and the Connected Directories:
$
Determine the information stored in the metadirectory
$
Determine the information reflected in the metadirectory
$
Determine the information that should be created by the
metadirectory


After you determine what information will be stored in the metadirectory, and
the authoritative sources for that information, the next step in the planning
process is to determine the behavior of the metadirectory. Metadirectory
behavior defines, at a high level, how and what information flows between the
metadirectory and the connected directories. In the design phase of the
metadirectory implementation, you will use these information flow

requirements to configure management agent modes and to design attribute
flow.
To define information flow, you need to determine the following:
!
The information that is stored in the metadirectory. This information is
determined by the metadirectory entries and attributes that you have
previously identified.
!
The information that is reflected through the metadirectory. For each
attribute stored in the metadirectory, you must determine the connected
directory that will reflect that attribute. You will use this information to
design the attribute flow strategy.
!
The information that is created by using the metadirectory. This information
will guide how you design an attribute flow strategy that ensures that the
appropriate connected directory will be authoritative for attribute
information.

Topic Objective
To identify components of
an information flow strategy.
Lead-in

14 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Determining Management and Security Requirements
!
Determine the MMS Management Method:

$
Use centralized management for a single site or for a single support
organization
$
Use distributed management for a widely distributed enterprise with
multiple support organizations
!
Determine the MMS Security Policy:
$
Internal privacy boundaries determine what attribute values are
accessible to owners, administrators, and users
$
Authentication requirements determine what access anonymous and
authenticated users have to the metadirectory data
$
Internal access control determines access categories for internal
users


In this phase of the planning process, you must determine who will manage the
metadirectory, and whether this management will occur in the connected
directories or in the metadirectory itself. Related to the decision on managing
the directory data, is to determine the security applied to the data. One option is
to continue to manage and secure connected directories using your existing
procedures.
Determining MMS Management
To determine how you want to manage MMS, determine which management
method best applies to your organization. MMS can be managed in two ways:
!
Centralized management. With this method, all MMS servers are managed

by your central support organization. Use centralized management when the
organization has a single site, or has multiple sites but a single support
organization.
!
Distributed management. With this method, multiple MMS servers are
managed by separate support organizations. Use distributed management if
your enterprise is widely distributed and has multiple support organizations.
Topic Objective
To define management and
security components of the
functional requirements.
Lead-in

Module 13: Planning a Metadirectory Implementation 15

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Determining MMS Security
The first step to determine metadirectory security is to understand the MMS
security framework. Basic MMS security allows partial read access to
everyone, and full read and write access to the authenticated owner of
information. The owner can be the logged-in user administering his or her own
directory data, or the administrator of a particular administrative area of the
directory.
To define your metadirectory security policy, consider the following security
guidelines:
!
Internal privacy boundaries. Determine what information must remain
private to the employee, and what is accessible to the rest of the group,
department, or enterprise.

!
Authentication requirements. Determine what information will be accessible
to anonymous users or users of weak authentication, and what information
requires strong authentication.
!
Internal access control. Determine what access to the directory is required
for internal users, and for administrators. Decide whether or not users will
be able to access their own data, and whether you will support anonymous
access across the Internet.
Early in the design process, you might find that the basic MMS security policy
is adequate for the needs of the organization. Later, you can easily modify your
security policy depending on the nature of the attributes you store in the
directory.

16 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Lab A: Determining the Functional Requirements for a
Metadirectory Implementation


Lab.doc
Topic Objective
To introduce the lab.
Lead-in
In this lab, you will plan an
metadirectory
implementation and develop
the functional requirements

based on a given scenario.
Explain the lab objectives.
Module 13: Planning a Metadirectory Implementation 17

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

Review
!
Overview of the Metadirectory Planning Process
!
Assessing the Existing Information Infrastructure
!
Identifying the Functional Goals of the Metadirectory
!
Determining the Information Requirements
!
Determining Management and Security Requirements


1. What is the primary deliverable that results from the metadirectory planning
process? How is this deliverable used?
The result of the planning process is the functional requirements for the
metadirectory. These requirements describe the content and behavior
for the proposed metadirectory, and will guide the MMS design and
development process,


2. When assessing the current information infrastructure for an organization,
what three areas will you investigate?
The current directories in the organization, the applications that use

those directories, and the business processes and rules that define how
identity information flows through the organization.


3. What is the purpose of identifying functional goals early on in the
metadirectory planning process?
By thinking about how the organization wants to use the metadirectory
to integrate identity information, high level functional goals can guide
how you approach the solution of integrating directories and managing
information flow.

Topic Objective
To reinforce module
objectives by reviewing key
points.
Lead-in
The review questions cover
some of the key concepts
taught in the module.
18 Module 13: Planning a Metadirectory Implementation

BETA MATERIALS FOR MICROSOFT CERTIFIED TRAINER PREPARATION PURPOSES ONLY

4. What four things do you have to determine to identify the content
requirements for a proposed metadirectory?
The type of entries that will reside in the metadirectory, which
directory will initially populate the metadirectory for each entry type,
the attributes for each entry type, and the directories that will be
authoritative for each attribute

5. What two factors influence the management requirements for MMS servers?
Whether the organization has a single site or multiple sites, and
whether the organization has a single support organization or multiple
support organizations.