Transcript Windows NT The Basics

Windows NT
The Basics
Bill Slater
Consultant
June 1996
(Revised September 1996)
1
Copyright 1996 By William F. Slater, III
Agenda
•
•
•
•
•
•
•
•
•
•
•
•
•
•
What is Windows NT?
Original NT Goals by Microsoft
NT Features
What is Win32?
What is Windows NT Server?
NT as a File & Print Services Server
NT as an Application Server
NT in a Workgroup Environment
NT in a Domain Environment
Why Use Windows NT?
What Do You Need to Run Windows NT? NT Server?
The Future of Windows NT
Conclusion
NT Resources
2
Copyright 1996 By William F. Slater, III
What is Windows NT?
• The world’s latest and most exciting operating system
• A modern, portable, multi-tasking, multi-threaded, robust,
secure, high performance operating system
• Over 10 million lines of code
• Possibly the most ambitious and aggressive system
software project ever attempted:
– 250+ developers
– 200 testers
– delivered first operational version within 5 years after coding
started
• The enterprise-quality operating system which Microsoft is
betting is betting against Novell Netware, UNIX, VMS, MVS,
and others
• An increasingly popular server platform for Internet servers
3
Copyright 1996 By William F. Slater, III
NT Folklore
• The NT in Windows NT stands for “New Technology”
supposedly
• Actually, WNT was intended to stand for:
V+1, M+1, S+1 = WNT
Similar to the method from
which Arthur C. Clarke’s
HAL 9000 computer name
was dervived.
H+1, A+1, L+1 = IBM
Who thought of WNT? David Cutler, the co-architect of VMS,
ex-Digital employee, Microsoft manager and father of Windows NT
4
Copyright 1996 By William F. Slater, III
Original NT Goals by Microsoft
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Security
Protects information assets
Performance
Delivers expected response
Scaleable
Scales up well
Portable
Runs on different hardware
Compatible
Runs older applications
Robust
A bad process won’t bring it down
Fault Tolerant
Resists several forms of threat
Modular design
OS parts are functional components
Layered device-driver model Leads to easier
Preemptive multitasking
Allows true multitasking
Generic microkernal
Allows portability
Object-oriented resource management
Better control and security
Centralized object access control
For better security
Processes run in separate address space
Fault tolerance
Kernal is privileged; applications nonprivileged Fault tolerance
5
Copyright 1996 By William F. Slater, III
NT Features
•
•
•
•
•
•
•
NT Architecture
NT Robustness
NT Scalability
NT Security
NT Fault Tolerance
Two Versions, Several Platforms
NT and Networking
6
Copyright 1996 By William F. Slater, III
NT Architecture
• Accomplishes the Microsoft NT design goals
–
–
–
–
–
–
–
Security
Performance
Scaleable
Portable
Compatible
Robust
Fault Tolerant
• Is closely related to other modern operating systems such
as UNIX, VMS and MACH 2
• Has two major modes: User and Privileged mode
• It has “client/server” functionality between each subsystem
and the NT Executive
7
Copyright 1996 By William F. Slater, III
NT Architecture
User Mode
DOS Win32
App. App.
Win32
App.
Security
Subsystem
Win32
Subsystem
Win16
Win16
App.App.
WOW
(Win16)
OS/2
App.
OS/2
Subsystem
Executive Services
POSIX
Subsystem
Kernel Mode
NT Executive
Hardware (Intel or MIPS or ALPHA or PowerPC)
8
Copyright 1996 By William F. Slater, III
NT Architecture
DOS Win32
App. App.
Win32
App.
Security
Subsystem
Win32
Subsystem
Win16
Win16
App.App.
WOW
(Win16)
OS/2
App.
OS/2
Subsystem
POSIX
Subsystem
Executive Services
I/O System
File Systems
Device Drivers
Object
Manager
Security
Reference
Monitor
Process
Manager
Virtual
Memory
Manager
Hardware Abstraction Layer (HAL)
Local
Procedure
Call
Facility
Kernel
Hardware (Intel or MIPS or ALPHA or PowerPC)
9
Copyright 1996 By William F. Slater, III
NT Compatibility
• NT runs most legacy applications written for DOS
and Windows 3.1 using the Win32 Subsystem
• NT runs OS/2 applications up through 1.3 using
the OS/2 Subsystem.
• NT runs some POSIX applications using the
POSIX Subsystem
10
Copyright 1996 By William F. Slater, III
NT Robustness
• Robustness is the quality of being strong enough
to withstand an adverse situation, and still remain
in operation.
• NT is robust because it isolates processes in
their own address space and controls each one,
protecting the rest of the system in the event of a
crash.
11
Copyright 1996 By William F. Slater, III
NT Scalability
• NT is scalable. It has symmetric multi-processing
capability meaning the NT will evenly balance the
load across the CPUs proving a much greater
capacity for processing.
• NT Workstation will accomodate one or two CPUs
• NT Server will accomodate one, two, or four CPUs.
NT Workstation
or
NT Server
or
or
12
Copyright 1996 By William F. Slater, III
NT Security Features
• User Logon and authentication required
• Resources are allocated and/or restricted by an
administrator, either at the user and/or group level
• Internally based on Access Control Lists, Access
Tokens, and Objects
• NTFS, the native NT File System is very secure and
provides auditing capabilities.
• FAT is not secure.
• Thorough and robust enough to be rated at “C2” by
the US Government, using their “Orange Book”
security standards
13
Copyright 1996 By William F. Slater, III
NT Fault Tolerant Features
• UPS
• RAID Levels



0
1
5
disk striping without parity (not fault tolerant)
disk mirroring (or duplexing if two controllers)
disk striping with parity
• Tape backup capability
• NTFS which has a transaction log similar to a database and
has “lazy writes”
14
Copyright 1996 By William F. Slater, III
What Is RAID 5?
Probably the best, and safest method method of online data
storage available today.
A sophisticated method (also known of striping with parity) of
fault tolerant disk storage technology which allows data to be
reconsitituted if a single drive fails. Windows NT provides RAID 5.
This is called “software RAID”.
When the RAID 5 capability is provided by a specialized controller
board, this is called “hardware RAID”. This type of RAID is good
because it frees the operating system to manage other resources.
Data
Parity
Data
Data
Data
Parity
Data
Data
Data
Parity
Data
Data
RAID 5 Disk Array with Four Disks
15
Copyright 1996 By William F. Slater, III
NT: Two Versions,
Several Hardware Platforms
• Two Versions:
– Windows NT Workstation
– Windows NT Server
• Several Platforms
–
–
–
–
–
Intel
Alpha
MIPS
PowerPC
Others
16
Copyright 1996 By William F. Slater, III
NT and Networking
•
•
NT has the ability to provide networking services built right into it
Can talk on a network to other computers using
–
–
–
•
Can interoperate with other computers:
–
–
–
–
–
–
–
•
TCP/IP
IPX
NetBEUI
DOS clients
Windows for Workgroup clients
Macintosh clients
Netware Servers and Clients
Other NT Workstation clients
Other NT Servers
UNIX workstations
Can provide access to networks by clients which are running
Windows NT Workstation, Windows for Workgroups, or NT Server,
via a Remote Access Services (RAS) connection.
17
Copyright 1996 By William F. Slater, III
What Is Win32?
• The Microsoft developer’s application programmer interface
(API), a library of approximately 1260 sub-routine calls
under Windows NT and Windows 95, which provides
shortcuts to developing applications because the calls
perform work which would require many hundreds of lines
of additional computer code.
• Usually used by C and C++ developers.
• Sometimes Visual Basic programmers use these.
• Replacement API for the Win16 API
18
Copyright 1996 By William F. Slater, III
Win32 API
• Win32 target platforms
– anything which runs Windows NT
– Windows 95 platforms (Intel only)
• Functions included in Win32 API
–
–
–
–
–
Windows manager
Graphics device interface (GDI)
Console interface
Operating system functions
Graphics device drivers
• Note that some Win32 functions only apply to the
Windows 95 architecture
19
Copyright 1996 By William F. Slater, III
What Is Windows NT Server?
• A special version of NT which has domain
administration and control built into it
• It has Windows NT Workstation built into it
• Permits use of RAID 5 fault tolerant technology
for disk storage
• Runs an optional software package called
Macintosh File and Print Services for NT which
allows file access and print services for MACs on
the same LAN
• Runs an optional software package called
Gateway Service for Netware which permits
interoperability with Netware Servers and clients
20
Copyright 1996 By William F. Slater, III
NT as a
File & Print Services Server
• NT Workstation can provide file and print services for the
following:
–
–
–
–
DOS clients
Windows for Workgroup clients
Other NT Workstation clients
UNIX workstations
• NT Server can provide file and print services for the
following:
–
–
–
–
–
–
DOS clients
Windows for Workgroup clients
Macintosh clients
Netware Servers and Clients
Other NT Workstation clients
UNIX workstations
21
Copyright 1996 By William F. Slater, III
NT as an
Application Server
• Runs the following important Microsoft server
apps:
–
–
–
–
NT SQL Server
Exchange Server
System Management Server
Internet Information Server (Web Server)
• Also runs
– ORACLE RDBMS
– SYBASE SQL Server
22
Copyright 1996 By William F. Slater, III
NT Tuning Options
• Can be optimized for file and print services or
• Client/Server application processing
• Other tuning options include
–
–
–
–
–
Adding more RAM
Increasing the Page File
Adding a Page File on each disk volume
Configuring for disk striping
Using PVIEW to set the processing priority of various
tasks
– Scheduling jobs with heavy I/O processing for afterhours.
23
Copyright 1996 By William F. Slater, III
NT in a Workgroup Environment
• NT Workstation computers may be arranged in a
Workgroup configuration.
• A Workgroup is a peer-to-peer arrangement of
computers where resources, such as disk space,
printers, etc. may be shared.
• Administratively, this arrangement is the default
when NT Workstation clients are set up.
• Each user is responsible for giving access to the
resources they control with their workstation.
24
Copyright 1996 By William F. Slater, III
NT in a Domain Environment
• As a a Primary Domain Controller (PDC), NT
Server centrally manages all user accounts,
security, and access control information.
• If a second server is added, it becomes the
Backup Domain Controller, with security and user
account information replicated automatically from
the PDC.
• The BDC provides login and management
functions if the PDC fails.
25
Copyright 1996 By William F. Slater, III
NT Domain Models
•
•
•
•
Single domain model
Master domain model
Multiple master domain model
Complete trust domain model
26
Copyright 1996 By William F. Slater, III
Single Domain Model
27
Copyright 1996 By William F. Slater, III
Single Domain Model
• Advantages:
– Easy to manage
– No trust relationships required
– Group definitions simpler
• Disadvantages
– Browsing may be slow
– Performance degrades if there are a lot of users
– Harder to administer departmental access & resources
28
Copyright 1996 By William F. Slater, III
Master Domain Model
Domain A
Domain B
29
Copyright 1996 By William F. Slater, III
Master Domain Model
• Advantages:
– Security management is centralized
– Non-master domains can organize resources logically to
reflect organizations, etc.
– Browsing activity is distributed trhough departmental
domains
• Disadvantages
– Logon activity takes place in a single domain (the
master domain)
– Performance degrades if there are a lot of users
30
Copyright 1996 By William F. Slater, III
Multiple Master Domain Model
31
Copyright 1996 By William F. Slater, III
Multiple Master Domain Model
• Advantages:
– Best scalability of any domain model
– Central management of security
– Non-master domains can organize resources logically to
reflect organizations, etc.
– Related users and groups can be grouped logically into
domains
• Disadvantages
– Users and trust relationships multiple rapidly as the
number of domains increases
– User accounts and groups are not in a single location,
making network documentation difficult
32
Copyright 1996 By William F. Slater, III
Complete Trust Model
33
Copyright 1996 By William F. Slater, III
Complete Trust Model
• Advantages:
–
–
–
–
No central administration required
Scales to any organizational size
Departments can maintain control of their resources
Users and resources are grouped logically by
departments
• Disadvantages
– Central security is lacking
– Large numbers of trust relationships are required
making administration difficult
– Departments are dependent on the management and
administration practices of other departments
34
Copyright 1996 By William F. Slater, III
Typical NT Server Admin Tasks
• The following several slides inclde the various subject
areas and job knowledge required to be a well-prepared NT
LAN Administrator:
– Planning
– Installation and Configuration
– Networking
– Managing Users, Accounts, and Policies
– Managing Disk Resources
– RAS
– Managing Printers
– System Tuning and Optimization
– Troubleshooting
35
Copyright 1996 By William F. Slater, III
Planning
• Solve specified business problems by using the
features of Microsoft Windows NT Server version
3.5.
• Implement the appropriate Windows NT Server
domain model for a given situation.
• Implement a one-way or two-way trust
relationship as appropriate.
• Choose the appropriate file system to use in a
given situation.
36
Copyright 1996 By William F. Slater, III
Planning
• Access a resource in a remote domain.
• Identify hardware requirements to meet specified
needs.
• Choose the appropriate protocol for a given
situation.
37
Copyright 1996 By William F. Slater, III
Installation and Configuration
• Install Windows NT Server 3.5 on Intel® and RISC
platforms.
• Install the appropriate file system to use for a specified
hard disk partition.
• Install and remove network adapter drivers, SCSI device
drivers, tape device drivers, printer drivers, and an
uninterruptible power supply.
• Install and configure multiple network protocols, network
adapters, and services.
• Change display, mouse, and keyboard drivers.
• Change the system and user environments.
38
Copyright 1996 By William F. Slater, III
Networking
• Install and configure the network components of Windows
NT Server.
• Set up a Microsoft Windows NT Workstation computer as a
client in a Windows NT Server domain.
• Set up a Microsoft Windows™ 3.1 computer as a client in a
Windows NT Server 3.5 domain.
• Set up a Windows for Workgroups computer as a client in a
Windows NT Server 3.5 domain.
39
Copyright 1996 By William F. Slater, III
Networking
• Set up a Macintosh® as a client in a Windows NT Server 3.5
domain.
• Configure a Windows NT Server computer for client-server
access by a NetWare® client computer.
• Move users’ permissions or rights from a NetWare
environment to a Windows NT Server 3.5 environment.
• Install gateway services for NetWare.
40
Copyright 1996 By William F. Slater, III
Networking
• Using addressing provided by DHCP, install TCP/IP as a
protocol on a Windows NT Server computer.
• Manage a Windows NT Server computer and domain from a
Windows for Workgroups client computer.
• Perform an over-the-network installation of Windows for
Workgroups and DOS client computers.
41
Copyright 1996 By William F. Slater, III
Managing Users, Accounts, and
Policies
• Administer Windows NT user accounts in your domain and
in other domains.
• Administer Windows NT group accounts in your domain
and in other domains.
• Administer Windows NT user rights in your domain and in
other domains.
• Administer Windows NT account policies in your domain
and in other domains.
• Audit changes to a user account database.
• Implement home directories and logon scripts.
42
Copyright 1996 By William F. Slater, III
Managing Disk Resources
•
•
•
•
Create and delete partitions.
Copy and move files between file systems.
Create and share resources.
Implement appropriate permissions and security on
resources.
• Establish file and directory auditing.
• Implement the appropriate fault tolerance for a given
situation.
• Set up directory replication.
43
Copyright 1996 By William F. Slater, III
Managing Printers
•
•
•
•
•
Install and configure network printers.
Implement printer pools and priorities.
Administer remote printers.
Connect to and print to a UNIX printer via TCP/IP.
Create a print gateway to a NetWare print server.
44
Copyright 1996 By William F. Slater, III
RAS
• Identify the networking technologies supported
by RAS.
• Identify the protocols supported by RAS.
• Identify the networks you can dial into with RAS.
• Identify the tasks you can perform with RAS.
• Install a RAS server.
• Install RAS clients.
• Implement RAS security.
45
Copyright 1996 By William F. Slater, III
System Tuning and Optimization
• Monitor Windows NT Server performance.
• Identify performance bottlenecks, and take the
appropriate course of action.
• Replicate a user account database over a LAN
without impacting the server’s performance.
• Optimize the virtual-memory paging file.
46
Copyright 1996 By William F. Slater, III
Troubleshooting
• Choose the appropriate course of action to take when the
boot process fails.
• Choose the appropriate course of action to take when a
print job fails.
• Choose the appropriate course of action to take when the
installation process fails.
• Modify the boot process for given parameters.
• Choose the appropriate course of action to take when RAS
fails.
• Choose the appropriate course of action to take when a
user cannot access a resource.
47
Copyright 1996 By William F. Slater, III
Troubleshooting
• Choose the appropriate course of action to take when fault
tolerance fails.
• Recover from a broken mirror set.
• Recover from a failed drive.
• Recover from the failure of a disk in a parity stripe set.
• Modify the registry for appropriate situations.
• Save a copy of the registry key to disk.
• Back up and restore the registry.
48
Copyright 1996 By William F. Slater, III
Why Use Windows NT?
• Proven technology
• Manufactured and supported by the world’s
leader in software
• Easy to use
• Robust & Fault Tolerant
• Increasly popular
49
Copyright 1996 By William F. Slater, III
What’s Required
to Use Windows NT Workstation on
Intel?
Component
Specified
Minimum
Recommended
Minimum
CPU
i486DX
33 MHz
Pentium
100 MHz
RAM
12 MB
16 MB
Hard Drive
75 MB
200 MB
Floppy
Monitor
High Density High Density
VGA
VGA
50
Copyright 1996 By William F. Slater, III
What’s Required
to Use Windows NT Server on Intel?
Component
Specified
Minimum
Recommended
Minimum
CPU
i486DX
33 MHz
Pentium
100 MHz
RAM
16 MB
32 MB
Hard Drive
120 MB
300 MB
Floppy
Monitor
High Density High Density
VGA
VGA
51
Copyright 1996 By William F. Slater, III
The Future of Windows NT
• Clustering -- Allowing the control of common disk and
printers resources, while coordinating the processing of
such functions as database processing, in case of the
failure of one or more servers in a network
• Replacement for Windows 95
• More applications will be written specifically for NT.
• Expect more applications using the Internet capabilities of
NT 4.0 and the NT RPC features
• More and more businesses will rely on NT for their
production servers and workstations
• NT is now seen as serious competition for the Novell
Netware market and for the UNIX market, we expect these
two competitive platforms to decrease in market share
while NT’s market share will continue to steadily increase
52
Copyright 1996 By William F. Slater, III
Conclusion
• NT is an excellent example of operating system
software engineering.
• NT Workstation and NT Server deliver an
outstanding technology value for the price you
pay.
• More and more businesses are willing to rely on
NT as a production platform.
• NT is exciting technology which is probably
important to your future as a computer
professional
53
Copyright 1996 By William F. Slater, III
NT Resources -Titles Worth Owning
• Networking Windows NT 3.51, second ed.
– By John Ruley, et al. Wiley, 1995
• NT Server: Management and Control
– By Kenneth L. Spencer. Prentice Hall, 1996
• Windows NT 3.51 Unleashed, third ed.
– By Robert Cowart. SAMS, 1996
• Mastering Windows NT Server 3.51, second ed.
– By Mark Minasi, et al. Sybex, 1996
54
Copyright 1996 By William F. Slater, III
NT Resources -Titles Worth Owning
• Inside Windows NT Server
– By Drew Heywood. New Riders, 1995.
• Windows NT Server Professional Reference
– By Karanjit Siyan. New Riders, 1995.
55
Copyright 1996 By William F. Slater, III
Microsoft’s Suggested
NT Reading List
• Inside the Windows NT File System, by Helen Custer, ISBN
# 15561-5660X
• Inside Windows NT, by Helen Custer (based on Windows
NT 3.1—read for concepts)
• Windows NT Answer Book, by Jim Groves (covers
administration and support questions)
56
Copyright 1996 By William F. Slater, III