Transcript 1: Overview of Planning a Windows Server 2003 Network

70-293: MCSE Guide to Planning a
Microsoft Windows Server 2003 Network,
Enhanced
Chapter 1:
Overview of Planning A
Windows Server 2003
Network
Objectives
• Understand the process of installing Windows Server
2003
• Understand which platforms support upgrades to
Windows Server 2003
• Describe components in the Windows Server 2003
networking architecture
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
2
Objectives (continued)
• List networking services available in Windows Server
2003
• Describe various editions of Windows Server 2003
• Plan a Windows Server 2003 network infrastructure
project
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
3
Installing Windows Server 2003
• Windows Server 2003 is easy to install
• Default installation settings are different from
Windows 2000
• Windows Server 2003 gives the Everyone group no
permissions to the file system and gives the Users
group Read access
• Windows Server 2003 does not install IIS by default
• The most common way to install Windows Server
2003 is by booting from CD-ROM
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
4
Activity 1-1: Installing Windows
Server 2003
• In this activity, you install Windows Server 2003 and
join the domain as a member server
• Follow steps 1-27 to complete the exercise
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
5
Upgrading to Windows Server
2003 from Other Platforms
• Not all Windows operating systems can be upgraded
to Windows Server 2003
• Supported platforms for upgrades are:
• Windows NT 4.0 Server with Service Pack
• Windows NT 4.0 Terminal Server Edition with Service
Pack 5
• Windows 2000 Server
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
6
Introducing Windows Server
2003 Network Architecture
• A network operating system (NOS) is an operating
system that is designed for network servers
• There are four major software components in
networking:
•
•
•
•
Client
Service
Protocol
Adapter
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
7
Introducing Windows Server
2003 Network Architecture
(continued)
• The operating system uses the network driver to
communicate with the network card
• Windows Server 2003 has two interfaces to create
clients, services, protocols, and adapter software:
• NDIS
• TDI
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
8
Introducing Windows Server
2003 Network Architecture
(continued)
• NDIS - Network Driver Interface Specification is a
programming interface that resides between protocols
and the adapter software
• TDI - Transport Driver Interface is a programming
interface that resides between clients and protocols as
well as between services and protocols
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
9
Windows Server 2003
Networking Architecture
(continued)
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
10
NDIS
• NDIS speeds the development of device drivers and
enhances networking capabilities
• NDIS is an intermediary for all communication
between the protocol and the network card driver
• When a protocol is configured to use an adapter, it is
referred to as a binding
• Bindings between protocols and adapters are controlled by
NDIS
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
11
TDI
• The TDI layer provides clients and services with
access to network resources
• Applications talk to the TDI layer and the TDI layer
passes on the requests to the protocols
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
12
Activity 1-2: Researching
Networking Architecture
• Use the glossary in the Support section to read the
different descriptions about NDIS and TDI layer
• Follow steps 1-10 to understand the difference
between the TDI layer and NDIS
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
13
Network Protocols
• Windows Server 2003 support four major protocols
•
•
•
•
(IPv4)
(IPv6)
(IPX/SPX)
AppleTalk
• IPv4 is the most common networking protocol
• IPv6 is a newer version of TCP/IP and offers
enhancements such as expansion of the address space
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
14
Activity 1-3: Viewing Available
Protocols
• In this activity, you view the list of available
protocols in the properties of a network connection
• Follow steps 1-9 to verify the protocols available for
installation
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
15
Understanding Network Services
• Windows Server 2003 can perform in a wide variety
of roles from file server to application server
• This level of flexibility is due to the wide variety of
services that run on Windows Server 2003
• Each service allows the server to perform a different
role
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
16
Default Services
• Windows Server 2003 default network services
include
•
•
•
•
•
•
•
Automatic Updates
Background Intelligent Transfer Service
Computer Browser
DHCP Client
Distributed File System
Distributed Transaction Coordinator
DNS Client
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
17
Default Services (continued)
•
•
•
•
•
•
•
•
•
•
•
•
Error Reporting Service
Insect Services
Network Connections
Network Location Awareness
Remote Procedure Call
Remote Registry
Server
TCP/IP NetBIOS Helper
Terminal Services
Windows Time
Wireless Configuration
Workstation
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
18
Services Added to a Domain
Controller
• A domain controller holds a copy of Active Directory
information
• This information is used to authenticate users and
configure network resources.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
19
Optional Network Services and
Features
• Windows Server 2003 has a wide variety of network
services that are optional
• Network services allow Windows Server 2003 to
perform many tasks
• These services can be combined onto a single server
if required
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
20
Activity 1-4: Viewing Installed
Services
• In this exercise you identify the installed network
services and verify that ICF - Internet Connection
Firewall, is not running
• Follow steps 1-6 to verify that ICF is not running
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
21
Activity 1-5: Viewing Available
Services
• In this activity, you go through the process of
installing new Windows components to see which
network services are available
• Follow steps 1-8 to verify the network services that
are available for installation
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
22
Selecting the Operating System
for the Enterprise
• Four versions of Windows Server 2003
•
•
•
•
Web Edition
Standard Edition
Enterprise Edition
Datacenter Edition
• Each version is designed to meet the needs of a
certain market segment
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
23
Web Edition
• Web Edition is a lower-cost version of Windows
Server 2003, optimized to be a dedicated Web server
• Intended to counter Linux in the utility server market
• Provides the easy manageability and performance of
Windows without the complexity of Linux
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
24
Standard Edition
• Standard Edition is most likely to be used as a
departmental file and print server or application
server
• Wide variety of available services such as Remote
Installation Services (RIS) and application
deployment through Group Policy
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
25
Standard Edition (continued)
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
26
Enterprise Edition
• Enterprise Edition enables large enterprises to deliver
highly available applications and Web services
• Available in 32-bit and 64-bit editions
• Logical upgrade from Windows 2000 Advanced
Server for enterprises implementing Web services
using the Common Language Runtime (CLR)
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
27
Enterprise Edition (continued)
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
28
Datacenter Edition
• Datacenter Edition is designed for mission-critical
applications that require the highest levels of
availability and scalability
• Available in 32-bit and 64-bit editions
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
29
How Client Operating Systems Use
Windows Server 2003 Services
• Windows Server 2003 provides a variety of different
services such as:
• SMB signing and secure channel encryption and signing
are used by newer Windows clients
• The Active Directory client for Windows 9x and Windows
NT adds the capability to access Active Directory features
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
30
Performing SMB Signing
• Server Message Block (SMB) is the protocol used by
Windows Server to share files and printers
• All Windows Server 2003 domain controllers use
SMB signing as a mechanism to ensure legitimate
communication between clients and servers
• SMB signing places a digital signature on each
packet; this prevents the modification of packets in
transit
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
31
Securing Channel Encryption
and Signing
• Secure channels used for communication between
Windows clients and servers that have a trust
relationship
• Windows Server 2003 requires secure channels be
encrypted or signed to ensure that communication is
legitimate
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
32
Accessing Active Directory
Features
• Features of the Active Directory client are:
•
•
•
•
•
Site Awareness
Active Directory Service Interfaces
Distributed File System
NTLM version 2 Authentication
Active Directory Searching
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
33
Activity 1-6: Comparing Windows
2000 Server and Windows
Server 2003
• In this exercise you will browse through the Help and
Support Utility to explain the new features of
Windows Server 2003 that are most beneficial for
your organization
• Follow steps 1-7
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
34
Activity 1-7: Viewing the Current
Edition of Windows Server 2003
• In this exercise you will identify the edition of
Windows Server 2003 that is running on a specific
machine
• Follow steps 1-6 and use the “Manage your server”
option to find out which edition of Windows Server
2003 is running
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
35
Activity 1-8: Viewing the
Features of Datacenter Edition
• In this exercise, you will identify the unique features
of the Datacenter edition of Windows Server 2003
• Follow steps 1-7
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
36
Planning a Windows Server 2003
Network Infrastructure
• The success of any information technology project is
based on good planning which must involve:
•
•
•
•
•
•
Choosing the members of the team
Identifying the goals of the team
Documenting the existing situation
Defining objectives and tasks
Testing the project
Rolling out the project
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
37
The Team
• A project team has representatives from
• All areas of IT
• Affected business units
• At least one representative to liaise with upper management
• Each representative ensures interests of their own
area are taken into account
• A defined project manager needs to be responsible for
• Ensuring resources to complete the project are available
• Ensuring the project is completed on time
• Liaising with other areas of the company to ensure that the
project is supported
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
38
Goals
• Any IT project should begin with a set of business
goals
• Goals should be clearly defined and obtainable
• When setting project goals try to avoid scope creep
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
39
Documentation
• When new network projects are implemented, a set of
documentation is usually created as well
• To ensure that existing documentation is up-to-date,
you can conduct:
• Site surveys
• Interviews
• Research
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
40
Site Surveys
• A site survey is visiting a site to either create new
documentation or confirm existing documentation
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
41
Interviews
• Useful to confirm the validity of existing
documentation
• Can be done as part of a site survey
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
42
Research
• The easiest place to start researching components is
by reading the manuals that came with them
• Most vendors offer documentation on their Web sites
as well as additional support information
• Web-based discussion groups on the Internet can be
helpful as long as you select reliable sources
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
43
Objectives and Tasks
• The objectives of a project are how the goals will be
accomplished
• Tasks are how the objectives will be implemented
• The project team must decide how the objective will
be attained based on issues such as risks, cost, and
time to implement
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
44
Testing
• IT projects need to be properly tested in a lab
environment before they are rolled out to users
• The test lab should be used to simulate all
conceivable situations and factors that may affect the
project
• Average users should be involved in the testing
process since they use new software in ways that an
experienced IT person would never dream of
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
45
Roll Out
• The roll out of an IT project is the actual
implementation of new software and services
• Proper preparation for a roll out includes training for
users and the help desk
• Everyone affected by the roll out, or potentially
affected by the roll out, should be informed it is
happening
• Most successful projects are phased in rather than
being completed in one step
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
46
Activity 1-9: Researching Project
Planning
• To ensure the success of your projects, in this
exercise you perform further research into best
practices for project planning
• Follow steps 1-6
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
47
Summary
• Windows Server 2003 is easy to install but default
installations are different when compared to other
releases of Windows operating systems
• The network architecture of Windows Server 2003 is
composed of four main networking components:
clients, services, protocols, and network adapters
• NDIS binds protocols to network adapters
• The TDI layer resides between clients and protocols
or between services and protocols
• Four protocols are supported by Windows Server
2003: IPv4, IPv6, IPX/SPX, and AppleTalk
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
48
Summary (continued)
• Windows Server 2003 installs a limited number of
services by default
• When a server is promoted to be a domain controller,
several network services are added
• Many network services are available in Windows
Server 2003, including DHCP, DNS, WINS, RRAS,
IAS, NAT, ICS, ICF, Insect, and PKI
• Four editions of Windows Server 2003: Web,
Standard, Enterprise, Datacenter
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
49
Summary (continued)
• A successful Windows Server 2003 network
infrastructure plan always takes into account the
team, goals, testing, and roll out
• The team should contain representatives from all
affected departments
• Goals should define what is done in the project
• Testing should be isolated from production network
• Roll out should minimize impact on existing network
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network
50