Tài liệu Module 3: Designing a Software Distribution and Management Strategy ppt

Contents

Module 3: Designing a
Software Distribution
and Management
Strategy

Overview

1

Determining Current Software Distribution
Strategy

2

Determining Software Distribution and
Management Needs

7

Evaluating Software Distribution and
Management Options

10

Selecting Software Distribution and
Management Options

17

Lab A: Meeting Organizational Software
Requirements

24

Review

32


Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the example companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, e-mail address,
logo, person, places or events is intended or should be inferred. Complying with all applicable
copyright laws is the responsibility of the user. Without limiting the rights under copyright, no
part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
 2001 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Active Desktop, Active Directory, IntelliMirror,
Outlook, PowerPoint, and Visio are either registered trademarks or trademarks of Microsoft
Corporation in the U.S.A. and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.

Module 3: Designing a Software Distribution and Management Strategy

iii

Instructor Notes
Presentation:
75 Minutes
Lab:
45 Minutes

This module examines how to identify current software distribution and
management methods and determine future software management needs.
Students evaluate four different software deployment technologies to determine
whether those technologies address the organizational needs and which ones are
appropriate to include in a Change and Configuration Management (CCM)
design.
After completing this module, students will be able to:



Determine how the organization currently manages software distribution.




Determine how the organization must manage software distribution.




Evaluate possible software distribution options.

Select the appropriate options to meet their business needs.

Materials and Preparation
This section provides the materials and preparation tasks that you need to teach
this module.

Required Materials
To teach this module, you need the following materials:



Microsoft® PowerPoint® file 2410a_03.ppt




Module 3, “Designing a Software Distribution and Management Strategy”




Trainer Materials compact disc

Preparation Tasks
To prepare for this module:



Read all of the materials for this module.

Read the technical white papers located on the Trainer Materials compact
disc.




Read any relevant information in the Microsoft Windows® 2000 or
Microsoft Windows XP Help files, and the Windows 2000 Resource Kit or
the Windows XP Resource Kit.




Be familiar with the principles and practice of CCM.




Read the instructor notes that precede each module. These contain
preparation suggestions for each module.




Read the review questions and be prepared to elaborate on the answers
provided in the text.




Complete the lab and be prepared to elaborate on the solutions found there.


iv

Module 3: Designing a Software Distribution and Management Strategy

Module Strategy
Use the following strategy to present this module:



Determining Current Software Distribution Strategy
In this section, students learn how to gather the information required for an
analysis of the current software distribution and management environment.
In addition, students learn how to determine the organization’s current
methods, and technologies used for software deployment and management.
Take the following actions:
• Establish that the management of software distribution must be treated
as a process, from initial packaging through to final removal of
packages. As with all processes, it must be managed as a continuous
series of activities.
• The best way to collect information is to treat it as an update of a
software management information base, rather than to generate a new
report on current software management methods. Clearly, this would
require some prior planning on how the information base is implemented
and managed.




Determining Software Distribution and Management Needs
In this section, students learn how to identify the limitations and
disadvantages of current technologies, and how to identify the
organization’s future requirements. In addition, students learn how the
various CCM technologies can benefit the organization and how these
technologies can be mapped onto the organization’s requirements for

software distribution and management.




Evaluating Software Distribution and Management Options
In this section, students identify four different software deployment
technologies available for the distribution and management of software in
an organization. Students then assess the suitability of these technologies to
organizational requirements. Take the following actions:
• Ensure that students understand that available technologies are
constantly developing, and that new products may offer new capabilities.
• The Windows Installer Service is described here for the first time, as a
service that can be used by either Microsoft IntelliMirror® or Microsoft
Systems Management Server (SMS).




Selecting Software Distribution and Management Options
In this section, students identify the deployment technologies that are
suitable for specific organizational requirements. Take the following
actions:
• Acknowledge that selecting options means deciding whether
IntelliMirror is appropriate and sufficient. If not, SMS is the best choice.


Module 3: Designing a Software Distribution and Management Strategy

v

Lab Strategy

Use the following strategy to present this lab.

Lab A: Meeting Organizational Software Requirements
The lab is designed to assist the student in applying the information presented
in this module. Students are expected to have:



Experience with deploying software to client computers.




Basic experience or knowledge of the Active Directory™ directory service.




Basic experience or knowledge of Group Policy.




Basic experience or knowledge of SMS.




The knowledge and skills necessary to define and implement a software
distribution and management plan.

The lab has three scenarios, each of which is based on a company requiring
facilities for software distribution and management. In this lab, students will
review each scenario and determine organizational requirements. They will then
use information from the module to make a number of design decisions

concerning the software distribution and management plan. Students will also
be asked to explain how they arrived at those decisions.
To conduct this lab:



Read through the lab carefully, paying close attention to the instructions and
to the details of the scenario.




Divide the class into groups of two or more students.




Present the lab and make sure that students understand the instructions and
the purpose of the lab.




Explain each of the scenarios and highlight any key information.




Remind students to consider the relative merits of SMS and IntelliMirror
regarding software distribution and management, and to think about the
suitability of each option to the scenarios.




While students are completing the lab, take the opportunity to assess each

student’s comprehension of the technology features of SMS and
IntelliMirror presented in the module.




Allow some time to discuss the solutions after the lab is completed. A
solution is provided on the Trainer Materials compact disc. Encourage
students to look critically at one another’s solutions and to discuss any ideas
for improving the designs.



Module 3: Designing a Software Distribution and Management Strategy

1

Overview
Topic Objective

To provide an overview of
the module topics and
objectives.

Lead-in

In this module, you will learn
the principles of evaluating
software distribution and
management options based
on business needs, and the

current and planned
environment.




Determining Current Software Distribution Strategy




Determining Software Distribution and Management
Needs




Evaluating Software Distribution and Management
Options




Selecting Software Distribution and Management
Options

*****************************ILLEGAL FOR NON-TRAINER USE******************************
As the administrator or designer of your network, you will provide a plan for
distributing and managing the software on client computers.
The technologies available to deploy and manage software can reduce an
organization’s total cost of ownership (TCO) and can streamline the desktop
delivery and configuration of application packages.
This module examines how to identify current software distribution and
management methods and determine future software management needs. You

will evaluate four different software distribution technologies to determine
whether they address the organizational needs and which ones are appropriate
to include in your Change and Configuration Management (CCM) design.
After completing this module, you will be able to:



Determine how the organization currently manages software distribution.




Define a strategy based on how the organization needs to manage software
distribution.




Evaluate possible software distribution options.




Select the appropriate options to meet your business needs.


2

Module 3: Designing a Software Distribution and Management Strategy


Determining Current Software Distribution Strategy
Topic Objective

To identify the steps

required to determine the
organization’s current
software management
environment.




Determining Current Software Management Process




Collecting Software Management Information

Lead-in




Identifying Current Software Environment

It is important to determine
your existing environment to
identify where and how
different software
management technologies
can help your organization.

*****************************ILLEGAL FOR NON-TRAINER USE******************************
One of the first tasks to help you to create the software distribution and
management plan is the assessment and analysis of the existing software
distribution methods and environment.

In this section, you will learn how to gather the information that is required for
the analysis of the current software distribution and management environment.
In addition, you will learn how to determine the organization’s current methods,
and you will learn about technologies used for software deployment and
management.


Module 3: Designing a Software Distribution and Management Strategy

3

Determining Current Software Management Process
Topic Objective

To define the stages of the
software management
process.

Lead-in

Each organization has its
own approach, but any
approach involves standard
stages.




Packaging—Preparing an Application for Installation

Distribution—Replicating Package Files to Distribution
Points




Targeting—Specifying Which Client Computers Will
Receive the Package




Installation—Getting the Package onto the Client
Computer




Removal—Removing Old Applications

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Before you can successfully create and implement a software distribution and
management plan, you must be aware of the basic process flow that your
organization currently uses:



Packaging—preparing an application for installation
Packaging is the process of preparing an application to be installed by a
software deployment technology. This may involve third-party packaging
tools.

Distribution—replicating package files to distribution points
Distribution is the process of setting up and managing distribution points or
server shares where client computers can access the package, and replicating
the package files to those distribution points.




Targeting—specifying which client computers will receive the package
Targeting is the process of specifying which client computers must receive
the package. It also determines if the user or the computer is the target for
packages.




Installation—getting the package onto the client computer
Installation is the process of getting the package onto a computer in a
running or ready-to-run state. After a specific user or computer receives the
targeting information and package details, installation must occur to
complete the deployment.




Removal—removing old applications
Removal is the process of how the organization removes installed
applications from client computers. At some point, your users will no longer
require certain software, and you must know how to remove it.


4

Module 3: Designing a Software Distribution and Management Strategy

Collecting Software Management Information
Topic Objective

To explain how to determine
the organization’s current
methodology for software
distribution and
management.




Lead-in

To create a software
management strategy, you
must determine which
methods the organization
currently uses for software
distribution.

Collection Techniques



Questionnaires

Interviews




Brainstorming sessions

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Your CCM infrastructure plan for software management will include assessing
whether you can improve upon current methods by using the technologies that
this module identifies.

Collection Techniques
To determine the strategies mentioned previously, you must obtain information
from the relevant parties. This information must be useful, manageable, and
given in a timely manner to fit in with your plan schedule. You may decide to
gather the appropriate information in one or possibly all of the following ways:



Questionnaires




Interviews




Brainstorming sessions

The information that you collect will help you determine the effectiveness of
the current strategy and identify where new technologies may provide more

benefit to you. Collect and document the responses that you receive from these
methods in a document called a planning worksheet.


Module 3: Designing a Software Distribution and Management Strategy

5

Identifying Current Software Environment
Topic Objective

To explain how to define the
organization’s current
software management
environment.




Lead-in

To create a software
distribution and
management strategy, you
must gather information
about the existing software
environment.

Identifying Currently Used Software



Mandatory software




Optional software




Function-based software

Identifying the User Base



Locations of users




Numbers of users

Identifying Who Manages the Software

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Before you can implement a software distribution and management strategy,
you must understand the critical decision points in your current software
environment in relation to your future strategy for software distribution and
management. Document this information so that you can reference it when

making crucial decisions during your CCM infrastructure plan.

Identifying Currently Used Software
You must identify and document which software the organization currently
uses, and you must categorize it as follows:



Mandatory software
Some software in your organization will be required by all staff to carry out
functions that are common to them. Examples include an e-mail application
and virus detection software.




Optional software
You must determine which software is available for users to install when
they choose. Examples include standard applications like word processing,
spreadsheets, and graphics software. However, you must also determine
whether any users must be prevented from installing this software.




Function-based software
Some software in your organization will be purely functional and is
provided for a certain task based on the user’s job role or department. You
must determine which users and departments require which software. You
must also identify any software that is specific to a particular computer.


6

Module 3: Designing a Software Distribution and Management Strategy

Identifying the User Base
To implement a targeting strategy, you must identify the characteristics of the
user base to which you will distribute software.
To help develop your plan, identify the following:



Where users are located
You must identify the location of the users to whom you will distribute
software, particularly those who are in remote locations across slow wide
area network (WAN) links.




The number of users to whom you provide software
It is important to determine the number of people to whom you are
distributing software, identifying where the needs are greatest, and planning
and allocating the extra resources required to service the users. These
resources may include network bandwidth, administration staff, and
distribution servers.

Identifying Who Manages the Software
You must identify which Information Technology (IT) staff are involved in
providing support to users for software distribution and management so that
you can plan how many staff are required and where to locate them. This
information will also help you identify where you can target your resources
most effectively.
Document who is responsible for each stage of software distribution and

management, namely:



Preparation




Distribution




Installation




Removal

Note In some environments, non-IT staff may manage certain activities. For
example, users at remote locations may be responsible for installing and
removing applications. Also, you must consider the amount of time typically
spent on distributing and managing software.


Module 3: Designing a Software Distribution and Management Strategy

7

Determining Software Distribution and Management
Needs
Topic Objective

To identify the
organization’s requirements
for software distribution and
management.

1

PREPARATION
PREPARATION
2

Lead-in

You must understand the
organization’s goals for the
provision of software
distribution and
management.

DISTRIBUTION
DISTRIBUTION
3

TARGETING
TARGETING
4

INSTALLATION
INSTALLATION

5

REMOVAL
REMOVAL

*****************************ILLEGAL FOR NON-TRAINER USE******************************
It is vitally important that you understand the organization’s requirements for
the distribution and management of software to its users.
From these business needs you will be able to identify the drawbacks and
limitations of current methods, and the benefits that Microsoft®
Windows® 2000 technologies can bring to the organization.
In addition, you will learn how the various CCM infrastructure technologies can
benefit the organization and how these technologies can be mapped onto the
organization’s requirements for software distribution and management.
In addition to the information that you have collected to assess the current
environment, consider how you would like the future environment to look. For
example, you could define what software you would like to manage, and the
person whom you would like to prepare software for distribution.
Collate information to cover your current and future needs in accordance with
the following topics.

General Information
General information includes:



The tools that you use.




How the tools function.

Whether the tools are compatible with Microsoft CCM technologies.

Preparation
Preparation information includes:



The software that you prepare for distribution.




Whether your software vendors provide packages in the correct format.


8

Module 3: Designing a Software Distribution and Management Strategy

Distribution
Distribution information includes:



Where your software is distributed from.




How users know that the software is available to install.

How much bandwidth is available for software distribution.




Whether you want to distribute from multiple locations.

Targeting
Targeting information includes:



Which users currently receive which applications.




Whether you have any roaming or mobile users, and how their needs are
addressed.




Which user software is mandatory, and which is optional.




Whether software is job specific or department based.




Whether you want to distribute to users in remote sites.

At what level software policies are set to provide software to users.

Installation
Installation information includes:



Whether applications are installed with the initial operating system or later.




How the software applications are installed.




Who installs the software.




How software upgrades and updates are installed.




Whether upgrades and updates are mandatory or optional.




How to provide application resilience when files are deleted or corrupted.

How to prevent users from installing unapproved software.




How you want users to start the installation of software.




Which software must be deployed to computers rather than to users.




Whether any departments have specific software needs.




How you handle failed software installations and upgrades.


Module 3: Designing a Software Distribution and Management Strategy

9

Removal
Removal information includes:

Who removes the installed applications.




Where the applications are removed from.




Whether software removal is mandatory or optional.




How to remove applications when the uninstall process fails.




How to prevent users from uninstalling mandatory or required software.




Whether you want removal to be optional or mandatory.

Note For more information about the appropriate information to gather on your
change and configuration management needs, see Deployment Planning
Worksheets in the Change and Configuration Management Deployment Guide,
Appendix A, on the Web page on the Student Materials compact disc.


10

Module 3: Designing a Software Distribution and Management Strategy


Evaluating Software Distribution and Management
Options
Topic Objective

To identify the available
software distribution and
management options.

Lead-in

You need to be aware of the
different methods for
distributing and managing
software in Windows 2000.




Windows Installer Service




IntelliMirror (Group Policy and Active Directory)




Systems Management Server

*****************************ILLEGAL FOR NON-TRAINER USE******************************

You must identify the available software distribution and management options,
and their strengths and weaknesses. You can then choose the options most
appropriate to your organizational requirements.
In this section, you will identify the different software deployment technologies
available for the distribution and management of software in your organization
and assess their suitability to your organizational requirements.
You will consider the capabilities and limitations of each and assess how
appropriate they are for your CCM infrastructure design.


Module 3: Designing a Software Distribution and Management Strategy

11

Windows Installer Service
Topic Objective

To introduce the features
and capabilities of the
Windows Installer service as
an appropriate option for
software distribution and
management.




Lead-in

To assess the suitability of
Windows Installer to meet

your requirements, it is
necessary to understand its
capabilities, requirements,
and uses.




Windows Installer



Provides enhanced installation functionality




Provides standardized methods

Windows Installer Components



Windows installer package (.msi file)




Application programming interface

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Windows Installer is a core Windows operating system service that helps you
manage the state of software during and after installation. It is included with
Windows 2000 and later and is also available for Microsoft Windows NT®
version 4.0, Microsoft Windows 98, and Microsoft Windows 95. It defines a

standard format for application setup and tracks components such as groups of
files, registry entries, shortcuts, and other aspects of the application that must be
managed together.

Windows Installer
The Windows Installer service provides the following:



Enhanced installation functionality
This functionality includes:
• Installation-on-demand
• Entire products
• Rollbacks of the system to its previous state in the case of installation
failure
• Auto-repair of applications
• Application removal




Standardized methods to install, remove, and repair applications
Regardless of the methods used to handle the distribution and targeting
portions of the software deployment process, you can access the
functionality of Windows Installer through application programming
interfaces (APIs) or through a command-line interface.


12

Module 3: Designing a Software Distribution and Management Strategy

Windows Installer Components
Windows Installer uses the following components to install and manage
software:



A Windows Installer package (an .msi file), which is a relational database
that contains information describing the installed state of the application




An API that allows applications and management tools to interact with
Windows Installer to install or remove additional features of the application
after the initial installation is complete

Note Several companies provide tools for creating native Windows Installer
packages, and for repackaging existing setups into .msi packages.


Module 3: Designing a Software Distribution and Management Strategy

13

IntelliMirror (Group Policy and Active Directory)
Topic Objective

To introduce the features
and capabilities of
IntelliMirror as an
appropriate option for
software distribution and

management.

Lead-in

To assess the suitability of
IntelliMirror to meet your
requirements, it is
necessary to understand its
capabilities, requirements,
and uses.

Windows
Installer

Group
Policy

Active
Directory

Distributed
File System

Packaging
Distribution
Targeting
Installation
Removal

*****************************ILLEGAL FOR NON-TRAINER USE******************************

In this section, you will examine the capabilities of the Software Installation
and Maintenance feature of Microsoft IntelliMirror® to understand its uses and
requirements. This will help you determine how appropriate it is for your CCM
design.

Packaging
IntelliMirror software deployment requires that packages be in the Windows
Installer (.msi) packaging format. IntelliMirror software deployment also
provides limited deployment features for existing, non–Windows Installer
packages through special text files, called .zap files, which describe enough of
the installation for Windows Installer to package existing setups. Repackaging
in IntelliMirror can be time-consuming, so make sure that you allow sufficient
time.
Note For more information about .zap files, see Creating Software Installation
Settings (.zap) Files in Chapter 9, “Improving Software Installation in Your IT
Infrastructure,” in the Change and Configuration Management Deployment
Guide, Appendix A, on the Web page on the Student Materials compact disc.

Distribution
IntelliMirror software deployment uses a share-based scheme to specify the
location that client computers use to access packages, and it allows only a
single location to be specified. To accommodate multiple physical package
locations, you can use the Distributed file system (Dfs) infrastructure. This
allows a single package location to be specified to the IntelliMirror software
deployment features, while still allowing multiple copies of the package to be
physically located close to the targeted recipients.


14

Module 3: Designing a Software Distribution and Management Strategy

Targeting
Group Policy objects containing software deployment Group Policy settings are
associated with sites, domains, or organizational unit containers in the
Active Directory™ directory service. The policy then applies to all
objects in the specified container and in all containers below it. You can further
constrain software deployment Group Policy settings by also requiring
membership in one or more security groups. Software deployment policies can
be applied to users and computers, and can be revoked as objects are moved in
Active Directory or changes to their group memberships.

Installation
You can deploy Windows Installer packages by means of IntelliMirror in two
ways, which are known as publishing or assigning. Publishing an application
makes it available for users to install as an option; assigning makes an
application mandatory for the targeted users and computers, and installs it
automatically the next time Group Policy is evaluated.

Removal
You can use IntelliMirror technologies in conjunction with Windows Installer
to provide a more controlled method of software removal. You can also use
Group Policy to create software removal packages that are optional or
mandatory.