M $ test plan Overview-Chapter 1st-Introduction

Purpose

The basic purpose of this document is to provide a plan and policy for organizations that use Microsoft Solutions for Management (MSM) to manage their Microsoft Windows Server 2003 environment, design and implement test solutions in a test lab environment. Initial tests enable information technology (IT) managers to confidently believe that solutions can play a role in their production environments.

This document describes the advanced test objectives, test scopes, and test strategies adopted by the MSM testing team to verify the instances of the MSM 2.0 solution in the MSM lab. This information should be used as a template so that IT managers can use it when designing, setting up, and operating their own test environments. Together with this document, we also provide a workbook of test case details, which provides the detailed information required to execute the test cases used in this test plan, the results obtained by the MSM testing team during their testing lab are also provided. Test Case Details workbooks can download http://go.microsoft.com/fwlink/ in the following locations? Linkid = 20211.

Target object

This document is used by IT practitioners, IT managers, and consulting companies responsible for designing and managing Windows Server 2003 product environments, and before deploying recommended solutions in their environments, measure the test taker's knowledge about the MSM testing method.

Anyone using this document should be familiar with the design and management concepts of the Windows Server 2003 series product environment, as well as Microsoft management technologies and products, such as Microsoft Software Update Service (SUS) microsoft System Management Service (SMS), Microsoft Operation Manager (MOM), and Microsoft Terminal Service. In addition, users should be familiar with and be able to use Microsoft's MOF processes, groups, and risk models.

Execution Overview

For organizations planning IT projects, they focus mainly on implementation and consider planning and pre-deployment as a secondary task for quickly benefiting from the Organization's investment, this is a common situation. A large number of similar projects have failed, but it is not because of major technical problems or defects. This is due to lack of knowledge about how technology works.

To avoid failure, the Organization should determine how the product or solution works, verify their assumptions about it, And before deploying it, ensure that any Molding Design meets business needs.

In short, organizations need to test products and solutions before they use them.

Ensure that products and solutions work as expected, verify that technical support staff understand how it works, and that the place where technical design works is not in the production environment, but in the test lab.

In the test lab, technicians can observe the design in operation, change configuration settings, and precisely adjust the design to ensure optimal performance, without affecting users. Testing minimizes risks, provides technical support staff with the skills and experience they need, and reduces the cost of poor design.

When executed in a testing lab simulating a customer's production environment, the tests mentioned in this document help to ensure a high degree of reliability in the solution and the skills and capabilities involved.

Participants

ProgramManager

Jeff yuhas,Microsoft Corporation

Lead author

Venugopal sankarapillai,Infosys Technologies Ltd.

Other participants

Ipshita nag,Infosys Technologies Ltd.

Test Manager

Greg gicewicz,Microsoft Corporation

QA manager

Jim ptaszynski,Microsoft Corporation

Lead technology author

Jerry Dyer,Microsoft Corporation

Technical author

Sheila hunter,Volt Technical Services

Chief Technical Editor

Laurie Dunham,Microsoft Corporation

Edit

Patricia rytkonen,Volt Technical Services

Christine waresak,VMC Consulting

Product editing

Kevin klein,Volt Technical Services

The information contained in the document represents the current views of Microsoft Corporation on the issue discussed at the date of publication. Microsoft does not guarantee the accuracy of the information given after the date of publication because Microsoft must comply with the changing market conditions.

This document is only used to provide information. Microsoft does not provide any express, implied or statutory warranty for the information in this document.

It is the user's responsibility to comply with all applicable copyright laws. Without the prior written consent of Microsoft, no part of this article shall be reproduced or disseminated for any purpose, in any form or by means (electronic, mechanical, photoprinting, recording, etc, it cannot be stored or imported into the retrieval system.

This document may involve Microsoft patents, patent applications, trademarks, copyrights and other intellectual property rights. Unless expressly provided by Microsoft through a written license agreement, this document does not give you any license to these patents, trademarks, copyrights or other intellectual property rights.

Unless otherwise stated, the companies, organizations, products, domain names, email addresses, logos, people, locations, and events described here are fictitious, it shall not be in connection with any real company, organization, product, domain name, email address, logo, person, location, or event, nor shall it conduct any speculation or inference based on this.

2003 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, windows, and Windows Server are registered trademarks or trademarks of Microsoft Corporation in the United States and (or) other countries.

The actual company and product names involved here may be trademarks of their respective owners.