Table of Contents
| Welcome to Installing, Configuring, and Administering Microsoft Windows 2000 Professional | |
| Objective Domain 1 | Installing Windows 2000 Professional | 1 |
| Objective Domain 2 | Implementing and Conducting Administration of Resources | 41 |
| Objective Domain 3 | Implementing, Managing, and Troubleshooting Hardware Devices and Drivers | 71 |
| Objective Domain 4 | Monitoring and Optimizing System Performance and Reliability | 123 |
| Objective Domain 5 | Configuring and Troubleshooting the Desktop Environment | 169 |
| Objective Domain 6 | Implementing, Managing, and Troubleshooting Network Protocols and Services | 219 |
| Objective Domain 7 | Implementing, Monitoring, and Troubleshooting Security | 249 |
| Index | 291 |
Read an Excerpt
Objective 1: Installing Windows 2000 Professional
...Objective 1.3 Upgrade from a previous version of Windows to Windows 2000 Professional.
The next step after assessing Windows 2000 hardware compatibility is performing a clean installation of Windows 2000 Professional, upgrading an existing operating system installation, or preserving the other operating system by installing Windows 2000 Professional in a separate folder.
When Windows 2000 Professional is installed to coexist with another operating system, the computer runs in a multiboot configuration (sometimes referred to as dual-boot.) In a multiboot configuration, it is important to consider Windows 2000 file system compatibility with the previous operating system. For example, the version of NTFS in Windows 2000 (version 5) isn't fully backward compatible with Windows NT, and Windows 9x cannot read NTFS partitions without the installation of a third-party utility. A local installation of Windows NT 4 requires Service Pack 4 (SP4) or later to read partitions formatted with NTFS version 5. If Windows NT 4 contains no service pack or a service pack prior to SP4, the Windows 2000 setup routine will warn you not to continue the installation. If the installation is continued, you will not be able to boot Windows NT 4 after Windows 2000 is installed.
You can upgrade an existing operating system to Windows 2000 Professional if the computer is running Windows 95, Windows 98, Windows NT Workstation 3.51, or Windows NT Workstation 4. In all cases, you run WINNT32.EXE to initiate the upgrade to these operating systems. Consequently, you can't use WINNT.EXE, the 16bit version of the setup routine for computers running MS-DOS and Windows 3.x, to upgrade the operating system to Windows 2000 Professional. Although no other operating system can be upgraded to Windows 2000 Professional, a multiboot configuration is an option. Make sure to disable virus-scanning software before starting a Windows 2000 Professional installation upgrade.
You might need to upgrade Windows 9x-compatible applications to run in Windows 2000. To determine compatibility, check with the application vendor and review the Microsoft software compatibility list. The Microsoft software compatibility list is located by searching for the keywords "software compatibility" at http://Www.microsoft.conil windows2000/ Windows 16-bit applications that use virtual device driver (VxD) files will not run properly in Windows 2000. To aid in detecting known compatibility issues, run the Windows 2000 Readiness Analyzer (CHKUPGRD.EXE) or the /checkupgradeonly installation switch. On a computer running Windows 9x, the upgrade report generated with the /checkupgradeonly switch is automatically logged locally to %windir% as UPGRADE.TXT. Upgrade reports can also be logged to a central location using an automated answer file. For more information on compatibility logging, read the Windows 2000 Professional Upgrade Guide. (See the "Further Reading" section.)
The Windows 2000 Professional setup routine allows you to upgrade third-party application dynamic-link libraries (DLLs) written for Windows 9x using migration DLLs that the application vendor provides. Using migration DLLs and carefully testing before a widespread upgrade ensures that the upgraded applications will run on Windows 2000 Professional.
An upgrade is broken into two phases: a report phase and an installation phase. The report phase displays any known incompatibilities so that they can be addressed before upgrade proceeds, and this phase generates an installation script (answer file). The installation phase migrates registry settings, user accounts, and local profiles; installs Windows 2000 Professional in the same directory as the existing Windows installation; and runs any migration DLLs specified.
Caution: If a computer running Windows 9x in a Windows NT or Windows 2000 domain will be upgraded to Windows 2000, make sure to create a computer account or a computer object in the domain prior to or during the upgrade.
Installation order is an important topic when configuring a computer for multiboot. For example, you should install Windows 2000 Professional only after you install Windows 98 on a multiboot computer. If you installed Windows 98 after Windows 2000 Professional, use the Emergency Repair Disk (ERD) to recover the system partition. For details on configuring a computer for multiboot, see the Microsoft Windows 2000 Professional Resource Kit, Chapter 6, "Setup and Startup," pages 259-261. (See this reference under Objective 1.5 in the "Further Reading" section.)
Objective 1.4 Deploy service packs.
Microsoft uses service packs to distribute numerous updates and hot fixes to an operating system. You can locate service packs for Microsoft operating systems on the Windows Update Web site, a centralized, online resource for Windows updates, including service packs, hot fixes, and drivers.
A shortcut to the Windows Update Web site is located near the top of the Start menu unless Group Policy restrictions remove it. This shortcut points to the Windows Update program UPDMGR.EXE, located in %systemroot%\system32. Running this program starts Microsoft Internet Explorer and connects to the Windows Update Web site. This Web site uses Active Setup and Microsoft ActiveX controls to provide product enhancements. These controls are downloaded and installed on the computer the first time you establish a connection with the site. Windows Update automatically compares device drivers installed on the computer with a database of updated drivers on the server. Any drivers newer than those currently installed are offered for installation.
In a medium to large network, distributing updates locally from the intranet is more efficient than applying updates externally from the Internet. To prevent users from accessing Windows Update, configure the Windows 2000 group policy setting: disable and remove links to Windows Update to restrict access to the Windows Update site.
You apply local updates using service packs. For earlier versions of Windows 32-bit operating systems such as Windows NT, you must reapply a service pack every time you install operating system components from the operating system's installation CD-ROM or a distribution point. A distribution point is a network share containing the operating system source files. A distribution point is synonymous with a distribution share.
In Windows 2000 Professional, slipstreaming avoids the administrative overhead of service pack reapplication. Slipstreaming allows you to apply a service pack update to the source files in the Windows 2000 Professional distribution point. When the distribution point is the source for an installation of Windows 2000 Professional, the new installation contains the service pack. Any services or drivers added to the local installation come from the distribution point, thus avoiding the need to reapply the service pack.
You complete a manual, local installation of a service pack by running the service pack UPDATE.EXE utility. If, after applying the service pack, you add any services or drivers to the local installation, you must reapply the service pack. To avoid manual service pack reapplication, type update -s: distributiou_ folder (where distribution-folder is the location containing the operating system files) to slipstream a distribution point. Then use the distribution point rather than the Windows 2000 Professional installation CD-ROM to add services or drivers to the local installation...
loading...