The following sections describe the software and hardware configurations used when setting their test lab environments. This example is a corporate data center, just like the environment introduced in the Microsoft Solutions Architecture Document.
Basic management service
In order to be able to manage the server, in addition to ignoring the design and implementation of the management infrastructure, there is a need to install a few key services on the server. These key services include:
• Hardware proxy. This service is usually included when purchasing a server, and usually only manages specific hardware, for example, Compaq Insight Manager for the Compaq server. The Hardware Agent will be required to manage and configure a component for hardware, such as a disk controller or network interface card (NIC). In some cases, you can configure the hardware agent to record the Windows NT event log when an exception occurred. The Windows NT event is then monitored by an event management system (such as MOM) and collects it together for centralized management. • SNMP service. Simple Network Management Agreement (SNMP) is a network management criteria that helps administrators manage remote networks using Transmission Control Protocol / Internet Protocol (TCP / IP). SNMP has two main elements: SNMP proxy and SNMP management system. These two elements communicate by using a routing message using the Internet Protocol (IP). One of the types of SNMP messages is the SNMP trap. When the SNMP agent detects a specific event, the SNMP agent sends an unsolicited message to the management system, that is, the SNMP trap. For example, when a proxy detects a problem with a network interface, the SNMP agent on the router sends a trap. Windows Server 2003 already includes SNMP proxy components. If you execute a SNMP administrative application, you need to enable this service. • WMI service. Windows Management Instrument (WMI) is a powerful infrastructure tool that provides administrative data and management methods by static inserting databases (knowledge bases) and dynamic constructing in runtime. Using a rich object model, that is, the intensive component object model (COM) interface can be retrieved by an instance of the management class. You can use a single instance unique path (object path) to retrieve data (instance) to retrieve data (instance), or you can retrieve data (instance), WMI query language is industry standard by running query using WMI Query Language (WQL). Structured Query Language (SQL) subset. For administrators, the usual practice to collect system information is a collection of single instances or instances returned by WMI. In addition, the system administrator can use WMI to monitor events in the network, for example, an unexpectedly stopped service, the server stops providing service or disk space has used 80% of events. WMI support provides event detection and submit to event users. • terminal service. Windows Terminal Services provides a remote access server desktop service that utilizes thin client software (used as a terminal simulator) to provide services. Terminal Services only transmits the user interface of the program to the client. The client then returns the keyboard and mouse operation to the server for processing. Each login user can only see his / her own session, which is transparently managed by the server operating system and is independent of any other client session. Many client hardware devices are able to run client software, including a computer and a Windows platform-provider server. Other devices, such as a Macintosh computer or a UNIX platform-based workstation, can also be connected to a server running a terminal service through additional third-party software. Terminal services can be deployed in the server in an application server mode or remote management mode. As an application server, in order to be able to release Windows-based programs using the web server, the terminal service provides a valid and reliable solution. In Application Server Mode, Terminal Services sends a Windows 2000 desktop and the most common Windows-based application to a computer that may not function properly in WINDOWS.
When the terminal service is used to remotely, it allows you to access the server from any node in the network to manage your server. Software requirements
The following list describes the software configuration used in the MSM test lab environment:
• Microsoft Windows Preinstallation Environment (Windows PE) is a minimal operating system based on a Windows XP kernel. Windows PE can be functionally replaced with Microsoft MS-DOS, and include the smallest features required to run a Windows installation, script, custom installer, 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 Services. • 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 tools listed in the following test tool chapters. • The following is the Windows Server 2003 Resource Toolkit tool listed in the Windows Server 2003 Resource Toolkit Tools section. • The Windows Server 2003 support tools listed in Windows Server 2003 support tool chapters.
Hardware requirements
The following table illustrates the hardware configuration used in the Microsoft test laboratory environment:
• 26 ProLiant DL360 G2 Server • 5 ProLiant DL360 G1 Server • 4 ProLiant DL360 G2 Server • 10 Client Computers • 1 MSA 1000 Sandbox • Switches for 170 ports • Direct Internet TAP Server connected to Internet
Management architecture
The management architecture is built in accordance with the management architecture guide. Details of different components and examples of individual sites are collected in the Management Architecture Guide.
Test process
The MSM test team performs three independent test processes to discover, determine and correct failures, and ensure that all solutions can be perfectly run in the production environment. These test processes are as follows:
• The formal test process. Run all test cases in an integrated test environment. • Regression test procedures retest all failed test cases in an integrated test environment. • Pre-production test flow. Retest the entire test plan in the pre-production environment.
Integrated test entrance conditions
In order to allow the MSM test team to integrate the scheme, the following entrance conditions must be met:
• Individual services require unit testing. • There is already a special hardware you need in the laboratory. • Test plan documents need to be reviewed and approved by the development team. • Test cases and expected results need to be prepared as documentation and approved by the test manager and development group.
In an integrated test environment, the MSM Test Panel subsequently received and implemented two test processes. The construction of this laboratory is as close as possible to the production environment in order to find special problems in the network and modify the plan. The first test process mainly tests the quality of the trial document and architecture. The 2nd test process is to retrospectively, to determine the defects in the first test process. Article 3 Integrated Test Processes To be implemented in the MSA laboratory environment, this environment is a simulated pre-product environment.
Test issuance
The main conditions that can be released have largely dependent on the severity of the defects found in the test phase. All potential defects that may threaten MSM successfully deployed, and then the test can continue after the test is verified. After all major document errors found during the document review, the MSM documentation can only be released. Special conditions for use are: • There is no public security loopholes 1 and 2. • All documents should have no comments or revisions. • All discovered defects have been screened by the MSM test team, and the impact of defects has been fully studied. • Test cases have successfully passed all 3 test processes. • All external reviews have been completed and all questions are resolved.
Qualified / unqualified conditions of test case
If the actual result of the test is consistent with the expected results of the document record, the test case has been tested. If the actual result is not consistent with the expected results, the instance has not passed the test and has been laminated.
If the test case does not pass the test, it is not possible to determine the functional defect. For example, misunderstanding, document incomplete or documentation is caused to fail. Each failure is analyzed based on the results and actual results described in the project document to find their causes. More qualified standards are as follows:
• No accidental errors occur during all processes. • All processes are completed within the allowable time range as specified in the function description. • The load test shows that the load level is satisfactory, and the system can be expanded by the appropriate steps if necessary.
Defect severity level
The following table lists the criteria for dividing defects. Defect severity is measured from 1 to 4 levels, with severe level 1 represents the highest level and level 4 represents the lowest level.
Table 8 Defects Severity Standard
Severe indication 1 fatal defect. The system does not work. The effective part of the system cannot operate and does not have a work area available. 2 serious defects. The system cannot meet basic business requirements and have no convenient workspace. Severe due to performance, function or use. 3 General defects. The system can meet business requirements. There is a quick and convenient work area for use. Performance, functionality or use is not serious. 4 tiny defects. Micro modification, I hope to make recommendations, it is best to correct it, but it is not required. Will not have a significant impact in terms of accuracy or practicality.
test tools
The following is a test tool for the MSM test team in the test MSM program:
• The bug tracking tool used by the Product Studio. MSM group. This is the internal tool used to track bugs. • Test Management System. To coordinate, record, and track internal tools for all test activities. • Adtest. Microsoft internal tool developed by the Windows 2000 Performance Group. This tool is used to generate a load in Active Directory. • Print Stress. Microsoft Internal Tools to generate a load on the print server. • NTBENCH. Software tools used to express disk data transfer performance. • WAN Simulator. Hardware devices or software tools simulate various network speeds, bandwidth, delay, and conductivity.
Windows Server 2003 Support Tools
Windows Server 2003 Support Tools can help Microsoft technical support staff and network administrators diagnose and resolve computer failures.
Details about these tools can be found at http://www.microsoft.com/resources/document/prodowsserv/2003/datacenter/proddocs/en-us/suptools_overview.asp. These tools are located under the I386 folder of Windows Server 2003 installation CD.
Windows Server 2003 Resource Toolkit Tool
