Windows NT Workstation Tutorial Version 0.6.0 December 1, 2000
This guide is meant to be a reference for learning NT workstation. It does not replace the more complete MCSE study guides, but is mainly intended as a reference and review help prior to testing. Other than that, the reader may use this guide to gain familiarity with NT operation and structure. This guide assumes basic knowledge in the use of the Windows operating system environment. To use this guide, if a term is not understood, look it up on the terms page.
Design Goals Of NT
- Compatibility - Backward compatable with previous Windows systems and applications along with limited DOS, OS/2 and POSIX programs.
- Distributed processing - Multiple concurrent processes run. Client and server communications are supported by named pipes, remote procedure calls, NetDDE, sockets, and more
- Modularity (extensibility) - The design of the operating system is modular (based on groups of components) which allows new capabilities to be added (the OS can be extended) as required.
- Internationalization - Enables support of various languages by supporting the International Standards Organization (ISO) Unicode standard.
- Networking - Supports protocols such as TCP/IP, NetBEUI, IPX/SPX (using NWLink), and DLC.
- Portability - Allows Windows NT to run on various platforms such as those with RISC or CISC processors.
- Reliability - Applications are run in their own memory and are unable to corrupt other applications or the system. System errors are logged.
- Scalability - NT can run on computers with multiple CPUs sharing the same memory.
- Security - Provides a standard security model.
NTs modular nature also allows it to run on multiple platforms.
Windows NT 4.0 Hardware Compatibility List (HCL) specifies hardware that can be run with the NT operating system.
Network Communications Models
- Workgroup - Small group with mainly peer to peer communications. Its size should be 10 users or less.
- Accounts, resources and security are not centralized.
- Each computer maintains its own database of user accounts, group accounts, and security policy information.
- Domain - Computers join a domain, but users must have an account on the domain.
- Needs one server to define the domain which is a primary domain controller (PDC)
- The goal is to have one account, password, and logon
- A global directory database is stored on the server
- Administration of accounts and security is centralized.
- There is one security policy for the domain.
- The domain is not necessarily on one network segment.