section 10: assigning and publishing software packages using msi packages to distribute software...

Section 10: Assigning and Publishing Software Packages

Using MSI Packages to Distribute Software

Using Group Policy as a Software Deployment

Method

Deploying Software

Setting Up Distribution Points

Using the System Center Configuration Manager

to Distribute Software

Managing Windows Environments with Group Policy

© 2013 Global Knowledge Training LLC. All rights reserved.

Section Objectives

After completing this section, you will be able to:Describe the basic elements of an MSI packageDetermine when to build a package or repackage

your ownDefine the requirements for distributing software via

Group PolicyDescribe when you might want to assign and publish

softwareExplain how to upgrade and remove packages

10-2


Section Objectives (cont.)

After completing this section, you will be able to:Explain how to set up distribution points for software

deploymentList the advantages of using SCCM to distribute

software instead of Group Policy

10-2


Using MSI Packages to Distribute Software

10-3

MSI Package Characteristics

Elements of an MSI Package Building an MSI Package Repackaging an Application What Is a Transform? The Windows Installer Service


MSI Package Characteristics

MSI packages have the following characteristics:

Collection of registry settings and files Support for software deployment Silent installation capability Clean uninstallation Self-healing capability Inherent patching and updating

10-4


Elements of an MSI Package

MSI packages include the following possible categories: Main program files (EXE, DLL, etc.) Files that can be shared with other applications from the same

vendor Modules (and whether they are required or optional) Shortcuts (typically on the Start menu) Icons Fonts *.ini files Registry additions and changes Differences between a fresh installation and an upgrade of an

earlier version Removal instructions

10-6


Building an MSI Package

Many tools are available to create MSI packages:

InstallShield MAKEMSI (free)

InstallAware MSIBuilder (free)

Wise Package Studio Ainstaller (free)

WinINSTALL Installer2GO

Desktop Authority MSI Studio War Setup (free, open source)

Advanced Installer (free and commercial versions available)

10-7


Repackaging an Application

Repackaging is the process of taking a “before” and “after” snapshot of the system.

The results are compared and the differences make up the installation.

Software So

ftw

are

After

Before

10-8


What Is a Transform?

10-9

Transforms (or modifications) are used to customize the installation of a software package.


The Windows Installer Service

The Windows Installer Service launches on demand when a software package is run.

Msiexec.exe can also be run manually to force certain modes of operation.

10-10


Using Group Policy as a Software Deployment Method

10-12

Advantages and Disadvantages of Policy-Based Software Deployment

Requirements for Distributing Software via Group Policy


Advantages Disadvantages

One integrated tool Deploy to computers

or users Deploy by site,

domain, or OU Massive, expensive

tools not required

No schedulingNo control over bandwidth

for distributionLittle, if any, reportingCumbersome

conditional deployments

Advantages and Disadvantages of Policy-Based Software Deployment

10-13


Requirements for Distributing Software via Group Policy

Target systems must be domain members.

An Active Directory domain must be present.

The software must be in MSI format.

10-14


Deploying Software

10-15

Assigning Software

Publishing Software to Users Upgrading Packages Removing Packages


Assigning Software

Software can be assigned to:

Computers Users

10-16


Assigning Software to Computers

Software packages assigned to a computer install at boot time.

A user is not required to log on for theinstallation to complete.

10-17


Selecting a Deployment Method

Software packages for the computer can only be assigned; they cannot be published.

The Advanced option immediately opens the properties for the package.

You can create published packages on the user side of Group Policy.

Published software requires user intervention.

10-18


Configuring Additional Options

The Advanced optionsinclude the ability to uninstall the application when it no longer applies to the user or computer that the package was distributed to.

10-19


Assigning Software to Users

Software distributed to the user requires the user to log on.

Packages can be assigned or published.

The package “follows” users fromone computer to another while the policy affects them.

10-20


Assigning Software to Users on Demand

When you assign a package to a user, it is possible to install the package at logon.

The package can alsobe left alone to installthe first time that a userclicks the icon for theapplication.

10-21


Publishing Software to Users

Published software is optional.Users must know that the package exists.Available packages are displayed in Control Panel:

Programs and Features: Windows Vista and Later Add/Remove Programs: Windows 2000, Windows XP,

and Windows Server 2003Programs follow users from one computer to another.

10-22


Upgrading Packages

When a new revision of an existing product is released, the new package can be created as an upgrade package.

10-23


Removing Packages

When a package is removed, you will be prompted to either: Immediately uninstall

the softwareContinue

to use the software

10-24


Setting Up Distribution Points

Always specify a UNC when adding a software package.

A warning is issued when you specify a drive letter for the software source.

The Event Viewer can also be used to find out when software is not being deployed from a UNC path.

Sites can be used to distribute packages from local servers.

Slow link detection can help prevent software from being deployed across slow links.

10-25


Specify a Network Location

Always distribute packages from a UNC path. If a drive letter is specified for the package, a warning

message will appear stating that the path to the file should be a network share.

10-26


Using the System Center Configuration Manager to Distribute Software

SCCM advantages:A scalable solution for large enterprisesAbility to upgrade the operating systemSchedulingReportingDiagnostics Inventory managementDeploy non-MSI packagesAll clients do not need to reside in Active Directory

10-28


Summary

Some of the basic elements of an MSI package are:Main program files (exe, dll, etc.)Shortcuts (typically on the Start menu)Registry additions and changesDifference between a fresh installation and an upgrade

of an earlier versionRemoval instructions

10-30


Summary (cont.)

Most vendors produce MSI packages that you can distribute via Group Policy without modifying them. If an application that you want to deploy via Group Policy does not come with an MSI package, you may want to build one from scratch. If you do not have access to the setup logic of a given application and you cannot obtain it, you may consider repackaging your own application.

10-30


Summary (cont.)

To distribute software via Group Policy your system must have the following:

MSI packages Active Directory Active Directory clients (workstations running Windows

2000 or later operating system)

10-30


Summary (cont.)

You can assign software in these situations:Assign software to computers: This forces the

installation at the next reboot and makes the software available to all users of the computer.

Assign the software to users: This forces the installation at the next logon if the user is in the Active Directory structure to which the policy applies.

Assign the software to users, but on demand: This forces the installation on a per-user basis but only when the user selects the program via the Start menu or a desktop shortcut.

10-30


Summary (cont.)

You can publish software only to users, not to computers. Publishing software via Group Policy is the best option when you want to give users the choice of whether to install an application or not.

To create your own upgrade behavior using the MMC Group Policy console, follow these steps:

1. Right-click the application policy and select Properties.

2. Click the Upgrade tab.

3. Specify the “upgrader” package and the “upgradee” package.

10-30


Summary (cont.)

To remove a package, follow these steps:1. Right-click the details pane of the Group Policy

console and select All Tasks, Remove.

2. Select the removal method.Distribution points are servers that have shared folders

for distributing software. These folders must be accessed via UNC paths and not by using mapped drive letters.

10-30/31


Summary (cont.)

Some of the advantages of using SCCM to distribute software are:A scalable solution for large enterprisesSchedulingReportingDiagnostics Inventory managementSupport for Windows 95, Windows 98, and Windows

NT 4 clients

10-31


Knowledge Check

1. Which of the following is a basic element of an MSI package? (Choose all that apply.)a. Shortcuts (typically on Start menu)

b. Removal instructions

c. Registry additions and changes

d. *.dll files

2. When might you want to publish software?

When you want to give users the choice of whether to install an application or not.

10-31


Knowledge Check (cont.)

3. If you choose to assign software to computers, this forces the installation at:a. Next reboot and makes the software available to all

users of the computer.

b. Next logon if the user is in the Active Directory structure to which the policy applies.

c. Next shutdown if the user is in Active Directory structure to which the policy applies.

d. Ongoing basis but only when the user selects the program via the Start menu or a desktop shortcut.

10-31



4. What are the advantages of using SCCM to distribute software? (Choose all that apply.)a. Inventory management

b. Programming

c. A scalable solution for large enterprises

d. Diagnostics

10-31



5. When creating a software package, a mapped drive can be used to specify the path to the file.a. True

b. False

10-31



6. What would you do if you did not have access to the setup logic of a given application and you could not obtain it?Consider repackaging your own application

7. What do you have to specify when you upgrade a package using the MMC Group Policy console?Specify the “upgrader” package and the “upgradee” package

10-31/32

section 10: assigning and publishing software packages using msi packages to distribute software...

Documents

global knowledge training

software deploymentlist

based software deployment10

software deployment

msi packagemsi packages

msi packagedetermine

disadvantages of policy

fresh installation