Microsoft® Windows® 2000: The Setup Process David Morgan Setup Support Engineer Microsoft Platforms Support Microsoft Corporation

Agenda Setup Requirements Major Changes to the Setup Process File System Conversion Scenarios Dual Booting Plug and Play Integration Driver Signing Service Pack Integration

Microsoft® Windows® 2000 Professional: System Requirements Pentium 133 or higher (recommended) 64 MB of RAM 2-GB hard disk with 650 MB free Supports up to two processors Windows NT Setup

Microsoft® Windows® 2000 Server: System Requirements Pentium 133 or higher 128 MB of RAM (minimum); 4 GB (maximum) 2-GB hard disk with 1 GB free Supports up to four processors Windows NT Setup

Microsoft® Windows® 2000 Advanced Server: System Requirements Pentium 133 or higher RAM 256 MB (recommended), 128 supported minimum); 8 GB (maximum) 2-GB hard disk with 1 GB free Supports up to eight processors Windows NT Setup

Setup Requirements: Foot Print Size Disk requirements account for all components. Disk requirements assume 32-KB FAT16 clusters. Numbers for NTFS and FAT32 are significantly lower. Winnt32.exe checks for free space before copying files. Free space requirements are kept in Dosnet.inf - [DiskSpaceRequirements] Windows NT Setup

Upgrade Paths: Windows 2000 Professional Supports up to two processors out of the box Microsoft® Windows® NT 4.0 and Microsoft® Windows® NT 3.51 Microsoft® Windows® 95 and Microsoft® Windows® 98 Windows 2000 RC2 or RC3

Upgrade Paths: Windows 2000 Server Four-processor support out of the box Windows NT 3.51, Windows NT 4.0, and Microsoft® Windows® NT Server 4.0, Terminal Server Edition Windows 2000 RC2 or RC3

Upgrade Paths: Windows 2000 Advanced Server Eight-processor support out of the box Upgrades Windows NT 3.51, Windows NT Server 4.0, and Terminal Server Edition Upgrades Microsoft® Windows® NT Server 4.0, Enterprise Edition Windows 2000 RC2 or RC3 Does not support any upgrades of Windows 2000 Server, Windows 20000 Professional, or Microsoft® Windows® NT Workstation 4.0

Major Changes: Windows 2000 Setup Plug and Play integration Driver signing Role of server (domain controller or member server) Add/change network card settings dialog box Accessories page (bitmaps, sound schemes, and so on) Default folder is now Winnt Upgrades can only be initiated using Winnt32.exe

Major Changes: Windows 2000 Setup Offending services are disabled before upgrades begin Upgrades and Setup now run in VGA mode using Vga.sys Creation of Emergency Repair Disk (ERD) is moved to Ntbackup.exe Repair process is changed extensively

File System Conversions FAT16 to NTFS v5 NTFS to NTFS v5 No path for FAT16 to FAT32 Windows NT Setup

File System Conversions (2) FAT to NTFS v5 Is left completely up to the user Wizard page asking if you want to convert the file system to NTFS is displayed Server installation defaults to “yes” Workstation installation defaults to “no” Affects only the partition on which the %WinDir% folder resides Unattended upgrade is driven by value in filesystem key Windows NT Setup

File System Conversions (3) NTFS - NTFS v5 Takes place during any installation or upgrade of Windows 2000 Conversion does not take place until Setup is finished All media is converted, including removable media If computer is running Service Pack 4 (SP4) or earlier, a warning message is displayed in Text-mode Setup Backwards compatibility for Windows NT 4.0 is provided by an updated Ntfs.sys file that is included in SP4

Dual Booting: Windows NT/Windows 2000 If the file system is FAT16, Windows NT 4.0 and previous versions can coexist with Windows 2000 You can reinstall the previous operating system, but you must use the updated Winnt32.exe with SP4 If NTFS Install Windows NT 4.0 first (SP4 at a minimum) You cannot reinstall Windows NT 4.0 after NTFS is converted Dual installations on the same partition are not supported by Microsoft

Plug and Play Integration Windows 2000 Implementation Advanced Configuration and Power Interface (ACPI) system BIOS Microsoft® Win32® Driver Model (WDM)

Windows 2000 Setup Process (Winnt32.exe) Command-line switches /unattend[num]:[answer_file] /copydir:folder_name /copysource:folder_name /cmd:command_line /debug[level][:filename] /udf:id[,UDF_file] /syspart:drive_letter /checkupgradeonly /cmdcons /makelocalsource /noreboot

Service Pack Integration No need to reapply a service pack after you change computer state Slipstreaming - applying the service pack to an installation share of Windows 2000 Dynamically built hives Layout.inf now points to new locations Compatibility exists on computers not installed from the service pack

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325553