TechMentor Fall, 2011 - Packaging Software for Automated Deployment with Windows 7

Windows 7 Deployment Deep DiveWindows 7 Deployment Deep Dive

Packaging Software for Packaging Software for Automated DeploymentAutomated Deployment

Greg Shields, MVP, vExpertGreg Shields, MVP, vExpertConcentrated Technologywww.ConcentratedTech.com

AgendaAgenda

Topics– Part I: The Art of Software

Packaging– Part II: The Science of Software

Deployment

Many IT Professionals have problems with automated software distribution because it feels like a complicated

topic.

But there are really two halves:Software Packaging

…and…Software Deployment

In this session, you’ll learn the nuances of both.

Automated Software DeploymentAutomated Software Deployment

There are two halves to rapidly and remotely installing applications:

• Repackaging – A software installation must first be reconfigured to install without prompting the user or requiring additional information.

• Deployment – The repackaged software installation is then loaded into a deployment tool and scheduled for deployment.

Part IPart IThe Art of Software PackagingThe Art of Software Packaging

4

RepackagingRepackaging

Consider the typical installation…• Insert the CD/DVD media

• Double-click setup.exe or setup.msi

• Next…Next…Finish…

• Head to the next desktop

RepackagingRepackaging

Consider the typical installation…• Insert the CD/DVD media

• Double-click setup.exe or setup.msi

• Next…Next…Finish…

• Head to the next desktop

In order to deploy the same software automatically and remotely, you must…• Figure out how to complete the software

installation without requiring input by the user.

• Figure out how to execute the reconfigured setup.exe or setup.msi file locally on designated desktops.

RepackagingRepackaging

Software installations arrive in one of essentially three formats.• .EXE-based setup files

• .MSI-based setup files

• Copy-it-yourself formats

RepackagingRepackaging

Software installations arrive in one of essentially three formats.• .EXE-based setup files

• .MSI-based setup files

• Copy-it-yourself formats

• Of the first two above, virtually all are packaged using one of the major packaging utilities:• Wise Package Studio• InstallShield• Inno Setup• Nullsoft Scriptable Install System

RepackagingRepackaging

Each format and packager has its own characteristics and switches.• Adobe Acrobat: AcroRd32.exe /s /v/qn

• Installation switches define the “hidden” parameters that can be used to install the package.

• Silent switches instruct the package to install without prompting for input.

• Some have neither. Some have nothing.

RepackagingRepackaging

• Each format and packager has its own characteristics and switches.• Adobe Acrobat: AcroRd32.exe /s /v/qn• Installation switches define the “hidden” parameters

that can be used to install the package.• Silent switches instruct the package to install without

prompting for input.• Some have neither. Some have nothing.

• Thus, while every software installation is different, they are in many ways the same.• You need to sleuth out if switches exist and what they

are!• Or…(More on that in a minute!)

Repackaging – MSI’sRepackaging – MSI’s

MSI installation uses the native Microsoft Installer• Microsoft Installer is the framework built into Windows.

• Like Microsoft Update, but for installing software.

• “Silent” switches are common across all installations.

Repackaging – MSI’sRepackaging – MSI’s

• MSI installation uses the native Microsoft Installer• Microsoft Installer is the framework built into Windows.• Like Microsoft Update, but for installing software.• “Silent” switches are common across all installations.

• Packaging tools automatically interrogate the MSI database to determine silent switches & customizations.

• Customization and silencing is done at command-line.• msiexec /i /qb- AppA.msi DESKTOP_SHORTCUTS=0• msiexec /i AppB.msi TRANSFORMS=custom.mst

MSI ExamplesMSI Examples

The standard command syntax for any MSI is…• msiexec.exe – Invokes the installer, and then…

/i – Install/a – administrative install/l* – Log all information/q – No user interface/qb- – Basic user interface with no dialog boxesPROPERTYNAME = PropertyValue

• msiexec /qb- /l* logfile.txt /i setup.msi NAME=Value

MSI ExamplesMSI Examples

The standard command syntax for any MSI is…• msiexec.exe – Invokes the installer, and then…

/i – Install/a – administrative install/l* – Log all information/q – No user interface/qb- – Basic user interface with no dialog boxesPROPERTYNAME = PropertyValue

• msiexec /qb- /l* logfile.txt /i setup.msi NAME=Value

• (Non-functioning) Example• msiexec /qb- /l* logfile.txt /i AcroRd32.msi

SERIALNUMBER=59a83b987c REBOOT=SUPRESS

DEMODEMOAnalyzing an MSI InstallationAnalyzing an MSI Installation

15

Repackaging – EXE’sRepackaging – EXE’s

EXE files have no common switch schema.• There’s no central authority that governs EXE switches.

• Depending on the packager used to create the EXE, there are some known tricks.

Finding the correct “silent switches” is key to installing properly. And they can be anything!• AppA.exe /s /v/qn

• AppB.exe /quiet /norestart

• AppC.exe /go /blowyournose

• AppD.exe /take /mywife:please

Don’t reinvent the wheel. Reference the Intertubes for applications and their silent switches.

www.AppDeploy.com

EXE ExamplesEXE Examples

InstallShield (Ol’ school)– Run the installer with the /r switch on a reference machine

– Proceed through the dialogs, answering prompts as you would on the client machine

– Complete the installation

– The installation will create a setup.iss file in %windows%

– Use this file to run the installation

– setup.exe /s /f1setup.iss [/f2logfile.txt]

InstallShield (Nu’ school, with Wrapped MSI)– Setup.exe /s /v/qb

– Characters after /v are passed to the wrapped MSI file.

Wise Package Studio, Others…– setup.exe /s

EXE ExamplesEXE Examples

Also Try…– /a

– /q:a /r:n

– /silent

– /passive

– /quiet

– /norestart

– /?

– /help

/? and /help sometimes pop up a dialog box that contains useful clues.

EXE ExamplesEXE Examples

Many EXEs these days are actually MSI wrappers– This means the EXE does little more than launch an MSI

installation

– fileName /s /v/qn – Anything after the /v is passed to the wrapped MSI file

EXE ExamplesEXE Examples

Many EXEs these days are actually MSI wrappers– This means the EXE does little more than launch an MSI

installation

– fileName /s /v/qn – Anything after the /v is passed to the wrapped MSI file

Trick #1: Use the /a switch to perform an “administrative install”, which sometimes will unpack that MSI.

EXE ExamplesEXE Examples

Many EXEs these days are actually MSI wrappers– This means the EXE does little more than launch an MSI

installation– fileName /s /v/qn – Anything after the /v is passed to the

wrapped MSI file

Trick #1: Use the /a switch to perform an “administrative install”, which sometimes will unpack that MSI.

Trick #2: Start the EXE installation, but don’t finish it!– Double-click the EXE.– Wait for it to unpack.– When the first prompt appears, check %temp% for

unpacked MSI install files.

DEMODEMOAnalyzing an EXE InstallationAnalyzing an EXE Installation

22

Repackaging – Diff’sRepackaging – Diff’s

Some software is exceedingly complicated, doesn’t include “silent switches”, or simply won’t install with the other two mechanisms.• For these, we run a “diff”, yo.

Repackaging – Diff’sRepackaging – Diff’s

• Some software is exceedingly complicated, doesn’t include “silent switches”, or simply won’t install with the other two mechanisms.• For these, we run a “diff”, yo.

• The process to do this…• Build a barebones desktop of the same OS/SP. Virtual

machines make this easy.• Snapshot its initial configuration.• Install and configure the application.• Re-Snapshot again.• Run the packager’s “diff” tool to log and subsequently

package the file/driver/registry changes.• In some cases this can be easier than an EXE

install.

Repackaging – Diff’sRepackaging – Diff’s

SLIGHT PROBLEM: Most packagers that can do this are expensive, natch.• Caphyon Advanced Installer

• WinINSTALL MSI Packager

• Wise for Windows Installer

• EMCO MSI Package Builder

• Acresso AdminStudio

• Acresso InstallShield

But there are some freeware alternatives…• Some of the above’s “free” versions

• AppDeploy Repackager

• SMSInstaller

• WinINSTALL LE We’ll use WinINSTALL LE in a sec…

DEMODEMOAnalyzing a “diff” InstallationAnalyzing a “diff” Installation

Get Your Free Copy of WinINSTALL LE at:

http://www.scalable.com/wininstall-le

Post-Installation CustomizationPost-Installation Customization

NEXT STOP: Customizing that app after its installed.

Post-Installation CustomizationPost-Installation Customization

• NEXT STOP: Customizing that app after its installed.• For nearly all Windows applications, customization

is stored in the registry.• Whole-machine customization in HKLM.• Per-user customization in HKCU.

• The easiest way to determine post-installation customization is using that same “diff” packager tool.• Snapshot after installation• Make a configuration change• Re-snapshot• Package registry change• Distribute the registry change.

Post-Installation CustomizationPost-Installation Customization

HKLM is easy to manipulate.• Settings are per-machine.

HKCU can be a little more difficult.• User must be logged in for HKCU hive to be loaded.

This process gets waaaaaay easier with Group Policy Preferences.• Are you seriously not using them yet?

• With GPPs, creating custom registry changes is crazy easy.

DEMODEMOUsing “diffs” forUsing “diffs” forConfiguration ControlConfiguration Control

Group Policy PreferencesGroup Policy Preferences

Applications and Windows itself store its configurations either in the registry or in files.

What then we need is…– A toolset that allows admins to easily input custom

configurations without requiring coding.

– Environment variables, files, folders, INI files, registry settings, network shares, shortcuts.

– Data sources, devices, folder options, local users and groups, network options, power options, printers, scheduled tasks, services.

Solution: GPPs!

DEMODEMOGroup Policy Group Policy PreferencesPreferences

32

Part IIPart IIThe Science of Software The Science of Software DeploymentDeployment

33

From Package to SoftwareFrom Package to Software

Now that you’ve got a software package, you need to get it deployed to machines.

Multiple software deployment solutions exist, with various price points…• Microsoft ConfigMgr

• Microsoft SCE

• Altiris

• Kaseya

• Kace KBOX

• Active Directory

• MDTFree

Not Free

One Way: GP Software One Way: GP Software InstallationInstallation

Group Policy Software Installation (GPSI) is free and has already bromanced your Active Directory– Generally limited to MSI installations.

Although ZAP files allow EXE installations.– Careful: Deleting a GP in the wrong way can

automatically uninstall software everywhere.

– GPs have no reporting component. No way to know where failures have occurred.

…but, it is free.

One Way: GP Software One Way: GP Software InstallationInstallation

Four Steps to installing software via GPSI:– Obtain a “silenced” MSI installation package

– Create a software distribution shared folder

– Create a GPO

– Assign or Publish the software

One Way: GP Software One Way: GP Software InstallationInstallation

Four Steps to installing software via GPSI:– Obtain a “silenced” MSI installation package

– Create a software distribution shared folder

– Create a GPO

– Assign or Publish the software

Assignment vs. Publishing– When a package is Assigned, the software isn’t

downloaded and installed until its initial use. The user must click its icon to start the process.Eliminates software that users don’t use, but increases the time to start on first use.

– When a package is Published, it appears in Add/Remove Programs.The user must choose to “Install a program from the network”You cannot Publish to Computer objects

Another Way: Task Sequences in Another Way: Task Sequences in Microsoft Deployment ToolkitMicrosoft Deployment Toolkit

MDT includes multiple ways to inject applications directly into installed OS images.– Select them at deployment time.

– Add them into a Task Sequence.

Deploying apps via MDT starts with repackaging…

Another Way: Task Sequences in Another Way: Task Sequences in Microsoft Deployment ToolkitMicrosoft Deployment Toolkit

Applications without source files is used for deploying prepackaged applications.

Application bundles link packages together.

Injecting Apps During MDT Injecting Apps During MDT InstallationInstallation

Create new applications in MDT.

Injecting Apps During MDT Injecting Apps During MDT InstallationInstallation

Once added, applications can be selected during the installation.

Injecting Apps During MDT Injecting Apps During MDT InstallationInstallation

– Alternatively,app installscan be addedto a TaskSequence.

– Adding thereeliminates thequestionsduring install.

Windows 7 Deployment Deep DiveWindows 7 Deployment Deep Dive

Packaging Software for Packaging Software for Automated DeploymentAutomated Deployment

Greg Shields, MVP, vExpertGreg Shields, MVP, vExpertConcentrated Technologywww.ConcentratedTech.com