390 likes | 523 Vues
This document provides a comprehensive overview of the Windows NT operating system, particularly geared towards medium-sized organizations with 200 to 20,000 users. It explores client compatibility, with an emphasis on Wintel systems, highlighting file and print sharing, user access control, and application server functionalities. The document details the OS's architecture, including memory management, security features, and network services. With over 90% uptime and extensive support, Windows NT is positioned as a cost-effective alternative to UNIX for many multi-user environments.
E N D
NT brief, brief overview For CSC 302 Ching-Wan Yip
OS • Run applications?
Scenerio • Medium size organization (200-20,000 users) • clients • 85% Wintel (NTWS, 95, 3.x, DOS), 10% UNIX boxes, 5% diehard Mac addicts • Services • file, print sharing, user, software access control • medium load web serving, mail, IP/DNS, applications server (Notes, RealAudio, R/3, Oracle, Backup, HelpDesk whatever) • Remote access, fax server, proxy, order, customer database • It works, 90+% uptime, 24-7 support
Criteria • General purpose only, not for • multi-users, non-backend server side application • 3D animation • Huge database • SciViz, calculation
Options • MacOS/BeOS • Novell • UNIX • Solaris, AIX, HP-UX, Digital UNIX, Irix, Linux, BSD... • NT
Why? • OS cost cheaper than expensive UNIX? • UNIX admin. is very expensive
Vs UNIX • 4/8processors SMP out of the box, up to 32 OEM • x86 in practice mostly 2,4,6,8, 10 CPU • 2G RAM 32-bit flat addressing in 3.5x?, 4G in 4.0 • 2G app/2G kernel in 3.5x; 3G app/1G kernel in Enterprise NT, 32G in 5.0 using VLM “Very Large Memory” in Alpha and Intel “Merced” • 2 server clustering failover in 4.0 Enterprise • ~25,000 users in domain • Iris 6.x, HP-UX 11.x, Digital UNIX 4.x full 64-bit • Solaris 2.6, upcoming AIX 4.3 partial 64 • Linux 64-bit on 64-bit platform?
Platforms • Intel x86 • DEC Alpha • defuncted - PowerPC, MIPS • workstation, server, enterprise
Login - Ctrl-Alt-Delete • logon
Just like 95? • Same Program manager/file manager as 95 • for a $4000 for 25 client OS
NOS • Mainly a NOS for file/print sharing, user management, DHCP/WINS, browsing
“Built-in” • can also be remote dial-in server, ftp, gopher, DNS server, routing • IIS web server (index, management, FrontPage) • Directory, Message Queue (MSMQ), media streaming (NetShow), Transcation (MTS), Clustering (MSCS)
Applications Platform • BackOffice 2.5 • NT Server 4.0 w/ Internet Information Server (IIS) 3.0 • Proxy Server 1.0 • SQL Server 6.5 • Exchange Server 5.0 • Systems Management Server (SMS) 1.2 • SNA Server 3.0 • Site Server, Commerce Internet Server • management, personalization
Setup/license • Per seat/server
Role in the network • PDC, BDC, server
Domain model • login required to gain access to resources • Single domain model
Accounts • vs. UNIX /etc/passwd • Different roles • security identifier (SID)group security identifiers(group SIDs) • S-1-5-21-76965814-1898335404-322544488-1001
User control • User policy • login script • Who can do what
Services • Vs UNIX daemons
Name services • DHCP - Dynamic Host Configuration Protocol • WINS - Windows Internet Name Service • DNS - Domain Name System
Print sharing • Serve different clients • vs UNIX lpd model
File sharing • vs UNIX’s NFS • or Samba (UNIX pretends to be NT)
File System • NTFS, FAT (no FAT32 until NT5 next year), HPFS (3.5x) • no security etc. on FAT • NTFS 16EB (2e64) b-tree, FAT 4G (2e32) linked list, RAID support • Universal Naming Convention (UNC) Names • \\server\share\subdirectory\filename
File permissions • chmod ugoa +/-rwxs
Replication • directory
monitoring • vs top
Admin. Friendly? • /etc/init*, win.ini • still Windows
Rock solid? • Still crash - Blue Screen of Dealth (BSOD) • Some configuration changes requires reboot, or command prompt • rebuild disks • drivers - OEM specific • HCL • SP1,2,3… buggy?
Architecture • kernel 3.51 vs 4.0
modular • Subsystems • 32-bit NT and most 32-bit 95 apps • Windows 16-bit - DOS, Windows 3.x • OS/2 - 16-bit character based apps on x86 • POSIX - IEEE 1003.1 apps compiled under NT
Interprocess Communication (IPC) • Named Pipes File Systems (NPFS) • ·Mailslots File Systems (MSFS) • ·NetBIOS • ·Windows Sockets • ·Remote Procedure Calls (RPC) • ·Network Dynamic Data Exchange (Net DDE) • 4.0 distributed component object model (DCOM) • builds on remote procedure call (RPC) • 5.0 COM+ DNA
others • Preemptive multitasking, performance tuning • memory management • security - C2, auditing • localization - unicode • fault-tolerance - RAID, UPS support • compatibility - no DOS, OS/2, Windows • Portability, Scalability, Reliability • Architecture - HAL, kernel