Requirements for four different Windows 2000 operating system products and three server classes are designated in these guidelines. The operating system products include:
-
Microsoft Windows 2000 Server
-
Microsoft Windows 2000 Advanced Server and Microsoft Windows 2000 Datacenter Server
-
Microsoft Small Business Server (formerly known as Microsoft BackOffice® Small Business Server)
The server classes in this guide are the same as in Hardware Design Guide Version 2.0: Basic Server, Enterprise Server, and SOHO Server. (For more information, see Chapter 1, “Overview of Server Design Issues.”) For ease of use in this guide, Basic, SOHO, and Enterprise class requirements are all defined together in the main body of the document, rather than in separate chapters.
Any class of server can run any server operating system product. Furthermore, there are no direct relationships that define which operating system product can or should run on each specific class of server. However, server platforms might need to meet additional requirements to meet the goals of a specific server class or to be a good target platform for a specific operating system.
The following examples show the format for differentiating server class-specific or operating system-specific requirements in this guideline. The first example is the simplest, where the requirement (or recommendation) applies to all classes of servers and all operating systems.
Ex.1. System and components support dates beyond 2000
Required
The BIOS, real time clock, CMOS, and the system as a whole must work correctly for dates from now to past the year 2000.
The second, more complex example presents specific requirements for different server classes and operating system products. The server types are defined in the left column, and the column headings designate specific operating system products.
Ex. 2. System includes intelligent RAID controller
|
|
Windows 2000 Server
|
Advanced Server, Datacenter Server
|
Small Business Server
|
Basic Server:
|
Recommended
|
Required
|
Recommended
|
SOHO:
|
Optional
|
Required
|
Optional
|
Enterprise:
|
Required
|
Required
|
Required
|
|
An intelligent Redundant Array of Independent Disks (RAID) controller provides the benefit of reduced demands on the host processor or processors….
|
The following represents some of the information resources, services, and tools available to help build hardware optimized to meet the requirements defined in this guide. This section also lists technical references for the specifications cited in this guide.
A specific hardware model is compatible with Windows 2000 if it has a Windows 2000 device driver designed to interact with that hardware model, and if Windows 2000 and that driver interoperate with the hardware in a stable manner.
Hardware Compatibility Tests (HCTs). Microsoft evaluates hardware compatibility using the Windows 2000 HCTs, which are run to test the interaction between device drivers and hardware. These tests issue the full range of commands available to applications and operating system software, and they stress hardware beyond the level of most real-world situations. The Windows 2000 HCT team runs the tests and reports results to the manufacturer. You can obtain a Windows 2000 HCT kit from the Windows Hardware Quality Labs (WHQL) web site at http://www.microsoft.com/hwtest/testkits/.
Hardware Compatibility List (HCL). Hardware that passes the HCTs is eligible to be included on the Windows 2000 HCL, available to customers by way of the World Wide Web and other sources. The HCL helps interested parties identify hardware and software that has been verified to run on Windows 2000 Server.
WHQL administers the hardware compliance testing programs at Microsoft. Hardware developers whose products pass the WHQL testing program receive a detailed report about how the system runs Windows 2000 Server based on the results of the testing. Hardware that passes testing is included on the Windows HCL at http://www.microsoft.com/hcl/.
Compliance Dates. Typically, these hardware design requirements go into effect on July 1, 2001, and are applicable to servers that are designed and built after this document’s initial publication date. Compliance testing for some requirements may begin later because of the time required for technology changes to become widely available. For information about actual compliance testing dates for specific requirements, or about any of the hardware testing programs at Microsoft, contact WHQL:
Windows Hardware Quality Labs Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399 USA
|
http://www.microsoft.com/hwtest/
E-mail: whqlinfo@microsoft.com
Fax: (425) 703-3872
|
Share with your friends: |