Editing Windows 2000 (section)

== Deployment ==
{{System requirements
|caption = Windows 2000 system requirements
|useminandrec = yes
|collapse =
|align = right
|font-size = 100%
<!-- Mandatory section -->
|platform1 = [[IA-32]] PCs
|cpu1 = Pentium 133 MHz
|cpu1rec = Pentium II 300 MHz
|memory1 = 32 MB (128 MB for Windows 2000 Server)
|memory1rec = 128 MB (256 MB for Windows 2000 Server)
|gpu1 = 800×600 VGA or better monitor
|gpu1rec = 1024×768 VGA or better monitor
|hdspace1 = 1 GB (2 GB for Windows 2000 Server)
|hdspace1rec = 5 GB
|input1 = Keyboard and/or mouse
}}

Windows 2000 can be [[software deployment|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 installation|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 [[initialization file|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 [[Sysprep|System Preparation Tool (Sysprep)]], via the Winnt32.exe program using the /syspart switch or via [[Remote Installation Services]] (RIS). The ability to [[Slipstream (computing)|slipstream]] a [[service pack]] into the original operating system setup files is also introduced in Windows 2000.<ref>{{Cite web |title=Make deployment easier in Windows 2000 |url=http://www.microsoft.com/technet/prodtechnol/windows2000pro/deploy/depopt/easydep.mspx#EKFAC |url-status=dead |archive-url=https://web.archive.org/web/20070615114603/http://www.microsoft.com/technet/prodtechnol/windows2000pro/deploy/depopt/easydep.mspx#EKFAC |archive-date=June 15, 2007 |access-date=November 13, 2011 |website=Microsoft.com |df=mdy-all}}</ref>

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 [[Hardware Abstraction Layer|HALs]], [[Advanced Configuration and Power Interface|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.<ref>Mark Minasi. ''Installing Windows 2000 on Workstations with Remote Installation Services''.</ref>
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 [[Read-only memory|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 [[Domain Name System|DNS]] Service, a [[Dynamic Host Configuration Protocol|DHCP]] service and the Active Directory services.<ref>''Microsoft Press'' (2000). ''MCSE 70–210, Microsoft Windows 2000 Professional'', pages 543–551.</ref>