WindowsNT Server (System Administration)

Windows NT v4.x Installation & Setup

Key Terms:
Administrator Login used for system configuration
BOOT.INI Controls booting in a dual-boot system
BOOTSECT.DOS Allows for dual-booting with another operating system
CTRL-ALT-DEL Welcome logon message
DHCP Provides for automatic TCP/IP configuration
Domain Controller (PDC) Authenticates logons and maintains the security policy
FAT Provides compatibility with MSDOS/Win95 file access
HPFS For compatibility with OS/2 (for conversion to NTFS only)
IPX/SPX (NWLink) Transport protocol used for NOVELL support
MEMORY.DMP Fatal error log file
NetBEUI Transport protocol used for Windows for Workgroups support
NETLOGON Share created to contain NTCONFIG.POL & CONFIG.POL
NTBOOTDD.SYS Allows booting from SCSI drives (SCSI host adapter driver)
NTDETECT.COM Identifies the computer hardware in your system
NTFS Provides long filename support, security, and auto-recovery
NTLDR WinNT Bootstrap Loader, loads and configures WinNT
PAGEFILE.SYS Virtual memory file for WinNT
Policies User Restrictions (Restricts what Explorer can do)
Registery(s) Files in the \systemroot\system32\CONFIG directory
SAM Security Accounts Manager (Security Database)(Bindery)
SPACEBAR Boot with "Last Known Good" feature
STOP ERROR Blue VGA debug screen 80 characters x 50 lines
TCP/IP Transport protocol used for Internet/UNIX/WAN support
UNC Universal Naming Convention (\\server-name\share)
WINS Provides dynamic mapping of Network names and IP addresses
Lecture Topics:
  • Why (sometimes major) hardware problems/conflicts just now show up?
    • MSDOS dosen't monitor the hardware (hardware conflicts or failures aren't noticed.)
    • Windows 95's hardware registery ... SYSTEM PROPERTIES, Device Manager
    • Windows NT see (1) SYSTEM PROPERTIES & (2) Windows NT Diagnostics

  • Before installation check the latest HCL (Hardware Compatibility List).
    • The HCL is the "hardware certification" program.
    • Microsoft Compatibility List
      http://www.microsoft.com/hwtest/hcl/
      "The Hardware Compatibility List (HCL) is a compilation of computers and computer hardware that have been extensively tested with Windows operating systems. Microsoft Product Support Services uses the HCL to determine whether or not a computer is supported for use with the Windows operating system."

  • Hardware Requirements to run Windows NT 4.x ...
    • CPU: 486 or better (Windows NT 4.x no longer supports the 386)
    • RAM: 16MB minimum, 32MB recommended
    • Video: VGA minimum (vendor must! be listed in the HCL)
    • CDROM: ATAPI IDE or SCSI-II
    • Hard Drive: 125MB available hard disk space
    • Mouse: PS/2 or InPort mouse recommended to free up a serial port
    • Serial Ports: for RAS and UPS

  • Choosing a File System...
    1. FAT16 - supported by DOS, Win31, WFW311, Win95, & WinNT
      (but slow, wasteful, & no advanced File System Security)
    2. FAT32 - only supported by Win95
      (fixes the wasteful 32K cluster slack space of FAT16 on large hard drives)
    3. HPFS - OS/2's / OS/3 Warp file system
      (only supported long enough to convert to NTFS during setup)
    4. NTFS - only supported by WinNT
      (fastest, most efficient, & needed for advanced File System security)
    5. CDFS - for CDROMs

    • NOTE: Windows NT cannot be installed on, nor can access volumes compressed with DRVSPACE (Drive Space) or DBLSPACE (Double Space). Windows NT 4.x supports its own internal file and directory compression.

  • Configuring your NIC (Network Interface Card)...
    • A PDC (Primary Domain Controller) or BDC (Backup Domain Controller) must be configured with a NIC at initial setup.
    • A stand alone Server or Workstation may be installed with no network during setup and the NIC configured later. (recommended)
    • *** areas for possible conflict... ***
      1. IRQ (interrupt)
      2. I/O Address (Port Address)
      3. DMA channel
      4. Adapter RAM addresses (ARAM)
      5. Adapter ROM addresses (ROM BIOS, BOOT ROM)
      6. BIA (network Burned In Address)

  • Windows Nt 4.x is not PnP (Plug-and-Play).
    • most PCI bus systems assume PnP (like Windows 95)
    • most PCI adapter cards are jumperless (also assume PnP)
    • most hybrid motherboards (ISA & PCI) assign a default IRQ by slot number
      (slot 1 = IRQ 9, slot 2 = IRQ 10, slot 3 = IRQ 11, ...)
    • You may have to run the configuration software for your NIC in a very plain system (one where the current settings do not conflict and the settings you are trying to configre to are not in conflict, then place the NIC into your server)

  • What you should know before running Windows NT Setup...
    1. What is the brand and model of the NIC?
    2. What IRQ, I/O address, DMA, etc. is the NIC configured to?
    3. What kind of disk adapter (& drivers) to you have?
    4. How do you want to partition the hard drive?
    5. What kind of server will this machine be? (PDC, BDC, or stand-alone)
      1. PDC - for a new domain
      2. BDC - for an existing domain
      3. Stand Alone - ordinary file server (Workgroup model)
      • Cannot change you mind later!
    6. What will be this machine's name?
    7. What will be this machine's Administrator Password?

    • (Optionally) What is the brand and model of the sound card?
    • What is the brand and model of the Video Card?
      (although, the video will be installed as standard VGA, you will update it after setup)
    • Which Domain or Workgroup do you wish to join? (this also can be configured later)

  • What is the difference between "Per Seat" & "Per Server" client licensing?
    • "Per Seat" - a license for the number of enterprise network users.
      (ie. one license for each user)
    • "Per Server" - concurrent licensing, a license for each concurent network session.
      (ie. license for the max number of concurrent connections)

  • What source medias can Windows NT be installed from?
    1. Boot from the Windows NT setup floppies (3), then install from the CDROM (ie. a supported CDROM)
    2. Run WINNT from the \I386 directory on a "non supported" CDROM. (ie. a CDROM accessable from DOS but not supported by WinNT)
      • (3) new "boot" floppies will be created
      • All necessary WinNT installation files will be copied to the hard drive into a directory \$WIN_NT$.~LS
      • This method can also be used if you lose the setup floppies.
    3. Install using the "auto run" or "bootable CDROM" menu.

  • Creating the Emergency Repair Disk:
    • You are prompted to create one during installation (You will need a blank disk.) This original repair disk contains a registery based on your initial setup. There are no user accounts except Administrator and Guest. None of your shares or permissions that you have created are on this original Emergency Repair Disk so you will need to update it anytime you add user accounts, shares, or change permissions.
    • This disk is not bootable. It contains the data (registery(s)) necessary to reconstruct a configuration if your NT system is no longer able to boot.
    • The information contained on the Emergency Repair Disk is stored on your hard drive in C:\WINNT\REPAIR.
    • You can update or recreate your Emergency Repair Disk by running RDISK.EXE. (RDISK.EXE is located in \WINNT\SYSTEM32).

 

Back   Next


| My Homepage |
aprabul@yahoo.com 1