Deploying Software with Group PolicyChapter Twelve

Exam Objectives in this Chapter: Distribute software using Group Policy Troubleshoot Group Policy application deployment

issues Maintain installed software by using Group Policy Distribute updates to software distributed by Group

Policy Configure automatic updates for network clients

using Group Policy

In this Chapter: Understanding Software Deployment with

Group Policy Deploying Software with Group Policy Maintaining Software Deployed with Group

Policy Troubleshooting Software Deployed with

Group Policy

To Complete this Chapter: Complete the requirements on pages 1 – 2.

Software Deployment with Group Policy You use the Software Installation and Maintenance

feature of IntelliMirror to create a managed software environment with the following characteristics: Users have access to the applications they need to do their

jobs, no matter which computer they log on to. Computers have the required applications, without

intervention from a technical support representative. Applications can be updated, maintained, or removed to

meet the needs of the organization.

Tools for Software Deployment with GPO Software Installation Extension allows

administrators to centrally manage: Initial deployment of software Upgrades, patches, and quick fixes for software Removal of software

Exam Tip Know the difference between assigningassigning

software and publishingpublishing software

Assigning Applications The application is advertised to the user on the Start

menu the next time he or she logs on to a workstation, and local registry settings, including filename extensions, are updated.

The application advertisement follows the user regardless of which physical computer he or she logs on to.

Publishing Applications The application does not appear installed on

the users’ computers. No shortcuts are visible on the desktop or

Start menu, and no updates are made to the local registry on the users’ computers

The Windows Installer Service The Windows Installer package is a file

containing information that describes the installed state of the application.

Because the Windows Installer service manages the state of the installation, it always knows the state of the software.

If there is a problem during software installation, Windows Installer can return the computer to its last known good state.

Windows Installer Packages A Windows Installer package is a file that

contains explicit instructions on the installation and removal of specific applications.

There are two types Native Windows Installer package (.msi) files Repackaged application (.msi) files

Customizing Windows Installer Packages You can customize Windows Installer

packages by using modifications, also called transforms.

File Types Transform (.mst) files These files provide a means

for customizing the installation of an application. Patch (.msp) files These files are used to update an

existing .msi file for soft-ware patches, service packs, and some software update files, including bug fixes.

Application (.zap) Files You can also deploy software using the

Software Installation extension by using an application file.

Application files are text files that contain instructions about how to publish an application, taken from an existing setup program (Setup.exe or Install.exe).

Add Or Remove Programs in Control Panel

You can control which software is available to users within Add Or Remove Programs in Control Panel by using Group Policy settings.

Users no longer need to look for a network share, use a CD-ROM, or install, fix, and upgrade software themselves.

Software Deployment Approaches Note table 12-1 on pages 7 – 8.

Distributing Windows Installer Packages

For large-scale deployments or deployments with computers running pre–Windows 2000 operating systems, you might also consider using the Microsoft Systems Management Server (SMS) along with Group Policy to handle software deployment.

Group Policy by using SMS: Some areas to use SMS:

Non–Windows 2000–based clients Deploying software over slow links Software licensing and metering Identification of computer configurations

Deploying Software with Group Policy Exam Tip

Know the tasks for deploying software with Group Policy.

First set up a Software Distribution Point (SDP)

Microsoft recommends use of DFS Next add a GPO

Software Deployment Process with GPO Create a new software package in your GPO

Software Deployment Process with GPO Browse through Network Places: Locate the

.msi file

Software Deployment Process with GPO

Now select either: Publish Assign or Advanced

Software Deployment Process with GPO

You may now use the properties of the software package to modify its deployment.

Software Installation Properties Four Tabs

GeneralGeneral Advanced File Extensions Categories

Software Installation Properties Four Tabs

General AdvancedAdvanced File Extensions Categories

Software Installation Properties Four Tabs

General Advanced File ExtensionsFile Extensions Categories

Software Installation Properties Four Tabs

General Advanced File Extensions CategoriesCategories

Adding Windows Installer Packages Through GPO and Selecting Package Deployment Method

Caution Be sure to enter the UNC path to the SDP in

the File Name list. If you merely browse and select the Windows Installer package to be added to the GPO, you have entered only the local path and clients will not be able to find the Windows Installer package.

Software Deployment Best Practices Assign or publish just once per GPO Assign or publish close to the root in the Active Directory hierarchy Make sure Windows Installer packages include modifications before

they are published or assigned Specify application categories for your organization Take advantage of authoring tools Repackage existing software Set properties for the GPO to provide widely scoped control Set properties for the Windows Installer package to provide fine

control Know when to use Group Policy Software Installation and Systems

Management Server (SMS)

Practice: Deploying Software with Group Policy

Exercise 1: Preparing Server2 Page 12-28

Exercise 2: Setting Up an SDP Exercise 3: Configure a GPO for Software Deployment (Assign)

Page 12-29 Exercise 4: Testing Software Deployment Exercise 5: Configure a GPO for Software Deployment (Publish)

Page 12-30 Exercise 6: Testing Software Deployment

Page 12-31

Maintaining Software Deployed with Group Policy After the deployment of software

applications, it might be necessary to redeploy, upgrade, or remove them at some point in the software life cycle.

Redeploying Applications Deployed with Group Policy

You can redeploy an application previously deployed with Group Policy if there are small changes that need to be made to the original software deployment configuration.

Upgrading Applications Deployed with Group Policy

Events in the life cycle of the software can trigger an upgrade The original developer of the software might

release a new version with new and improved features.

The organization might choose to use a different vendor’s application.

Removing Applications If you delete a GPO that deploys a software

application, the application cannot be uninstalled with Group Policy.

If the application cannot be uninstalled with Group Policy, you (or the users) must manually uninstall the application from each client computer.

Deleting To avoid this hazard, you must remove

applications deployed with Group Policy in three steps: Choose the software removal method you want to

implement. Allow the software removal to be processed. Delete the GPO

Software Removal Methods There are two options

You can immediately uninstall the software from users and computers (known as a forced removal), or

You can allow users to continue to use the software, but prevent new installations (known as an optional removal).

Note When you originally deploy the software, if

you want the application to be removed when a GPO no longer applies, select the Uninstall This Application When It Falls Out Of The Scope Of Management option in the Deployment tab in the Properties dialog box for the package

Exam Tip Know how to use Gpresult to troubleshoot

software deployed with Group Policy.

Troubleshooting Scenarios Pages 41 – 45.

Summary Case Scenario Exercise

Pages 47 – 49. Troubleshooting Lab

Pages 49 - 51 Exam Highlights

Key points page 52 Key terms page 51