Module 6: Using Group Policy to Manage Software v
Module Strategy
Use the following strategy to present this module:
?? Introduction to Managing Software Deployment
In this topic, you will introduce managing software deployment by using
Group Policy. Briefly discuss each phase in software installation but avoid
going into detail about each phase.
?? Windows Installer Technology
In this topic, you will introduce Windows Installer and describe the role that
it plays in software installation and maintenance. Discuss some of the
problems typically encountered by administrators when deploying and
managing software in an organization.
?? Deploying Software
In this topic, you will introduce deploying software. Provide an overview of
the software deployment process. Describe the process of creating a
software distribution point. Discuss the guidelines for creating a software
distribution point. Explain how to assign and publish software. Discuss the
advantages of advertising software as opposed to installing it. Explain the
difference between assigning software to a user and assigning software to a
computer. Discuss situations in which assigning software to a user would be
more appropriate, and occasions when it might be better to assign software
to computers. Demonstrate how users can use Add/Remove Programs in
Control Panel to install software. Demonstrate the process that occurs when
a user double-clicks an unknown file type. Illustrate the procedure for using
Group Policy to assign and publish software packages. Demonstrate how to
change the deployment options for an application.
?? Lab A: Using Group Policy to Deploy Software
Prepare students for the lab in which they will use Group Policy to assign
and publish software. Make sure that students run the command file for the
lab, and tell them that they will work with their partner’s computers. After
students have completed the lab, ask them if they have any questions.
?? Configuring Software Deployment
In this topic, you will introduce configuring software deployment. Illustrate
the concept of adding modifications to a software package. Show students
the Modifications tab in the Properties dialog box for a published
application, and describe how to add a transform file. Explain how software
categories are used to classify applications within Add/Remove Programs.
Explain the concept of managing file name extensions with Software
Installation. Emphasize that a list of file name extensions (and the
applications associated with them) is stored in Active Directory
™
directory service.
?? Maintaining Deployed Software
In this topic, you will introduce maintaining software. Illustrate the
procedure for deploying a mandatory or an optional upgrade. Demonstrate
how to redeploy software. Emphasize the fact that redeployment involves
not only obtaining the updated application files, but also obtaining a new
Windows Installer package file.
vi Module 6: Using Group Policy to Manage Software
?? Removing Deployed Software
In this topic, you will introduce removing deployed software. Illustrate
the procedure for removing deployed software. Emphasize that when
you configure a Group Policy object (GPO), the software is
automatically removed.
?? Deploying non-Windows Installer Packages
In this topic, you will introduce deploying non-Windows Installer packages.
Discuss the three-step process of repackaging an application. Describe the
limitations of .zap files and the two sections of a .zap file. Emphasize the
fact that applications using .zap files can only be published, not assigned.
Explain how the File Extensions section can be used to register file name
extensions in Active Directory.
?? Lab B: Using Group Policy to Upgrade Software
Prepare students for the lab in which they will deploy mandatory and
optional upgrades of software by using Group Policy. They will also remove
software previously deployed by using Group Policy. Make sure that
students run the command file for the lab, and tell them that they will work
with their partner’s computers. After students have completed the lab, ask
them if they have any questions.
?? Lab C: Creating and Deploying a non-Windows Installer Package File
Prepare students for the lab in which they will create and deploy a non-
Windows Installer package file. Make sure that students run the command
file for the lab, and tell them that they will work with their partner’s
computers. After students have completed the lab, ask them if they have
any questions.
?? Troubleshooting Software Deployment
In this topic, you will introduce troubleshooting options for resolving the
problems that may occur when using Group Policy to deploy software. Tell
students that they may encounter problems when deploying software with
Group Policy. Present some of the more common problems that they may
encounter, along with suggested strategies for resolving them.
?? Best Practices
Present best practices for using Group Policy to manage software.
Emphasize the reason for each best practice.
Module 6: Using Group Policy to Manage Software vii
Customization Information
This section identifies the lab setup requirements for a module and the
configuration changes that occur on student computers during the labs. This
information is provided to assist you in replicating or customizing Microsoft
Official Curriculum (MOC) courseware.
The labs in this module are also dependent on the classroom
configuration that is specified in the Customization Information section at the
end of the Classroom Setup Guide for course 1558a, Advanced Administration
for Microsoft Windows 2000.
Lab Setup
The following list describes the setup requirements for the labs in this module.
Setup Requirement 1
The labs in this module require a regular user account for the student. To
prepare student computers to meet this requirement, create the user
account manually.
Setup Requirement 2
The labs in this module require the Log on locally right on domain controllers
to be assigned to the Everyone group. To prepare student computers to meet
this requirement, perform one of the following actions:
?? Run C:\MOC\Win1558A\Labfiles\Lab06\Setup\Lab06.cmd.
?? Manually assign the right.
Setup Requirement 3
The labs in this module require that a shortcut for Active Directory Domains
and Trusts, Active Directory Users and Computers, and Active Directory
Sites and Services exist on the desktop of the regular user account. To
prepare student computers to meet this requirement, perform one of the
following actions:
?? Run C:\MOC\Win1558A\Labfiles\Lab06\Setup\Lab06.cmd.
?? Create the shortcuts manually and place them in
C:\Winnt\Profiles\All Users\Desktop.
Setup Requirement 4
The labs in this module require the following organizational units (OUs) and
user accounts:
This OU In this organizational unit
Information Services x Top Level OU in the domain
Customer Support Information Services x
Help Desk Information Services x
Important
viii Module 6: Using Group Policy to Manage Software
This user account In this organizational unit
Information Services User x Information Services x
Information Services Admin x Information Services x
Customer Support User x Customer Support
Help Desk User x Help Desk
To prepare student computers to meet this requirement, perform one of the
following actions:
?? Run C:\MOC\Win1558A\Labfiles\Lab06\Setup\Lab06.cmd.
?? Create the OUs and user accounts manually.
Lab Results
Performing the labs in this module introduces the following configuration
changes:
?? Students create GPOs linked to the Information Services OU and child OUs.
?? Students use Group Policy to install Green, Red, Blue, Cosmo1, and
Cosmo2 for Information Services users on all computers.
?? Students use Group Policy to install PowerPoint Viewer 97 for the
ISAdminx account in their domains on all computers.
You can run
C:\MOC\Win1558A\Labfiles\Lab06\Setup\Lab06rm.cmd to remove most
configuration changes introduced during the labs in the module. Remove the
Log on Locally right from the Everyone group manually. Manually delete the
GPOs created by students. Uninstall remaining applications manually.
Important
Module 6: Using Group Policy to Manage Software 1
Overview
? Introduction to Managing Software Deployment
? Windows Installer Technology
? Deploying Software
? Configuring Software Deployment
? Maintaining Deployed Software
? Removing Deployed Software
? Deploying non-Windows Installer Packages
? Troubleshooting Software Deployment
? Best Practices
Microsoft® Windows® 2000 includes a new feature called Software Installation
and Maintenance that uses Active Directory
™
directory service, Group Policy,
and Windows Installer to install, maintain, and remove software on computers
in your organization. By using a policy-based method for managing software
deployment, you can ensure that the applications that users need to perform
their jobs are available whenever and wherever they are needed.
At the end of this module, you will be able to:
?? Describe how to manage software deployment by using Group Policy.
?? Describe the role that Windows Installer plays in software installation
and maintenance.
?? Use Group Policy to deploy software.
?? Use Group Policy to configure software deployment.
?? Use Group Policy to maintain software.
?? Deploy non-Windows Installer packages.
?? Troubleshoot common problems with software deployment.
?? Apply best practices for deploying software.
Slide Objective
To provide an overview of
the module topics and
objectives.
Lead-in
In this module, you will learn
how to use Group Policy to
deploy and manage
software.
2 Module 6: Using Group Policy to Manage Software
Introduction to Managing Software Deployment
Removal
Software is removed
Maintenance
Software is upgraded or
redeployed
Deployment
Software is installed
Preparation
Software installation files
are acquired
In Windows 2000, you can use Group Policy to centrally manage (one location)
the software deployment process. You can apply Group Policy settings to users
or computers in an Active Directory container (site, domain, or organizational
unit) to automatically install, upgrade, or remove software for the users and
computers in the container. By applying Group Policy settings to software, you
can manage the various phases of software deployment without having to visit
each computer individually.
The following list describes each phase in the software installation and
maintenance process:
1. Preparation. In this phase, you prepare the files that will enable software
deployment. You copy the software installation package files (Windows
Installer package files) for an application to a software distribution point (a
shared folder on the network) before that application can be deployed with
Group Policy. You can acquire a Windows Installer package file from the
vendor, or you can create a package file by using a third-party utility.
2. Deployment. In this phase, the software is installed on the computer. An
administrator creates a Group Policy object (GPO) that installs the software
and links the GPO to an appropriate Active Directory container. The
software is installed either when the computer starts or when a user logs on.
3. Maintenance. In this phase, deployed software is upgraded (with new
versions) or redeployed (with service packs and patches) by modifying the
GPO that originally deployed the software. The software is automatically
upgraded either when the computer starts or when a user logs on.
4. Removal. In this phase, you eliminate software that is no longer required by
removing the software package setting from the GPO that originally
deployed the software. The software is automatically removed either when
the computer starts or when a user logs on.
Slide Objective
To provide an overview of
how you can use Group
Policy to manage software
deployment.
Lead-in
Managing software is a
process that consists of four
phases: preparation,
deployment, maintenance,
and removal.
Briefly discuss each phase
in the software installation
process but avoid going into
detail about each phase.
Module 6: Using Group Policy to Manage Software 3
Windows Installer Technology
Windows Installer Service
Windows Installer Service
Windows Installer Service
? A Client-Side Service That
Fully Automates the
Software Installation and
Configuration Process
? Is Used to Modify or Repair
an Existing Application
Installation
? A Client-Side Service That
Fully Automates the
Software Installation and
Configuration Process
? Is Used to Modify or Repair
an Existing Application
Installation
Windows Installer Package
Windows Installer Package
Windows Installer Package
? Contains All the Information Required by the
Windows Installer Service to Install or Uninstall
an Application
? Consists of an .msi File and Any External Source
Files That Are Required to Install the Application
? Contains Standard Summary Information About
Both the Application and the Package
? Contains a Reference to an Installation Point
Where Product Files Reside
? Contains All the Information Required by the
Windows Installer Service to Install or Uninstall
an Application
? Consists of an .msi File and Any External Source
Files That Are Required to Install the Application
? Contains Standard Summary Information About
Both the Application and the Package
? Contains a Reference to an Installation Point
Where Product Files Reside
Benefits of Employing Windows Installer Technology
Benefits of Employing Windows Installer Technology
Benefits of Employing Windows Installer Technology
? Resilient Applications
? Clean Removal
? Resilient Applications
? Clean Removal
To enable the use of Group Policy to deploy and manage software,
Windows 2000 employs the Windows Installer technology. This technology
contains two components: the Windows Installer service and the Windows
Installer package.
?? Windows Installer service. The Windows Installer service is a client-side
service that fully automates the software installation and configuration
process. The Window installer service is also used to modify or repair an
existing application installation. The Windows Installer service installs an
application either directly (by CD-ROM) or through Group Policy.
?? Windows Installer package. The Windows Installer package contains all of
the information that the Windows Installer service requires to install or
uninstall an application. A package consists of an .msi file (Windows
Installer file) and any external source files (additional installation files) that
are required to install the application. A package file also contains standard
summary information about both the application and the package itself. It
also contains the product files or a reference to an installation point where
the product files reside.
The benefits of employing the Windows Installer technology include:
?? Resilient applications. If a critical file is deleted or becomes corrupt, the
application will automatically return to the installation source and acquire a
new copy of the file, without requiring user intervention.
?? Clean removal. Applications are uninstalled without leaving orphaned files
and without inadvertently breaking another application (for example, by
deleting a shared file required by another application). In addition, all
application-related registry settings are removed.
Slide Objective
To introduce Windows
Installer and describe the
role that it plays in software
installation and
maintenance.
Lead-in
Windows 2000 includes
Windows Installer
technology that can help
administrators overcome the
challenges inherent in
deploying and managing
software throughout
an organization.
Discuss some of the
problems typically
encountered by
administrators when
deploying and managing
software in an organization.
Key Point
Windows Installer contains
two components: the
Windows Installer service
and the Windows
Installer package.
4 Module 6: Using Group Policy to Manage Software
? Deploying Software
? Software Deployment
? Creating a Software Distribution Point
? Assigning Software
? Publishing Software
? Using Group Policy to Deploy Software Packages
Software Installation, a component of Group Policy, allows you to
deploy software to users and computers. Deploying software ensures that
required applications are available at any computer to which a user logs on.
Administrators can either install software for users in advance, or give users the
option to install the software that they require as it is needed. From the user’s
point of view, software is always available and functional.
Slide Objective
To introduce the topics
related to deploying
software.
Lead-in
Windows 2000 provides an
entirely new way for
administrators to deploy
software in an organization.
Module 6: Using Group Policy to Manage Software 5
Software Deployment
Tasks
Tasks
Tasks
Create or modify a Group Policy object
Create or modify a Group Policy object
Acquire a Windows Installer
package file
Acquire a Windows Installer
package file
Place the package on software
distribution point
Place the package on software
distribution point
Configure the Group Policy object
Configure the Group Policy object
When you deploy software, you are specifying how applications are installed
and maintained within your organization. To use Group Policy to deploy new
software, perform the following tasks:
1. Acquire a Windows Installer package file. You must have a package file for
an application before that application can be deployed by using Group
Policy. A package will contain an .msi file and any related installation files
that are necessary. The related installation files are the application files that
will be installed on the local hard disk.
2. Place the package file and any related installation files on a software
distribution point. A software distribution point is a shared folder on
your network.
3. Create or modify a GPO. You will need to create a GPO for the container in
which you want to deploy the application.
4. Configure the GPO to deploy the application. You can configure the GPO
to deploy software for a user account or for a computer account. This task
also includes selecting the type of deployment that you will need.
Deployment types, and the differences between deploying an application to
users and computers, will be discussed later in this module.
Slide Objective
To provide an overview of
the software deployment
process.
Lead-in
When deploying software,
you use Group Policy to
specify how applications are
installed and maintained
within your organization.
Tell students that they must
obtain a license to run the
software that they are
deploying. Windows Installer
does not manage
software licenses.
Key Points
You must have a Windows
Installer package file for an
application before that
application can be deployed
by using Group Policy.
Depending on your
requirements, you can
configure the GPO to deploy
software for a user account
or for a computer account.
6 Module 6: Using Group Policy to Manage Software
Creating a Software Distribution Point
To Create a Software Distribution Point:
To Create a Software Distribution Point:
To Create a Software Distribution Point:
When Creating a Software Distribution Point:
When Creating a Software Distribution Point:
When Creating a Software Distribution Point:
Create a shared folder
Create a shared folder
Create appropriate folders in the shared folder
Create appropriate folders in the shared folder
Copy the Windows Installer packages and application
executables to appropriate folders
Copy the Windows Installer packages and application
executables to appropriate folders
Assign users the Read and Execute permissions so
they can gain access to the shared folder
Assign users the Read and Execute permissions so
they can gain access to the shared folder
R,E
R,E
?Create a folder for .msi applications named for the application
?Use a hidden shared folder
?Use Dfs to provide a single share point for all applications
?Create a folder for .msi applications named for the application
?Use a hidden shared folder
?Use Dfs to provide a single share point for all applications
A software distribution point is a shared folder that contains the package files
for deploying software. Installer packages and software files have to be
available on a software distribution point, because when software is installed on
a computer, files are copied from this point to the local computer. Keeping the
files for each application together simplifies administration.
To create a software distribution point, perform the following tasks:
1. Create a shared folder.
2. Create the appropriate application folders in the shared folder.
3. Copy the Windows Installer packages and application executables to the
appropriate folders.
4. Set the appropriate permissions for the shared folder. Assign users the Read
and Execute permissions so that they can gain access to the software
installation files on the software distribution point.
When creating a software distribution point, use the following guidelines:
?? Create a folder for .msi packages that is named for the application, and place
the .msi package file, and all required installation files, in that folder. Even
though you can store the .msi package file separately from the application
installation files, it will simplify administration to store them in the
same location.
?? Use a hidden shared folder (for example, packages$), to prevent users from
browsing the contents of the shared folder on the software distribution point.
?? Use Distributed file system (Dfs) to provide a single share point for all
published applications. This allows you to take advantage of Dfs
redundancy and load-balancing features. For more information on Dfs, see
module 9, “Sharing File Resources by Using Dfs,” in course 1558A,
Advanced Administration for Microsoft Windows 2000.
Slide Objective
To describe the process of
creating a software
distribution point.
Lead-in
All package files are kept at
a common location so that
they can be located easily.
This common location is the
software distribution point.
Explain the tasks involved in
creating a software
distribution point.
Discuss the guidelines for
creating a software
distribution point.
Briefly explain Dfs and tell
students that it is covered in
detail in module 9, “Sharing
File Resources by Using
Dfs,” in course 1558A,
Advanced Administration for
Microsoft Windows 2000.
Key Point
A software distribution point
is a shared folder that
contains the package files
for deploying software.
Không có nhận xét nào:
Đăng nhận xét