Software installation process

The software installation process has three phases: preinstallation activities, the main installation,
and postinstallation activities.

1. Preinstallation activities:

You can do these activities days or even a few weeks in advance. To plan and prepare
your server before you install your software, use the appropriate planning and
preparation topics to guide you through the activities that you need to do.

o Upgrading to V5R3 from either V5R1 or V5R2: Checklist: Software upgrade or

replacement readiness
o Replacing Licensed Internal Code and i5/OS™ of the same version and release to
support new hardware: Checklist: Software replacement (V5R3 to V5R3)
o Installing V5R3 on a new server or logical partition: Checklist: Software
installation readiness

These activities include verifying your order, checking the amount of available disk
space, backing up your server, and cleaning your media device. In a software upgrade or
replacement, some of the tasks are required. If you do not perform these required tasks,
you will be forced to restart the installation.

2. The installation process:

The installation process begins when you start performing the instructions in one of the
procedural topics. For example, to upgrade to the new release, you might have chosen
automatic installation. The automatic installation process installs the Licensed Internal
Code, the operating system (i5/OS), and licensed programs. You would have minimal
interaction with the system, except to load the optical distribution media and to monitor
the system.

Your only installation activity might be changing the primary language or installing
additional licensed programs. Or, perhaps you want to perform these activities after an
automatic or manual installation.

3. Postinstallation activities:

The last step of each procedure directs you to use a completion checklist. You might be
directed to additional steps, such as saving your system and performing installation
activities on workstations for IBM® eServer™ iSeries™ Access Family products. Other
activities could include customizing your system, or setting usage limits for user-based
priced products. Before you begin production work on your system, be sure to
adequately protect your system from unauthorized use.
 The following figure shows an example of one type of software installation. (Your
particular installation might not include all of the topics that are shown in this figure.)

Figure 1. Overview of the installation process

The procedure that you use for software installation depends on what you plan to install.

Install software on a new server

If you just received a new server, the operating system and other licensed programs
might or might not be installed already.

Upgrade or replace existing software

If you are upgrading or replacing your existing OS/400® or i5/OS software, use either
the automatic installation method or the manual installation method.
 Automatic installation
This replaces your existing release with minimal user interaction. The language feature
code on the distribution media is installed as the primary language on the server. The
automatic installation process keeps the current environment and system values. The
process can add all nonconfigured disk units to the system auxiliary storage pool (ASP)
and retain the ASP configuration of previously configured disk units. The automatic
installation process is recommended for use with most servers.

Manual installation
This interactively replaces your existing release by using the Work with Licensed
Programs menu. Displays that require responses appear on the console. During a manual
installation, you can change installation options. Use the manual installation process if
you are doing any of the following installation procedures:

 Adding a disk device using mirrored protection, device parity protection, or user
auxiliary storage pools.
 Changing the environment (i5/OS or System/36™), system values, language
feature code, or configuration values.
 Planning to use an alternate installation device when you upgrade.
 Creating logical partitions during the installation process.
 Using tapes created with the Save System (SAVSYS) command. (The SAVSYS
command creates tapes that are meant for recovery.)

Add licensed programs

When you add additional licensed programs (in addition to those done already in the
methods mentioned above) or optional parts of licensed programs, you use the method
done through option 11 (Install licensed programs) of the Work with Licensed Programs
(LICPGM) menu. Typically you use option 11 when you need to install a new licensed
program or to replace a single licensed program.

Add or change globalization support

When you add a secondary language, you add additional language objects for the
licensed programs that are installed on your system.

When you change the primary language, you replace the existing language objects.
Depending on the procedure that you use, you can also replace program objects.

If a failure occurs during the installation process, Troubleshooting software installation problems
contains information that can help you determine the problem and the necessary recovery steps.

Installation (computer programs)

From Wikipedia, the free encyclopedia

Jump to: navigation, search

 This article has multiple issues. Please help improve it or discuss these issues on the talk page.

 It needs additional references or sources for verification. Tagged since April 2010.
 It may need a complete rewrite to meet Wikipedia's quality standards. Tagged since
May 2009.

Installation (or setup) of a program (including drivers, plugins, etc.) is the act of putting the
program onto a computer system so that it can be executed.

Because the requisite process varies for each program and each computer, many programs
(including operating systems) come with a general-purpose or dedicated installer – a specialized
program which automates most of the work required for their installation.

Contents
[hide]

 1 Overview
 2 Type of Installations
 3 Installer
o 3.1 Bootstrapper
o 3.2 Common installers
 4 See also
 5 References
 6 External links

[edit] Overview

Some software can be executed by simply copying it to a computer and executing it with no
further ado; no installation procedure as such is required. Other programs are supplied in a form
not suitable for immediate execution, and require an installation procedure. Installation may
include unpacking of files supplied in a compressed form, copying them to suitable locations,
tailoring the software to suit the hardware and the user's preferences, providing information
about the program to the operating system, and so on. The installer may test for system
suitability and available mass storage space.

Some software is designed to be installed simply by copying their files to the desired location,
and there is no formal installation process. This was once usual for many programs running
under MS-DOS, Mac OS, Atari TOS, and AmigaOS. This is the "de facto" standard in Mac OS
X applications and is also used for many Windows applications. Windows applications that do
not require installation are often times called "portable," as they do not require an installation to
run, and may be run for many different computers with only the executable. There are versions
of some operating systems which do not require installation and can be run directly from a
bootable CD, DVD, or USB drive. This allows one to test out the operating system without
altering the existing setup. Examples are AmigaOS 4.0, different Linux distribution, MorphOS
AmigaOS clone, or Mac OS 1-9.

Installation usually implies that once installed, the program can be executed again and again,
without the need to reinstall before each execution. Some software does not need installation at
all. There is server-based software that mimics locally-installed software, and can be run inside
of a web browser, using only the local system's cache. This allows portability among computers
with access to the server. This technique is often referred to as cloud computing.

Common operations performed during software installations include creation or modification of:

 Shared and non-shared program files

 Folders/directories
 Windows registry entries
 Configuration file entries
 Environment variables
 Links or shortcuts

[edit] Type of Installations

Silent installation

Installation that does not display messages or windows during its progress. "Silent installation"
is not the same as "unattended installation", though it is often improperly used as such.

Unattended installation

Installation that is performed without user interaction during its progress or, in a stricter sense,
with no user present at all, except eventually for the initial launch of the process. An installation
process usually requires a user who "attends" it to make choices at request: accepting an EULA,
specifying preferences and passwords, etc. In graphical environments, installers that offer a
wizard-based interface are common. However these installers may also provide command line
switches that allow performing unattended installations.

Answer file

Some unattended installations can be driven by a script providing answers to the various choices
such as the answer file which can be used when installing Microsoft Windows on a large
number of machines.

Self installation

Unattended installation, without the need of initial launch of the process (i.e. Vodafone Mobile
Connect USB Modem or Huawei E220's Mobile Partner software that self-installs from the USB
port).

Headless installation
 Installation performed without using a monitor connected to the destination computer (in
particular, on a computer with no video output at all). This can be an (attended) installation
performed from another machine connected via LAN or via a serial cable.

Unattended and headless installations are common tasks for system administrators.

Clean installation

Given the complexity of a typical installation there are many factors that may interfere with its
successful completion. In particular files that are leftover from old installations of the same
program or an unstable situation of the operating system may all act to prevent a given program
from installing and working correctly. An installation performed in absence of such interfering
factors (which may vary from program to program) is called a clean installation. In particular, a
clean operating system installation can be performed by formatting its destination partition
before the actual installation process.

Flat installation

An installation of a program performed from a copy (called a flat copy) of its original media
contents (mostly CDs or DVDs) to a hard drive, rather than directly from the media. This may
help in some situations where the target machine isn't able to cope with random access reads
from CD/DVD at the same time as performing the CPU-intensive tasks often required by an
installation, or where the target machine does not have an appropriate physical drive.

Network Installation

An installation of a program from a shared network drive. This may simply be a copy of the
original media (as in a Flat Installation), but frequently, software publishers which offer site
licenses for institutional customers provide a version intended for installation over a network.

Virtual installation

AmigaOS features a centralized standard installation utility called Installer since version 2.0 in
1991. It is driven by a LISP language interpreter, and users have the faculty of editing the
installation scripts as these are plain text files. Installer also features the unsurpassed chance for
users to perform virtual installations and verify any possible problem before committing the real
installation.

[edit] Installer

An installation program or installer is a computer program that installs files, such as applications,
drivers, or other software, onto a computer. Some installers are specifically made to install the
files they contain; other installers are general-purpose and work by reading the contents of the
software package to be installed.

The differences between a package management system and an installer are:

 Package Management System Installer

Typically part of the operating

Each product comes bundled with its own installer.
system.

Performs its own installation, sometimes recording information

Uses a single installation database.
about that installation in a registry.

Can verify and manage all packages

Only works with its bundled product.
on the system.

Single package management system

Multiple installer vendors.
vendor.

Single package format. Multiple installation formats.

[edit] Bootstrapper

During the installation of computer programs it is sometimes necessary to update the installer or
package manager itself. To make this possible, a technique called bootstrapping is used. The
common pattern for this is to use a small executable file (e.g. setup.exe) which updates the
installer and starts the real installation after the update. This small executable is called
bootstrapper. Sometimes the bootstrapper installs other prerequisites for the software during the
bootstrapping process too.

[edit] Common installers

Cross platform installer builders that produce installers for Windows, Mac OS X and Linux
include InstallAnywhere (Flexera Software), JExpress (DeNova),[1] and InstallBuilder (BitRock
Inc.).

Installers for Microsoft Windows include Windows Installer, a software installation component.
Additional third party commercial tools for creating installers for Windows include InstallShield
(Flexera Software), InstallAware (InstallAware Software),[2] Wise Installation Studio (Wise
Solutions, Inc.), SetupBuilder (Lindersoft, Inc.),[3] Installer VISE (MindVision Software), MSI
Studio (ScriptLogic Corporation), Actual Installer (Softeza Development),[4] Smart Install Maker
(InstallBuilders Company),[5] MSI Factory and Setup Factory (Indigo Rose Software), Centurion
Setup (Gammadyne Corporation)[6]. Free alternative installer-authoring tools include NSIS,
IzPack, Clickteam, InnoSetup, InstallSimple and WiX.

Mac OS X includes Installer, a native Package Manager software. Mac OS X also includes a
separate software updating application, Software Update but only supports Apple and system
software. Included in the dock as of 10.6.6, the Mac App Store shares many attributes with the
successful App Store for iOS devices, such as a similar app approval process, the use of Apple
ID for purchases, and automatic installation and updating. Although this Apple's preferred
delivery method for Mac OS X,[7] previously purchased licenses can not be transferred to the
Mac App Store for downloading or automatic updating. Commercial applications for Mac OS X
may also use a third-party installer, such as Mac version of Installer VISE (MindVision
Software) or InstallerMaker (StuffIt).

Step-by-Step Guide to Software Installation and Maintenance

Software Installation and Maintenance for the Windows® 2000 operating system allows administrators to manage
software for their organizations, including applications, service packs, and operating system upgrades. This
overview guide explains how to use the Software Installation extension of the Group Policy Microsoft Management
Console snap-in to specify policy settings for application deployment for groups of users and computers.

On This Page

Introduction
Prerequisites and Initial Configuration
Software Installation Snap-in CONFIGURATION
Software Installation and Maintenance Scenarios
Appendix – An Excel 97 .Zap File
Related Links

Introduction

This document is part of a set of step-by-step guides that introduce the Change and Configuration Management
features of the Windows® 2000 operating system. This guide presents an overview of Software Installation and
Maintenance. It also explains how to use the Software Installation extension of the Group Policy Microsoft
Management Console snap-in to specify policy settings for application deployment for groups of users and
computers.

Software Installation and Maintenance is dependent upon both the Active Directory and Group Policy.
Administrators who are responsible for Software Installation and Maintenance should be familiar with both of these
technologies.

Publish vs. Assign

Administrators can use Software Installation and Maintenance to either publish or assign software:

 Publish. Administrators publish applications that users may find useful, allowing users to decide whether to
install the application. You can only publish to users, not computers.

 Assign. Administrators assign applications that users require to perform their jobs. Assigned applications
are available on users' desktops automatically.

For a comparison of these capabilities, see Table 1 below. Administrators deploy applications in Group Policy
objects (GPOs) that are associated with Active Directory containers such as sites, domains, and organizational units
(OUs).

Table 1 Publishing and Assigning Software

Assign to
Publish to Users Assign to Users Computers

After the If an application is deployed in If an application is deployed in The next time the
 administrator a GPO that is already applied a GPO that is already applied computer starts
deploys the to the user from a previous to the user from a previous (reboot).
software, it is logon, it is available for logon, it is available for
available for installation in the current installation in the current logon
installation: logon session (from the session (from the Add/Remove
Add/Remove Programs Control Programs Control Panel). If the
Panel). If the application is application is deployed in a
deployed in a new GPO that is new GPO that is not already
not already associated with the associated with the user, then
user, then it is available at the it is available at the next
next logon. logon.

Typically, users The Add/Remove Programs in Start menu shortcut. The software is
install the software Control Panel. Desktop shortcut. already installed.
from: Add/Remove Programs in
Control Panel.

If the software is Yes. Yes. The software is

not installed and already installed.
the user opens a
file associated with
the software, will
the application
install?

Can the users Yes. Users can re-install the Yes. The software will be re- No. Only the local
remove the application from the advertised immediately. This administrator can
software using the Add/Remove Programs in means that the shortcuts will remove the
Add/Remove Control Panel. be present in the users' software. A user
Programs in desktops and they can re- can run a repair
Control Panel? install the application by on the software.
clicking on a shortcut, for
example.

Supported Windows Installer packages Windows Installer packages Windows Installer

installation file (.msi files), and ZAP files. (.msi files) packages (.msi
types: files)

Supported Installation File Types

Software Installation and Maintenance supports Windows Installer packages (.msi files), repackaged files, and .zap
files.

A Windows Installer package (.msi file) contains all the information necessary to describe to the Windows Installer
how to set up an application. It covers every conceivable situation: various platforms, different sets of previously
installed products, earlier versions of a product, and numerous default installation locations. Some applications
such as Office 2000 provide their own .msi files. These are referred to as natively-authored Windows Installer
packages.

You can create Windows Installer packages for your applications by using package-authoring tools provided by
various vendors such as InstallShield Software Corporation and WISE Solutions, Inc. See the section on Windows
Installer Applications for more information.
You can also repackage an existing application for use with the Windows Installer. To create a package for the
application, you use a repackaging tool such as the VERITAS WinInstall LE, described later in this document.

Non-Windows Installer-based applications must use a .zap file to describe their existing setup program. A .zap file
is a text file (similar to .ini files) that provides information about how to install a program, the application
properties, and the entry points that the application should install. A sample .zap file is included in the appendix -
An Excel 97 .Zap File.

Top of page

Prerequisites and Initial Configuration

Prerequisites

This Software Installation and Maintenance document is based on the two-part, "Step-by-Step Guide to a Common
Infrastructure for Windows 2000 Server Deployment"
http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp

Before beginning the steps in this guide, you need to build the common infrastructure, which specifies a particular
hardware and software configuration. If you are not using the common infrastructure, you need to make the
appropriate changes to this guide.

Software Installation and Maintenance is dependent on Group Policy. It is highly recommended that you complete
the Group Policy step-by-step guide before the Software Installation and Maintenance guide.

Note: If you completed the Group Policy guide, it may be necessary to disable some of the policies particularly the
loopback policies, as they may not allow people to install software from the Add/Remove Programs in the Control
Panel.

Additionally, you may want to use the "Step-by-Step Guide toRepackaging Software for the Windows Installer
Using VERITAS WinINSTALL LE "and repackage some software before you continue with this guide.

Windows Installer Applications

Software Installation and Maintenance leverages the new Windows Installer service that is a part of the Windows
family of operating systems. (The Windows Installer is available in Windows 2000, Windows NT 4.0, Windows 98
and Windows 95.)For the best performance and the greatest reduction in TCO, you need to use applications that
support the Windows Installer.

No sample applications are supplied for these guides. You must acquire applications such as Microsoft Office 2000
that supply a natively authored Windows Installer package (an .msi file). Or you must use an authoring or
repackaging tool to create Windows Installer packages for your software.

You can author a Windows Installer package using a package-authoring tool if you have all of the files and know
the architecture of the application. Package authoring tools are available from the following vendors:

 InstallShield Software Corporation. Information is available at the InstallShield Web site

http://www.installshield.com.

 WISE Solutions, Inc. For information, see the WISE Solutions Web site http://www.wisesolutions.com.

If you want to use Software Installation and Maintenance with an existing application, you may want to consider
repackaging the application to support the Windows Installer. The VERITAS WinInstall LE for repackaging of
existing applications for use by the Windows Installer is available on the Windows 2000 Server CD. If you are
unfamiliar with repackaging software, see the "Step-by-Step Guide to Repackaging Software for the Windows
Installer Using VERITAS WinINSTALL LE," which explains how to use their repackager.

For more information on this tool, please see the VERITAS Web site http://www.veritas.com.
Best Practice

 You may want to consider natively authoring a Windows Installer package rather than repackaging the
application if you have all of the files for an application, if you know the changes that application makes to
the registry for installation, and if there are not too many files.

 Success with repackaging is affected by the state of the computer where the repackaging is performed.
For best results, you should always start the repackaging of an application with a clean computer. For the
purpose of repackaging, a clean computer is defined as a computer that has only the operating system
and operating system service packs installed prior to running the VERITAS Discover program.

Other companies will provide their applications with native Windows Installer support. Please contact your favorite
application vendors for information on their Windows Installer support plans.

Non-Windows Installer Applications

It is possible to publish applications that do not install with the Windows Installer. They can only be published to
users and they are installed using their existing Setup programs.

Because these non-Windows Installer applications use their existing Setup programs, such applications cannot:

 Use elevated privileges for installation.

 Install on the first use of the software.

 Install a feature on the first use of the feature.

 Rollback an unsuccessful operation, such a install, modify, repair, or removal, or take advantage of other
features of the Windows Installer.

 Detect a broken state and automatically repair it.

Before an existing Setup program can be used with Software Installation and Maintenance, it must be described in
a ZAP (.zap) file, which is a text file, similar to .ini files, which provides the following information:

 How to install the program -- which command line to use.

 The properties of the application -- name, version, language.

 The entry points that the application should automatically install -- for file extension, CLSID, and ProgID.

Note that .zap files are stored in the same location on the network as the Setup program they reference. The
appendix contains an example of a .zap file.

Creating a Software Distribution Point for the Windows Installer Applications

To manage software, you must create a software distribution point (SDP) that contains all the Windows Installer
packages (.msi files), .zap files, and the actual software files.

To create a software distribution point, you do the following:

 Create a network share along with the appropriate folders for software distribution.

 Copy the Windows Installer packages, application executable files, and .zap files to the appropriate shared
folder.
  Set the appropriate permissions for the high-level network shared folder. Users must have the ability to
read from the software distribution point. Set the following Discretionary Access Control (DACL)
permissions:

Everyone: Read
Administrators: Full Control, Change, and Read.

The following procedure shows you how to set up the distribution point.

To create the software distribution point:

1. Log on to the HQ-RES-DC-01 server as an administrator.

2. Double-click the My Computer icon.

3. Double-click the hard-drive icon of the local disk where you want to create the software distribution point.

4. On the File menu, select New, and then click Folder.

5. Under the New Folder in the selected drive pane, type Managed Applications.

6. Right-click the Managed Applications folder, and select Properties from the context menu.

7. In the Managed Applications Properties page, click the Sharing tab, click Share this folder, and then
type Reskit Managed Applications in the Comment text box.

8. Click Permissions. In the Permissions for Managed Applications dialog box, select Everyone, and
then under Permissions, clear the Allow permission for the Full Control and Change check boxes.
Ensure that Everyone has only Read access to the folder. Click Add.

9. In the Select Users, Computers or Groups dialog box, under Name click Administrators, and then
click Add. (Note the Look in text box should be pre-populated with reskit.com.) Click OK.

10. In the Permissions for Managed Applications dialog box, select Administrators, and then under
Permissions, set the Full Control and Change permissions to Allow. Ensure that Administrators have
Full Control, Change, and Read access to the folder. Click OK.

11. In the Managed Applications Properties dialog box, click OK.

At this point, you should repeat the preceding steps to create any additional folders for the software you are
managing. Note that each sub-folder does not need to be explicitly shared or have permissions set. Afterwards,
you should copy the Windows Installer packages, .zap files, and the application files to the appropriate shared
folders.

You should note that for computer-assigned applications, the network share needs to be reachable by the local
system account. This is not the default for Windows NT 4.0 and Novell servers.

Best Practice Administrators should consider using either the distributed file system (Dfs) feature of Windows
2000 Server or Microsoft Systems Management Server to manage their software distribution points.

Top of page
Software Installation Snap-in CONFIGURATION

The Active Directory Users and Computers snap-in is part of the Administrative Tools program group. It already has
a Group Policy and Software Installation snap-in. You may either follow these steps to configure your own tool, a
saved snap-in, or use the Active Directory Users and Computers snap-in.

Creating a Software Installation Snap-in Tool

To create the Software Installation snap-in:

1. Log on to the HQ-RES-DC-01 server as an administrator.

2. Click Start, click Run, type mmc, and then click OK.

3. In the MMC console, click Add/Remove Snap-in on the Console menu.

4. In the Add/Remove Snap-in dialog box, click Add.

5. In the Add Stand-alone Snap-in dialog box, click Active Directory Users and Computers on the
Available Standalone Snap-ins list, and then click Add. Click Close, then click OK.

6. In the console tree, double-click Active Directory Users and Computers to expand the tree, double-
click the reskit.com domain, double-click the Accounts organizational unit (OU).

7. Click the + next to the Headquarters OU.

Saving the Software Installation Snap-in Tool

As you go through this guide, you may want to save changes to the MMC console.

To save your changes:

1. In the MMC console, click Save on the Console menu.

2. In the Save dialog box, type SIM Tool in the File name text box, and then click Save.

Your snap-in will look similar to Figure 1 below.

Figure 1: Software Installation Snap-In

Creating a Group Policy Object

If you have already completed the Group Policy step-by-step guide, then you may have already created the
necessary Group Policy objects (GPOs).

To create a Group Policy Object (GPO):

1. In the Software Installation snap-in tool you just saved (SIM Tool console), in the console tree, double-
click Active Directory Users and Computers, double-click reskit.com, and then double-click
Accounts.

2. Right-click Headquarters, and select Properties from the context menu.

3. In the Headquarters Properties dialog box, click the Group Policy tab, and then click New.

4. Type HQ Policy.

This creates a new Group Policy object called HQ Policy.

At this point, you could add another GPO—giving each one that you create a meaningful name—or you
could choose to edit a GPO, which starts the Group Policy and Software Installation snap-ins. If you have
more than one GPO associated with an Active Directory folder, verify the order; a GPO that is higher in the
list is processed first.

5. Click Close.

Best Practice Consider using security descriptors (DACLs) on the GPO to increase the granularity of software
management for your organization.

To close the Software Installation snap-in:

1. In the SIM Tool console, click Save on the Console menu.

2. Click Exit on the Console menu.

To edit a Group Policy Object (GPO):

1. Log on to the HQ-RES-DC-01 server as an administrator.

2. Click Start, point to Programs, click Administrative Tools, and then click SIM Tool.

3. In the SIM Tool console, double-click Active Directory Users and Computers, double-click
reskit.com, and then double-click Accounts.

4. Right-click Headquarters, and select Properties from the context menu. In the Headquarters
Properties dialog box, click the Group Policy tab. Right-click HQ Policy in the Group Policy Object
Links list box, and click Edit.

This opens the Group Policy snap-in.

5. In the Group Policy snap-in, under Computer Configuration node, double-click Software Settings.

6. In the console tree, under the User Configuration node, double-click Software Settings.
You have opened the Software Installation snap-in for the HQ Policy GPO. Your snap-in should look like Figure 2
below.

Figure 2: Group Policy Snap-In

You can use the Software Settings node in the console tree under HQ Policy and Computer Configuration to
assign an application to computers that are managed by this GPO. You use the Software Settings node under the
User Configuration node to assign or publish an application to users who are managed by this GPO.

Configuring the Software Installation Defaults for a Group Policy Object

You can configure default settings for Software Installation on a per-Group Policy Object (GPO) basis.

To specify software installation defaults for the selected Group Policy object, you use the Software Installation
Properties dialog box, shown below in Figure 3. This section explains some of the available options.
Figure 3: The Software Installation Properties page

Setting Options for New Packages and Installation User Interface

To control what happens when you add a new package to the selected GPO, you use the General tab in the
Software Installation Properties dialog box, and set options in the New packages frame. The default behavior
is that the Deploy Software dialog box appears each time, and the administrator can select one of the choices
from that dialog box.

If you are going to deploy several packages to a GPO as published without transforms, you can select Publish in
the New Packages frame, and every package that is deployed is automatically published. If you are going to add
a package with a transform (customization or .mst file), you must select Advanced published or assigned.

Note: You cannot add or change transforms (.mst files) after the software is deployed.

This setting is most useful when an administrator is adding several applications at one time. For example, if an
administrator is adding five applications to this GPO and they are all to be published with no transforms, then the
administrator could set this to Publish.

Similarly, the options in the Installation user interface options frame allow the administrator to set how much
of the user interface (UI) the Windows Installer presents to a user during installation. The Basic UI (the default
option) only presents progress bars and messages; no user choices are presented other than Cancel. The
Maximum UI option shows the UI that the author of the Windows Installer package defined.

Setting Options for Categories

When an organization has a large amount of software to manage, administrators can create categories for
software. These categories can then be used to filter the software in the Add/Remove Programs in Control
Panel. For example, you could create a category called Productivity Applications and include software such as word
processing and database management applications.
Although there is a Categories tab on the Software installation Properties dialog box, categories are
established on a per-domain basis. This means the domain administrator can create and edit the categories from
any of the Software installation Properties pages for any GPO in the domain. Administrators can then use these
categories with software they are managing within any GPO in the domain. There are no default or supplied
categories.

Best Practice Because Categories are established per domain rather than per GPO, an organization should
standardize the Categories and create them in a centralized manner.

To configure the default settings:

1. In the Group Policy snap-in console tree, right-click Software installation under User Configuration,
and then click Properties. This opens the Software Installation Properties dialog box. You use this
dialog box to set defaults for software installation in the current GPO. You can set the default package
location to the network location of the software distribution point you created earlier. Then you do not
have to browse for each package that you add.

2. In the Software installation Properties dialog box, click Browse.

You need to browse for the software distribution point you created in the previous section relative to the
network share location, rather than the local drive on the server. This ensures that you are managing
software from the network share location that users can access. Users cannot access the package from
the local drive of the server.

3. In the Browse for Folder dialog box, click the plus sign (+) next to My Network Places, double-click
Entire Network, double-click Microsoft Windows Network, and then double-click reskit.com.

4. Double-click HQ-RES-DC-01, click Managed Applications, and then click OK.

Note: The exact navigation above may differ on your network. Be sure that you are pointing to the
software distribution point relative to the network rather than relative to the local drive on the server.

5. In the Software Installation Properties dialog box, click the General tab, select the Display the
Deploy Software dialog box (default) in the New Packages field, and select Basic (default) in the
Installation user interface options field.

6. In the Software installation Properties dialog box, click the Categories tab. Click Add.

7. In the Enter new category dialog box, type Productivity Applications in the Category text box, and
then click OK. In the Categories tab, click Add.

8. In the Enter new category dialog box, type System Applications in the Category text box, and then
click OK. Click OK.

Later, if you want to change these defaults or add additional categories for the organization, you can return to the
Software installation Properties dialog box. As mentioned previously, categories are per-domain, not per GPO.

At this point you can either close the Software Installation snap-in or proceed with the scenarios described next.

Top of page
Software Installation and Maintenance Scenarios

Scenarios Covered in this Document

This guide covers a few basic scenarios for Software Installation and Maintenance, including:

 Assigning repackaged Microsoft Word 97 (to users).

 Publishing Microsoft Excel 97 (using a .zap file).

 Removing Excel 97.

 Upgrading Word 97 to Microsoft Office 2000 (using an Office 2000 transform).

 Assigning Windows 2000 to a computer (a new build).

As the packages for these applications are not included, you may have to modify the step-by-step guide. You may
use applications that either natively support the Windows Installer or that you have repackaged for the Windows
Installer.

Please note that this guide does not describe all of the possible Software Installation and Maintenance scenarios.
You should use this guide to gain an understanding of Software Installation and Maintenance. Then think about
how your organization might use software installation and the other IntelliMirror features to reduce TCO.

Note: If you completed the Group Policy step-by-step guide, it may be necessary to undo some of the Group Policy
to complete this guide. For example, the Loopback policy disables the ability to access the Add/Remove Programs
in the Control Panel.

Assigning Repackaged Word

Whether publishing or assigning software, the basic steps are fundamentally the same. This guide presents a
scenario for assigning a repackaged version of Microsoft Word 97 for users.

This procedure assumes that you have already created a Word97 folder in the software distribution point created
earlier, and that you are using a repackaged version of Microsoft Word 97.

Note: To assign to users, start in the Group Policy snap-in User Configuration node. To assign to computers, start
in the Computer Configuration node.

To assign repackaged Word or other software:

1. Log on to the HQ-RES-DC-01 server as an administrator.

2. Click Start, point to Programs, click Administrative Tools, and then click SIM Tool.

3. In the SIM Tool console, double-click Active Directory Users and Computers, double-click
reskit.com, and then double-click Accounts.

4. Right-click Headquarters, and select Properties from the context menu. In the Headquarters
Properties dialog box, click the Group Policy tab. Right-click HQ Policy in the Group Policy Object
Links list box, and click Edit to open the Group Policy snap-in.

5. In the Group Policy snap-in, under User Configuration, double-click Software Settings, right-click
Software installation, and then select New from the context menu. Click Package.

6. In the Open dialog box, click the Word97 folder.

 7. You need to substitute the folder for the software you are going to deploy, from the software distribution
point you created earlier.

8. Click Open. Click Word, and click Open. In the Deploy Software dialog, click Assigned, and then click
OK.

Note: If you are going to deploy a Windows Installer package with a transform, you have to select Configure
package properties in the Deploy Software dialog so that you can associate the transform with the package.
Make any other changes to the properties at this point, before you press OK to either assign or publish the
software.

The application is added to the Software Installation snap-in as assigned. After the application is assigned, you can
right-click the application entry in the details pane to view the assigned applications property pages.

The application is assigned to all the users managed by the Headquarters GPO.

Verifying the Effect of Assigning Word

To verify the effect of assigning Word 97 to the Headquarters GPO, you can log on to Windows 2000 Professional
as a user who is managed by the Headquarters OU. (If you are using the common infrastructure, you could log on
to the client as [email protected], for example.)

When you log on to Windows 2000 Professional, you should see a Microsoft Word icon on the Start menu.

If you select Word, the Windows Installer installs Word for you. While the installation is proceeding, you should see
a progress indicator from the Windows Installer. When the installation is complete, Word starts and you can edit a
document.

If the software installation becomes damaged, then the next time the user selects Word from the Start menu, if all
the key files as defined in the Windows Installer package for Word are present, Word starts. If a key file is missing
or damaged, the Windows Installer repairs Word and then starts it.

Publishing Legacy Excel

To publish Excel 97 without repackaging it for the Windows Installer, you must first create a .zap file for Excel. Use
the .zap file example in the appendix as a model. You also need to create a folder for Excel97 in the software
distribution point you created earlier.

Open the Software Installation snap-in saved previously, and edit the Headquarters GPO. (See the steps in the
preceding section.) When you are ready to publish Excel 97, the snap-in should look like it did when you assigned
Word 97 in the previous section.

To publish Excel:

1. In the SIM Tool console, double-click Active Directory Users and Computers, double-click reskit.com,
and then double-click Accounts.

2. Right-click Headquarters, and click Properties.

3. In the Headquarters Properties dialog box, click the Group Policy tab, click the HQ Policy GPO, and
then click Edit to open the Group Policy snap-in.

In the Group Policy snap-in console tree, under User Configuration, double-click Software Settings,
right-click Software installation, and then select New from the context menu. Click Package.

4. In the Open dialog box, click the Excel97 folder, and click Open.
 In the Files of type combo box, click the down arrow, and then click ZAW Down-level applications
package (*.zap). Click Excel97, and click Open.

5. In the Deploy Software dialog box, the Publish option is already selected, click OK.

Excel 97 is published to the users managed by the Headquarters GPO.

Because a ZAP file publishes the existing Setup, the Setup will not run with elevated privileges. Therefore, you will
need to supply administrative privileges during the Setup. This can be done by using the Install Program as
Other User dialog box. Accessing this dialog is controlled by policy. A policy called Request credentials for
network installations is available in the Group Policy snap-in, under User Configuration\Administrative
Templates\Windows Components\Windows Explorer. If enabled, this policy displays the Install Program
As Other User dialog box even when a program is being installed from files on a network computer across a local
area network. For more information, see the Explain tab on this policy property page.

To set the Request Credentials for network installations policy:

1. In the SIM Tool console, navigate to the Headquarters OU, and then right-click Headquarters and click
Properties.

2. In the Headquarters Properties dialog box, double-click the HQ Policy GPO to open the Group Policy
snap-in.

3. In the Group Policy snap-in, under User Configuration, click the + next to Administrative Templates.

4. In the Request credentials for network installations dialog box, click Enabled, and click OK. Close
the Group Policy snap-in

In the Headquarters Properties dialog box, click OK.

5. In the SIM Tool console, click Save on the Console menu. Click Exit on the Console menu.

Verifying the Effects of Publishing Excel 97

To verify the effect of publishing Excel 97 to the Headquarters GPO, first log on to Windows 2000 Professional as a
user who is managed by the Headquarters OU. (If you are using the common infrastructure, you could log on as
[email protected], for example.)

To confirm the effects of publishing Excel 97:

1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.

2. In the Add/Remove Programs dialog box shown in Figure 4 below, click Add New Programs.

Note: Word 97, which was assigned, is listed in the Add/Remove Programs dialog box. This is so that
users can add or remove the assigned program if they need to. Even if a user removes the assigned
application, it is available for installation again the next time the user logs on.
 Figure 4: Add/Remove Excel 97

3. Select Microsoft Excel 97 from the Add programs from your network list, and click Add.

You should see the Install Program As Other User dialog box shown in Figure 5 below because you are
installing a non-Windows Installer based application.

Figure 5: Install Program as Other User

4. In the Install Program As Other User dialog box, click Run the program as the following user, type
Administrator in the User Name text box, and type the domain name (reskit) in the Domain box. If
you have an Administrator password set for this computer, you must enter this as well.

5. Click OK.
 Excel now installs using the original Setup program. You should follow the instructions in the original
Setup UI to complete the installation. After you have installed Excel, you can close the application.

6. Close Add/Remove Programs, and then close Control Panel.

7. Log off Windows 2000 Professional.

To remove Excel 97:

1. In the SIM Tool console, double-click Active Directory Users and Computers, double-click reskit.com,
and then double-click Accounts.

2. Right-click Headquarters, and click Properties.

3. In the Headquarters Properties dialog box, click the Group Policy tab, click the HQ Policy GPO, and
then click Edit to open the Group Policy snap-in.

4. In the details pane, right-click Microsoft Excel 97, and select All Tasks from the context menu.

5. Click Remove.

6. In the Remove Package dialog box, click Yes.

Note: Because Excel 97 was installed using a .zap file, you do not have the option to force the removal as
you would with a Windows Installer file.

Microsoft Excel 97 no longer appears in the details pane.

7. Log on to the Windows 2000 Professional as the Local Administrator (remember, Excel was installed as
Administrator in the preceding scenario).

8. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.

9. In the Add/Remove Programs dialog box, click the Microsoft Excel 97 entry in the Change or
Remove Programs frame, and then click Change/Remove.

10. The Excel 97 Setup program starts. In the Microsoft Excel 97 Setup dialog box, click Remove All.

11. When Setup prompts you about removing Microsoft Excel 97, click Yes. Click OK.

12. Close Add/Remove Programs, and then close Control Panel. Log off Windows 2000 Professional.

Upgrade Microsoft Word 97 to Office 2000 With a Transform

Office 2000 comes with a Windows Installer package natively authored. Before performing this upgrade, use the
Office 2000 Customization Wizard to create a transform. You must substitute the name of your transform in this
scenario.

This procedure assumes that you have placed the necessary files (.msi, .mst, and so on) in a folder called Office in
the software distribution point.

To upgrade Word 97 to Office 2000

 1. In the SIM Tool console, double-click Active Directory Users and Computers, double-click reskit.com,
and then double-click Accounts.

2. Right-click Headquarters, and click Properties.

3. In the Headquarters Properties dialog box, click the Group Policy tab, click the HQ Policy GPO, and
then click Edit to open the Group Policy snap-in.

4. In the Group Policy snap-in, under User Configuration, double-click Software Settings, right-click
Software installation, click New, and then click Package.

5. In the Open dialog box, click the Office folder, and click Open. Select the Office 2000 Windows Installer
package (data1.msi), and click Open.

6. In the Deploy Software dialog box, click Advanced published or assigned, and click OK.

7. In the Microsoft Office 2000 Properties dialog box, click the Modifications tab, and click Add.

8. In the Open dialog box, click Office, and then click Open. Select the Office 2000 transform (.mst), and
click Open.

Note: It is important that you do not click OK until you have set all the options for the modifications.

9. In the Microsoft Office 2000 Properties dialog box, click the Upgrades tab, and click Add.

10. In the Add Upgrade Package dialog box, Microsoft Word 97 should be highlighted in the Package to
Upgrade list box. If not, click it to select it. Click Uninstall the existing package, then install the
upgrade package, and then click OK.

11. In the Microsoft Office 2000 Properties dialog box, click the Required Upgrade for existing
packages checkbox. Do not click OK yet.

12. In the Microsoft Office 2000 Properties dialog box, click the Deployment tab, click Assigned in the
Deployment type field, and accept the default option (Basic) in the Installation user interface
options field.

Review all the tabs to make sure you have edited all the properties and you are ready to assign the
upgrade. Click OK.

Office 2000 with the transform is added to the Software Installation snap-in. The snap-in should now show Office
2000 as assigned, and it should show an upgrade relationship between Word 97 and Office 2000.

At this point, if you log on to Windows 2000 as a user in the HQ Policy GPO, you should see Word 97 being
removed, the start of the upgrade. When you select any of the Office icons from the Start menu, you install Office
2000 to complete the upgrade.

Assigning Windows 2000 to a Computer Upgrading Windows 2000

You can upgrade Windows 2000 to the release version.

Note: The operating system build being upgraded must be older than the build you are upgrading to.

If you completed the Group Policy guide before this, you may have turned off applying Group Policy to computers.
If this is the case, you need to change this before this Software Installation policy can be applied on the computers.
In this scenario, you assign the upgrade of Windows 2000 to computers managed by a policy created for the
Desktops OU under Resources. You could just as easily publish it for users.

The RES-WKS-01 computer should be in the Desktops OU. If it is not, you need to move it to one of the OUs under
the Resources OU. You can move the computer by highlighting it in the details pane of the Active Directory Users
and Computers Snap-in and then selecting Move from the context menu.

Note: To deploy the Winnt32.msi package, you need to modify the Unattend.txt file to include the Windows 2000
CD key information. Otherwise, the Setup program would ask for this information in a non-interactive desktop and
wait indefinitely.

1. Open the SIM Tool console you created earlier.

2. Double-click Active Directory Users and Computers, double-click reskit.com, and then double-click
Resources.

3. Right-click Desktops, and click Properties.

4. Click the Group Policy tab, click New, and type Desktop OS Upgrades. Press Enter. Click Edit.

5. In the Group Policy snap-in, under Computer Configuration, double-click Software Settings.

6. Right-click Software installation, click New, and then click Package.

7. Browse to the network to the software distribution point that has the Windows 2000 files.

Note: You may want to place the Windows 2000 CD in the CD drive of the server, and share the CD-ROM
drive as the software distribution point for these files. This saves having to copy all the files to the
software distribution point, although if the CD-ROM drive is not fast, the install may take longer.

8. Click the i386 folder, click Open, click WINNT32 (.msi file), and then click Open.

9. In the Deploy Software dialog box, the Assigned option on the Deploy Software dialog box is already
selected. Click OK.

10. Close the Group Policy snap-in, then in the Desktop Properties dialog box, click Close in the Group
Policy page.

11. In the SIM Tool console, click Save on the Console menu, and then click Exit on the Console menu.

At this point you should restart the RES-WKS-01 computer. When you do, the normal shutdown and startup
messages are displayed.

Eventually, in the Windows 2000 Professional startup dialogs you should see the following messages:

Applying Software Installation settings…

Followed by:

Windows Installer installing managed software Windows 2000 Professional…

The computer restarts and continues the upgrade.

Important Notes

The example company, organization, products, people, and events depicted in these guides are fictitious. No
association with any real company, organization, product, person, or event is intended or should be inferred.

This common infrastructure is designed for use on a private network. The fictitious company name and DNS name
used in the common infrastructure are not registered for use on the Internet. Please do not use this name on a
public network or Internet.

The Microsoft Active Directory™ structure for this common infrastructure is designed to show how Microsoft
Windows 2000 Change and Configuration Management works and functions with the Active Directory. It was not
designed as a model for configuring an Active Directory for any organization—for such information see the Active
Directory documentation.

Top of page

Appendix – An Excel 97 .Zap File

Below is an example .zap file for Microsoft Excel 97.

Use notepad to create the following text file and save it as excel.zap in the network folder that contains the Excel
97 setup program. The comments (any line that starts with ';') explain what each entry in the file is for.

The underscore ( _ ) is a continuation symbol, these lines should appear together on one line.

While the following example shows all of the possible entries in a ZAP file, note that many of these entries are
optional. The smallest possible ZAP file to publish Excel 97 using the existing setup would be:

[Application]
FriendlyName = "Microsoft Excel 97"
SetupCommand = \\servername\sharename\Excel 97\setup.exe
; ZAP file for Microsoft Excel 97
[Application]
; Only FriendlyName and SetupCommand are required,