NT Test Notes/ Possible Test Questions
RAS- Remote Access Service: Lets remote users connect using dial up lines, a WAN link or ISDN.   NT RAS Server supports up to 256 remote users.  *NT Workstation RAS Server supports only 2.
Win NT has only 2 fault tolerant features for RAID-Redundant Array of Inexpensive/Independant Disks

  • 0- Striping; is available but it is not fault tolerent-Striping w/out parity, not recommended as it puts you at more danger of losing data not less.

  • 1- Disk Mirroring and Duplexing, mirroring; 2 identical disks same data accessed by 1 disk controller, duplexing has two separate controllers and is more fault tolerant.

  • 5- Stripping w/parity distributed across multiple drives. ** RAID 2-4 are not available, but they are ealier versions of disk stripping w/parity only with ECC and on only one disk, so not as fault tolerant as 5.

Volume Set- (used as trick ?) No fault tolerance- lose one and you're dead in the water.  NT boot & system partitions cannot reside in volume sets.  2-32 areas of unformatted free space can be used on the same physical disk, cannot reclaim space w/out losing all data stored in volume set.  Can be formatted w/FAT(this can't be extended) or NTFS (this can be extended)
RAID 0 Stripe Set, none fault tolerant, more controllers, faster read, 2-32 disks, amount used must = smallest unpartitioned space on disks.  *Can't be extended, and NO NT boot & system files allowed*
Sector Sparing- none RAID fault tolerant system in Win Nt.  "Hot Fixing", Auto adds sector-recovery capabilities to file system during operation.  *Only works on SCSI devices, no ESDI/IDE.
Mirror Set Recovering from disk failures- form fault tolerance menu in Disk Administrator choose Break Mirror isolate failed partition (Event Viewer- System Log), replace damaged partititon.  If Boot partition failed modify arcpath in boot.ini and reestablish mirror set.
What virtual machines run in user mode? Win32 subsystem.
Work Group Model- small networks w/peer-to-peer orientation, no central server.  Each computer in group must maintain it's own security policy & security accounts manager database.  Like a stand alone. (Usually 4-6 machines in close proximity).  Allows shared resources, simple design and implementation.
Domain Model- centralized admin.-trust relationships, authentification performed by one of the domain controllers in the domain, centralized domain SAM(Security Account Manager) database to use centralized security & maintain user profiles for the domain users.
Types of NT Servers;

  • Primary Domain Controller (PDC)- "There can be only one!" *

  • Backup Domain Controller- suggested 1, can be 0-whatever, recommended 1 for every 2000 users **

  • Member Server (Server) -as many as needed*** * PDC- usually machine that authenticates users- all login, security, user accounts, etc.  (SAM database-40 MB) ** BDC- usually file & print servers *** Member Servers- machine thats not a domain controller, example: webserverver, mail server etc.

FAT File System- supports long file names, *Does not support local security*, maximum file/partition size 4 GB, WinNT can't read FAT32 file systems, on some OEM versions of Win95 Dual Boot Stations won't be recognized.
NTFS File- * Supports local security*; maximum partition size 16 Exabyte (theoretical);,2 Terabytes (actual); file name up to 255 characters, 16 bit unicode w/multiple periods allowed; file size/partition size 4 GB; directory B-tree; all info. including data is treated as attributes; built in security, fast access w/security.
Creating unattended installations- the setup mngr. creates an answer file which can be sued with winnt.exe for unattended installations.  Located in /support/deptools/i386/setupmgr.exe.  To utilize the answer file: -winnt\u:<answerfile>