Windows 2000

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Windows 2000
Part of the Microsoft Windows family
Windows 2000 logo.png
Windows 2000.png
Screenshot of Windows 2000 Professional
Developer
Microsoft
Website technet.microsoft.com/en-us/windowsserver/bb643141
Releases
Release to
manufacturing
December 15, 1999; 14 years ago (1999-12-15) [info]
General
availability
February 17, 2000; 14 years ago (2000-02-17) [info]
Latest stable
version
5.0 (Build 2195: Service Pack 4) (September 13, 2005; 8 years ago (2005-09-13)) [info]
Source model Shared source[1]
License Proprietary commercial software
Kernel type Hybrid kernel
Update method Windows Update
Platform support IA-32
Preceded by Windows NT 4.0 (1996)
Succeeded by Windows XP (2001) and Windows Server 2003 (2003)
Support status
Unsupported as of July 13, 2010[2]

Windows 2000 is an operating system for use on both client and server computers. It was produced by Microsoft and released to manufacturing on December 15, 1999[3] and launched to retail on February 17, 2000.[4] It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation.[5] It is succeeded by Windows XP (released in October 2001) and Windows Server 2003 (released in April 2003). During development, Windows 2000 was known as Windows NT 5.0.

Four editions of Windows 2000 were released: Professional, Server, Advanced Server, and Datacenter Server;[6] the latter was both released to manufacturing and launched months after the other editions.[7] While each edition of Windows 2000 was targeted at a different market, they shared a core set of features, including many system utilities such as the Microsoft Management Console and standard system administration applications.

Support for people with disabilities was improved over Windows NT 4.0 with a number of new assistive technologies,[8] and Microsoft increased support for different languages[9] and locale information.[10]

All versions of the operating system support NTFS 3.0,[11] Encrypting File System, as well as basic and dynamic disk storage.[12] The Windows 2000 Server family has additional features,[13] including the ability to provide Active Directory services (a hierarchical framework of resources), Distributed File System (a file system that supports sharing of files) and fault-redundant storage volumes. Windows 2000 can be installed through either a manual or unattended installation.[14] Unattended installations rely on the use of answer files to fill in installation information, and can be performed through a bootable CD using Microsoft Systems Management Server, by the System Preparation Tool.[15]

Microsoft marketed Windows 2000 as the most secure Windows version ever at the time;[16] however, it became the target of a number of high-profile virus attacks such as Code Red and Nimda.[17] For ten years after its release, it continued to receive patches for security vulnerabilities nearly every month until reaching the end of its lifecycle on July 13, 2010.[2]

History[edit]

Windows 2000 is a continuation of the Microsoft Windows NT family of operating systems, replacing Windows NT 4.0. The original name for the operating system was Windows NT 5.0. Beta 1 of NT 5.0 was released in September 1997, followed by Beta 2 in August 1998.[18] On October 27, 1998, Microsoft announced that the name of the final version of the operating system would be Windows 2000, a name which referred to its projected release date.[19] Windows 2000 Beta 3 was released in January 1999.[18] NT 5.0 Beta 1 was similar to NT 4.0, including a very similar themed logo. NT 5.0 Beta 2 introduced a new 'mini' boot screen, and removed the 'dark space' theme in the logo. The NT 5.0 betas had very long startup and shutdown sounds, though these were changed in the early Windows 2000 beta, but during Beta 3, a new piano-made startup and shutdown sounds were made, featured in the final version as well as for Windows ME. The new login prompt from the final version made its first appearance in Beta 3 build 1946 (the first build of Beta 3). The new, updated icons (for My Computer, Recycle Bin etc.) first appeared in Beta 3 build 1976. The Windows 2000 boot screen in the final version first appeared in Beta 3 build 1994. Windows 2000 did not have a codename because, according to Dave Thompson of Windows NT team, "Jim Allchin didn't like codenames".[20]

Windows 2000 Service Pack 1 was codenamed "Asteroid"[21] and Windows 2000 64-bit was codenamed "Janus."[22][23] During development, there was a build for the Alpha which was abandoned some time after RC1[24] after Compaq announced they had dropped support for Windows NT on Alpha. From here, Microsoft issued three release candidates between July and November 1999, and finally released the operating system to partners on December 12, 1999.[25] The public could buy the full version of Windows 2000 on February 17, 2000. Three days before this event, which Microsoft advertised as "a standard in reliability," a leaked memo from Microsoft reported on by Mary Jo Foley revealed that Windows 2000 had "over 63,000 potential known defects."[26] After Foley's article was published, Microsoft blacklisted her for a considerable time.[27] However, Abraham Silberschatz et al. claim in their computer science textbook that "Windows 2000 was the most reliable, stable operating system Microsoft had ever shipped to that point. Much of this reliability came from maturity in the source code, extensive stress testing of the system, and automatic detection of many serious errors in drivers."[28] InformationWeek summarized the release "our tests show the successor to NT 4.0 is everything we hoped it would be. Of course, it isn't perfect either."[29] Wired News later described the results of the February launch as "lackluster."[30] Novell criticized Microsoft's Active Directory, the new directory service architecture, as less scalable or reliable than its own Novell Directory Services (NDS) alternative.[31]

Windows 2000 was first planned to replace both Windows 98 and Windows NT 4.0. However, that changed later. Instead, an updated version of Windows 98 called Windows 98 Second Edition was released in 1999 and Windows ME was released in late 2000.[18]

On or shortly before February 12, 2004, "portions of the Microsoft Windows 2000 and Windows NT 4.0 source code were illegally made available on the Internet."[32] The source of the leak remains unannounced. Microsoft issued the following statement:

"Microsoft source code is both copyrighted and protected as a trade secret. As such, it is illegal to post it, make it available to others, download it or use it."

Despite the warnings, the archive containing the leaked code spread widely on the file-sharing networks. On February 16, 2004, an exploit "allegedly discovered by an individual studying the leaked source code"[32] for certain versions of Microsoft Internet Explorer was reported.

Microsoft planned to release two additional editions of Windows based on the Windows 2000 codebase, Advanced Server Limited Edition and Datacenter Server Limited Edition, which ran on 64-bit Intel Itanium microprocessors.[33] However, the first officially-released edition was considered part of the Windows Server 2003 family of products.[34]

New and updated features[edit]

Windows 2000 introduced many of the new features of Windows 98 and Windows 98 SE into the NT line,[35] such as the Windows Desktop Update,[35] Internet Explorer 5 (Internet Explorer 6, which came in 2001, is also available for Windows 2000),[35] Outlook Express, NetMeeting, FAT32 support,[36] Windows Driver Model,[37] Internet Connection Sharing,[35] Windows Media Player, WebDAV support[38] etc. Certain new features are common across all editions of Windows 2000, among them NTFS 3.0,[11] the Microsoft Management Console (MMC),[39] UDF support, the Encrypting File System (EFS),[40] Logical Disk Manager,[41] Image Color Management 2.0,[42] support for PostScript 3-based printers,[42] OpenType (.OTF) and Type 1 PostScript (.PFB) font support,[42] the Data protection API (DPAPI),[43] an LDAP/Active Directory-enabled Address Book,[44] usability enhancements and multi-language and locale support. Windows 2000 also introduced USB device class drivers for USB printers, Mass storage class devices,[45] and improved FireWire SBP-2 support for printers and scanners, along with a Safe removal applet for storage devices.[46] Windows 2000 is also the first Windows version to support hibernation at the operating system level (OS-controlled ACPI S4 sleep state) unlike Windows 98 which required special drivers from the hardware manufacturer or driver developer.[47]

A new capability designed to protect critical system files called Windows File Protection was introduced. This protects critical Windows system files by preventing programs other than Microsoft's operating system update mechanisms such as the Package Installer, Windows Installer and other update components from modifying them.[48] The System File Checker utility provides users the ability to perform a manual scan the integrity of all protected system files, and optionally repair them, either by restoring from a cache stored in a separate "DLLCACHE" directory, or from the original install media.

Microsoft recognized that a serious error or a stop error could cause problems for servers that needed to be constantly running and so provided a system setting that would allow the server to automatically reboot when a stop error occurred.[49] Also included is an option to dump any of the first 64 KB of memory to disk (the smallest amount of memory that is useful for debugging purposes, also known as a minidump), a dump of only the kernel's memory, or a dump of the entire contents of memory to disk, as well as write that this event happened to the Windows 2000 event log.[49] In order to improve performance on servers running Windows 2000, Microsoft gave administrators the choice of optimizing the operating system's memory and processor usage patterns for background services or for applications.[50] Windows 2000 also introduced core system administration and management features as the Windows Installer,[51] Windows Management Instrumentation[52] and Event Tracing for Windows (ETW)[53] into the operating system.

Plug and Play and hardware support improvements[edit]

The most notable improvement from Windows NT 4.0 is the addition of Plug and Play with full ACPI and Windows Driver Model support. Similar to Windows 9x, Windows 2000 supports automatic recognition of installed hardware, hardware resource allocation, loading of appropriate drivers, PnP APIs and device notification events. The addition of the kernel PnP Manager along with the Power Manager are two significant subsystems added in Windows 2000.

Windows 2000 introduced version 3 print drivers (user mode printer drivers).[54] Generic support for 5-button mice is also included as standard [55] and installing IntelliPoint allows reassigning the programmable buttons. Windows 98 lacked generic support. [56] Driver Verifier was introduced to stress test and catch device driver bugs.[57]

Shell[edit]

Windows 2000 introduces layered windows that allow for transparency, translucency and various transition effects like shadows, gradient fills and alpha blended GUI elements to top-level windows.[58] Menus support a new Fade transition effect.

The integrated media player in Windows Explorer playing a MIDI sequence.

The Start Menu in Windows 2000 introduces personalized menus, expandable special folders and the ability to launch multiple programs without closing the menu by holding down the SHIFT key. A Re-sort button forces the entire Start Menu to be sorted by name. The Taskbar introduces support for balloon notifications which can also be used by application developers. Windows 2000 Explorer introduces customizable Windows Explorer toolbars, auto-complete in Windows Explorer address bar and Run box, advanced file type association features, displaying comments in shortcuts as tooltips, extensible columns in Details view (IColumnProvider interface), icon overlays, integrated search pane in Windows Explorer, sort by name function for menus, and Places bar in common dialogs for Open and Save.

Windows Explorer has been enhanced in several ways in Windows 2000. It is the first Windows NT release to include Active Desktop, first introduced as a part of Internet Explorer 4.0 (specifically Windows Desktop Update), and only pre-installed in Windows 98 by that time.[59] It allowed users to customize the way folders look and behave by using HTML templates, having the file extension HTT. This feature was abused by computer viruses that employed malicious scripts, Java applets, or ActiveX controls in folder template files as their infection vector. Two such viruses are VBS/Roor-C[60] and VBS.Redlof.a.[61] Other features new to Explorer include customizable toolbars, auto-complete in address bar and Run box, advanced file type association features and a Places bar in common dialogs.

The "Web-style" folders view, with the left Explorer pane displaying details for the object currently selected, is turned on by default in Windows 2000. For certain file types, such as pictures and media files, the preview is also displayed in the left pane.[62] Until the dedicated interactive preview pane appeared in Windows Vista, Windows 2000 had been the only Windows release to feature an interactive media player as the previewer for sound and video files, enabled by default. However, such a previewer can be enabled in previous versions of Windows with the Windows Desktop Update installed through the use of folder customization templates.[63] The default file tooltip displays file title, author, subject and comments;[64] this metadata may be read from a special NTFS stream, if the file is on an NTFS volume, or from an OLE structured storage stream, if the file is a structured storage document. All Microsoft Office documents since Office 4.0[65] make use of structured storage, so their metadata is displayable in the Windows 2000 Explorer default tooltip. File shortcuts can also store comments which are displayed as a tooltip when the mouse hovers over the shortcut. The shell introduces extensibility support through metadata handlers, icon overlay handlers and column handlers in Explorer Details view.[66]

The right pane of Windows 2000 Explorer, which usually just lists files and folders, can also be customized. For example, the contents of the system folders aren't displayed by default, instead showing in the right pane a warning to the user that modifying the contents of the system folders could harm their computer. It's possible to define additional Explorer panes by using DIV elements in folder template files.[59] This degree of customizability is new to Windows 2000; neither Windows 98 nor the Desktop Update could provide it.[67] The new DHTML-based search pane is integrated into Windows 2000 Explorer, unlike the separate search dialog found in all previous Explorer versions. The Indexing Service has also been integrated into the operating system and the search pane built into Explorer allows searching files indexed by its database.[68]

NTFS 3.0[edit]

Windows 2000 supports disk quotas, which can be set via the "Quota" tab found in the hard disk properties dialog box.

Microsoft released the version 3.0 of NTFS[11] (sometimes incorrectly called NTFS 5 in relation to the kernel version number) as part of Windows 2000; this introduced disk quotas (provided by QuotaAdvisor), file-system-level encryption, sparse files and reparse points. Sparse files allow for the efficient storage of data sets that are very large yet contain many areas that only have zeros.[69] Reparse points allow the object manager to reset a file namespace lookup and let file system drivers implement changed functionality in a transparent manner.[70] Reparse points are used to implement volume mount points, junctions, Hierarchical Storage Management, Native Structured Storage and Single Instance Storage.[70] Volume mount points and directory junctions allow for a file to be transparently referred from one file or directory location to another.

Windows 2000 also introduces a Distributed Link Tracking service to ensure file shortcuts remain working even if the target is moved or renamed. The target object's unique identifier is stored in the shortcut file on NTFS 3.0 and Windows can use the Distributed Link Tracking service for tracking the targets of shortcuts, so that the shortcut file may be silently updated if the target moves, even to another hard drive.[71]

Encrypting File System[edit]

The Encrypting File System (EFS) introduced strong file system-level encryption to Windows. It allows any folder or drive on an NTFS volume to be encrypted transparently by the user.[40] EFS works together with the EFS service, Microsoft's CryptoAPI and the EFS File System Runtime Library (FSRTL).[72] To date, its encryption has not been compromised.

EFS works by encrypting a file with a bulk symmetric key (also known as the File Encryption Key, or FEK), which is used because it takes less time to encrypt and decrypt large amounts of data than if an asymmetric key cipher were used.[72] The symmetric key used to encrypt the file is then encrypted with a public key associated with the user who encrypted the file, and this encrypted data is stored in the header of the encrypted file. To decrypt the file, the file system uses the private key of the user to decrypt the symmetric key stored in the file header. It then uses the symmetric key to decrypt the file. Because this is done at the file system level, it is transparent to the user.[73]

For a user losing access to their key, support for recovery agents that can decrypt files is built into EFS. A Recovery Agent is a user who is authorized by a public key recovery certificate to decrypt files belonging to other users using a special private key. By default, local administrators are recovery agents however they can be customized using Group Policy.

Basic and dynamic disk storage[edit]

Windows 2000 introduced the Logical Disk Manager and the diskpart command line tool for dynamic storage.[12] All versions of Windows 2000 support three types of dynamic disk volumes (along with basic disks): simple volumes, spanned volumes and striped volumes:

  • Simple volume, a volume with disk space from one disk.
  • Spanned volumes, where up to 32 disks show up as one, increasing it in size but not enhancing performance. When one disk fails, the array is destroyed. Some data may be recoverable. This corresponds to JBOD and not to RAID-1.
  • Striped volumes, also known as RAID-0, store all their data across several disks in stripes. This allows better performance because disk reads and writes are balanced across multiple disks. Like spanned volumes, when one disk in the array fails, the entire array is destroyed (some data may be recoverable).

In addition to these disk volumes, Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server support mirrored volumes and striped volumes with parity:

  • Mirrored volumes, also known as RAID-1, store identical copies of their data on 2 or more identical disks (mirrored). This allows for fault tolerance; in the event one disk fails, the other disk(s) can keep the server operational until the server can be shut down for replacement of the failed disk.
  • Striped volumes with parity, also known as RAID-5, functions similar to striped volumes/RAID-0, except "parity data" is written out across each of the disks in addition to the data. This allows the data to be "rebuilt" in the event a disk in the array needs replacement.

Accessibility[edit]

With Windows 2000, Microsoft introduced the Windows 9x accessibility features for people with visual and auditory impairments and other disabilities into the NT-line of operating systems.[8] These included:

  • StickyKeys: makes modifier keys (ALT, CTRL and SHIFT) become "sticky": a user can press the modifier key, and then release it before pressing the combination key. (Activated by pressing Shift five times quickly.)
  • FilterKeys: a group of keyboard-related features for people with typing issues, including:
    • SlowKeys: Ignore any keystroke not held down for a certain period.
    • BounceKeys: Ignore repeated keystrokes pressed in quick succession.
    • RepeatKeys: lets users slow down the rate at which keys are repeated via the keyboard's key-repeat feature.
  • ToggleKeys: when turned on, Windows will play a sound when the CAPS LOCK, NUM LOCK or SCROLL LOCK key is pressed.
  • SoundSentry: designed to help users with auditory impairments, Windows 2000 shows a visual effect when a sound is played through the sound system.
  • MouseKeys: lets users move the cursor around the screen via the numeric keypad.
  • SerialKeys: lets Windows 2000 support speech augmentation devices.
  • High contrast theme: to assist users with visual impairments.
  • Microsoft Magnifier: A screen magnifier that enlarges a part of the screen the cursor is over.[74]

Additionally, Windows 2000 introduced the following new accessibility features:

Languages and locales[edit]

Windows 2000 introduced the Multilingual User Interface (MUI).[76] Besides English, Windows 2000 incorporates support for Arabic, Armenian, Baltic, Central European, Cyrillic, Georgian, Greek, Hebrew, Indic, Japanese, Korean, Simplified Chinese, Thai, Traditional Chinese, Turkic, Vietnamese and Western European languages.[9] It also has support for many different locales.[10]

Games[edit]

Windows 2000 included version 7.0 of the DirectX API, commonly used by game developers on Windows 98.[77] The last version of DirectX that Windows 2000 supports is DirectX 9.0c (Shader Model 3.0), that shipped with Windows XP Service Pack 2. Microsoft published quarterly updates to DirectX 9.0c through the February 2010 release after which support was dropped in the June 2010 SDK. These updates contain bug fixes to the core runtime and some additional libraries such as D3DX, XAudio 2, XInput and Managed DirectX components. The majority of games written for versions of DirectX 9.0c (up to the February 2010 release) can therefore run on Windows 2000.

Windows 2000 included the same games as Windows NT 4.0 did: FreeCell, Minesweeper, Pinball, and Solitaire.[78]

System utilities[edit]

The Windows 2000 Computer Management console can perform many system tasks. It is pictured here starting a disk defragmentation.

Windows 2000 introduced the Microsoft Management Console (MMC), which is used to create, save, and open administrative tools.[39] Each of these is called a console, and most allow an administrator to administer other Windows 2000 computers from one centralised computer. Each console can contain one or many specific administrative tools, called snap-ins.[39] These can be either standalone (with one function), or an extension (adding functions to an existing snap-in). In order to provide the ability to control what snap-ins can be seen in a console, the MMC allows consoles to be created in author mode or user mode.[39] Author mode allows snap-ins to be added, new windows to be created, all portions of the console tree to be displayed and consoles to be saved. User mode allows consoles to be distributed with restrictions applied. User mode consoles can grant full access to the user for any change, or they can grant limited access, preventing users from adding snapins to the console though they can view multiple windows in a console. Alternatively users can be granted limited access, preventing them from adding to the console and stopping them from viewing multiple windows in a single console.[79]

The main tools that come with Windows 2000 can be found in the Computer Management console (in Administrative Tools in the Control Panel).[80] This contains the Event Viewer—a means of seeing events and the Windows equivalent of a log file,[81] a system information utility, a backup utility, Task Scheduler and management consoles to view open shared folders and shared folder sessions, configure and manage COM+ applications, configure Group Policy,[82] manage all the local users and user groups, and a device manager.[83] It contains Disk Management and Removable Storage snap-ins,[84] a disk defragmenter as well as a performance diagnostic console, which displays graphs of system performance and configures data logs and alerts. It also contains a service configuration console, which allows users to view all installed services and to stop and start them, as well as configure what those services should do when the computer starts. CHKDSK has significant performance improvements.[85]

Windows 2000 comes with two utilities to edit the Windows registry, REGEDIT.EXE and REGEDT32.EXE.[86] REGEDIT has been directly ported from Windows 98, and therefore does not support editing registry permissions.[86] REGEDT32 has the older multiple document interface (MDI) and can edit registry permissions in the same manner that Windows NT's REGEDT32 program could. REGEDIT has a left-side tree view of the Windows registry, lists all loaded hives and represents the three components of a value (its name, type, and data) as separate columns of a table. REGEDT32 has a left-side tree view, but each hive has its own window, so the tree displays only keys and it represents values as a list of strings. REGEDIT supports right-clicking of entries in a tree view to adjust properties and other settings. REGEDT32 requires all actions to be performed from the top menu bar. Windows XP is the first system to integrate these two programs into a single utility, adopting the REGEDIT behavior with the additional NT features.[86]

The System File Checker (SFC) also comes with Windows 2000. It is a command line utility that scans system files and verifies whether they were signed by Microsoft and works in conjunction with the Windows File Protection mechanism. It can also repopulate and repair all the files in the Dllcache folder.[87]

Recovery Console[edit]

The Recovery Console is usually used to recover unbootable systems.

The Recovery Console is run from outside the installed copy of Windows to perform maintenance tasks that can neither be run from within it nor feasibly be run from another computer or copy of Windows 2000.[88] It is usually used to recover the system from problems that cause booting to fail, which would render other tools useless, like Safe Mode or Last Known Good Configuration, or chkdsk. It includes commands like 'fixmbr', which are not present in MS-DOS.

It has a simple command line interface, used to check and repair the hard drive(s), repair boot information (including NTLDR), replace corrupted system files with fresh copies from the CD, or enable/disable services and drivers for the next boot.

The console can be accessed in either of the two ways:

  1. Booting from the Windows 2000 CD, and choosing to start the Recovery Console from the CD itself instead of continuing with setup. The Recovery Console is accessible as long as the installation CD is available.
  2. Preinstalling the Recovery Console on the hard disk as a startup option in Boot.ini, via WinNT32.exe, with the /cmdcons switch.[89] In this case, it can only be started as long as NTLDR can boot from the system partition.

Windows Scripting Host 2.0[edit]

Windows 2000 introduced Windows Script Host 2.0 which included an expanded object model and support for logon and logoff scripts.

Server family features[edit]

The Windows 2000 server family consists of Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server.

All editions of Windows 2000 Server have the following services and features built in:

Screenshot of Windows 2000 Server

The Server editions include more features and components, including the Microsoft Distributed File System (DFS), Active Directory support and fault-tolerant storage.

Distributed File System[edit]

The Distributed File System (DFS) allows shares in multiple different locations to be logically grouped under one folder, or DFS root. When users try to access a network share off the DFS root, the user is really looking at a DFS link and the DFS server transparently redirects them to the correct file server and share. A DFS root can only exist on a Windows 2000 version that is part of the server family, and only one DFS root can exist on that server.

There can be two ways of implementing a DFS namespace on Windows 2000: either through a standalone DFS root or a domain-based DFS root. Standalone DFS allows for only DFS roots on the local computer, and thus does not use Active Directory. Domain-based DFS roots exist within Active Directory and can have their information distributed to other domain controllers within the domain – this provides fault tolerance to DFS. DFS roots that exist on a domain must be hosted on a domain controller or on a domain member server. The file and root information is replicated via the Microsoft File Replication Service (FRS).[94]

Active Directory[edit]

A new way of organizing Windows network domains, or groups of resources, called Active Directory, is introduced with Windows 2000 to replace Windows NT's earlier domain model. Active Directory's hierarchical nature allowed administrators a built-in way to manage user and computer policies and user accounts, and to automatically deploy programs and updates with a greater degree of scalability and centralization than provided in previous Windows versions. User information stored in Active Directory also provided a convenient phone book-like function to end users. Active Directory domains can vary from small installations with a few hundred objects, to large installations with millions. Active Directory can organise and link groups of domains into a contiguous domain name space to form trees. Groups of trees outside of the same namespace can be linked together to form forests.

Active Directory services could always be installed on a Windows 2000 Server, Advanced Server, or Datacenter Server computer, and cannot be installed on a Windows 2000 Professional computer. However, Windows 2000 Professional is the first client operating system able to exploit Active Directory's new features. As part of an organization's migration, Windows NT clients continued to function until all clients were upgraded to Windows 2000 Professional, at which point the Active Directory domain could be switched to native mode and maximum functionality achieved.

Active Directory requires a DNS server that supports SRV resource records, or that an organization's existing DNS infrastructure be upgraded to support this. There should be one or more domain controllers to hold the Active Directory database and provide Active Directory directory services.

Volume fault tolerance[edit]

Along with support for simple, spanned and striped volumes, the server family of Windows 2000 also supports fault-tolerant volume types. The types supported are mirrored volumes and RAID-5 volumes:

  • Mirrored volumes: the volume contains several disks, and when data is written to one it is also written to the other disks. This means that if one disk fails, the data can be totally recovered from the other disk. Mirrored volumes are also known as RAID-1.
  • RAID-5 volumes: a RAID-5 volume consists of multiple disks, and it uses block-level striping with parity data distributed across all member disks. Should a disk fail in the array, the parity blocks from the surviving disks are combined mathematically with the data blocks from the surviving disks to reconstruct the data on the failed drive "on-the-fly."

Deployment[edit]

Windows 2000 system requirements
Minimum Recommended
IA-32 PCs
CPU Pentium 133 MHz Pentium II 300 MHz
Memory 32 MB (128 MB for Server) 128 MB
Hard drive 1 GB (2 GB for Server) 5 GB
Graphics hardware 800×600 VGA or better monitor 1024×768 VGA or higher monitor
Input device(s) Keyboard or mouse Keyboard and mouse

Windows 2000 can be deployed to a site via various methods. It can be installed onto servers via traditional media (such as CD) or via distribution folders that reside on a shared folder. Installations can be attended or unattended. During a manual installation, the administrator must specify configuration options. Unattended installations are scripted via an answer file, or a predefined script in the form of an INI file that has all the options filled in. An answer file can be created manually or using the graphical Setup manager. The Winnt.exe or Winnt32.exe program then uses that answer file to automate the installation. Unattended installations can be performed via a bootable CD, using Microsoft Systems Management Server (SMS), via the System Preparation Tool (Sysprep), via the Winnt32.exe program using the /syspart switch or via Remote Installation Services (RIS). The ability to slipstream a service pack into the original operating system setup files is also introduced in Windows 2000.[95]

The Sysprep method is started on a standardized reference computer – though the hardware need not be similar – and it copies the required installation files from the reference computer to the target computers. The hard drive does not need to be in the target computer and may be swapped out to it at any time, with the hardware configured later. The Winnt.exe program must also be passed a /unattend switch that points to a valid answer file and a /s file that points to one or more valid installation sources.

Sysprep allows the duplication of a disk image on an existing Windows 2000 Server installation to multiple servers. This means that all applications and system configuration settings will be copied across to the new installations, and thus, the reference and target computers must have the same HALs, ACPI support, and mass storage devices – though Windows 2000 automatically detects "plug and play" devices. The primary reason for using Sysprep is to quickly deploy Windows 2000 to a site that has multiple computers with standard hardware. (If a system had different HALs, mass storage devices or ACPI support, then multiple images would need to be maintained.)

Systems Management Server can be used to upgrade multiple computers to Windows 2000. These must be running Windows NT 3.51, Windows NT 4.0, Windows 98 or Windows 95 OSR2.x along with the SMS client agent that can receive software installation operations. Using SMS allows installations over a wide area and provides centralised control over upgrades to systems.

Remote Installation Services (RIS) are a means to automatically install Windows 2000 Professional (and not Windows 2000 Server) to a local computer over a network from a central server. Images do not have to support specific hardware configurations and the security settings can be configured after the computer reboots as the service generates a new unique security ID (SID) for the machine. This is required so that local accounts are given the right identifier and do not clash with other Windows 2000 Professional computers on a network.[96] RIS requires that client computers are able to boot over the network via either a network interface card that has a Pre-Boot Execution Environment (PXE) boot ROM installed or that the client computer has a network card installed that is supported by the remote boot disk generator. The remote computer must also meet the Net PC specification. The server that RIS runs on must be Windows 2000 Server and it must be able to access a network DNS Service, a DHCP service and the Active Directory services.[97]

Editions[edit]

Microsoft released various editions of Windows 2000 for different markets and business needs: Professional, Server, Advanced Server and Datacenter Server. Each was packaged separately.

Windows 2K cover.PNG Windows 2000 Professional was designed as the desktop operating system for businesses and power users. It is the client version of Windows 2000. It offers greater security and stability than many of the previous Windows desktop operating systems. It supports up to two processors, and can address up to 4 GB of RAM. The system requirements are a Pentium processor (or equivalent) of 133 MHz or greater, at least 32 MB of RAM, 650 MB of hard drive space, and a CD-ROM drive (recommended: Pentium II, 128 MB of RAM, 2 GB of hard drive space, and CD-ROM drive).[98]
Windows 2K Server cover.PNG Windows 2000 Server shares the same user interface with Windows 2000 Professional, but contains additional components for the computer to perform server roles and run infrastructure and application software. A significant new component introduced in the server versions is Active Directory, which is an enterprise-wide directory service based on LDAP (Lightweight Directory Access Protocol). Additionally, Microsoft integrated Kerberos network authentication, replacing the often-criticised NTLM (NT LAN Manager) authentication system used in previous versions. This also provided a purely transitive-trust relationship between Windows 2000 domains in a forest (a collection of one or more Windows 2000 domains that share a common schema, configuration, and global catalog, being linked with two-way transitive trusts). Furthermore, Windows 2000 introduced a Domain Name Server which allows dynamic registration of IP addresses. Windows 2000 Server supports up to 4 processors and 4GB of RAM, with a minimum requirement of 128 MB of RAM and 1 GB hard disk space, however requirements may be higher depending on installed components.[98]
Windows 2K Advanced Server.PNG Windows 2000 Advanced Server is a variant of Windows 2000 Server operating system designed for medium-to-large businesses. It offers clustering infrastructure for high availability and scalability of applications and services, including support for up to 8 CPUs, a main memory amount of up to 8 gigabytes (GB) on Physical Address Extension (PAE) systems and the ability to do 8-way SMP. It supports TCP/IP load balancing and enhanced two-node server clusters based on the Microsoft Cluster Server (MSCS) in Windows NT Server 4.0 Enterprise Edition.[99] System requirements are similar to those of Windows 2000 Server,[98] however they may need to be higher to scale to larger infrastructure.
Windows 2K Datacenter Server.PNG Windows 2000 Datacenter Server is a variant of Windows 2000 Server designed for large businesses that move large quantities of confidential or sensitive data frequently via a central server.[100] Like Advanced Server, it supports clustering, failover and load balancing. Its minimum system requirements are normal, but it was designed to be capable of handing advanced, fault-tolerant and scalable hardware—for instance computers with up to 32 CPUs and 32 GBs RAM, with rigorous system testing and qualification, hardware partitioning, coordinated maintenance and change control. System requirements are similar to those of Windows 2000 Advanced Server,[98] however they may need to be higher to scale to larger infrastructure. Windows 2000 Datacenter Server was released to manufacturing on August 11, 2000[101] and launched on September 26, 2000.[102] This edition was based on Windows 2000 with Service Pack 1[100] and was not available at retail.[103]


Service packs[edit]

Windows 2000 has received four full service packs and one rollup update package following SP4, which is the last service pack. These were: SP1 on August 15, 2000, SP2 on May 16, 2001, SP3 on August 29, 2002 and SP4 on June 26, 2003. Microsoft phased out all development of its Java Virtual Machine (JVM) from Windows 2000 in SP3. Internet Explorer 5.01 has also been upgraded to the corresponding service pack level.

Microsoft had originally intended to release a fifth service pack for Windows 2000, but Microsoft cancelled this project early in its development, and instead released Update Rollup 1 for SP4, a collection of all the security-related hotfixes and some other significant issues.[104] The Update Rollup does not include all non-security related hotfixes and is not subjected to the same extensive regression testing as a full service pack. Microsoft states that this update will meet customers' needs better than a whole new service pack, and will still help Windows 2000 customers secure their PCs, reduce support costs, and support existing computer hardware.[105]

Security[edit]

During the Windows 2000 period, the nature of attacks on Windows servers changed: more attacks came from remote sources via the Internet. This has led to an overwhelming number of malicious programs exploiting the IIS services – specifically a notorious buffer overflow tendency.[106] This tendency is not operating-system-version specific, but rather configuration-specific: it depends on the services that are enabled.[106] Following this, a common complaint is that "by default, Windows 2000 installations contain numerous potential security problems. Many unneeded services are installed and enabled, and there is no active local security policy."[107] In addition to insecure defaults, according to the SANS Institute, the most common flaws discovered are remotely exploitable buffer overflow vulnerabilities.[108] Other criticized flaws include the use of vulnerable encryption techniques.[109]

Code Red and Code Red II were famous (and much discussed) worms that exploited vulnerabilities of the Windows Indexing Service of Windows 2000's Internet Information Services (IIS).[110] In August 2003, two major worms called Sobig and Blaster began to attack millions of Microsoft Windows computers, resulting in the largest downtime and clean-up cost to that date[citation needed]. The 2005 Zotob worm was blamed for security compromises on Windows 2000 machines at the U.S. Department of Homeland Security, the New York Times Company, ABC and CNN.[111]

On September 8, 2009, Microsoft skipped patching two of the five security flaws that were addressed in the monthly security update, saying that patching one of the critical security flaws was "infeasible."[112] According to Microsoft Security Bulletin MS09-048: "The architecture to properly support TCP/IP protection does not exist on Microsoft Windows 2000 systems, making it infeasible to build the fix for Microsoft Windows 2000 Service Pack 4 to eliminate the vulnerability. To do so would require re-architecting a very significant amount of the Microsoft Windows 2000 Service Pack 4 operating system, [...] there would be no assurance that applications designed to run on Microsoft Windows 2000 Service Pack 4 would continue to operate on the updated system." No patches for this flaw were however released for the newer Windows XP (32-bit) and Windows XP Professional x64 Edition either, despite both also being affected.[113]

Support lifecycle[edit]

Windows 2000 was superseded by newer Microsoft operating systems: Windows 2000 Server products by Windows Server 2003, and Windows 2000 Professional by Windows XP Professional.

The Windows 2000 family of operating systems moved from mainstream support to the extended support phase on June 30, 2005. Microsoft says that this marks the progression of Windows 2000 through the Windows lifecycle policy. Under mainstream support, Microsoft freely provides design changes if any, service packs and non-security related updates in addition to security updates, whereas in extended support, service packs are not provided and non-security updates require contacting the support personnel by e-mail or phone. Under the extended support phase, Microsoft continued to provide critical security updates every month for all components of Windows 2000 (including Internet Explorer 5.0 SP4) and paid per-incident support for technical issues. Because of Windows 2000's age, updated versions of components such as Windows Media Player 11 and Internet Explorer 7 have not been released for it. In the case of Internet Explorer, Microsoft said in 2005 that, "some of the security work in IE 7 relies on operating system functionality in XP SP2 that is non-trivial to port back to Windows 2000."[114]

While users of Windows 2000 Professional and Server are eligible to receive the upgrade license for Windows Vista Business or Windows Server 2008, neither of these operating systems can directly perform an upgrade installation from Windows 2000; a clean installation must be performed instead or a two-step upgrade through XP/2003. Microsoft has dropped the upgrade path from Windows 2000 (and earlier) to Windows 7. Users of Windows 2000 must buy a full Windows 7 license.

Although Windows 2000 is the last NT-based version of Microsoft Windows which does not include product activation, Microsoft has introduced Windows Genuine Advantage for certain downloads and non-critical updates from the Download Center for Windows 2000.

Windows 2000 reached the end of its lifecycle on July 13, 2010. It will not receive new security updates and new security-related hotfixes after this date.[2][115] In Japan, over 130,000 servers and 500,000 PCs in local governments are affected; many local governments said that they will not update as they do not have funds to cover a replacement.[116]

As of 2011 Windows Update still supports the Windows 2000 updates available on Patch Tuesday in July 2010, e.g., if older optional Windows 2000 features are enabled later. Microsoft Office products under Windows 2000 have their own product lifecycles. While Internet Explorer 6 for Windows XP did received security patches up until it lost support, this is not the case for IE6 under Windows 2000. The Malicious Software Removal Tool  mrt.exe installed monthly by Windows Update for XP and later versions can be still downloaded manually for Windows 2000.[117]

Total cost of ownership[edit]

In October 2002, Microsoft commissioned IDC to determine the total cost of ownership (TCO) for enterprise applications on Windows 2000 versus the TCO of the same applications on Linux. IDC's report is based on telephone interviews of IT executives and managers of 104 North American companies in which they determined what they were using for a specific workload for file, print, security and networking services. IDC determined that the four areas where Windows 2000 had a better TCO than Linux – over a period of five years for an average organization of 100 employees – were file, print, network infrastructure and security infrastructure. They determined, however, that Linux had a better TCO than Windows 2000 for web serving. The report also found that the greatest cost was not in the procurement of software and hardware, but in staffing costs and downtime. While the report applied a 40% productivity factor during IT infrastructure downtime, recognizing that employees are not entirely unproductive, it did not consider the impact of downtime on the profitability of the business. The report stated that Linux servers had less unplanned downtime than Windows 2000 servers. It found that most Linux servers ran less workload per server than Windows 2000 servers and also that none of the businesses interviewed used 4-way SMP Linux computers. The report also did not take into account specific application servers – servers that need low maintenance and are provided by a specific vendor. The report did emphasize that TCO was only one factor in considering whether to use a particular IT platform, and also noted that as management and server software improved and became better packaged the overall picture shown could change.[118]

See also[edit]

References[edit]

  1. ^ "Enterprise Source Licensing Program". Microsoft. Retrieved April 5, 2007. 
  2. ^ a b c "Microsoft Product Lifecycle for Windows 2000 family". 
  3. ^ "Microsoft Releases Windows 2000 to Manufacturing". Microsoft.com. Retrieved November 13, 2011. 
  4. ^ "Gates Ushers in Next Generation of PC Computing With Launch of Windows 2000". Microsoft.com. February 17, 2000. Retrieved November 13, 2011. 
  5. ^ "Windows 2000 is a name that reflects NT's continued move to the technology mainstream". Microsoft.com. October 27, 1998. Retrieved November 13, 2011. 
  6. ^ "Microsoft Unveils SQL Server 2000, Windows 2000 Integration". Microsoft.com. October 27, 1998. Retrieved November 13, 2011. 
  7. ^ "Microsoft Announces Final Packaging for Windows 2000". Microsoft.com. 1999-08-17. Retrieved 2013-01-09. 
  8. ^ a b "Windows 2000 Professional Accessibility Resources". Microsoft.com. Retrieved November 13, 2011. 
  9. ^ a b Microsoft Support KB 292264: List of Languages Supported in Windows 2000, Windows XP and Windows Server 2003.
  10. ^ a b Windows 2000 List of Locale IDs and Language Groups.
  11. ^ a b c "New Capabilities and Features of the NTFS 3.0 File System". 
  12. ^ a b "Disk Management: Microsoft Technet". Microsoft.com. Retrieved November 13, 2011. 
  13. ^ "Windows 2000 Server Family". Microsoft.com. Retrieved November 13, 2011. 
  14. ^ "Windows 2000 Unattended Setup Guide". Microsoft.com. Retrieved November 13, 2011. 
  15. ^ "Automating Windows 2000 Installations with Sysprep". Msdn.microsoft.com. Retrieved November 13, 2011. 
  16. ^ "Microsoft and CyberSafe Extend Windows 2000 Security Across the Enterprise" (Press release). Microsoft. January 17, 2000. Retrieved September 17, 2006. 
  17. ^ Code Red/Nimda Worm Activity as seen at Archvillain.com
  18. ^ a b c Road to Gold: A Look at the Development of Windows 2000
  19. ^ Trott, Bob (October 27, 1998). "It's official: NT 5.0 becomes Windows 2000". infoWorld. Archived from the original on March 2, 2005. Retrieved April 22, 2006. 
  20. ^ Thurrott, Paul (8 August 2013). "SuperSite Flashback: NT’s First Decade". Paul Thurrott's SuperSite for Windows. Penton Media. Retrieved 10 August 2013. 
  21. ^ "Windows 2000 service pack nearing release". Zdnetasia.com. January 27, 2000. Retrieved November 13, 2011. 
  22. ^ Thurrott, Paul (July 27, 1999). "64-bit Windows 2000 on track for mid-2000". Windows IT Pro. 
  23. ^ "Windows 2000 to Launch at Comdex, 64-Bit Janus in the Wings". Findarticles.com. August 26, 1999. Retrieved November 13, 2011. 
  24. ^ "RC1 was the build 2072 from June 1999 (and last public Alpha/2000 build), the last known internal build was 2128 and the "Gold" release of Windows 2000 was build 2195". Alphant.com. Retrieved November 13, 2011. 
  25. ^ "Windows 2000 history". ActiveWin. Retrieved April 22, 2006. 
  26. ^ Bugfest! Win2000 has 63,000 'defects' February 14, 2000
  27. ^ Mary Jo Foley: The Exit Interview September 20, 2006
  28. ^ John Wiley & Sons (2010). Operating System Concepts with Java, 8th Edition, page 901.
  29. ^ InformationWeek, December 28, 1999, "Special Report"
  30. ^ Wired News, November 2000, "The Truth, The Whole Truth, and Nothing But The Truth"
  31. ^ "NDS eDirectory vs. Microsoft Active Directory?". Novell. November 17, 1999. Retrieved April 22, 2006. "NDS eDirectory is a cross-platform directory solution that works on NT 4.0, Windows 2000 when available, Solaris and NetWare 5. Active Directory will only support the Windows 2000 environment. In addition, eDirectory users can be assured they are using the most trusted, reliable and mature directory service to manage and control their e-business relationships – not a 1.0 release." 
  32. ^ a b "Statement from Microsoft Regarding Illegal Posting of Windows 2000 Source Code". Microsoft. February 20, 2004. Retrieved January 11, 2007. 
  33. ^ "Microsoft and Intel Announce Preview Release of 64-Bit Windows for Intel Itanium Processor" (Press release). Microsoft. July 12, 2000. Retrieved October 4, 2007. 
  34. ^ "Introducing Windows Advanced Server, Limited Edition". Microsoft. Archived from the original on 22 October 2002. Retrieved 12 January 2013. 
  35. ^ a b c d "Introducing Windows 2000 Professional". Microsoft.com. Retrieved November 13, 2011. 
  36. ^ Description of the FAT32 File System,
  37. ^ "Windows Driver Model (WDM)". Microsoft.com. April 15, 2002. Retrieved November 13, 2011. 
  38. ^ "Overview of Web Folders in Internet Explorer 5". Support.microsoft.com. March 29, 2007. Retrieved November 13, 2011. 
  39. ^ a b c d "Microsoft Management Console – Overview". Technet.microsoft.com. Retrieved November 13, 2011. 
  40. ^ a b "Implementing the Encrypting File System in Windows 2000". Microsoft.com. Retrieved November 13, 2011. 
  41. ^ "Disk Management". Microsoft.com. Retrieved November 13, 2011. 
  42. ^ a b c "Windows 2000 To Include New On-Screen And Printed Scalable Color Solution". Findarticles.com. September 6, 1999. Retrieved November 13, 2011. 
  43. ^ "How to troubleshoot the Data Protection API (DPAPI)". Support.microsoft.com. December 3, 2007. Retrieved November 13, 2011. 
  44. ^ "How to Configure the Address Book to Query Users Contained in Active Directory". Support.microsoft.com. January 24, 2007. Retrieved November 13, 2011. 
  45. ^ "USB FAQ: Introductory level". Microsoft.com. August 25, 2008. Retrieved November 13, 2011. 
  46. ^ "IEEE 1394 and the Windows platform". Msdn.microsoft.com. December 14, 2001. Retrieved November 13, 2011. 
  47. ^ "Windows and Power Management". Microsoft.com. January 1, 2002. Retrieved November 13, 2011. 
  48. ^ "Microsoft KB article 222193: Description of the Windows File Protection Feature". 
  49. ^ a b "How to configure system failure and recovery options in Windows". Support.microsoft.com. May 23, 2006. Retrieved November 13, 2011. 
  50. ^ "Analyzing processor activity: Windows 2000 Professional Resource Kit". Microsoft.com. Retrieved November 13, 2011. 
  51. ^ "Using Windows Installer in Windows 2000 beta 3". Entmag.com. October 7, 2011. Retrieved November 13, 2011. 
  52. ^ "Programming with Windows Management Instrumentation". Informit.com. October 4, 2000. Retrieved November 13, 2011. 
  53. ^ "Event Tracing for Windows (ETW): MSDN". Msdn.microsoft.com. Retrieved November 13, 2011. 
  54. ^ "Choosing User Mode or Kernel Mode". Msdn.microsoft.com. Retrieved November 13, 2011. 
  55. ^ Windows and the 5-Button Wheel Mouse
  56. ^ Fourth and Fifth Mouse Buttons Not Recognized by Windows
  57. ^ Driver Verifier at MSDN. Microsoft.
  58. ^ "Layered Windows: MSDN". Msdn.microsoft.com. Retrieved November 13, 2011. 
  59. ^ a b Esposito, Dino (June 2000). More Windows 2000 UI Goodies: Extending Explorer Views by Customizing Hypertext Template Files. MSDN Magazine. Retrieved August 26, 2007. 
  60. ^ Sophos, VBS/Roor-C threat analysis. Retrieved August 26, 2007.
  61. ^ "Virus.VBS.Redlof.a". Virus Encyclopedia. Viruslist.com. January 15, 2004. Retrieved August 26, 2007. 
  62. ^ "Managing Files, Folders, and Search Methods: Microsoft TechNet". Microsoft.com. Retrieved November 13, 2011. 
  63. ^ "How to Enable Preview for Multimedia Files". Microsoft. January 31, 2000. Retrieved March 29, 2012. 
  64. ^ Windows 2000 Registry: Latest Features and APIs Provide the Power to Customize and Extend Your Apps. MSDN Magazine. November 2000. Retrieved August 26, 2007. 
  65. ^ Kindel, Charlie (August 27, 1993). OLE Property Sets Exposed (– Scholar search). MSDN Magazine. Retrieved August 26, 2007. [dead link][dead link]
  66. ^ "Windows 2000 UI Innovations: MSDN Magazine". Msdn.microsoft.com. Retrieved November 13, 2011. 
  67. ^ Figure 1 Windows Shell Extensions. MSDN Magazine. June 2000. Archived from the original on August 31, 2004. Retrieved August 26, 2007. 
  68. ^ "What is Indexing Service?: MSDN". Msdn.microsoft.com. Retrieved November 13, 2011. 
  69. ^ "Sparse Files Use Quota Equal to Total Allocated Length". Support.microsoft.com. February 26, 2007. Retrieved November 13, 2011. 
  70. ^ a b "Improved NTFS File System". Microsoft.com. Retrieved November 13, 2011. 
  71. ^ "Distributed Link Tracking and Object Identifiers (Windows)". TechNet. Microsoft. 16 October 2012. Retrieved 27 November 2012. 
  72. ^ a b "How Encrypting File System Works". Technet2.microsoft.com. July 19, 2011. Retrieved November 13, 2011. 
  73. ^ "Encrypting File System." Microsoft.
  74. ^ a b A review of Microsoft Magnifier and Narrator[dead link]
  75. ^ On-screenk keyboard[dead link]
  76. ^ "Writing Win32 Multilingual User Interface Applications". Microsoft.com. Retrieved November 13, 2011. 
  77. ^ Ask the Windows 2000 Dev Team.
  78. ^ Ford, Jerry Lee, Jr (2000). Upgrading to Microsoft Windows 2000 Professional: A Migration Guide for Windows 98 and Windows NT Users. Lincoln, NE: iUniverse.com, Inc. p. 90. ISBN 0595148042. Retrieved January 8, 2013. 
  79. ^ Microsoft Press (2000). MCSE 70–210, Microsoft Windows 2000 Professional, pages 58–63.
  80. ^ "Managing Microsoft Windows 2000 Workstations and Servers". Technet.microsoft.com. Retrieved November 13, 2011. 
  81. ^ "Event Logging and Viewing". Technet.microsoft.com. Retrieved November 13, 2011. 
  82. ^ "Step-by-Step Guide to Understanding the Group Policy Feature Set". Technet.microsoft.com. Retrieved November 13, 2011. 
  83. ^ "Description of Device Manager in Windows 2000 and Windows XP". Support.microsoft.com. May 7, 2007. Retrieved November 13, 2011. 
  84. ^ "Windows 2000: Removable Storage and Backup". Microsoft.com. Retrieved November 13, 2011. 
  85. ^ "Windows 2000 Chkdsk Management". Retrieved November 13, 2011. 
  86. ^ a b c "Differences between Regedit.exe and Regedt32.exe". Support.microsoft.com. January 19, 2007. Retrieved November 13, 2011. 
  87. ^ "Microsoft KB article 222471: Description of the Windows 2000 System File Checker (Sfc.exe)". 
  88. ^ "Description of the Windows 2000 Recovery Console". Support.microsoft.com. February 26, 2007. Retrieved November 13, 2011. 
  89. ^ "How to install the Windows Recovery Console". Support.microsoft.com. October 26, 2007. Retrieved November 13, 2011. 
  90. ^ "Elements of Secure Remote Access". Technet.microsoft.com. Retrieved November 13, 2011. 
  91. ^ "How to use Remote Storage in Windows 2000 Server". Support.microsoft.com. October 30, 2006. Retrieved November 13, 2011. 
  92. ^ "An Overview of Windows 2000 Quality of Service". Technet.microsoft.com. Retrieved November 13, 2011. 
  93. ^ "Basic Operation of the Windows Time Service". Support.microsoft.com. October 26, 2007. Retrieved November 13, 2011. 
  94. ^ "Microsoft KB article 812487: Overview of DFS in Windows 2000". 
  95. ^ "Make deployment easier in Windows 2000". Microsoft.com. Retrieved November 13, 2011. 
  96. ^ Mark Minasi. Installing Windows 2000 on Workstations with Remote Installation Services.
  97. ^ Microsoft Press (2000). MCSE 70–210, Microsoft Windows 2000 Professional, pages 543–551.
  98. ^ a b c d "System requirements for Microsoft Windows 2000 operating systems". Retrieved May 23, 2008. 
  99. ^ Microsoft. Windows 2000 Resource Kit, Chap. 1, "Introducing Windows 2000 Deployment Planning."
  100. ^ a b "The Datacenter Program and Windows 2000 Datacenter Server Product". Support.microsoft.com. February 28, 2007. Retrieved November 13, 2011. 
  101. ^ "Microsoft Ships Windows 2000 Datacenter Server to Program Partners". Microsoft.com. 2000-08-11. Retrieved 2013-01-09. 
  102. ^ "Microsoft Windows Datacenter Program - All Systems Go". Microsoft.com. Retrieved 2013-01-09. 
  103. ^ "Microsoft Announces Datacenter Program for Windows 2000". Microsoft.com. 2000-02-15. Retrieved 2013-01-09. 
  104. ^ Naraine, Ryan (November 26, 2004). "Microsoft Scraps Plans for Windows 2000 SP5". Retrieved May 30, 2009. 
  105. ^ "Windows 2000 Update Rollup 1 for Service Pack 4". Microsoft. Archived from the original on January 13, 2006. Retrieved September 27, 2006. 
  106. ^ a b "Worms Wreak Havoc". ECommerce-Guide. August 19, 2003. Retrieved February 25, 2010. 
  107. ^ "governmentsecurity.org". 
  108. ^ "SANS Institute". 
  109. ^ McCullagh, Declan (May 16, 2000). "Critics Blast MS Security". Wired News. Retrieved February 25, 2010. 
  110. ^ "cert.org". cert.org. Retrieved November 13, 2011. 
  111. ^ Wired News, April 12, 2006, "Border Security System Left Open"
  112. ^ Techworld, September 9, 2009, "Microsoft: Windows 2000 too old to update"
  113. ^ "microsoft.com". microsoft.com. Retrieved November 13, 2011. 
  114. ^ "Windows 2000 users to miss out on IE 7". news.com. Archived from the original on July 13, 2012. Retrieved January 11, 2007. 
  115. ^ "Windows 2000 Transitions to Extended Support". 
  116. ^ "Windows 2000 still in use locally". The Japan Times. August 20, 2010. Retrieved August 20, 2010. 
  117. ^ "Malicious Software Removal Tool". n (KB890830). Microsoft. 2011. Retrieved July 24, 2011. 
  118. ^ "Windows 2000 Versus Linux in Enterprise Computing," IDC.

Further reading[edit]

External links[edit]