M $ test plan Overview-Chapter 4th-software and hardware configuration

The following sections describe the software and hardware configurations used by the MSM testing team when setting up their testing lab environment. This example is an enterprise data center, just like the environment described in the Microsoft solution Architecture Specification document. Basic Management Service

In order to manage the server, in addition to ignoring the design and implementation of the management infrastructure, several key services need to be installed on the server. These key services include:

•	Hardware proxy. This service is usually included when you purchase servers, and can only manage specific hardware, such as Compaq Insight Manager for Compaq servers. The hardware agent is required to manage and configure hardware-specific components, such as a disk controller or network interface card (NIC ). In some cases, you can configure the hardware proxy to record Windows NT Event Logs when exceptions occur. Windows NT events are subsequently monitored and collected by the event management system (such as mom) for centralized management.
•	SNMP service.Simple Network Management Protocol (SNMP) is a network management standard used to help administrators manage remote networks that use Transmission Control Protocol/Internet Protocol (TCP/IP. SNMP has two main elements: SNMP proxy and SNMP management system. These two elements communicate by using Internet Protocol (IP) routing messages. One of the types of SNMP messages is the SNMP Trap. When the SNMP Agent detects a specific event of a managed element, the SNMP agent sends an unsolicited message to the management system, that is, the SNMP Trap. For example, the SNMP proxy on the vro sends a trap when the system detects a problem with the network interface. Windows Server 2003 contains the SNMP proxy component. If you execute the SNMP management applicationProgramTo enable the service.
•	WMI Service. Windows management instrument (Wmi) is a powerful infrastructure tool that inserts data into a database (Knowledge Base) statically) and dynamically construct these two types of layers at runtime to provide management data and management methods. You can search management instances by using a rich set of object models (called com. You can use the unique path (Object Path) of a single instance to address it to retrieve data (instance), or use the WMI query language (WQL) run queries to retrieve data (instances). The WMI query language is a subset of the industry standard Structured Query Language (SQL. For administrators, the common way to collect system information is to use a single instance or a collection of instances returned by WMI. In addition, the system administrator can use WMI to monitor network events, such as unexpected service shutdown, service shutdown on the server, or 80% disk space usage. WMI supports event detection and submission to event users.
•	Terminal Service.Windows Terminal Service provides remote access to the server desktop. It uses thin client software (used as a terminal simulator) to provide services. The terminal service only transmits the user interface of the program to the client. The client then returns the keyboard and mouse operations to the server for processing. Each logged-on user can only see his/her own sessions, which are managed transparently by the server operating system and independent from any other client sessions. Many client hardware devices can run client software, including computers and servers that provide Terminal Services Based on Windows platforms. Other devices, such as Macintosh computers or UNIX-based workstations, can also use additional third-party software to connect servers running Terminal Services. Terminal Services can be deployed on servers in Application Server mode or remote management mode. As an application server, Terminal Services provide an effective and reliable solution to use network servers to publish Windows-based programs. In the Application Server mode, Terminal Services Send Windows 2000 desktops and the most common Windows-based applications to computers that may not run properly. When the terminal service is used for remote management, it allows you to access the server from any node in the network to manage your server.

Software requirements

The following lists the software configurations used in the MSM test lab environment:

•	Microsoft Windows preinstallation environment (Windows PE) is the smallest Operating System Based on Windows XP kernel. Windows PE can functionally replace Microsoft MS-DOS and contains the minimum functionality required to run Windows installations, scripts, custom installers, and image processing applications.
•	Windows Server 2003.
•	Windows Server 2003 automated deployment service (ADS ).
•	Microsoft Operations Manager (MOM) Server SP1.
•	Microsoft Systems Management Services (SMS) Server 2.0 SP5.
•	Microsoft Software Update Services (SUS) SP1.
•	Windows terminal service.
•	Exchange 2000 Server.
•	Exchange 2000 Server Service Pack 3.
•	SQL Server 2000.
•	SQL Server 2000 Service Pack 3.
•	Microsoft Internet Security and Acceleration (ISA) server.
•	ISA Service Pack 1.
•	The test tool listed in the following test tools section.
•	The following are the Windows Server 2003 Resource Kit tools listed in the Windows Server 2003 Resource Kit tool chapter.
•	The following Windows Server 2003 support tools are listed in the Windows Server 2003 support tools section.

Hardware requirements

The following table describes the hardware configurations used in the Microsoft test lab environment:

•	26 ProLiant dl360 G2 Server
•	5 ProLiant dl360 G1 Server
•	4 ProLiant dl360 G2 Server
•	10 client computers
•	1 Sha box with MSA 1000
•	Vswitch with 170 ports
•	Connect to the internet's direct Internet tap Server

Management Architecture

The management architecture is based onManagement Architecture Guide. Details of different components and examples of individual sites are collected and sorted inManagement Architecture guide.

Test procedure

The MSM testing team executes three independent test procedures to identify, identify, and correct failures and ensure that all solutions work perfectly in the production environment. The test procedure is as follows:

•	Formal test process. Run all test cases in the integrated test environment.
•	Regression testing processTest all failed test cases again in the integrated test environment.
•	Pre-production test process.Re-test the entire test plan in the pre-production environment.

Integration Test entry criteria

To enable the MSM testing team to perform integrated testing of the scheme, the following entry criteria must be met:

•	Unit tests are required for individual services.
•	The lab already has the required special hardware.
•	The test plan document needs to be reviewed and approved by the development team.
•	The test cases and expected results need to be documented and approved by the test Manager and the development team.

In an integrated testing environment, the MSM testing team subsequently received and executed two testing procedures. The construction of this lab is as close to the production environment as possible to identify special problems in the network and modify the plan accordingly. The first test process mainly tests the quality of the documents and architecture to be put into trial use. The 2nd testing procedure was a retrospective test to identify defects in the first test procedure. 3rd integration test procedures should be performed in the MSA lab environment, which is a simulated pre-production environment.

Test release conditions

The main criteria for testing the release are largely determined by the severity of the defects found during the testing phase. All potential defects that may threaten the successful deployment of the MSM can be corrected, and the test can continue only after being verified in the test. All major document errors found during document review are corrected before the MSM document can be published. Special conditions are as follows:

•	No public security vulnerabilities 1 and 2.
•	All documents should not be annotated or revised.
•	All detected defects have been screened by the MSM testing team, and the impact of the defects on the plan has been fully studied.
•	The test case has successfully passed all three test procedures.
•	All external reviews have been completed and all problems have been solved.

Test Case qualification/non-conformity Conditions

If the actual test results are consistent with the expected results recorded in the document, it is determined that the test case has passed the test. If the actual results do not match the expected results, it indicates that the instance has not passed the test and an error has occurred.

If the test case does not pass the test, the functional defects cannot be determined. For example, the test fails if the project document is not complete or the document is inaccurate. Analyze each failure based on the results and actual results described in the project document to find the cause. More criteria are as follows:

•	No unexpected error occurs during all processes.
•	All processes are completed within the allowed time range according to the benchmark specified in the function description.
•	The load test shows that the load level is satisfactory and, if necessary, the system can be expanded through appropriate steps.

Severity Level

The following table lists the criteria for determining the severity levels of defects. The severity of a defect is measured by 1 to 4 levels. Among them, Severity Level 1 indicates the highest level and Level 4 indicates the lowest level.

Table 8 defect severity criteria

Severity	Description
1	Critical defects. The system does not work. The valid part of the system cannot be operated and there is no available workspace.
2	Serious defects. The system cannot meet basic business requirements and there is no convenient workspace available. Severe performance, functionality, or usage failures.
3	General defects. The system can meet business requirements. A quick and convenient workspace is available. Performance, functionality, or usage are not seriously unsatisfactory.
4	Minor defects. Minor changes. If you want to make suggestions, you 'd better correct the changes, but not necessary. There is no significant impact on release accuracy or practicality.

Test Tool

the following are the testing tools used by the MSM testing team in the test of the MSM Protocol:

•	product studio. the bug tracking tool used by the MSM team. This is an internal tool used to track bugs.
•	Test Management System. is an internal tool used to coordinate, record, and track all test activities.
•	adtest. Microsoft internal tool developed by the Windows 2000 performance team. This tool is used to generate loads in Active Directory.
•	Print stress. the Microsoft internal tool is used to generate load on the printing server.
•	ntbench. is a software tool that represents the disk data transmission performance.
•	WAN Simulator. hardware devices or software tools can simulate various network speeds, bandwidths, latencies, and conductivity.

Tools supported by Windows Server 2003

Windows Server 2003 support tools help Microsoft technical support staff and network administrators diagnose and resolve computer faults.

For details about these tools, refer to the following URL. These tools are located in the i386 folder of Windows Server 2003 installation CD.

Windows Server 2003 resource toolkit

The Windows Server 2003 Resource Kit provides a detailed description of the operating system and its configuration, and provides a complete set of tools to help enterprises manage and optimize the use of Windows Server 2003 technology. For more information about the resource kit, visit http://www.microsoft.com/windowsserver2003/techinfo/reskit/resourcekit.mspx.