Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 36 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
36
Dung lượng
1,01 MB
Nội dung
Contents
Overview 1
Identifying Domain Roles 2
Identifying Active Directory
Considerations 7
Identifying Application and Service
Requirements 15
Managing Servers Running
Datacenter Server 21
Identifying Tools for Interoperating
with Other Operating Systems 23
Configuration Check Tool 25
Demonstration: Configuration Check Tool 28
Winsock Direct for SANs 29
Review 31
Module 3:Integrating
Windows 2000
Datacenter Server
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.
2001 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, BackOffice, FrontPage, Outlook, PowerPoint, Visual Studio,
Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of
Microsoft Corporation in the U.S.A. and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective
owners.
Program Manager: Don Thompson
Product Manager: Greg Bulette
Instructional Designers: April Andrien, Kelley Umphrey
Subject Matter Experts: Conrad Cahill (Entirenet), Jack Creasey
Classroom Automation: Lorrin Smith-Bates
Graphic Designer: Andrea Heuston (Artitudes Layout & Design)
Editing Manager: Lynette Skinner
Editor: Lori Kane
Copy Editor: Gwen Bloomsburg (S&T Consulting)
Production Manager: Miracle Davis
Build Manager: Julie Challenger
Print Production: Lori Walker (S & T Consulting)
CD Production: Eric Wagoner
Test Manager: Eric R. Myers
Test Lead: Robertson Lee (Volt)
Creative Director: David Mahlmann
Media Program Manager: Scott Daniels
Media Producer: Dean Connolly
Lead Production Artist: Scott Serna
Localization Manager: Rick Terek
Operations Coordinator: John Williams
Manufacturing Support: Laura King; Kathy Hershey
Lead Product Manager, Release Management: Bo Galford
Lead Technology Manager: Sid Benavente
Lead Product Manager: Ken Rosen
Group Manager, Courseware Infrastructure: David Bramble
Group Product Manager, Content Development: Julie Truax
Director, Training & Certification Courseware Development: Dean Murray
General Manager: Robert Stewart
Module3:IntegratingWindows2000DatacenterServer iii
Instructor Notes
This module provides students with the knowledge to identify issues and
situations that may occur when integrating a data center and Microsoft
®
Windows
® 2000DatacenterServer into a computing environment. For students
to be successful, they must be aware of the special considerations and
requirements that apply to planning, server installation, and hardware
verification.
After completing this module, students will be able to configure and manage
Windows 2000Datacenter Server, including:
Identifying planning considerations for making DatacenterServer the
domain controller.
Identifying Microsoft Active Directory
™
directory service considerations
and requirements prior to installation of Datacenter Server.
Identifying application and service considerations and requirements prior to
installation of Datacenter Server.
Identifying management services considerations and requirements prior to
installation of Datacenter Server.
Identifying tools for interoperating with other operating systems.
Running the Windows2000DatacenterServer Configuration Check tool.
Identifying the benefits of Winsock Direct for system area networks
(SANs).
Materials and Preparation
This section provides the materials and preparation tasks that you need to teach
this module.
Required Materials
To teach this module, you need the following materials:
Microsoft PowerPoint® file 2089a_03.ppt
Module 3, “Integrating Windows2000Datacenter Server”
Preparation Tasks
To prepare for this module, you should:
Read all of the materials for this module.
Complete the demonstration.
Presentation:
60 Minutes
iv Module3:IntegratingWindows2000DatacenterServer
Module Strategy
Use the following strategy to present this module:
Identifying Domain Roles
This topic discusses the roles of DatacenterServer as a domain controller or
a member server. It covers operations masters, multimaster replication of
directory data on a SAN, large global catalogs, and protecting the forest
root. In addition, there is a discussion on justifying directory services on
Datacenter Server and another discussion justifying DatacenterServer as a
member server.
Identifying Active Directory Considerations
Prior to installing Datacenter Server, students need to determine how to
integrate the data center with their Active Directory directory service
structures. This topic covers containers, groups, and Group Policy object
association.
Identifying Application and Service Requirements
Prior to installing Datacenter Server, the students need to consider how
various applications and services will interact with and depend on
Datacenter Server. This topic covers considerations and requirements for
line-of-business applications, cluster-aware applications, supported
Microsoft products, Microsoft SQL Server
™
2000, and Microsoft
Exchange 2000 Server.
Managing Servers Running DatacenterServer
Prior to installing Datacenter Server, the students need to identify how to
efficiently manage the servers within a data center environment. This topic
discusses Terminal Services and Windows Management Instrumentation.
Identifying Tools for Interoperating with Other Operating Systems
This topic covers Microsoft Windows Services for UNIX and Microsoft
Host Integration Server2000. Interoperability is an important factor when
placing DatacenterServer in existing data centers.
Configuration Check Tool
This topic introduces the Configuration Check tool. The students will learn
the major functions of the tool and how they can use it to manage data
center server.
Demonstration: Configuration Check Tool
This is a very simple demo that shows the use of the Configuration Check
tool. You might want to create additional files to compare against the
Datacenter Server.
Winsock Direct for SANs
This topic is a brief introduction to Winsock Direct for SANs. If the student
is an administrator in a SAN, they will need to identify this feature of
Windows 2000Datacenter Server, because it allows existing applications to
become transparently SAN-enabled.
Module3:IntegratingWindows2000DatacenterServer 1
Overview
Identifying Domain Roles
Identifying Active Directory Considerations
Identifying Application and Service Requirements
Managing Servers Running Datacenter Server
Identifying Tools for Interoperating with Other Operating
Systems
Configuration Check Tool
Winsock Direct for SANs
*****************************I
LLEGAL FOR NON-TRAINER USE*****************************
Before you install Microsoft
® Windows® 2000Datacenter Server, you must
decide whether to configure it as a domain controller or as a member server.
You also need to consider how to design and implement Microsoft
Active Directory
™
, the directory service for Microsoft Windows2000 Server.
Applications and services that are installed in the data center can have
dependencies or requirements that need to be evaluated if they are configured
for a four-node cluster, critical line-of-business applications, or applications
certified to run on Datacenter Server. As the data center administrator there are
several tools or management features in DatacenterServer that you can use to
efficiently manage the data center.
This module identifies issues and situations that may occur when you integrate
a data center and Windows2000DatacenterServer into your computing
environment. After completing this module, you will be able to configure and
manage Datacenter Server, including:
Identifying planning considerations for making DatacenterServer the
domain controller or member server.
Identifying Active Directory directory service considerations and
requirements prior to installation of Datacenter Server.
Identifying application and service considerations and requirements prior to
installation of Datacenter Server.
Identifying management services considerations and requirements prior to
installation of Datacenter Server.
Identifying tools for interoperating with other operating systems.
Running the Windows2000DatacenterServer Configuration Check tool.
Identifying the benefits of Winsock Direct for system area networks
(SANs).
Topic Objective
To provide an overview of
the module topics and
objectives.
Lead-in
In this module, you will learn
about the integration of
Windows 2000
Datacenter Server.
Explain the purpose of this
module.
2 Module3:IntegratingWindows2000DatacenterServer
Identifying Domain Roles
Configuring Windows2000DatacenterServer as a
Domain Controller
Configuring Windows2000DatacenterServer as a
Member Server
*****************************I
LLEGAL FOR NON-TRAINER USE*****************************
Windows 2000DatacenterServer can be either a domain controller or a
member server. Before installing Datacenter Server, you must think about its
role in the data center and identify its role in the domain. Depending on the
applications and services that will be located on Datacenter Server, you may
need to configure DatacenterServer as a domain controller.
An important planning issue is determining where to locate domain controllers
and global catalog servers for your enterprise. This is because after
Active Directory is installed and configured, the majority of Active Directory
traffic is related to Active Directory clients querying Active Directory for
information. Directory replication traffic is usually a less important
consideration, unless the organization is in a state of constant change. Placing a
domain controller at each geographical site optimizes queries but can increase
replication traffic. Nevertheless, placing a domain controller at a site that has
users in that domain is usually the best solution.
It is not recommended that DatacenterServer be installed in a workgroup (not a
member of a domain) because services such as four-node clustering require
domain accounts to function.
Topic Objective
To identify planning
considerations and
requirements for making
Datacenter Server the
domain controller.
Lead-in
Windows 2000
Datacenter Server can be
either a domain controller or
a member server.
Module3:IntegratingWindows2000DatacenterServer 3
Configuring DatacenterServer as a Domain Controller
Install Domain Controller on DatacenterServer to:
Protect the forest root
Protect operations masters
Support large global catalogs
DatacenterServer as Domain Controller Would Be
Justified for:
Operations masters and critical services
Directory-aware applications
Domain accounts for four-node clusters
*****************************I
LLEGAL FOR NON-TRAINER USE*****************************
A server running Windows2000DatacenterServer in a domain can have one of
two roles: domain controller or member server. Domain controllers contain
matching copies of the user accounts and other Active Directory data in a given
domain. Multiple domain controllers provide better support for users than just
one domain controller. Multiple domain controllers provide automatic backup
for user accounts and other Active Directory data, and they work together to
support domain controller functions. You would configure Windows2000
Datacenter Server as a domain controller to:
Protect the forest root.
Protect single operation masters.
Support very large Active Directory schemas.
Support applications that must be installed on a domain controller.
Provide high performance with large global catalogs.
Features of Datacenter Server, such as Winsock Direct and Enterprise Memory
Architecture (EMA), are designed to meet the demands of specialized domain
controllers in your computing environment. The increased reliability of
Datacenter Server makes it an ideal system to protect operations masters as well
as the forest root. The expanded EMA support of DatacenterServer can
increase performance in the largest Active Directory implementations. Winsock
Direct provides high bandwidth, low latency communication for super-fast
directory replication within SANs.
Topic Objective
To configure Windows2000
Datacenter Server as a
domain controller.
Lead-in
Servers running
Windows 2000
Datacenter Server in a
domain can have one of two
roles: domain controller or
member server.
4 Module3:IntegratingWindows2000DatacenterServer
Protecting the Forest Root
The forest root is the domain controller that you promote first. The most
important server in any Active Directory implementation is the forest root. The
forest root is the location of the root domain. It cannot be renamed or removed.
It is the location of the schema master and the domain-naming master. If the
forest root becomes unavailable, your entire Active Directory service structure
ceases to function. If the forest root is permanently unavailable, your forest is
gone and must be rebuilt from scratch. The best place to put the forest root is on
the server in your organization that is the most stable and most reliable.
Datacenter Server is the most appropriate host for the forest root in your
organization.
Protecting Operations Masters
Because DatacenterServer is the most reliable server in the forest, it is the
logical home for the schema and domain-naming masters. In the
Active Directory directory service, there are certain operations that are single
master, which means that they are not permitted to occur in different places in
the network at the same time. These operations, called operations masters, must
be protected and controlled.
Large Global Catalogs
Any Active Directory implementation loads as much of the global catalog into
main memory as possible. This speeds any Active Directory directory service
operations but, depending on available resources, can impede local services on
the domain controller. With up to 64 gigabytes (GB) of memory by using EMA,
Datacenter Server supports fast and large Active Directory structures. Locating
directory services is a decision you may need to make. There are some
considerations that will help you make the best choice for your organization’s
needs.
If the domain tree is large, you should not place a global catalog server at each
site because this can create large amount of replication traffic. You should place
global catalog servers only at large regional sites. Remember that replication of
modifications made to your Active Directory might take some time to
propagate throughout your enterprise. For example, if you create a new user
account object, it might be a few minutes before the user can actually log on to
the network using the account.
Justification to Locate Directory Services on
Datacenter Server
In some cases it is best to have directory services hosted on your
Datacenter Server. It is recommended that you put directory services on
Datacenter Server computers if you must:
Protect operations masters or other critical services.
Provide directory services to a directory-aware application.
Support a server cluster or a number of server clusters.
Module3:IntegratingWindows2000DatacenterServer 5
A domain controller is necessary to a Windows-based environment to service
server clusters. A Windows Clustering server cluster requires access to a
domain controller or it fails. So, if you have clustered critical services on
Datacenter Server, you must have a domain controller accessible by the cluster
to protect cluster services. If the cluster service account cannot authenticate to a
domain controller, the service fails and the server cluster fails with it.
6 Module3:IntegratingWindows2000DatacenterServer
Configuring DatacenterServer as a Member Server
Make DatacenterServer a Member Server When:
You need the highest performance
You have reliable directory services local to your data
center
*****************************I
LLEGAL FOR NON-TRAINER USE*****************************
A member server is a computer that is running Windows2000
Datacenter Server and is a member of a domain and not a domain controller.
Member servers belong to a domain but do not contain a copy of the
Active Directory data. Because it is not a domain controller, a member server
does not handle the account logon process, does not participate in
Active Directory replication, and does not store domain security policy
information.
If you are seeking the highest performance from the DatacenterServer
platform, do not host Active Directory services on a member server. If you have
reliable directory services local to your data center, those services may prove
sufficient to your needs.
Topic Objective
To configure Windows2000
Datacenter Server as a
member server.
Lead-in
A member server is a
computer that is running
Windows 2000
Datacenter Server and is a
member server of a domain
and not a domain controller.
[...]... Host Integration Server do not require more than eight processors Windows Services for UNIX 2.0 Module 3:IntegratingWindows2000DatacenterServer 19 Exchange 2000Server Topic Objective To identify Exchange 2000Server considerations prior to installing DatacenterServer Lead-in Windows2000DatacenterServer supports Microsoft Exchange 2000Server with the release of Exchange 2000Server Service... on its own logical drive 20 Module3:IntegratingWindows2000Datacenter Server SQL Server 2000 Topic Objective To identify SQL Server2000 considerations prior to installing DatacenterServer Supports the AWE API for Addressing 64GB of Main Memory Lead-in Supports Four-Node Clustering SQL Server2000 was built to achieve maximum performance on Windows2000DatacenterServer Supports 32-Way SMP For... Windows2000DatacenterServer is SQL Server2000 Microsoft is working to certify the following Microsoft products on Datacenter Server: Application Center 2000 Commerce Server 4.0 Office 2000, including Outlook® Site Server 3.0 Commerce Edition Systems Management Server 2.0 Microsoft will provide support for the following Microsoft applications and services on Windows2000Datacenter Server: SQL Server. .. performance, SQL Server2000 should run on dedicated, clustered servers By running a partitioned SQL database across all four nodes of a DatacenterServer cluster, you can achieve greater performance levels than those previously known on the Windows platform Module 3:IntegratingWindows2000DatacenterServer 21 Managing Servers Running DatacenterServer Topic Objective Windows Management Windows Management... service redundancy 10 Module3:IntegratingWindows2000DatacenterServer Active Directory Directory Service Containers Topic Objective To describe how to plan the DNS services in a data center DatacenterServer in an DatacenterServer in an Domain Organizational Unit Domain Organizational Unit OU DatacenterDatacenterServer in Server in Site 1 Site 1 a domain a domain Lead-in Windows2000 Active Directory... Module 3:IntegratingWindows2000DatacenterServer 23 Identifying Tools for Interoperating with Other Operating Systems Topic Objective Windows2000Windows2000DatacenterServerDatacenterServer To describe interoperability tools for existing data center environments Lead-in Because many organizations already support current data centers, interoperability is an important factor when placing Windows. .. 2000Server2000Windows Services for Windows Services for UNIX 2.0 UNIX 2.0 Applications must be certified to run Windows2000DatacenterServerServer cluster Server cluster nodes supported nodes supported SNA Server 4.0 SP3 SNA Server 4.0 SP3 Lead-in Microsoft Microsoft product or service product or service Cluster-unaware Cluster-unaware 8 8 32 32 4 4 64 64 Server 7.0 SP2 Server 7.0 SP2 Exchange Server. .. management of Windows Services for UNIX components 24 Module3:IntegratingWindows2000DatacenterServer Host Integration Server2000 Host Integration Server 2000, an update to Microsoft SNA Server 4.0, is a comprehensive integration platform that provides a way to interoperate at the Internet, intranet, and client /server levels while preserving investments in existing systems Host Integration Server includes... command prompt, type cfgcmp /s filename Module 3:IntegratingWindows2000DatacenterServer 29 Winsock Direct for SANs Topic Objective User Requests from unmodified user level applications that use Winsock and TCP/IP To describe Winsock Direct for SANs, a feature of Windows2000DatacenterServer Winsock switch Winsock Direct is a feature of the Windows2000DatacenterServer network architecture SAN Winsock.. .Module 3:IntegratingWindows2000DatacenterServer 7 Identifying Active Directory Considerations Topic Objective To describe the considerations for integrating Active Directory within a DatacenterServer environment Lead-in Typical multi-application configurations on Windows2000DatacenterServer can include directory-aware applications Planning . this
module.
2 Module 3: Integrating Windows 2000 Datacenter Server
Identifying Domain Roles
Configuring Windows 2000 Datacenter Server. the server cluster fails with it.
6 Module 3: Integrating Windows 2000 Datacenter Server
Configuring Datacenter Server as a Member Server
Make Datacenter