UGSI – Unisys Global Services-India

Test Plan for SCCM Implementation

Version 1.0
Author: UGSI
 Test Plan for SCCM Implementation

Statement of Confidentially
Confidentiality of customer information is the paramount objective of Unisys. The information
contained in this document is proprietary and confidential in nature. This specifically includes
pricing information, methodology, materials, and consulting documents as may be described.

No part of this document may be reproduced in any form, including photocopying or

transmission electronically to any computer, without prior written consent of Unisys Corporation.
The information contained in this document is confidential and proprietary to Unisys Corporation
and may not be used or disclosed except as expressly authorized in writing by Unisys
Corporation.

Trademarks
Unisys is a registered trademark of the Unisys Corporation.

Product names mentioned in this document may be trademarks or registered trademarks of

their respective companies and are hereby acknowledged.

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 2 of 10

 Test Plan for SCCM Implementation

I. Document information

Filename Test Plan for SCCM

Document reference
Version Version 1.0
Last change Date & Time
Status
Saved by UGSI

II. Version

Version Date Author Change

1.0 05.11.2008 UGSI First Draft version

III. Document reference

Nr. Title Reference

IV. Distribution list

Name Company Responsibility Task

V. Sign off

Name Date Signature

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 3 of 10

 Test Plan for SCCM Implementation

TABLE OF CONTENTS

1. ACTIVITIES DURING THE PLANNING PHASE 5

1.1 DEFINE TESTING SCOPE AND OBJECTIVES:.............................................................................................................5

2. PREPARATION OF TEST LABS 5

2.1 PLANNING CHECKLIST.......................................................................................................................................5

2.2 PREPARE THE TEST SCHEDULE.............................................................................................................................6
2.3 IDENTIFY REQUIRED TEST TYPES..........................................................................................................................6
2.4 DETERMINE THE TEST STRATEGY.........................................................................................................................7

3. CONFIGURATION MANAGER PERFORMANCE COUNTERS 8

4. BUG RATING, REPORTING, AND TRACKING 10

5. CHANGE CONTROL 10

6. Risks and Dependencies 10

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 4 of 10

 Test Plan for SCCM Implementation

1. Activities during the Planning Phase

Activities during the Planning Phase are crucial to the success of the testing process. The Test
feature team plans its test activities and determines its strategies in part by examining the
interaction among and operational effectiveness of the organization, its users, and internal IT
processes in addition to the business goals defined for the Implementation.
Define Testing scope and objectives:
This will include vision scope approval for the testing plan. Before the actual implementation of the
servers implementation team need to perform lab testing as per the Numonyx requirement. The
scope will be testing the following process in the lab environment:
 Installation of SQL 2005 SP2
 Installation of SCCM R2 Version
 Configuration of SCCM
 Deployment of Operating System, Application and Software Updates.
 Checking the performance of the SCCM Server

2. Preparation of Test Labs

1. Hardware Configuration of physical Server
 2 CPU’s Intel Xeon with a L3 cache sized to 1 MB and a minimum clock frequency of
2 GHz,
 4 GB of dynamic RAM memory DDR,
 CD-ROM or DVD reader,
 2 disks 300 GB unformatted with Ultra SCCI interface and 10,000 or 15,000 rpm
rotation speed,
 1 Ethernet 10/100 Mbps embedded network cards,

2. Software Configuration
 SQL 2005 SP2
 SCCM R2 Version
 SQL Std edition 2005 64bit
 Windows Server 2008
 Windows Server 2003
 Virtual Server 2005

3. Lab Server Details

 SCCM R2 will be installed on Physical server 64bit edition along with SQL 2005 SP2.
 One virtual server - windows 2003 AD

Planning Checklist
The Test feature team must determine specific aspects of the test process. These include the test
strategy, the required tests for their environment, creating a test plan, and preparing a test
schedule to keep things in line with the overall timeline of the project.
Author : UGSI Status: Yet to Approve
Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 5 of 10

 Test Plan for SCCM Implementation

Prepare the test schedule

This step includes the following tasks:

1. Test environment setup : SCCM Implementation Team

2. Documentation review : Implementation Team (Ganga, Lakshmi & Ismail)
3. Preparation of high-level test scenarios : This will include configuration of SCCM, Package
Testing & OSD and performance counters
4. Test execution : Once the lab server are in place, ready to go with test execution
5. Number and duration of test cycles :
 Installation of SQL 2005 SP2 and Monitoring: 2 Days
 Installation of Windows Server and SCCM – 1 Day
 Monitoring of SCCM installation and all its components: 2 Days
 Testing the OSD & Application Package – 3 Days
 Software update & Testing Progress Update : 2 Days

Identify required test types

Determine which test types are required.

The following tests will be carried out:

1. Unit testing: The first test type focuses on the analysis of a single deployment component.
As they prepare to build the overall deployment project, team members from each feature
team begin analyzing the components for which they are responsible. At this point, team
members often install these components in isolated environments to validate the
components’ capabilities. This test type is often performed by individuals on a single
computer.

Note: Unit testing will carried out per application basis like SCCM, Application Server in our
lab environment

2. Functional testing: After the individual teams become more familiar with the technological
components for which they are responsible, they move on to functional testing—validation
that products and components work as designed. Guidance for this test type is derived from
the functional specifications of the overall project.

Note: This will be carried out for Multipurpose Server Testing during our testing process

3. Pilot and production testing: The final stage of testing often involves the same components
used in production. When the teams implement the deployment project in an actual
production environment, they begin with a pilot deployment—targeting a small, representative
population of users in the production environment to perform a final validation of all of the
implementation strategies and procedures before deploying the system to the entire
production environment. This test type focuses more on training, communications, and
support strategies than on actual technological strategies, although these are also validated.
Pilot testing is linked to production testing, because if all goes well, the technologies and
components introduced for the pilot program become the components used in full production.

Note: This will be carried during first phase of implementation in the production environment

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 6 of 10

 Test Plan for SCCM Implementation

Determine the test strategy

In this test strategy implementation unit will create step-by-step directions that outline how to
perform an activity for the preparation of each test type.

This test plan involve of implementation team which is segregated into sub teams:

a. SCCM Implementation Team (Ismail, Nagendra & Lakshmi)

b. Application Packaging Team (Kiran & team) and
c. Management Team

Sr.No Task Owner Scheduled Status Remarks

Date
1 Installation test SCCM
servers Implementation
Team
2 Installation IIS, WDS SCCM
& MS Deployment Implementation
Toolkit on SCCM Team
test Server
3 Installation of SQL SCCM
2005 Implementation
Team
4 Installation of WSUS SCCM
Implementation
Team
5 Installation & SCCM
Configuration SCCM Implementation
R2 Team
6 Deployment of Application
Operating System Implementation
Image Team
7 Distribution of Application
Application Package Implementation
Team
8 Distribution of Application
Software Update Implementation
Team
9 Monitoring the SCCM
Performance Implementation
Team
10 Review of testing Management &
process Implementation
Team

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 7 of 10

 Test Plan for SCCM Implementation

3. Configuration Manager Performance Counters

Performance Monitoring will be carried during the course of OSD and distribution package during
pilot test.

Performance Performance Data to be Monitored

Counter Category Counter : Instance
Processor % Processor Time : Average CPU for all cores.
Total
Process % Processor Time : Configuration Manager main process CPU usage.
smsexec
Process % Processor Time : SQL Server instance CPU usage.
sqlservr
Physical Disk Avg. Disk Queue Select one of these counters for each volume that is involved
Length : Volume in Configuration Manager processes. This includes the
operating system installation volume, ConfigMgr installation
(inbox) volume, as well as the SQL Server tempdb, site
database, and log volumes.
Physical Disk % Disk Time Select one of these counters for each volume that is involved
in Configuration Manager data processing. This includes the
operating system installation volume, ConfigMgr installation
(inbox) volume, as well as the SQL Server tempdb, site
database, and log volumes.
SqlServer:General Temp Tables General SQL Server statistics.
Statistics Creation Rate
SqlServer:General Logouts/sec General SQL Server statistics.
Statistics
SqlServer:General Logins/sec General SQL Server statistics.
Statistics
SqlServer:SQL SQL Re- General SQL Server statistics.
Statistics Compilations/sec
SqlServer:SQL SQL General SQL Server statistics.
Statistics Compilations/sec
SqlServer:SQL Batch Requests/sec General SQL Server statistics.
Statistics
SqlServer:Memory Lock Memory General SQL Server statistics.
Manager
SQLServer:Locks Lock Requests/sec General SQL Server statistics.
SQLServer:Locks Number of General SQL Server statistics.
Deadlocks/sec
SqlServer:Databases Transactions/sec : General SQL Server statistics.
SCCM db
SqlServer:Databases Transactions/sec : General SQL Server statistics.
Wsus Db
SMS Discovery Data Total DDRs Configuration Manager discovery data record processing
Manager Processed rates.
SMS Discovery Data DDRs Current discovery data record processing rate.
Manager Processed/min
SMS Discovery Data Total Client Client registrations processed.
Manager Registration

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 8 of 10

 Test Plan for SCCM Implementation

requests Processed
SMS Discovery Data Total Bad DDRs Bad Configuration Manager discovery data record
Manager Processed processing rates.

Performance Counter Performance Data to be Monitored

Category Counter : Instance
SMS Inbox File Current Count Provides a count of the files in each inbox that are queued for
processing. This counter is updated every 15 minutes by
default.
List of Instances for this performance counter:
 Auth\statesys.box>incoming (state system)
 Auth\sinv.box (software inventory)
 Auth\ddm.box (DDRs)
 Auth\ddm.box>regreq (client registration requests)
 Auth\dataldr.box (hardware inventory)
 Statmgr.box\statmsgs (status messages)
 Distmgr.box\incoming (distribution manager)
 Colleval.box (collection evaluator)
 Swmproc.box\usage (software metering usage)
SMS Inventory Data Total MIFs Hardware inventory report processing.
Loader processed
SMS Inventory Data MIFs Hardware inventory report processing.
Loader Processed/min
SMS Inventory Data Total Bad MIFs Hardware inventory report processing.
Loader Processed
SMS Software Total SINVs Software inventory report processing.
Inventory Processor Processed
SMS Software SINVs Software inventory report processing.
Inventory Processor Processed/Min
SMS Software Total Bad SINVs Software inventory report processing.
Inventory Processor Processed
SMS Software SWM Usage Software metering data processing.
Metering Processor Records
Processed/min
SMS Software Total SWM Usage Software metering data processing
Metering Processor Records Processed
SMS Software Total Bad SWM Software metering data processing.
Metering Processor Usage Files
Processed
SMS State System Summary Task State system processing.
Running
SMS State System Message Files State system processing.
Processed/min
SMS State System Message records State system processing.
processed/min
SMS State System Total Bad Message State system processing.

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 9 of 10

 Test Plan for SCCM Implementation

Files Processed
SMS State System Total Invalid State system processing.
Message Records
Processed
SMS Status System Processed/sec : Status message processing.
Total
SMS Status System Corrupt : Total Status message processing.
SMS Status System Written to SMS Status message processing.
Database : Total

4. Bug Rating, Reporting, and Tracking

The Test feature team develops the method for reporting and tracking bugs. The mechanism for bug
reporting and tracking must include features that allow the Test feature team to assign bugs to the
right person or team, prioritize bugs, assign severity numbers to them, reopen closed bugs, link bugs,
generate different views of the same bug, and create reports. The Test feature team is also
responsible for developing a process for bug triage and creating a schedule to track the status of all
test bugs.

5. Change Control
Change control ensures that the core team is aware of and agrees to any changes to lab hardware or
software. The Test feature team follows the change control process established by the lead team and
that is used . The test lead must post the status of hardware and software in the lab, in addition to the
testing schedules, so that the various feature teams are aware of all lab activity. The test lead must
also have procedures in place to restore the lab to its original state at the completion of the project.

6. Risks and Dependencies

The Test feature team typically looks for and assesses the following types of risks, and then factors
them into the test plan and test schedule:

Lab requirements, based on the development plan, might exceed the Test feature team’s budget and
time allocations. The test lab build might not have been completed by the start of the Stabilizing
Phase because of an inability to procure and install all of the lab equipment. The test lab does not
properly reflect the production environment. For example, it might not include proper firewall
configurations or even all of the Group Policy objects (GPOs) found in production. The goal is to
make the test lab as similar to production as possible.

Note: In our environment we can’t identify any risk till we do test implement and if any sort of risk
or dependencies required that will be updated to the management team after doing proper
analysis

Author : UGSI Status: Yet to Approve

Version: 1.0

Saved: 3/22/2022 09:22:00 AM Page 10 of 10