Installation Utility

Installation Utility
Reference Manual
Supporting
Installation Utility 7.5.52
November 2006
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address
BMC SOFTWARE INC

2101 CITYWEST BLVD
HOUSTON TX 77042-2827
USA
Telephone
713 918 8800 or

800 841 2031
Fax
(01) 713 918 8000
Fax
713 918 8000
Outside United States and Canada

Telephone
(01) 713 918 8800
Copyright 2006 BMC Software, Inc., as an unpublished work. All rights reserved.
BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks
or trademarks of BMC Software, Inc.
IBM is a registered trademark of International Business Machines Corporation.
All other trademarks belong to their respective companies.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this
information is subject to the terms and conditions of the applicable End User License Agreement for the product and the
proprietary and restricted rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE
COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the
U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS
252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is
BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to
this address.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer
Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home.
From this website, you can
read overviews about support services and programs that BMC offers
find the most current information about BMC products
search a database for issues similar to yours and possible solutions
order or download product documentation
report an issue or ask a question
subscribe to receive proactive e-mail alerts when new product notices are released
find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or
send an e-mail message to [email protected]. Outside the United States and Canada, contact your local support center for
assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
product information
product name
product version (release number)
license number and password (trial or permanent)
operating system and environment information
machine type
operating system type, version, and service pack or other maintenance level such as PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service pack or
maintenance level
sequence of events leading to the issue
commands and options that you used
messages received (and the time and date that you received them)
product error messages

messages from the operating system, such as file system full
messages from related software
Installation Utility Reference Manual
Contents
Chapter 1
Installation overview
About the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The installation utility interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options for installing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options for selecting products to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting products by using the default installation path . . . . . . . . . . . . . . . . . . . .
Selecting products by using the custom installation path. . . . . . . . . . . . . . . . . . . .
Installing and configuring sudo to create a privileged account . . . . . . . . . . . . . . . . . .
Performing a multiple CD installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gathering product configuration information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
10
11
11
12
13
14
15
Chapter 2
17
Installing and uninstalling products in a Windows environment
Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing to a Windows Server 2003 computer from a network drive . . . . . . . . .
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying installation utility online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory and disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating, distributing, and installing installable images . . . . . . . . . . . . . . . . . . . . . . . .
Installable image files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Account requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an installable image of products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deploying the installable image to your environment . . . . . . . . . . . . . . . . . . . . . .
Installing an installable image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing control files for installable images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the ctltool to edit control files for installable images . . . . . . . . . . . . . . . . . .
Locating log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling BMC Software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing an attended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing an unattended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
18
18
19
21
21
22
22
23
24
42
42
43
43
45
46
49
49
51
52
53
54
57
Chapter 3
59
Installing and uninstalling products in a UNIX environment
Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Contents
Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Displaying installation utility online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Memory and disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Starting the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Creating, distributing, and installing installable images . . . . . . . . . . . . . . . . . . . . . . . . 79
Installable image files and directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Creating an installable image of products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Deploying the installable image to your environment. . . . . . . . . . . . . . . . . . . . . . . 81
Installing an installable image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Editing control files for installable images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using the ctltool to edit control files for installable images. . . . . . . . . . . . . . . . . . . 86
Locating log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Product installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Uninstalling BMC Software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Performing an attended uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Performing an unattended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Appendix A
Troubleshooting a Windows environment
93
Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
The installation utility will not launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
The computer on which you want to install products does not have a web
browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Online help does not display properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Installation fails with a failed to run script error . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Installable image installation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Installation fails with unable to connect to remote host error. . . . . . . . . . . . . . . . 98
Installation will not proceed past the specify installation directory page. . . . . . . 99
Installation utility may stop responding if double quotes and angle brackets are
used in a directory path during a multiple CD installation . . . . . . . . . . . . . . . . 99
After a product installation, Internet Explorer 5.0 stops responding and
consumes 99 percent CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
After a product installation, the installation utility cannot change a Windows
Server 2003 Itanium Terminal Server computer from install mode to execute
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
The installation utility is unable to perform directory-related functions on
Windows platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Where to find diagnostic information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Generating debug information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Sending diagnostic information to BMC Software Support . . . . . . . . . . . . . . . . . 104
Appendix B
Troubleshooting a UNIX environment
105
Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Typing errors cannot be corrected in an X-emulator . . . . . . . . . . . . . . . . . . . . . . . 107
The display cannot be opened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6
The installation utility will not launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Javascript error messages are displayed during installation . . . . . . . . . . . . . . . . 109
Installation utility encounters problems during installation . . . . . . . . . . . . . . . . 109
browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Online help does not display properly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Installation utility pages turn blank when resized . . . . . . . . . . . . . . . . . . . . . . . . . 111
Perl error message is displayed when the -serveronly option is used . . . . . . . . 111
Installation fails with unable to install perl error message . . . . . . . . . . . . . . . . . 112
Installation fails or configuration scripts cannot be run after an installation. . . 112
Installation fails with unable to connect to remote host error . . . . . . . . . . . . . . 113
Installation will not proceed past the specify installation directory page . . . . . 113
Unable to run root scripts error message is displayed on computers running Red
Hat Enterprise Linux AS 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Mozilla browser renders installation utility pages with extra space . . . . . . . . . . 115
Cannot extract a compressed installable image that is saved to a network share
on AIX platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Installation fails on computers running Red Hat and SuSE Linux . . . . . . . . . . . 115
The installation utility is unable to run root scripts and reports an invalid root
password on computers running Red Hat Enterprise Linux AS 4.0. . . . . . . . 116
Error messages are displayed when launching the installation utility on
computers running Red Hat Enterprise Linux AS 4.0 on Itanium . . . . . . . . . 116
Where to find diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Generating debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Sending diagnostic information to BMC Software support . . . . . . . . . . . . . . . . . 119
Index
121
Contents
Chapter
This chapter provides information about the installation utility. It presents the
following topics:
About the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The installation utility interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options for installing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options for selecting products to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting products by using the default installation path . . . . . . . . . . . . . . . . . . . .
Selecting products by using the custom installation path. . . . . . . . . . . . . . . . . . . .
Installing and configuring sudo to create a privileged account . . . . . . . . . . . . . . . . . .
Performing a multiple CD installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gathering product configuration information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1 Installation overview
10
10
10
11
11
12
13
14
15
About the installation utility
About the installation utility

By using the BMC Software installation utility, you can perform a local installation or
uninstallation of BMC Software products on computers running Windows or UNIX
operating systems.
Alternatively, you can use the installation utility to create a product image that can be
transferred to and installed locally on remote computers.
The installation utility interface

The installation utility interface consists of three panes:
a navigation pane that displays an indicator of where you are in the installation
process
a data entry pane that displays each page that requires input during the
installation
a footer pane that displays a Help button, Back and Next buttons, Exit button, and
on certain pages, the following additional buttons:
Undo Changes - returns any values that you enter in the currently displayed
page to the default values.
Show/Hide Advanced - displays or hides optional advanced product
configuration data entries. Consult the product documentation for the products
that you are installing to determine the conditions under which you will need to
enter any advanced configuration information.
Options for installing products

You can install products on the computer on which you are running the installation
utility, or you can create an installable image of products that can be installed at a
later time. For detailed instructions on how to install products, see the getting started
or installation guides for the products that you are installing. For detailed instructions
on how to create an installable image, see Creating, distributing, and installing
installable images on page 42 for Windows platforms and Creating, distributing,
and installing installable images on page 79 for UNIX platforms.
10
Options for selecting products to install
Options for selecting products to install

The list of products that you can select to install is based on the installation type and,
optionally, on a system role that you select. Some products do not require different
installation types or system roles. If this is the case for the product that you are
installing, the Select Type of Installation and the Select System Roles pages are not
displayed in the installation utility. The following sections describe installing a
product that uses two installation types.
Selecting products by using the default installation path

If you select the default installation path, you will see a product selection tree similar
to the one shown in Figure 1.
Figure 1
Example of a product selection tree view for PATROL productsdefault

installation path
The only selectable options shown are product solutions or groups, which are
comprehensive sets of products designed to work together. If you are installing
products using the default installation path, you can select only these comprehensive
solutions or groups from the product selection tree. When you select a solution or
group, all of the products included in that product set are automatically selected; you
may not be able to deselect individual products that you do not want to install if you
use the default path.
In addition, you are presented with subsequent pages to enter only mandatory
product configuration information.
Use the default installation path if your installation scenario is similar to one of the
following examples:
You are installing products for the first time.

You would like to use default values for most product configuration information.
You are not familiar with the product set that you are installing.
You want to select a prepackaged group of products with predefined
configurations.
Chapter 1
11
Selecting products by using the custom installation path
Selecting products by using the custom installation path

If you select the custom installation path, you will see a product selection tree similar
to the one shown in Figure 2.
Figure 2
Example of a product selection tree view for PATROL productscustom

installation path
Click this
check box...
and all products that belong to the specified

solution are automatically selected.
The selectable options shown are solutions or groups and individual products. When
you select a solution or group, all of the products that belong to that product set
(including required and optional products) are automatically selected. However, by
using the custom installation path, you can deselect any of the optional products that
you do not want to install.
In addition, you are presented with subsequent pages to enter both mandatory and
optional product configuration information about these products.
Use the Custom installation path if your installation scenario is similar to one of the
following examples:
12
You are upgrading a previous product installation (you can also use the Custom
path if you are installing a product for the first time).
You would like to select and deselect products within product groups.
You want to more fully customize your product configuration.
You are familiar with the product set that you are installing.
Installing and configuring sudo to create a privileged account
Installing and configuring sudo to create a

privileged account
Some products that you install will require that you enter a root account and
password to perform product configuration tasks. Instead of entering the root
account and password, you can install and configure sudo, then create a sudoprivileged account and enter the sudo account and password in place of the root
account and password. You must install and configure sudo before you begin the
product installation.
To install and configure sudo

1 Download sudo version 1.6.7p5 or later from the following URL:
www.courtesan.com/sudo.
2 Install sudo in the /usr/local/bin directory. If you install it in another location, create
a link in /usr/local/bin directory to the location where sudo is installed.
3 Reconfigure sudo to turn off password caching by entering the following

command:
./configure --with-timeout=0
Password caching causes sudo sessions to be on a timer, meaning one sudo

operation could allow multiple operations without password authentication. The
installation utility code that is used to support sudo expects a password prompt
every time sudo is invoked; therefore, password caching should be turned off for
sudo to work correctly with the installation utility.
4 On the computer where you install sudo, enter the following lines for the User
privilege specification in the sudoers file located in the local /etc directory:
install_accountname ALL=(ALL) PASSWD:ALL
Defaults: install_accountname shell_noargs, timestamp_timeout=0, !set_logname
The variable install_accountname is the name that you give to your sudo-privileged
account. These entries authenticate the user. The installation utility always expects
a password prompt, so sudo must be configured to supply the password. No
entries are required for the host alias, user alias, or command alias specifications.
Following is an example sudoers file:
# /etc/sudoers example file
# Host alias specification
Chapter 1
13
Performing a multiple CD installation
# User alias specification

# Cmnd alias specification
# User privilege specification
install_accountname ALL=(ALL) PASSWD:ALL
Defaults: install_accountname shell_noargs, timestamp_timeout=0, !set_logname
The variable install_accountname is the name that you give to your sudo-privileged
account.
After sudo is installed and configured, run the installation utility to perform the
product installation and in the pages that require the root account and password,
enter the sudo-privileged account and password instead.
Performing a multiple CD installation

Some products may require using multiple CDs to install all their associated
components. To perform a multiple CD installation, you must provide a temporary
storage location on your computer. You enter this location in the Temporary space for
copying external components page in the installation utility. You need to provide only
a directory location (for example, C:\temp for Windows or /tmp for UNIX). If the
directory that you enter does not exist, the installation utility will attempt to create it.
NOTE
When you select the products that you want to install, the installation utility displays the
approximate disk space required to complete the installation. When you perform a multiple
CD installation, you must also make sure that the temporary directory that you specify has
adequate disk space to make a copy of all the components required by the product.
Enter the name of the directory and click Next. The installation utility
creates the temporary directory, if necessary

creates a directory within the temporary directory called bmc_install_temp_space
begins to copy the files required for the product installation from the current CD
image.
A progress bar is displayed on the installation utility page while this process is
running. After the directories have been created and the files copied from the first
product CD, the installation utility displays the Additional CDs Needed page. On the
Additional CDs Needed page, you will be asked to load each of the required product
CDs in sequence. Insert each CD and click Next to copy the files to the temporary
14
Gathering product configuration information
directory. After the files have been copied from each of the required CDs, you will be
asked to place the original CD back in the CD-ROM drive. The installation utility
copies the required pieces from each CD to the temporary space that you designate
and combines all the files for the installation.
NOTE
On UNIX systems, you cannot eject removable media while the media is being accessed;
therefore, if your installation requires multiple product images and you are using removable
media, from a command line, cd to / then launch the installation utility by specifying the
absolute path; for example, /mnt/cdrom/setup.sh.
After the installation is complete, the installation utility removes the copied files and
the temporary directory if it was created by the installation utility during this
installation. If you selected an existing directory as the temporary space to store the
product files, then the installation utility removes only the copied files and the
bmc_install_temp_space directory.
NOTE
If the installation does not complete successfully, the installation utility will display the MultiCD Temporary Area page after the Installation Results page and give you the option to save
the product files in the temporary directory or have the installation utility remove the files
and the directory. If you choose to save the files, you will not be asked to copy the product
files again when you restart the installation.

To install products, you will be asked to enter product configuration information in
the installation utility for the products that you are installing. The type and amount of
information depends on the products and the type of installation that you are
performing (Default or Custom). Consult the product getting started guides and
release notes for details on the information that you must enter for each product.
Chapter 1
15
16
Chapter
Installing and uninstalling products

in a Windows environment
2
This chapter describes requirements and options for installing and uninstalling
products in Windows environments. It presents the following topics:
Installing to a Windows Server 2003 computer from a network drive . . . . . . . . .
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Account requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Installing and uninstalling products in a Windows environment
18
18
18
19
21
21
22
22
23
24
42
42
43
43
45
46
49
49
51
52
53
54
57
17
Checking installation requirements

When you plan an installation of BMC Software products, you must consider
whether limitations or restrictions exist in your environment.
Before you launch the installation utility, ensure that your environment meets the
hardware and software requirements described in the following sections. Also, before
you install any product to your environment, consult the product getting started or
installation guides and release notes for the requirements for each product that you
want to install and for detailed installation information.
Installing to a Windows Server 2003 computer from a network

drive
If you are performing a local or -serveronly installation from a product image on a
shared network drive to a Windows Server 2003 computer, the installation may time
out before the installation utility is launched. If this occurs, you must either:
use a product CD instead of a network image.
start the installation utility from a command line and use the -timeout command
line option. This option increases the amount of time that the installation utility
waits to connect to the Perl HTTP server before it times out. The installation utility
uses the Perl HTTP server to install products.
For more details on the command line options, see Command line options on
page 24.
NOTE
For details and recommendations from Microsoft about installing and administering in a
Windows Server 2003 environment, see the Microsoft website at
www.microsoft.com/technet.
Hardware requirements
The hardware requirements include
18
a CD-ROM drive (or network access to a CD-ROM product image)

a FAT or NTFS file system (HPFS is not supported)
a high color (16-bit) or true color (32-bit) display environment on any computer
where you will be using a browser
Web browser requirements

A web browser is required to run the installation utility.
NOTE
If you use pop-up blocker software to prevent pop-up windows from being displayed in your
Web browser, you must temporarily disable the software on the computer on which you want
to install products to run the installation utility. The procedures and requirements for
disabling pop-up blocker software vary depending on the software that you are using.
Consult the documentation provided with the pop-up blocker software for instructions.
If you do not have a web browser on the computer on which you want to install
products, you can:
create an installable image on a computer with a browser then install the image on
the computer that does not have a browser. For more details, see Creating,
distributing, and installing installable images on page 42.
use the -serveronly command line option to start the Perl HTTP server on the
computer without the browser then connect to that server from a computer that
has a browser. For more details, see Command line options on page 24.
NOTE
The installation utility will not run in Internet Explorer if any of the following conditions exist:
The computer on which you are running the installation utility is located in a Web content
zone that has a security setting of High. Security options are set in the Internet Options
dialog box
The option Use HTTP 1.1 is deselected. This setting is located on the Advanced tab in the
Internet Options dialog box
You used the -serveronly command line option to start the Perl HTTP server on another
computer, and you are connecting to that server from a Windows Server 2003 computer
that has the component Internet Explorer Enhanced Security Configuration installed and
enabled. You can verify if this component is installed in the Add/Remove Programs
dialog box.
Using proxy server definitions

If you have defined a proxy server for internet connections, your browser may be
unable to connect to the Perl HTTP server that is used by the installation utility. To
resolve this issue, perform one of the following tasks for the browser that you are
using:
Remove the proxy server connection setting by selecting Tools => Internet Options
=> Connections tab => LAN Settings and clearing the Use a proxy server check box.
19
Bypass the setting by selecting Tools => Internet Options => Connections tab => LAN
Settings => Bypass proxy server for local addresses.
Setting font size

If the font size in your browser is too large or too small, you can adjust the size by
performing the following task:
Choose View => Text Size and then one of the options that appears in the drop-down
menu, Largest, Larger, Medium, Smaller, or Smallest.
20
Displaying installation utility online help

The installation utility includes a browser-based online Help system that can be
accessed from the Help button on each page in the installation utility. To properly
display the online Help
the web browser that you are using to run the installation utility must be Javaenabled
you must have a Java Virtual Machine (JVM) or Java Plug-in version 1.1.2 or later
installed
If you are running the installation utility on a Windows computer that has Internet
Explorer configured to use the Java Virtual Machine version 1.3.1, accessing the Help
system will cause the installation session to hang. To resolve this issue, perform one
of the following tasks:
upgrade to a newer version of the JVM
configure Internet Explorer to use a different JVM version if multiple versions are
installed on your computer
use the -serveronly command line option to start the installation utility Perl HTTP
server on the computer that is running the JVM version 1.3.1, then connect to that
server from a computer that has a different version of the JVM installed.
Memory and disk space requirements

Check the memory and disk space requirements listed in the getting started or
installation guide for the products that you are installing to determine the amount of
disk space and memory required to install each product. The installation utility also
provides an estimate of how much disk space is required for all products that you
select to install in one installation session.
21
Network requirements
You must have a properly installed TCP/IP local area network.
WARNING
The installation utility provides a command line option called -serveronly that you can use to
start the Perl HTTP server on one computer and connect to that server across a network from
a browser running on another computer. The installation utility uses standard, unsecured
HTTP for network communications, which can create security risks for passwords and other
information that you may want to be secured across network traffic. Therefore, BMC Software
recommends that you install locally or create an installable image to distribute to remote
systems rather than use the
-serveronly command line option in an unsecured network. For more information on
command line options, see Command line options on page 24.
Before you begin installing

Complete the following tasks before you install to computers running Windows
operating systems.
Close all open applications on the computer where you are running the installation
utility.
Map all drives that you will use during the installation.
If you are installing on a computer that is running Windows 2000 Terminal

Services, Windows NT Terminal Server Edition, or Windows Server 2003 Terminal
Services, make sure that the change.exe file exists in the Windows\System32
directory. The installation utility uses this file to change the installation mode on
computers running these services.
If the file does not exist, you must either copy the file from another Terminal
Services or Terminal Server computer, or launch the installation utility from the
Add/Remove Programs utility and use the -no_change_exe command line option. For
more details, see Command line options on page 24.
22
If you are installing products on a backup domain controller, review the following
procedure
Starting the installation utility
To install on a backup domain controller

NOTE
Installing on a backup domain controller applies only to Windows NT 4.0 environments.
If you are installing products on a backup domain controller (BDC) without first
installing to the primary domain controller (PDC) in a single domain, you must
perform the following procedure before you install the products.
1 From the User Manager for Domains, create a default account.

2 Assign the required advanced user rights to the default account.
3 Synchronize the entire domain. This process updates all the BDCs in the domain
with the updated user account database.
Once you have completed this procedure, you can install products on a BDC using
the account that you created.

To start the installation utility, perform one of the following tasks:
Use Windows Explorer to open the CD directory and double-click setup.exe. (Do
this only if you do not want to specify any special command line options.)
Open a DOS command window and change to the CD-ROM drive where the
product CD is located. At the prompt, type setup.exe and any other command line
options you would like to include (if any), then press Enter.
When you launch the installation utility from a command line, you can specify certain
command line options to access additional functionality. For details on command line
options, see Command line options on page 24.
NOTE
Only one installation session should be started at one time. If you need to perform multiple
installations on the same computer, close out of each installation session and close all
associated browser windows before beginning a new session.
23
Command line options

Table 1 describes the options that you can use when you launch the installation utility
from a command line and references the page numbers where you can find detailed
information for each option.
Table 1
24
Command line options for Windows installation (part 1 of 2)
Option
Definition
For details
-h, -?, -help
displays the list of command line options.
see page 26
-createcontrolfile
lets you create a control file instead of perform see page 27

a product installation. The control file that you
create shows the list of products that would be
installed and the product configuration values
that the installation utility would use to
perform the product installation. Use this
option to debug a failed installation, look for
potential problems with the installation before
actually installing products, vary product
configuration values to see the impact on the
installation, or change the product
configuration values associated with an
installable image by creating a new control file
to use with the image. Also, you can use this
option to create a control file that you can use to
perform a silent uninstallation.
-host_override hostname
lets you override the default host name that the see page 28
installation utility uses to connect to the Perl
HTTP server. You can enter either a host name
or an IP address. This option can be used
standalone or with the
-serveronly option.
-locale locale
installs language-specific resource files for the

language that you specify
-no_change_exe
lets you install products on a computer running see page 30

Windows 2000 Terminal Services, Windows NT
Terminal Server Edition, or Windows Server
2003 Terminal Services if the change.exe file
does not exist on the computer. The installation
utility uses the change.exe file to change the
installation mode of a computer running these
services. If the file is not found, the installation
will fail. To use this option, you must launch
the installation utility from the Add/Remove
Programs utility.
see page 29
Table 1
Command line options for Windows installation (part 2 of 2)
Option
Definition
For details
-override_file location
see page 32
lets you install previously released BMC
Software products onto new versions of
compatible platforms. With this option, you
specify the location of a file that contains new
platform definitions that override the platform
information stored in a product's installation
files. The installation files are used to
communicate installation information to the
installation utility when the product is
installed. You can also use the override file to
update the platforms that you can select when
you create an installable image.
-port portnum
lets you specify a port number to use to connect see page 33

to the Perl HTTP server used by the installation
utility to perform product installations.
-releaseversion version
use this option to install a new KM into a

previous release of PATROL.
-repository_designator role
lets you select a system role from the command see page 35
line so that only those products designated for
that system role are displayed in the Select
Products and Components to Install page.
-serveronly
use this option if you do not have a browser on see page 36

the computer on which you want to install
products; lets you start the Perl HTTP server on
one computer, then connect to that server using
a browser on another computer.
-shutdownservice minutes
lets you increase the number of minutes that

the installation utility will wait for a service to
shutdown before proceeding with an
installation.
-skipuserright
see page 38
tells the installation utility to not assign user
rights to a default installation account during a
product installation or to not unassign user
rights from a default installation account
during a product uninstallation. If you use this
option, you must set the user rights manually.
-timeout seconds
lets you specify the number of seconds that the see page 39
installation utility will wait to connect to the
Perl HTTP server before timing out.
-trace
records detailed information about activities in see page 40

the installation utility interface during
installation.
-v
displays the version number for the installation see page 41

utility.
see page 34
see page 37
25
-h, -?, -help

This option displays the list of command line options.
Command format
setup.exe -h
setup.exe -?
setup.exe -help
Options
None.
26
-createcontrolfile
This option lets you create a control file instead of perform a product installation. You
navigate through the installation utility as you would if you were performing a
product installation; however, at the end of the process, no products are actually
installed. Instead, a control file is created, and the installation utility displays a link to
the control file so that you can view it. The installation utility uses control files to
perform product installations.
The control file that you create shows a list of the products that will be installed and
the product configuration values that the installation utility will use to install the
products. Use this option to help you debug a failed installation, look for potential
problems with an installation before actually installing products, vary the product
configuration values to see the impact on the installation, or change the product
configuration values associated with an installable image by creating a new control
file to use with the image. The control file is located in the following directory
depending on your operating system:
For Windows 2000, Windows XP, and Windows Server 2003:
drive:\Documents and Settings\username\Application Data\BMCinstall
For Windows NT:

drive:\winnt\Profiles\username\Application Data\BMCinstall
NOTE
You can use this option to create a control file to perform a product uninstallation. For more
details, see Performing an unattended uninstallation on page 57.
command format
setup.exe -createcontrolfile
Options
None.
27
This option lets you override the default host name that the installation utility uses to
connect to the Perl HTTP server. By default, the installation utility connects to
localhost for a local product installation. If you launch the installation utility by using
the -serveronly command line option, the installation utility uses the primary IP
address of the computer where the Perl HTTP server is launched as the default host.
This option lets you override this default so that you can specify the host name or IP
address that you want the installation utility to use on computers with multiple IP
addresses. This option can be used standalone or with the -serveronly option.
Command format
setup.exe -host_override hostname
setup.exe -serveronly -host_override IPaddress
Options
None.
28
-locale locale
This option lets you select and install only those products that are compatible with
the locale (language) that you specify. You can specify only one locale. The
installation utility will filter the list of products that will be displayed in the Select
Products and Components to Install page to display only those products that are
either specific to the locale that you specify or that do not have a locale designation.
If you do not specify an option, then the locale from the system on which you are
running the installation utility is used. If the system locale is not supported by the
installation utility, then the English locale, en_US, is used. This option does not
change the language of the text displayed in the installation utility. The installation
utility will run in English regardless of the system locale or the -locale option that you
enter except as noted. In addition, you will be able to input only English characters.
NOTE
If you set the -locale option to be the same as the system locale, you will install the
appropriate products and language resource files, but the installation utility will run in either
English or the system locale language and will accept input in either English or the system
locale language.
Command format
setup.exe -locale en_US
Options
Language
Option
English
en_US
Traditional Chinese
zh_TW
Simplified Chinese
zh_CN
Korean
ko_KR
Japanese
ja_JP
29
-no_change_exe
This option lets you install products on a computer running Windows 2000 Terminal
Services, Windows NT Terminal Server Edition, or Windows Server 2003 Terminal
Services if the change.exe file does not exist on the computer. The installation utility
uses the change.exe file to change a computer running one of these services to install
mode if it is not already in install mode. If the file does not exist, the installation fails
with an error message that the installation terminated abnormally. To bypass the
change.exe requirement, launch the installation utility from the Add/Remove Programs
utility to put the computer in install mode and specify this option so that the
installation utility will not look for the change.exe file.
Command format
setup.exe -no_change_exe
Enter this command in the Add/Remove Programs utility as follows depending on

your operating system:
1 Click Start => Settings => Control Panel => Add/Remove Programs.
2 In the Add/Remove Programs dialog box, click Add New Programs.
3 Click the CD or Floppy button.
4 In the Install Program From Floppy Disk or CD-ROM dialog box, click Next.
5 In the Run Installation Program dialog box, browse to the location of the product
image and select setup.exe or if you are installing products from an installable
image, select install.exe.
6 In the Open text box, enter -no_change_exe after setup.exe or install.exe and click
Finish.
30
For Windows NT:
1 Click Start => Settings => Control Panel => Add/Remove Programs.
2 In the Add/Remove Programs Properties dialog box, click Install.
3 In the Install Program From Floppy Disk or CD-ROM dialog box, click Next.
4 In the Run Installation Program dialog box, browse to the location of the product
image and select setup.exe or if you are installing products from an installable
image, select install.exe.
5 In the Command line for installation program text box, enter -no_change_exe after
setup.exe or install.exe and click Finish.
Options
None.
31
This option lets you specify a file (override.dat) that will override platform definitions
in product installation files so that you can:
install previously released products onto new versions of compatible platforms.

update the platforms that you can select when you create an installable image of
products.
The product installation files contain product-specific installation instructions, such

as supported platforms, that communicate to the installation utility how to install the
product.
When BMC Software authorizes support for new platforms, Customer Support will
provide a valid override.dat file with new platform definitions that you will be able to
download from an ftp site located at the following URL:
ftp://ftp.bmc.com/pub/patrol/patches/COMMON_INSTALL_override.dat
After you have downloaded an updated override.dat file, when you install products,
launch the installation utility from a command line and use this option to specify the
location where you downloaded the file.
WARNING
Do not edit the contents of the override.dat file. The installation utility may be unable to read
the edited file.
Command format
setup.exe -override_file c:\temp\override.dat
Options
None.
NOTE
Although this functionality is being provided in this version of the installation utility, it
cannot be used at this time because a valid override.dat file does not currently exist on the ftp
site.
32
-port portnum
This option lets you specify a port number to use to connect to the Perl HTTP server.
Use this option if the default port number to the server is locked and you want to
specify another open port, or if you are using the -serveronly command line option
and you need to open a port through a firewall. If not specified, the installation utility
uses a default of 50001. If the default port number is in use, the installation utility
increases the number by one and tries again to connect to the server.
Command format
setup.exe -port 3184
setup.exe -serveronly -port 3184
Options
Any number from 1025 to 65534.
33
In a PATROL environment, this option lets you install a new KM into an existing
PATROL environment.
Command format
setup.exe -releaseversion 3.4
Options
34
Option
Description
3.2
for 3.2.x platforms and components
3.3
3.4
3.5,7.1
for 3.5.x and 7.1.x platforms and components. These options

should always be specified together.
7.2
for 7.2 platforms and components.
7.4
or 7.4 platforms and components. This is the default for this

version of the installation utility.
This option lets you select a system role from a command line so that only those
products specified for a particular system role will be displayed in the Select Products
and Components to Install page. Each role has a specific code associated with it. The
roles (codes) that you can enter vary from product to product. Valid options can be
found in the sysrole.xml file in the \Index directory of the product image that you are
installing from. If you specify this option, the Select System Roles page will not be
displayed in the installation utility.
Command format
setup.exe -repository_designator PAT,PAA
Options
Depends on the products that you are installing. See the sysrole.xml file for valid
options.
35
-serveronly
This option lets you start the Perl HTTP server on one computer, then connect to that
server using a browser on another computer. Use this option if you do not have a
browser on the computer where you want to install products. When you launch the
installation utility with this command line option, the Perl HTTP server is started,
and a message box is displayed that shows a URL. Leave this message box open. On
the computer with the browser, start the browser and enter the URL displayed in the
message box to connect to the Perl HTTP server.
By default, this option uses port number 50001 to connect to the Perl HTTP server. If
that port is busy, the installation utility automatically increases the number by one
and tries again to connect. You can specify the port that you want to use by using the
-port command line option with this option.
WARNING
The -serveronly command line option is not secure over a network and using it in an
unsecured network environment could result in security violations. If this is an issue for your
environment, you may want to consider either performing only local installations or creating
an installable product image that can be sent to a remote computer and installed on it locally,
rather than installing over an unsecured network. For details on creating an installable image,
see Creating, distributing, and installing installable images on page 42.
Command format
setup.exe -serveronly
setup.exe -serveronly -port 3184
Options
None.
36
-shutdownservice minutes
This option lets you increase the number of minutes that the installation utility waits
for a service to shutdown before proceeding with an installation. The installation
utility typically waits two minutes for a service to shut down. This option lets you
increase that number up to five minutes.
Command format
setup.exe -shutdownservice 3
Options
37
-skipuserright
This option keeps the installation utility from assigning user rights to a default
installation account, if one is required, during a product installation. If you use this
option, you must set the user rights for the installation account manually. Use this
option if the computer on which you are running the installation utility is not
connected to a network or if you are getting error messages when the installation
utility attempts to assign the user rights.
Command format
setup.exe -skipuserright
NOTE
You can also use this option to keep the installation utility from unassigning user rights from
the installation account during a product uninstallation. Change to the BMC product
installation directory\Uninstall directory and enter:
uninstall.exe -skipuserright
Options
None.
38
-timeout seconds
This option lets you specify the number of seconds that the installation utility will
wait to connect to the Perl HTTP server before timing out.
Command format
setup.exe -timeout 120
Options
39
-trace
This option lets you record detailed information about what is happening in the
installation utility interface during a product installation. The installation utility adds
this information to the beginning of the standard log file. You can view the standard
log file from the installation utility when the installation is complete. This option also
saves the control file that the installation utility uses to install products. Normally, the
installation utility deletes the control file after the installation is complete. You can
use the saved control file and the information generated by this option for debugging
For information on the installation log files created and where to find the log files, see
Locating log files on page 51.
Command format
setup.exe -trace
Options
None.
WARNING
Using this option causes the installation utility to record passwords unencrypted in the
installation log files.
40
-v
This option displays a dialog box that shows the version number for the installation
utility.
Command format
setup.exe -v
Options
None.
41
Creating, distributing, and installing installable images
Creating, distributing, and installing

installable images
This section describes using the installation utility to create an installable image,
options for distributing the image to remote computers, and installing the image on
computers to which it was distributed.
NOTE
You cannot create an installable image that can be installed on both Windows and UNIX
computers. You must create one image for all Windows operating systems and one image for
all UNIX operating systems; however, you can create the images from either a Windows or
UNIX computer.
Installable image files and directories

The installable image consists of the following files and directories. You will use or
refer to these files and directories when you launch the installation utility from an
installable image.
install.exerun this executable from a command line to install the products in the
image on the computer where the image is located.
*.ctlThis extension designates the control file that stores the installation and
product configuration information that you enter in the installation utility when
you create an installable image. The installation engine uses the information stored
in the control file to install the products in the location and with the configuration
that you specify.
*.logwhen the installation is complete, log files are created in the user's profile
directory under Application Data\BMCinstall unless you use one of the command
line options listed in Table 2 on page 47 to redirect the files to a new location.
The installation utility uses information stored in the following directories to install
the image.
Productsthis directory contains subdirectories that store the product files needed
by the installation utility to install the products that are part of the image.
42
Account requirements
Installthis directory contains two subdirectories, instbin, which stores the

installation engine binaries and installation tools such as ctltool, and instdata,
which stores the default text files that control the order in which the products are
installed and that list the operating systems that are recognized by the installation
utility.
If you selected the option to compress and save the image to a .zip file, you will see
the following files:
inst_timestamp.zipthis file contains the compressed installable image directories
and files.
cizip.exerun this executable from a command line to extract the installable image
files.
Account requirements
To create an installable image on Windows platforms, you must be a member of the
local Administrator group on the computer on which you are creating the image. To
install the image, the person performing the installation must be a member of the
local Administrator group on the computer on which the image is installed.
Creating an installable image of products

This procedure describes how to create an installable image on a local computer for
local installation on other computers.
To create an installable image of products

1 Start the installation utility.
2 On the Welcome page, click Next.
3 Review the license agreement and select Accept. Click Next.
4 On the Select Installation Option page, select Create an image to be installed later.
5 Enter the name of a directory on your computer where you want the image stored
after it has been created.
6 Optionally, select to have the image compressed and saved to a .zip file. Click Next.
43
7 Select the target operating systems on which you want to install the image. Click
Next.
You can select multiple Windows or UNIX platforms for each image that you
create. Alternatively, you can select the Local System option, which lets you create
an image that can be installed only on computers with the same platform and
configuration as the computer on which you are creating the image. This includes
service pack level.
NOTE
UNIX computer.
8 Select the products that you want to include in the image. Click Next.
9 Proceed through the installation as you would if you were installing products
locally, entering all required product configuration information.
10 On the Review Selections and Create Image page, click Create Image.
11 When the status indicator reaches 100 percent, click Next on the Export Status page.
12 Verify that the process was successful and optionally view the log file. Click Next.
13 Review or enter any postinstallation product configuration information.
14 Click Finish to exit the installation utility.
When you create an installable image, the product configuration information that you
enter, such as product installation directory, account names, passwords, and so forth,
must be the same for all computers on which the image is installed. If you want to
specify different product configuration values for different computers, you can
44
create a separate image for each set of values that you want to implement.
launch the installation utility from a command line and use the -createcontrolfile
command line option to create a new control file to use with the image. For more
details, see Command line options on page 24.
use the ctltool to change the variables stored in the image's control file after the
image is generated. For more details, see Editing control files for installable
images on page 49.
Deploying the installable image to your environment

Once you have created an installable product image, you can deploy it to your
environment in several ways:
Tar the image and use ftp or secure ftp to send it to a remote computer.
Use a third-party distribution system such as Microsoft Systems Management

Server (SMS).
Burn the image to a CD and distribute the CD.
Place the image on a shared network drive.
Selecting the Compress Installable Image option in the installation utility to create
a .zip file that you can then send to other computers.
NOTE
If you created an installable image on a Windows computer to be installed on UNIX
computers, you must make sure that the method that you use to transfer the image (for
example, tarring the image) maintains execute permissions on the installable image files when
you unpack the files on the UNIX computer. If the permissions are not maintained, you may
receive an error message similar to the following when you try to install the image: "Error:
Executable not found './thorinst.s25'. To correct the file permissions, before you
install the image, perform one of the following tasks depending on where the installable
image directory resides:
If you exported the image to a directory that is at the root level, for example, /image, change to
the root directory and enter
chmod -R 755 /image
If you exported the image to a directory that is not at the root level, for example,
/image/myimage, change to the directory in which the image directory is located (/image),
and enter
chmod -R 755 /image/myimage
Once the image is copied to the computer, it can be installed as described in

Installing an installable image on page 46.
45
Installing an installable image

This procedure describes installing an installable product image locally in a Windows
environment.
To install an installable image on a Windows computer

1 Open a command prompt.
2 Change to the directory that contains the image files.
3 If you selected the option to compress the image, unzip the file by entering the
following command:
cizip.exe -u filename directory
The option filename is the name of the .zip file that contains the installable image
directories and files, and the option directory is the path to the directory where the
files will be placed after they are extracted from the .zip file. If you specify a
directory that does not exist, the directory will be created. If you do not specify a
drive with the directory name, the directory will be created in the same directory
where the .zip file is located.
4 Change to the directory where the unzipped files are located.

5 Launch the installation utility by entering the following command:
install.exe options
For options, enter any command line options that you want to specify as listed in
Table 2 on page 47.
6 You can optionally unzip the file and automatically start the installation by
entering the following command:
cizip.exe -u -x filename directory
The -x option launches the installation utility after the file is unzipped. If you
choose this option, you cannot specify any of the command line options listed in
Table 2.
46
Table 2
Installable image command line options for Windows (part 1 of 2)
Option
Definition
-v
displays the installation utility version on the command line

then returns to the command line prompt
-h
displays the available command line options
-path directory
lets you specify the path name to the installable image if you
are not in the same directory
-log location filename
lets you specify the location where you want to store the
comprehensive log file and the name of the log file to be
stored in that location. You can specify a complete path and
filename or just the file name. If you specify just the file
name, the log file is stored in the same directory where the
installable image files are located. The location and file
naming convention that you use for this option will also be
used for the product log, user log, and standard output log
unless you use the additional command line options to
specify the location and file names for these log files. For
example, if you name the comprehensive log file testing.log
and store the log file in a directory called c:\install\logfiles,
the product log file will be named testing-product.log, the
user log file will be named testing-user.log, and the standard
output log will be named testing-output.log and these log
files will also be stored in the c:\install\logfiles directory.
-productlog location filename
product log file and the name of the product log file to be
installable image files are located.
-userlog location filename
lets you specify the location where you want to store the user
log file and the name of the user log file to be stored in that
location. You can specify a complete path and filename or
just the file name. If you specify just the file name, the log file
is stored in the same directory where the installable image
files are located.
-install location filename
installs the products listed in a control file stored in the

location that you specify. If the location is not specified, the
installation utility looks for the control file in the directory
where the image was created.
-no_change_exe
lets you install the image on a computer running Windows

2000 Terminal Services, Windows NT Terminal Server
Edition, or Windows Server 2003 Terminal Services if the
change.exe file does not exist on the computer. The
installation utility uses the change.exe file to change the
installation mode of a computer running these services. If the
file is not found, the installation will fail. To use this option,
you must launch the installation utility from the
Add/Remove Programs utility. For details on using this
option, see Command line options on page 24.
47
Table 2
Installable image command line options for Windows (part 2 of 2)
Option
Definition
-output location filename
standard output log file and the name of the log file to be
-nooutput
lets you send output messages to standard output instead of

to a log file.
-skipuserright
keeps the installation utility from assigning user rights to a

default installation account, if such an account is required for
a product installation; this option also keeps the installation
utility from unassigning user rights during a product
uninstallation. If you use this option, you must set the user
rights manually. For details on using this option, see
Command line options on page 24.
-shutdownservice min
lets you increase the number of minutes that the installation

utility waits for a service to shutdown before proceeding
with an installation. For details on using this option, see
Command line options on page 24.
The installation utility executes and installs the products associated with the image to
the installation directory that you specified when you created the image. When the
process is complete, one of the following status messages is displayed on the
command line:
The installation completed successfully

The user log contains the following fatal messages and a list of the
messages
The product log contains the following non-fatal messages and
a list of the messages.
No status messages are displayed until the installation is complete.

Log files are created and stored in the user's profile directory under Application
Data\BMCinstall unless you use one of the command line options listed in Table 2 on
page 47 to redirect them to another location. If you use the -log command line option
only, all log files will be stored to the same location and with the same file naming
convention that you specify for the -log option.
For Windows NT environments, the default directory is:
C:\Winnt\Profiles\username\Application Data\BMCinstall
For Windows 2000, Windows XP, and Windows Server 2003 environments, the
default directory is:
48
Editing control files for installable images
C:\Documents and Settings\username\Application Data\BMCinstall
In previous releases of the installation utility, log files were stored in the same
directory as the installable image files.

Each computer on which you want to install an image must have the same product
configuration values as those stored in the images control file.
To change the product configuration values, you can either create a new image, or
edit the control file associated with the existing image. Ctltool is a utility that you can
use to change the product configuration values in an existing control file to create a
new control file. Then, you can use the new control file to install the same image on
computers that require the different values.
Using the ctltool to edit control files for installable images

This procedure describes how to edit the variables stored in an installable images
control file.
To use the ctltool to edit control files in Windows environments

1 Open a command prompt.,
2 Change to the \Install\instbin directory in the directory where the installable
image is stored.
3 Enter the following command:

ctltool.exe drive:\path\inputfile.ctl drive:\path\outputfile.ctl
The option drive:\path\inputfile.ctl represents the path to and name of the control
file that you want to edit (the control file that was created with the installable
image), and the option drive:\path\outputfile.ctl represents the path to and name of
the new control file that you want to create.
49
For example, you create an installable image and store the image in a directory on
your D: drive called installable image. When you create the image, the installation
utility creates a .ctl file named install.ctl and stores that file in that directory along
with the image files. To edit this control file and create a new one in the same
directory, at the command prompt, you would change to D:\installable
image\Install\instbin, and enter
ctltool.exe D:\installable image\install.ctl D:\installable image\newfile.ctl.
NOTE
If the path that you enter for the input control file or the output control file has a space in it,
you must enclose the path in quotes.
The installation utility displays the first value stored in the control file.
4 Type a new value and press Enter to save your entry and display the next variable.
To keep the existing value, press Enter. If you are changing a password variable,
the value is encrypted in the new control file.
When the ctltool has finished displaying all the variables in the control file, the
command prompt is displayed.
5 Rename the new control file to install.ctl so that when you install the image, the
installation utility uses the new control file. The installation utility looks for a
control file named install.ctl to perform the installation.
NOTE
Optionally, you can use the -install command line option when you install the image to
specify the location and name of the new control file that you want to use. For more details
on the -install command line option, see Installing an installable image on page 46.
50
Locating log files
Locating log files

The installation utility creates the following log files:
concatenated logContains information from all other log files created during a
user logLists error messages about fatal errors that caused an installation to fail.
The information in this log file is the first section in the concatenated log file.
product logLists nonfatal error messages and post-installation information

messages, such as if a reboot is required after the installation is complete. The
information in this log file is the second section in the concatenated log file.
standard output log Lists messages that are usually sent to standard output. The
information in this log file is the third section in the concatenated log file.
comprehensive or main logLists all actions performed by the installation utility

during a product installation such as the products that were installed or added to
an image, files that were copied or removed, registry entries made, and any
version checking that was performed. The information in this log file is the fourth
section in the concatenated log file.
front end trace logShows detailed information about activities in the installation
utility interface during installation. This file is created if you launch the installation
utility from a command line and use the -trace command line option. The
information in this log file is the fifth section in the concatenated log file. For more
details on using the -trace command line option, see Command line options on
page 24
When the installation utility finishes installing products or creating an installable

image, a page is displayed in the installation utility that shows a status message
indicating the success or failure of the process. This page also contains a link, View
Log, to the concatenated log file and displays the log files location and name. The log
files name is determined at runtime and contains the name of the computer on which
the installation utility was run and an incremental time stamp.
All log files are deleted after the installation is complete except for the concatenated
log file unless:
you started the installation utility and used the -trace command line option or the
-createcontrolfile command line option
the installation failed with an out-of-space error
51
Product installation directory structure
The installation utility stores the log files in the following directories:
For Windows NT:
C:\winnt\Profiles\username\Application Data\BMCinstall

C:\Documents and Settings\username\Application Data\BMCinstall
By default, the Application Data directory on Windows operating systems is hidden.

To view this directory so that you can locate the installation log files, open Windows
Explorer and for Windows NT, choose View => Options => Show all files. For
Windows 2000, Windows XP, and Windows Server 2003, choose Tools => Folder
Options => View => Show hidden files and folders.

When you install products or create an installable image, you will need to provide the
name of a directory into which the products that you select will be installed. The
installation utility provides a default directory that you can use, or you can enter a
new directory.
WARNING
You cannot enter a root directory as the product installation directory for BMC Software
products, because if you uninstall products from that directory, you may unintentionally
uninstall products other than BMC Software products. If you need to install into a root
directory to install a product upgrade, you can create an installable image and specify the root
directory as the installation directory for the products in the image; however, if you need to
uninstall the products from the root directory, do not use the uninstall-all.ctl file to perform
the uninstall.
WARNING
Product installation directories are stored in installation utility history files as full path names;
therefore, do not rename the product installation directory after you install products, because
the installation utility will be unable to find the renamed directory if you uninstall products.
By default, the installation utility uses c:\Program Files\BMC Software as the product
installation directory. When you install products, the installation utility creates a
subdirectory in the product installation directory for each product that you install
and the following additional subdirectories that store information required by the
installation utility:
52
Uninstalling BMC Software products
Install\insthiststores files that contain installation utility history information,
such as which products you installed during a particular installation session
itoolsstores utilities that may be used by the products that you install
Uninstall\Install\instbasestores the Perl binaries and the Perl HTTP server code;
Perl is used by installation utility to install products
Uninstall\Install\instbinstores the installation engine binaries and installation
tools such as ctltool
Uninstall\Install\instcommonstores the xml files that are used to format and

display the standard installation utility pages
Uninstall\Install\instdatastores default text files that control the order of the list
of products that you can select to install and the order in which the products are
installed, and that list the operating systems that are recognized by the installation
utility

You can use the installation utility in uninstall mode to select and uninstall only those
products that were installed with version 7.2 or later of the installation utility.
Products installed with a previous version of the installation program must use that
versions uninstallation utility.
WARNING
Performing the tasks described in this section might remove files needed by a previous
version of the installation program to uninstall products installed with that version. Likewise,
if you use a previous version of the installation program to uninstall products, you might
remove files needed by this version of the installation utility to perform the uninstallation
tasks.
In addition, FTP and Telnet are not required for the uninstallation process on Windows.
53
Performing an attended uninstallation

Use the installation utility to select and uninstall individual products. All
components associated with those products will also be uninstalled unless they are
required by another installed product.
If the installation utility detects hidden, or orphaned, components on your computer,
an additional page is displayed during the uninstallation that gives you the option to
remove all of these components. Orphaned components are product components that
were originally installed as non-selectable required product components during a
previous product installation but are no longer required by any of the products
installed on your computer.
If you select to uninstall all products and any orphaned components, an additional
page is displayed that gives you the option to uninstall the uninstallation utility.
To uninstall products, orphaned components, and the uninstallation utility

1 From the Uninstall directory in your BMC Software product installation directory,
double-click uninstall.exe to launch the uninstallation utility.
NOTE
You can optionally launch the uninstallation utility by choosing Start => Settings =>
Control Panel => Add/Remove Programs and in the Add/Remove Programs Properties
dialog box, in Windows NT environments, double-clicking on BMC Software Tools, and
in Windows 2000 environments, selecting BMC Software Tools and clicking
Change/Remove.
The Welcome page is displayed. Click Next.
2 Select the installation directory from which you want to remove a product. Click
Next.
3 Enter pre-uninstallation product information.

The pages displayed during this phase of the uninstallation may present only
information that you should know prior to uninstalling the products or may
require you to enter information that the uninstallation utility will use to perform
validation checking before the uninstallation process begins.
The pages displayed will vary depending on the products installed on your
computer. For some groups of products, no pre-uninstallation pages will be
displayed.
4 Select the product or products that you want to uninstall. Click Next.
54
5 (optional) If the uninstallation utility detects any orphaned components, select to

remove these components from your computer.
6 Enter any additional requested information in the displayed pages.

The information that you are required to enter depends on the products that you
are uninstalling; for example, you may be required to enter account information,
such as a user name and password, to uninstall the selected products. These pages
may also display only information that you need to know once the products are
uninstalled, such as if a reboot is required after the uninstallation is complete.
7 (optional) Select to uninstall the uninstallation utility.

All files and directories will be removed except those used by the installation
utility at the time the uninstallation is performed, such as thorinst.exe, bwcpwk.dll,
and GlobalC language files. Log files, configuration files, user modified files, and
files created as a result of running scripts during the installation are also retained.
8 Review your selections and click Uninstall.

After the uninstallation is complete, a page is displayed that tells you the status of
the uninstallation and provides a link to the log file.
Alternatively, you can use the uninstallation utility to uninstall all products and
orphaned components as described in the previous procedure, then use the following
procedure to uninstall the uninstallation utility, log files, and configuration files from
the specified product installation directory.
To uninstall all products, uninstallation files, log files, and configuration files
NOTE
You must reboot your computer after you perform this procedure.
1 Uninstall each product and any orphaned components as described in

To uninstall products, orphaned components, and the uninstallation utility on
page 54. Do not uninstall the uninstallation utility.
2 Locate the uninstall-all.ctl file in the BMC Products Installation

directory\Uninstall\Install\instdata directory.
55
WARNING
Do not use the uninstall-all.ctl file to uninstall products from a root product installation
directory, such as C:\. Doing so may unintentionally uninstall products other than BMC
Software products.

4 Change to the BMC Products Installation directory\Uninstall\ Install\ instbin
directory.

thorinst.exe -uninstall BMC products installation directory\Uninstall\Install\instdata\
uninstall-all.ctl -log path to log file -output path to output log file
The options -log and -output let you specify a location for a standard log file and an
output log file. The standard log file contains all installation status information,
and the output log file contains messages on the progress of the installation that
are normally sent to standard output. The path to log file and path to output log file
variables can be any valid path and file name (with a .txt extension) that you
specify. If the path includes spaces, you must enclose it with quotes.
For example, if C:\Program Files\BMC Software is your product installation
directory, you would change to C:\Program Files\BMC Software\Uninstall\
Install\instbin directory and enter the following:
thorinst.exe -uninstall C:\Program Files\BMC
Software\Uninstall\Install\instdata\uninstall-all.ctl -log
Z:\NetworkLogs\MyLogs.txt -output Z:\NetworkLogs\MyLogs.out
This procedure removes all installation files and directories. The files used to
perform the uninstallation will be marked for deletion and will be removed when
the computer on which the products were uninstalled is rebooted.
56
Performing an unattended uninstallation

You can use the -createcontrolfile command line option to create a control file that
you can use to perform an unattended, or silent, uninstallation of products.
To create a control file to uninstall products

2 Change to the BMC Products Installation directory\Uninstall directory.
3 Start the uninstallation utility by entering the following command:
uninstall.exe -createcontrolfile

5 Enter the name of the directory from which you want to uninstall products. Click
Next.
6 Select the products that you want to uninstall. Click Next.

7 If you selected to uninstall all products, optionally select to uninstall the
uninstallation utility.
8 Proceed through the uninstallation, entering any requested information.

9 On the Review Settings for Control File page, click Create Control File.
10 Verify that the process was successful and optionally view the control file.
By default, the new control file is stored in the users profile directory under
Application Data\BMCinstall.
After the control file is created, you can rename it and copy it to another location or to
other computers, then use the following procedure to uninstall products.
NOTE
The computer where you use the control file must have the same configuration, such as
operating system, installed products, product installation directory, and so forth, as the
computer on which the control file was created.
57
To uninstall products by using the new control file

2 Change to the BMC Products Installation directory\Uninstall\Install\instbin
directory.

thorinst.exe -uninstall path to control file -log path to log file -output path to output log
file
The option path to control file is the path to and name of the control file that you
created in the previous procedure. The options -log and -output let you specify a
location for a standard log file and an output log file. The standard log file contains
all installation status information, and the output log file contains messages on the
progress of the installation that are normally sent to standard output. The path to
log file and path to output log file variables can be any valid path and file name (with
a .txt extension) that you specify. If the paths to the control file and log files include
spaces, you must enclose them with quotes.
58
Chapter
Installing and uninstalling products

in a UNIX environment
3
This chapter describes requirements and options for installing and uninstalling
products in UNIX environments. It presents the following topics:
Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
60
60
62
63
63
63
64
65
79
79
80
81
82
85
86
87
88
89
90
91
59

When you plan an installation of BMC Software products, you must consider
whether limitations or restrictions exist in your environment.
Before you launch the installation utility, ensure that your environment meets the
requirements described in the following sections. Also, before you install any product
to your environment, consult the product getting started or installation guides and
release notes for the requirements for each product that you want to install and for
detailed installation information.

NOTE
If you use pop-up blocker software to prevent pop-up windows from being displayed in your
Web browser, you must temporarily disable the software on the computer on which you want
to install products to run the installation utility. The procedures and requirements for
disabling pop-up blocker software vary depending on the software that you are using.
Consult the documentation provided with the pop-up blocker software for instructions.
If you do not have a web browser on the computer on which you want to install
products, you can:
create an installable image on a computer with a browser then install the image on
the computer that does not have a browser. For more details, see Creating,
distributing, and installing installable images on page 79.
NOTE
You must have JavaScript enabled in Netscape.
60
Setting the character sets in Netscape for Japanese locales

If you are using Netscape to run the installation utility in Japanese, you must set the
character set to Japanese and set this character set as the default before you run the
installation utility so that the proper characters are displayed in the installation utility
pages.
To change the character set to Japanese and use Japanese as the default character set,
perform the following procedure:
NOTE
You must have Web fonts installed to perform this procedure.
1 Start Netscape.
2 Click View => Character Set => Japanese (Auto-Detect) to change the character set to
Japanese.
3 Click View => Character Set => Set Default Character Set to set Japanese as the default
character set.
You may also need to change the font settings. To do this, perform the following
procedure:
1 Start Netscape.
2 Click Edit => Preferences.
3 Under Appearance, click Fonts.
4 Select the fonts and sizes that you want to use.
5 Click OK.
Using proxy server definitions
If you have defined a proxy server for internet connections, your browser may be
unable to connect to the Perl HTTP server that is used by the installation utility. To
resolve this issue, perform one of the following tasks for the browser that you are
using:
Remove the proxy server connection setting by selecting Edit => Preferences =>
Advanced => Proxies => Direct Connection to the Internet.
Chapter 3
61
Bypass the setting by selecting Edit => Preferences => Advanced => Proxies =>
Manual Proxy Configuration. Enter your domain in the No Proxy for text box.
Setting font size

If the font size in your browser is too large or too small, you can adjust the size by
performing the following task:
Choose View => Increase Font Size or View => Decrease Font Size.

The installation utility includes a browser-based online Help system that can be
accessed from the Help button on each page in the installation utility. To properly
display the online Help
you must have a Java virtual machine or Java Plug-in version 1.1.2 or later installed
if you are using Netscape, the java40.jar file must exist in your Netscape installation
directory
If it does not exist, you must download and reinstall Netscape.
the variable MOZILLA_HOME should be set to point to the root of the Netscape
installation directory
EXAMPLE
For sh or ksh users, if the Netscape installation directory is /opt/netscape, enter the following
commands to set this variable:
MOZILLA_HOME=/opt/netscape
export MOZILLA_HOME
EXAMPLE
For csh users, if the Netscape installation directory is /opt/netscape, enter the following command to set
this variable:
setenv MOZILLA_HOME /opt/netscape
62

Check the memory and disk space requirements listed in the getting started or
installation guide for the products that you are installing to determine the amount of
disk space and memory required to install each product. The installation utility also
provides an estimate of how much disk space is required for all products that you
select to install in one installation session.
You must have a properly installed TCP/IP local area network.
WARNING
The installation utility provides a command line option called -serveronly that you can use to
start the Perl HTTP server on one computer and connect to that server across a network from
a browser running on another computer. The installation utility uses standard, unsecured
HTTP for network communications, which can create security risks for passwords and other
information that you may want to be secured across network traffic. Therefore, BMC Software
recommends that you install locally or create an installable image to distribute to remote
systems rather than use the
-serveronly command line option in an unsecured network. For more information on
command line options, see Command line options on page 65.
Before you begin installing

Complete the following tasks before you install to computers running UNIX
operating systems.
Mount the CD-ROM.
Set the umask setting to 022.
Map all drives that you will use during the installation.
Set the DISPLAY environment variable as follows so that the GUI interface will be
displayed properly on your system.
For csh users, set your display variable to point to the DISPLAY terminal by
typing the following command:
setenv DISPLAY myworkstation:0.0
Chapter 3
63
For sh users, set your display variable by typing the following command:
DISPLAY=myworkstation:0.0; export DISPLAY
For ksh users, set your display variable by typing the following command:
export DISPLAY=myhostname:0.0
Disable any profiles that affect the login and root accounts. The installation and
root accounts should have a clean login meaning that the login should be free of
any special processing before a shell prompt is displayed.
Make sure you have write permissions for the $HOME and $HOME/BMCINSTALL
directories.
NOTE
The installation utility supports only Bourne shells. A Korn shell, C shell, or Bash shell is
acceptable, but these shell types are not supported and, on rare occasions, may cause
intermittent problems during the installation; for example, the installation utility may be
unable to access the root account to perform the installation.

To start the installation utility, mount the CD-ROM and type ./setup.sh at the root of
the CD.
NOTE
On UNIX systems, you cannot eject removable media while the media is being accessed;
therefore, if your installation requires multiple product images and you are using removable
media, then from a command line, cd to / and launch the installation utility by specifying the
absolute path; for example, /mnt/cdrom/setup.sh.
You can specify certain command line options to access additional functionality. For
details on command line options, see Command line options on page 65.
NOTE
Only one installation session should be started at one time. If you need to perform multiple
installations on the same computer, close out of each installation session and close all
associated browser windows before beginning a new session.
64

Table 3 describes the command line options that you can use when you launch the
installation utility from a command line in UNIX environments and references the
page numbers where you can find detailed information for each option.
Table 3
Command line options for UNIX installation (part 1 of 2)
Option
Definition
For details
-h
displays the list of command line options.
see page 67
-createcontrolfile
lets you create a control file instead of perform see page 68

a product installation. The control file that you
create shows the list of products that would be
installed and the product configuration values
that the installation utility would use to
perform the product installation. Use this
option to debug a failed installation, look for
potential problems with the installation before
actually installing products, vary product
configuration values to see the impact on the
installation, or change the product
configuration values associated with an
installable image by creating a new control file
to use with the image. Also, you can use this
option to create a control file that you can use to
perform a silent uninstallation.
lets you override the default host name that the see page 69
installation utility uses to connect to the Perl
HTTP server. You can enter either a host name
or an IP address. This option can be used
standalone or with the
-serveronly option.
-locale locale
installs language-specific resource files for the

language that you specify.
see page 71
lets you install previously released BMC
Software products onto new versions of
compatible platforms. With this option, you
specify the location of a file that contains new
platform definitions that override the platform
information stored in a product's installation
files. The installation files are used to
communicate installation information to the
installation utility when the product is
installed. You can also use the override file to
update the platforms that you can select when
you create an installable image.
-port portnum
lets you specify a port number to use to connect see page 72

to the Perl HTTP server used by the installation
utility to perform product installations.
Chapter 3
see page 70
65
Table 3
66
Command line options for UNIX installation (part 2 of 2)
Option
Definition
For details
-releaseversion ver
use this option to install a new KM into a

previous release of PATROL.
see page 73
lets you select a system role from the command see page 74
line so that only those products designated for
that system role are displayed in the Select
Products and Components to Install page.
-serveronly
use this option if you do not have a browser on see page 75

the computer on which you want to install
products; lets you start the Perl HTTP server on
one computer, then connect to that server using
a browser on another computer.
-timeout seconds
lets you specify the number of seconds that the see page 76
installation utility will wait to connect to the
Perl HTTP server before timing out.
-trace
records detailed information about activities in see page 77

the installation utility interface during
installation.
-v
displays the version number for the installation see page 78

utility.
-h
This option displays the list of command line options.
Command format
./setup.sh -h
Options
None.
Chapter 3
67
-createcontrolfile
This option lets you create a control file instead of perform a product installation. You
navigate through the installation utility as you would if you were performing a
product installation; however, at the end of the process, no products are actually
installed. Instead, a control file is created, and the installation utility displays a link to
the control file so that you can view it. The installation utility uses control files to
perform product installations.
The control file that you create shows a list of the products that will be installed and
the product configuration values that the installation utility will use to install the
products. Use this option to help you debug a failed installation, look for potential
problems with an installation before actually installing products, vary the product
configuration values to see the impact on the installation, or change the product
configuration values associated with an installable image by creating a new control
file to use with the image. The control file is located in the $HOME/BMCINSTALL
directory in a subdirectory with the naming convention computername-PID-timestamp.
A subdirectory is created for each installation session
NOTE
You can use this option to create a control file to perform a product uninstallation. For more
details, see Performing an unattended uninstallation on page 91.
Command format
./setup.sh -createcontrolfile
Options
None.
68
This option lets you override the default host name that the installation utility uses to
connect to the Perl HTTP server. By default, the installation utility connects to
localhost for a local product installation. If you launch the installation utility by using
the -serveronly command line option, the installation utility uses the primary IP
address of the computer where the Perl HTTP server is launched as the default host.
This option lets you override this default so that you can specify the host name or IP
address that you want the installation utility to use on computers with multiple IP
addresses. This option can be used standalone or with the -serveronly option.
Command format
./setup.sh -host_override hostname
./setup.sh -serveronly -host_override IPaddress
Options
None.
Chapter 3
69
-locale locale
This option lets you select and install only those products compatible with the locale
(language) that you specify. You can specify only one locale. The installation utility
will filter the list of products that will be displayed in the Select Products and
Components to Install page to display only those products that are either specific to
the locale that you specify or that do not have a locale designation.
If you do not specify an option, then the locale from the system on which you are
running the installation utility is used. If the system locale is not supported by the
installation utility, then the English locale, en_US, is used. This option does not
change the language of the text displayed in the installation utility. The installation
utility will run in English regardless of the system locale or the -locale option that you
enter except as noted. In addition, you will be able to input only English characters.
NOTE
If you set the -locale option to be the same as the system locale, you will install the
appropriate products and language resource files, but the installation utility will run in either
English or the system locale language and will accept input in either English or the system
locale language.
Command format
./setup.sh -locale en_US
Options
70
Language
Option
English
en_US
Traditional Chinese
zh_TW
Simplified Chinese
zh_CN
Korean
ko_KR
Japanese
ja_JP
This option lets you specify a file (override.dat) that will override platform definitions
in product installation files so that you can:
install previously released products onto new versions of compatible platforms.

update the platforms that you can select when you create an installable image of
products.
The product installation files contain product-specific installation instructions, such

as supported platforms, that communicate to the installation utility how to install the
product.
When BMC Software authorizes support for new platforms, Customer Support will
provide a valid override.dat file with new platform definitions that you will be able to
download from an ftp site located at the following URL:
ftp://ftp.bmc.com/pub/patrol/patches/COMMON_INSTALL_override.dat
After you have downloaded an updated override.dat file, when you install products,
launch the installation utility from a command line and use this option to specify the
location where you downloaded the file.
WARNING
Do not edit the contents of the override.dat file. The installation utility may be unable to read
the edited file.
Command format
./setup.sh -override_file /tmp/override.dat
Options
None.
NOTE
Although this functionality is being provided in this version of the installation utility, it
cannot be used at this time because a valid override.dat file does not currently exist on the ftp
site.
Chapter 3
71
-port portnum
This option lets you specify a port number to use to connect to the Perl HTTP server.
Use this option if the default port number to the server is locked and you want to
specify another open port, or if you are using the -serveronly command line option
and you need to open a port through a firewall. If not specified, the installation utility
uses a default of 50001. If the default port number is in use, the installation utility
increases the number by one and tries again to connect to the server.
Command format
./setup.sh -port 3184
./setup.sh -serveronly -port 3184
Options
72
In a PATROL environment, this option lets you install a new KM into an existing
PATROL environment.
Command Format
./setup.sh -releaseversion 3.4
Options
Option
Description
3.2
3.3
3.4
3.5,7.1
for 3.5.x and 7.1.x platforms and components. These options

should always be specified together.
7.2
for 7.2 platforms and components.
7.4
or 7.4 platforms and components. This is the default for this

version of the installation utility.
Chapter 3
73
This option lets you select a system role from a command line so that only those
products specified for a particular system role will be displayed in the Select Products
and Components to Install page. Each role has a specific code associated with it. The
roles (codes) that you can enter vary from product to product. Valid options can be
found in the sysrole.xml file in the /Index directory of the product image that you are
installing from. If you specify this option, the Select System Roles page will not be
displayed in the installation utility.
Command format
./setup.sh -repository_designator PAT,PAA
Options
Depends on the products that you are installing. See the sysrole.xml file for valid
options.
74
-serveronly
This option lets you start the Perl HTTP server on one computer, then connect to that
server using a browser on another computer. Use this option if you do not have a
browser on the computer where you want to install products. When you launch the
installation utility with this command line option, the Perl HTTP server is started,
and a message box is displayed that shows a URL. Leave this message box open. On
the computer with the browser, start the browser and enter the URL displayed in the
message box to connect to the Perl HTTP server.
By default, this option uses port number 50001 to connect to the Perl HTTP server. If
that port is busy, the installation utility automatically increases the number by one
and tries again to connect. You can specify the port that you want to use by using the
-port command line option with this option.
WARNING
The -serveronly command line option is not secure over a network and using it in an
unsecured network environment could result in security violations. If this is an issue for your
environment, you may want to consider either performing only local installations or creating
an installable product image that can be sent to a remote computer and installed on it locally,
rather than installing over an unsecured network. For details on creating an installable image,
see Creating, distributing, and installing installable images on page 79.
Command format
./setup.sh -serveronly
./setup.sh -serveronly -port 3184
Options
None.
Chapter 3
75
-timeout seconds
This option lets you specify the number of seconds that the installation utility will
wait to connect to the Perl HTTP server before timing out.
Command format
./setup.sh -timeout 120
Options
76
-trace
This option lets you record detailed information about what is happening in the
installation utility interface during a product installation. The installation utility adds
this information to the beginning of the standard log file. You can view the standard
log file from the installation utility when the installation is complete. This option also
saves the control file that the installation utility uses to install products. Normally, the
installation utility deletes the control file after the installation is complete. You can
use the saved control file and the information generated by this option for debugging.
For information where to find installation log files, see Locating log files on
page 87.
Command format
./setup.sh -trace
Options
None.
WARNING
Using this option causes the installation utility to record passwords unencrypted in the
Chapter 3
77
-v
This option displays a dialog box that shows the version number for the installation
utility.
Command format
./setup.sh -v
Options
None.
78
Creating, distributing, and installing installable images
Creating, distributing, and installing

installable images
This section describes using the installation utility to create an installable image,
options for distributing the image to remote computers, and installing the image on
computers to which it was distributed.
NOTE
UNIX computer.
Installable image files and directories

The installable image consists of the following files and directories. You will use or
refer to these files and directories when you launch the installation utility from an
installable image.
install.shrun this executable or script from a command line to install the products
in the image on the computer where the image is located.
*.ctlThis extension designates the control file that stores the installation and
product configuration information that you enter in the installation utility when
you create an installable image. The installation engine uses the information stored
in the control file to install the products in the location and with the configuration
that you specify.
*.logwhen the installation is complete, log files are created and stored in a
subdirectory in the $HOME/BMCINSTALL directory unless you use one of the
command line options listed in Table 4 on page 83 to redirect the files to a new
location.
The installation utility uses information stored in the following directories to install
the image.
Productsthis directory contains subdirectories that store the product files needed
by the installation utility to install the products that are part of the image.
Chapter 3
79
Installthis directory contains two subdirectories, instbin, which stores the

installation engine binaries and installation tools such as ctltool, and instdata,
which stores the default text files that control the order in which the products are
installed and that list the operating systems that are recognized by the installation
utility.
If you selected the option to compress and save the image to a .zip file, you will see
the following files:
inst_timestamp.zipthis file contains the compressed installable image directories
and files.
cizip.shrun this executable or script from a command line to extract the

installable image files.

This procedure describes how to create an installable image on a local computer for
local installation on other computers.
To create an installable image of products

1 Start the installation utility.
3 Review the license agreement and select Accept. Click Next.
4 On the Select Installation Option page, select Create an image to be installed later.
5 Enter the name of a directory on your computer where you want the image stored
after it has been created.
6 Optionally, select to have the image compressed and saved to a .zip file. Click Next.
7 Select the target operating systems on which you want to install the image. Click
Next.
You can select multiple Windows or UNIX platforms for each image that you
create. Alternatively, you can select the Local System option, which lets you create
an image that can be installed only on computers with the same platform and
configuration as the computer on which you are creating the image.
80
NOTE
UNIX computer.
8 Select the products that you want to include in the image. Click Next.
9 Proceed through the installation as you would if you were installing products
locally, entering all required product configuration information.
10 On the Review Selections and Create Image page, click Create Image.
11 When the status indicator reaches 100 percent, click Next on the Export Status page.
12 Verify that the process was successful and optionally view the log file. Click Next.
13 Review or enter any postinstallation product configuration information.
When you create an installable image, the product configuration information that you
enter, such as product installation directory, account names, passwords, and so forth,
must be the same for all computers on which the image is installed. If you want to
specify different product configuration values for different computers, you can
create a separate image for each set of values that you want to implement.
use the -createcontrolfile command line option to create a new control file to use
with the image. For more details, see Command line options on page 65.
use the ctltool to change the variables stored in the image's control file after the
image is generated. For more details, see Editing control files for installable
images on page 85.

Once you have created an installable product image, you can deploy it to your
environment in several ways:
Tar the image and use ftp or secure ftp to send it to a remote computer.
Use a third-party distribution system such as Microsoft Systems Management

Server (SMS).
Chapter 3
81
Burn the image to a CD and distribute the CD.
Place the image on a shared network drive.
Selecting the Compress Installable Image option in the installation utility to create
a .zip file that you can then send to other computers.
NOTE
If you created an installable image on a Windows computer to be installed on UNIX
computers, you must make sure that the method that you use to transfer the image (for
example, tarring the image) maintains execute permissions on the installable image files when
you unpack the files on the UNIX computer. If the permissions are not maintained, you may
receive an error message similar to the following when you try to install the image: "Error:
Executable not found './thorinst.s25'. To correct the file permissions, before you
install the image, perform one of the following tasks depending on where the installable
image directory resides:
If you exported the image to a directory that is at the root level, for example, /image, change to
the root directory and enter
chmod -R 755 /image
If you exported the image to a directory that is not at the root level, for example,
/image/myimage, change to the directory in which the image directory is located (/image),
and enter
chmod -R 755 /image/myimage
Once the image is copied to the computer, it can be installed as described in

Installing an installable image.

This procedure describes installing an installable product image locally in a UNIX
environment.
To install an installable image on a UNIX computer

1 Change to the directory that contains the image files.
2 If you selected the option to compress the image, unzip the file by entering the
following command:
./cizip.sh -u filename directory
82
The -u option unzips the file, the filename option is the name of the .zip file that
contains the installable image directories and files, and the directory option is the
path to the directory where the files will be placed after they are extracted from the
.zip file. If you specify a directory that does not exist, the directory will be created.
If you do not specify a drive with the directory name, the directory will be created
in the same directory where the .zip file is located.
3 Change to the directory where the unzipped files are located.

4 Launch the installation utility by entering the following command:
./install.sh options
For options, enter any command line options that you want to specify as listed in
Table 4.
5 You can optionally unzip the file and automatically start the installation by
entering the following command:
./cizip.sh -u -x filename directory
The -x option launches the installation utility after the file is unzipped. A platformspecific script is stored in the /tmp directory and the installation is run from that
script. The script is not removed after the installation is complete. If you choose the
-x option, you cannot specify any of the command line options listed in Table 4.
NOTE
The cizip utility can be used only on computers that have a dd binary that supports the
following command line options in their standard formats: if, of, bs, skip, and count.
Table 4
Installable image command line options for UNIX (part 1 of 2)
Option
Definition
-v
displays the installation utility version on the command line

then returns to the command line prompt
-h
displays the available command line options
-path directory
lets you specify the path name to the installable image if you
are not in the same directory
Chapter 3
83
Table 4
84
Installable image command line options for UNIX (part 2 of 2)
Option
Definition
-log location filename
comprehensive log file and the name of the log file to be
installable image files are located. The location and file
naming convention that you use for this option will also be
used for the product log, user log, and standard output log
unless you use the additional command line options to
specify the location and file names for these log files. For
example, if you name the comprehensive log file testing.log
and store the log file in a directory called /install/logfiles, the
product log file will be named testing-product.log, the user
log file will be named testing-user.log, and the standard
output log will be named testing-output.log and these log
files will also be stored in the /install/logfiles directory.
-productlog location filename
product log file and the name of the product log file to be
-userlog location filename
lets you specify the location where you want to store the user
log file and the name of the user log file to be stored in that
location. You can specify a complete path and filename or
just the file name. If you specify just the file name, the log file
is stored in the same directory where the installable image
files are located.
-install location filename
installs the products from a control file stored in the location

that you specify. If the location is not specified, the
installation utility looks for the control file in the directory
where the image was created.
-output location filename
standard output log file and the name of the log file to be
-nooutput
lets you send the output messages to standard output instead

of to a log file.
The installation utility executes and installs the products associated with the image to
the installation directory that you specified in the installation utility when you
created the image. When the process is complete, one of the following status
messages is displayed on the command line:
The installation completed successfully

The user log contains the following fatal messages and a list of the
messages
The product log contains the following non-fatal messages and
a list of the messages.
No status messages are displayed on the command line until the installation is
complete.
Log files are created and stored in the $HOME/BMCINSTALL directory unless you use
one of the command line options listed in Table 4 on page 83 to redirect them to
another location. If you use the -log command line option only, all log files will be
stored to the same location and with the same file naming convention that you
specify for the -log option. In previous releases of the installation utility, log files were
stored in the same directory as the installable image files.

Each computer on which you want to install an image must have the same product
configuration values as those stored in the images control file.
To change the product configuration values, you can either create a new image, or
edit the control file associated with the existing image. Ctltool is a utility that you can
use to change the product configuration values in an existing control file to create a
new control file. Then, you can use the new control file to install the same image on
computers that require the different values.
Chapter 3
85

This procedure describes how to edit the variables stored in an installable images
control file.
To use the ctltool to edit control files in UNIX environments

1 Change to the /Install/instbin directory in the directory where the installable image
is stored.

ctltool.sh path/inputfile.ctl path/outputfile.ctl
The option path/inputfile.ctl represents the path to and name of the control file that
you want to edit (the control file that was created with the installable image), and
the option path/outputfile.ctl represents the path to and name of the new control file
that you want to create.
For example, you create an installable image and store the image in a directory
called installableimage. When you create the image, the installation utility creates a
.ctl file named install.ctl and stores that file in that directory along with the image
files. To edit this control file and create a new one in the same directory, at the
command prompt, you would change to installableimage/install/instbin, and enter
ctltool.sh installableimage/install.ctl installableimage/newfile.ctl.
The installation utility displays the first value stored in the control file.
3 Type a new value and press Enter to save your entry and display the next variable.
To keep the existing value, press Enter. If you are changing a password variable,
the value is encrypted in the new control file.
When the ctltool has finished displaying all the variables in the control file, the
command prompt is displayed.
4 Rename the new control file to install.ctl so that when you install the image, the
installation utility uses the new control file. The installation utility looks for a
control file named install.ctl to perform the installation.
NOTE
Optionally, you can use the -install command line option when you install the image to
specify the location and name of the new control file that you want to use. For more details
on the -install command line option, see Installing an installable image on page 82.
86
Locating log files
Locating log files

The installation utility creates the following log files:
concatenated logContains information from all other log files created during a
user logLists error messages about fatal errors that caused an installation to fail.
The information in this log file is the first section in the concatenated log file.
product logLists nonfatal error messages and post-installation information

messages, such as if a script needs to be run manually because an invalid root
password was entered. The information in this log file is the second section in the
concatenated log file.
standard output logLists messages that are usually sent to standard output. The
information in this log file is the third section in the concatenated log file.
comprehensive or main logLists all actions performed by the installation utility

during a product installation such as the products that were installed or added to
an image, files that were copied or removed, scripts that were run and any output
from those scripts, and any version checking that was performed. The information
in this log file is the fourth section in the concatenated log file.
front end trace logShows detailed information about activities in the installation
utility interface during installation. This file is created if you launch the installation
utility from a command line and use the -trace command line option. The
information in this log file is the fifth section in the concatenated log file. For more
details on using the -trace command line option, see Command line options on
page 65.
root script logLists the root scripts that should be run during an installation
session and each scripts arguments. If root scripts fail to run during a product
installation, you can use this log file to determine what scripts you will need to run
manually after the installation is complete.
When the installation utility finishes installing products or creating an installable

image, a page is displayed in the installation utility that shows a status message
indicating the success or failure of the process. This page also contains a link, View
Log, to the concatenated log file and displays the log files location and name. The log
files name is determined at runtime and contains the name of the computer on which
the installation utility was run and an incremental time stamp.
Chapter 3
87
All log files are deleted after the installation is complete except for the concatenated
log file unless:
when you started the installation utility, you used either the -trace or the
the installation failed with an out-of-space error
The installation utility stores the log files in a subdirectory in the

$HOME/BMCINSTALL directory. A subdirectory is created for each installation
session and has the following naming convention: computername-PID-timestamp.

When you install products or create an installable image, you will need to provide the
name of a directory into which the products that you select will be installed. The
installation utility provides a default directory that you can use, or you can enter a
new directory.
WARNING
You cannot enter a root directory as the product installation directory for BMC Software
products, because if you uninstall products from that directory, you may unintentionally
uninstall products other than BMC Software products. If you need to install into a root
directory to install a product upgrade, you can create an installable image and specify the root
directory as the installation directory for the products in the image; however, if you need to
uninstall the products from the root directory, do not use the uninstall-all.ctl file to perform
the uninstall.
WARNING
Product installation directories are stored in installation utility history files as full path names;
therefore, do not rename the product installation directory after you install products, because
the installation utility will be unable to find the renamed directory if you uninstall products.
By default, the installation utility uses /opt/bmc as the product installation directory.
When you install products, the installation utility creates a subdirectory in the
product installation directory for each product that you install and the following
additional subdirectories that store information required by the installation utility:
Install/insthiststores files that contain installation utility history information,
such as which products you installed during a particular installation session
88
itoolsstores utilities that may be used by the products that you install
Uninstall/Install/instbasestores the Perl binaries and the Perl HTTP server code;
Perl is used by installation utility to install products
Uninstall/Install/instbinstores the installation engine binaries and installation
tools such as ctltool
Uninstall/Install/instcommonstores the xml files that are used to format and
display the standard installation utility pages
Uninstall/Install/instdatastores default text files that control the order of the list of
products that you can select to install and the order in which the products are
installed, and that list the operating systems that are recognized by the installation
utility

You can use the installation utility in uninstall mode to select and uninstall only those
products that were installed with version 7.2 or later of the installation utility.
Products installed with a previous version of the installation program must use that
versions uninstallation utility.
WARNING
Performing the tasks described in this section may remove files needed by a previous version
of the installation program to uninstall products installed with that version. Likewise, if you
use a previous version of the installation program to uninstall products, you may remove files
needed by this version of the installation utility to perform the uninstall tasks.
Chapter 3
89

Use the installation utility to select and uninstall individual products. All
components associated with those products will also be uninstalled unless they are
required by another installed product.
If the installation utility detects hidden, or orphaned, components on your computer,
an additional page is displayed during the uninstallation that gives you the option to
remove all of these components. Orphaned components are product components that
were originally installed as non-selectable required product components during a
previous product installation but are no longer required by any of the products
installed on your computer.
If you select to uninstall all products and any orphaned components, an additional
page is displayed that gives you the option to uninstall the uninstallation utility.
To uninstall products, orphaned components, and the uninstallation utility

1 Change to the Uninstall directory in your BMC Software product installation
directory and enter the following command to launch the uninstallation utility:
./uninstall.sh
The Welcome page is displayed. Click Next.
2 Select the installation directory from which you want to remove a product. Click
Next.
3 Enter pre-uninstallation product information.

The pages displayed during this phase of the uninstallation may present only
information that you should know prior to uninstalling the products or may
require you to enter information that the installation utility will use to perform
validation checking or execute scripts before the uninstallation process begins.
The pages displayed will vary depending on the products installed on your
computer. For some groups of products, no pre-uninstallation pages will be
displayed.
4 Select the product or products that you want to uninstall. Click Next.
5 (optional) If the uninstallation utility detects any orphaned components, select to
remove these components from your computer.
6 Enter any additional requested information in the displayed pages.
90
The information that you are required to enter depends on the products that you
are uninstalling; for example, you may be required to enter a root password to run
a script. These pages may also display only information that you need to know
once the products are uninstalled, such as if a script needs to be run manually after
the uninstallation is complete.
7 (optional) Select to uninstall the uninstallation utility.

All files and directories will be removed except those used by the uninstallation
utility at the time the uninstallation is performed, such as the setperm.sh archive
file. Log files, configuration files, user modified files, and files created as a result of
running scripts during the installation are also retained. These files can be
removed manually after the uninstallation is complete.
8 Review your selections and click Uninstall.

After the uninstallation is complete, a page is displayed that tells you the status of the
uninstallation and provides a link to the log file.

You can use the -createcontrolfile command line option to create a control file that
you can use to perform an unattended, or silent, uninstallation of products.
To create a control file to uninstall products

2 Change to the BMC Products Installation directory/Uninstall directory.
3 Start the uninstallation utility by entering the following command:
./uninstall.sh -createcontrolfile

5 Enter the name of the directory from which you want to uninstall products. Click
Next.
6 Select the products that you want to uninstall. Click Next.

7 If you selected to uninstall all products, optionally select to uninstall the
uninstallation utility.
8 Proceed through the uninstallation, entering any requested information.

Chapter 3
91
9 On the Review Settings for Control File page, click Create Control File.
10 Verify that the process was successful and optionally view the control file.
By default, the new control file is stored in $HOME/BMCINSTALL in a subdirectory
with the naming convention computername-PID-timestamp.
After the control file is created, you can rename it and copy it to another location or to
other computers, then use the following procedure to uninstall products.
NOTE
The computer where you use the control file must have the same configuration, such as
operating system, installed products, product installation directory, and so forth, as the
computer on which the control file was created.
To uninstall products by using the new control file

2 Change to the BMC Products Installation directory/Uninstall/Install/instbin directory.
./thorinst.sh -uninstall path to control file -log path to log file -output path to output log
file
The option path to control file is the path to and name of the control file that you
created in the previous procedure. The options -log and -output let you specify a
location for a standard log file and an output log file. The standard log file contains
all installation status information, and the output log file contains messages on the
progress of the installation that are normally sent to standard output. The path to
log file and path to output log file variables can be any valid path and file name (with
a .txt extension) that you specify.
92
Appendix
Troubleshooting a Windows
environment
A
This appendix contains information for troubleshooting the installation utility in

Windows environments. It presents the following topics:
Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Where to find diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Generating debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Sending diagnostic information to BMC Software Support . . . . . . . . . . . . . . . . . 104
Appendix A
93
Common problems
Common problems
This section contains troubleshooting information for the following common
problems:
94
Problem Type
Reference
The installation utility will not launch
page 95
browser
page 96
Online help does not display properly
page 96
Installation fails with a failed to run script error
page 97
Installable image installation fails
page 98
Installation fails with unable to connect to remote host error
page 98
Installation will not proceed past the specify installation directory page
page 99
Installation utility may stop responding if double quotes and angle brackets
are used in a directory path during a multiple CD installation
page 99
After a product installation, Internet Explorer 5.0 stops responding and

consumes 99 percent CPU
page 99
After a product installation, the installation utility cannot change a Windows

Server 2003 Itanium Terminal Server computer from install mode to execute
mode
page 100
The installation utility is unable to perform directory-related functions on

Windows platforms
page 101

The installation utility cannot connect to the Perl HTTP server that it uses to perform
a product installation and therefore will not start.
Explanation
Solution
You have specified a proxy server for internet

connections in your web browser.
Remove or bypass the proxy server setting. See

To fix the problem.
You are installing into a Windows Terminal Services

or Terminal Server environment and the change.exe
file does not exist in the Windows\System32
directory on the computer on which you are installing
products. The installation utility uses this file to
change to install mode, if necessary, in a Terminal
Services or Terminal Server environment.
Copy the change.exe file from another Terminal

Services or Terminal Server computer or launch the
installation utility from the Add/Remove Programs
utility and use the -no_change_exe command line
option. See Command line options on page 24.
The following error message is displayed:
Select Yes to close the installation utility, then

temporarily disable the pop-up blocker software. The
procedures and requirements for disabling pop-up
blocker software vary depending on the software that
you are using. Consult the documentation provided
with the pop-up blocker software for instructions.
You are trying to close this window;

close yes or no
Pop-up blocker software is running on the computer
where you are installing products. The installation
utility will not launch if pop-up blocker software is
running.
To fix the problem

Perform the appropriate task for the browser that you are using:
Internet Explorer
Netscape
Manual Proxy Configuration. For 4.7x versions, choose View and enter your domain
in the Exceptions text box for versions 4.75 and 4.76 and in the No Proxy for text box
for versions 4.77 and 4.78. For version 7, enter your domain in the No Proxy for text
box.
Appendix A
95
The computer on which you want to install products does not have a web browser
The computer on which you want to install products does not

have a web browser
To fix the problem

Perform one of the following tasks:
create an installable image then install the image on the computer that does not
have a browser. For more details, see Creating, distributing, and installing
installable images on page 42.

The installation utility Help does not display properly; for example, the Contents,
Index, and Search tabs are not displayed in the Help window.
To fix the problem

To properly display the help:
on the computer where you are running the installation utility
If you are running the installation utility on a Windows computer that has Internet
Explorer configured to use the Java Virtual Machine version 1.3.1, accessing the Help
system will cause the installation session to hang. To resolve this issue, perform one
of the following tasks:
96
upgrade to a newer version of the JVM
configure Internet Explorer to use a different JVM version if multiple versions are
installed on your computer
use the -serveronly command line option to start the installation utility Perl HTTP
server on the computer that is running the JVM version 1.3.1, then connect to that
server from a computer that has a different version of the JVM installed.

The installation fails with the following error message:
Error: Failed to run script [C:\Program]"
This error occurs when there is a directory or file called Program and Program Files in
the same target installation directory.
To fix The problem

Delete the Program directory or file.
Rename the Program directory or file, perform the installation, then rename the
directory or file back to its original name.
Install products to a directory that does not have a Program directory or file.
When you specify the destination path to install the products, use the short name
such as C:\progra~1\bmcsof~1 instead of using C:\Program Files\BMC Software.
Appendix A
97

Installation of an installable image fails with the following error message:
Silent install package can not be used for the current host."
This error message will be displayed in the following situations:
You used the Local System option to create the image and you installed the image
on a computer that does not have the same platform or configuration (including
the service pack level) as the computer on which you created the image.
You are installing the product on a platform that you did not select when you
created the image.
You are installing the product on a platform that is not supported by the product.
To fix the problem

Create a new image and select the applicable Windows platforms in the Select
Platform page.

http://localhost:50001/ 425 HTTP Error Unable to connect with
remote host
The installation utility is unable to connect to the primary IP address of the computer
on which the products are being installed. The installation utility uses the primary IP
address to connect to the Perl HTTP server that it uses to perform a product
installation.
To fix the problem

Launch the installation utility from a command line with the following command:
setup.exe -host_override hostname
This option allows you to specify the host name or IP address that you want the
installation utility to use on computers with multiple IP addresses. For more details
on the -host_override command line option, see Command line options on page 24.
98
Installation will not proceed past the specify installation

directory page
When you specify the product installation directory that you want to install to and
click Next to proceed to the Select Products and Components to Install page, the
installation utility displays the following error message:
There are no visible products on the image -- nothing to select
for install
Explanation
Solution
The installation utility and a product file downloaded Make sure that the installation utility and product
from either the BMC Software ftp or download sites files reside in the same directory before you extract
are not in the same directory.
the files and start the installation.
You may be installing a component, such as a patch,
that is designed for another operating system.
Verify the system requirements for the products and

components that you are installing as specified in the
product documentation (release notes, technical
bulletins, getting started guides, and so forth).
Installation utility may stop responding if double quotes and

angle brackets are used in a directory path during a multiple
CD installation
During a product installation that requires multiple CDs, if double quotes () or angle
brackets (< >) are entered in the directory path on the Additional CDs Needed page,
the installation utility may stop responding, and you will be unable to continue with
the installation. These characters are not supported by the installation utility and their
use should be avoided.
After a product installation, Internet Explorer 5.0 stops

responding and consumes 99 percent CPU
If you use Internet Explorer 5.0 to install products, when you exit the installation
utility after a product installation has completed, a message is displayed asking if you
want javascript to close a parent window. When you select Yes on the message dialog
box, the Internet Explorer process (IEXPLORER.EXE) stops responding and consumes
99 percent of the available CPU.
Appendix A
99
After a product installation, the installation utility cannot change a Windows Server 2003 Itanium Terminal Server
To fix the problem

Perform the following steps:
1 Open Task Manager.

2 Click on the Processes tab.
3 Select the IEXPLORE.EXE process that is consuming 99% CPU.
4 Click End Task.
The status of the installation is not affected by stopping the process, because the installation
was completed before Internet Explorer stopped responding.
After a product installation, the installation utility cannot

change a Windows Server 2003 Itanium Terminal Server
computer from install mode to execute mode
After performing an installation on a computer running Windows Server 2003
Itanium configured as a Terminal Server, the installation is successful but the
installation utility can not change the computer from install mode to execute mode.
The following error is displayed in the log file:
DoTerminalServer:Start: bIsTerminalServer[1]
bIfInstallMode[1], InstallMode[0]
DoTerminalServer:Changing to execute mode.
DoTerminalServer:Error: Unable to create process
To fix the problem

After the installation is complete, log off then log back on before you use any other
applications. This resets the computer to execute mode.
100
The installation utility is unable to perform directory-related functions on Windows platforms
The installation utility is unable to perform directory-related

functions on Windows platforms
On Windows platforms, the installation utility can not
create a temporary directory during a multiple CD installation

access directory paths with the Browse buttons
create an installable image
create the product installation directory during a local installation causing the
installation utility to stop responding
These problems result from POSIX not being installed or enabled on the computer
where you want to install products. The installation utility uses the POSIX subsystem
on Windows computers to perform directory-related commands. To see if POSIX is
enabled, check the following registry key:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session
Manager/Subsystems
If the following entries are not present, then POSIX is disabled:

Optional: REG_MULTI_SZ : Os2 Posix...
Posix: REG_EXPAND_SZ : %SystemRoot%\system32\psxss.exe
To fix the problem

Install or enable POSIX on the computer where you want to install products. If POSIX
can not be enabled for security reasons, create an installable image on a POSIXenabled Windows computer or on a UNIX computer, then use that image to install
products on the computer that does not have POSIX enabled.
Appendix A
101
Gathering diagnostic information

This section contains general information on gathering diagnostic information for the
installation utility.
Where to find diagnostic information

The following table lists locations where you can find diagnostic information for
problems with the installation utility.
Type
Location
Description
Installation
logs
drive:%HOMEPATH%\BMCinstall
The Application Data directory is hidden. For

more details on log files and displaying the
Application Data directory, see Locating log
files on page 51.
For Windows NT:

C:\winnt\Profiles\username\
Application Data\BMCinstall
For Windows 2000, Windows XP, and
Windows Server 2003:
C:\Documents and Settings\username\
Application Data\BMCinstall
Status page
This page is displayed in the installation The status page displays the following
utility while products are being installed, information:
an installable image is being created, or
products are being uninstalled.
a message indicating what action the
installation utility is currently taking
the status of that action
the percent complete of the process
You can review this information while the
process is being performed and look for any
potential problems with the installation.
102
Generating debug information

The following table lists tasks for generating debug and other diagnostic information.
Task
Reference
Turning on trace modeTurning on trace mode
page 103
Determining the installation utility version number
page 103
Creating a control file
page 104
Turning on trace mode

To create a trace log file that can be used to help you debug problems with a product
installation, launch the installation utility from a command line and use the -trace
command line option. If you specify this option, the control file and log files created
during the installation are saved. For details on this options, see Command line
options on page 24.
WARNING
Turning on trace mode causes passwords to be recorded in plain text and not encrypted in the

This version of the installation utility might be different from the version included on
another product CD or from a version that you downloaded from the BMC Software
product download site. Review the release notes for the version that you are using to
identify any open issues and workarounds to help you troubleshoot potential
problems. If a call to Customer Support is necessary to help you resolve an issue,
your Support representative will ask you what version of the installation utility you
are using.
To determine the installation utility version number

2 Navigate to the directory where the installation utility is located.
setup.exe -v
A message box displays the version of the installation utility.
Appendix A
103
Sending diagnostic information to BMC Software Support

You can create a control file (.ctl) instead of installing products locally or creating an
installable image. This control file can be used to help debug problems with a product
installation or can be used to identify potential problems with the installation before
you actually install products. To create a control file, launch the installation utility
from a command line and use the -createcontrolfile command line option. For details
on this option, see Command line options on page 24.
Sending diagnostic information to BMC Software Support

If you experience problems that require you to contact Customer Support, email the
following diagnostic information to [email protected] when you open your case. This
will help Customer Support troubleshoot your case more quickly.
104
Error messages generated during the installation
The name of the product CD (or downloaded product image) that you are
installing
The installation logs (located in your users profile directory in the Application
Data\BMCinstall directory)
The operating system on which you are installing products, including version and
service pack
The method you used to start the installation utility and any command line options
that you specified
Amount of disk space on the computer where you are installing products
Appendix

This appendix contains information for troubleshooting the installation utility in
UNIX environments. It contains the following topics:
Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Where to find diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending diagnostic information to BMC Software support . . . . . . . . . . . . . . . . .
Appendix B
106
117
117
117
119
105
Common problems
Common problems
This section contains troubleshooting information for the following common
problems:
Problem Type
Reference
Typing errors cannot be corrected in an X-emulator
page 107
The display cannot be opened
page 107
page 108
Javascript error messages are displayed during installation
page 109
Installation utility encounters problems during installation
page 109
browser
page 110
page 110
Installation utility pages turn blank when resized
page 111
Perl error message is displayed when the -serveronly option is used
page 111
Installation fails with unable to install perl error message
page 112
Installation fails or configuration scripts cannot be run after an installation
page 112
page 113
page 113
Unable to run root scripts error message is displayed on computers running

Red Hat Enterprise Linux AS 3.0
page 114
Mozilla browser renders installation utility pages with extra space
page 115
Cannot extract a compressed installable image that is saved to a network share page 115
on AIX platforms
Installation fails on computers running Red Hat and SuSE Linux
page 115
The installation utility is unable to run root scripts and reports an invalid root page 116
password on computers running Red Hat Enterprise Linux AS 4.0
Error messages are displayed when launching the installation utility on
computers running Red Hat Enterprise Linux AS 4.0 on Itanium
106
page 116

You cannot correct typing errors in installation utility pages when you use an Xemulator on a PC to run the installation utility. This can be caused by some X
emulation software.
To fix the problem

Use one of these three controls to delete typed characters: Backspace, Delete, or Ctrl+H.
The display cannot be opened

The display cannot be opened so the installation utility interface cannot be displayed.
Explanation
Solution
Your machine does not have permission to open the

requested X11 display.
Type the following command in the OS login window

to permit displays on your terminal:
xhost +your-hostname
Your DISPLAY environment variable is not set or is

improperly set.
For details on setting the DISPLAY environment

variable, see Before you begin installing on page 63.
There is a configuration setting that prohibits the

display of graphics or remote interfaces.
See To fix The problem.
There is a problem with the Netscape installation.
See To fix The problem.
To fix The problem

Exit the current installation session and restart the installation utility using the
-serveronly command line option to start the Perl HTTP server. To connect to the
server, on another computer, open Netscape or Internet Explorer and in the
browser enter the URL returned by the setup command. For more details on the
-serveronly option, see Command line options on page 65.
Leave the current installation session running. On the same computer, launch
Netscape and enter the following URL:
http://localhost:50001/
Appendix B
107

The installation utility cannot connect to the Perl HTTP server that it uses to perform
a product installation and therefore will not start.
Explanation
Solution
You have specified a proxy server for internet

connections in your web browser.
Remove or bypass the proxy server setting. See

To fix the problem.
The following error message is displayed:
Select Yes to close the installation utility, then

temporarily disable the pop-up blocker software. The
procedures and requirements for disabling pop-up
blocker software vary depending on the software that
you are using. Consult the documentation provided
with the pop-up blocker software for instructions.
You are trying to close this window;

close yes or no
Pop-up blocker software is running on the computer
where you are installing products. The installation
utility will not launch if pop-up blocker software is
running.
To fix the problem

You have specified a proxy server for internet connections in your web browser.
Remove or bypass the proxy server definition by performing one of the following
task for the browser that you are using:
Netscape
Manual Proxy Configuration. For 4.7x versions, choose View and enter your domain
in the Exceptions text box for versions 4.75 and 4.76 and in the No Proxy for text box
for versions 4.77 and 4.78. For version 7, enter your domain in the No Proxy for text
box.
Internet Explorer
108

The following error messages are seen during a product installation:
javascript error - line 67, screen not defined
javacript error - line 145, setInterval is not defined.
To fix the problem

You are using a version of Netscape that is not supported by the installation utility.
Use one of the following versions:
For English platforms:
4.75, 4.76, 4.77, or 4.78 on all platforms

Netscape 7 on AIX 4.3.3, 5.1, 5.2; Red Hat Linux 7.0, 7.1, and 7.2; HPUX 11.0 and
11i; and Solaris 7, 8, and 9.
For CTKJ platforms:
4.75, 4.76, or 4.77 on all platforms

4.78 for Red Hat Linux 7.2
4.73 for Korean platforms running Red Hat Linux 7.0, and 7.1
4.72 for Japanese platforms running Red Hat Linux 7.1
4.70 for Japanese platforms running Solaris 2.6, 7, and 8
Netscape 7 on AIX 5.1, 5.2; Red Hat Linux 7.0, 7.1, and 7.2; HPUX 11.0 and 11i; and
Solaris 7, 8, and 9.
Installation utility encounters problems during installation

The installation utility may encounter problems such as not being able to access the
root account during installation.
To fix the problem

If you are using a Korn shell, C shell, or Bash shell to perform the installation, switch
to a Bourne. Only Bourne shells are supported for this version of the installation
utility. While Korn shells, C shells, and Bash shells are acceptable and can be used,
they are not supported and may cause intermittent problems during the installation.
Appendix B
109
The computer on which you want to install products does not have a web browser
The computer on which you want to install products does not

have a web browser
To fix the problem

Perform one of the following task:
create an installable image then install the image on the computer that does not
have a browser. For more details, see Creating, distributing, and installing
installable images on page 79.

The installation utility Help does not display properly; for example, the Contents,
Index, and Search tabs are not displayed in the Help window.
To fix the problem

To properly display the Help
on the computer where you are running the installation utility
the java40.jar file must exist in your Netscape installation directory

If it does not exist, you will need to download and reinstall Netscape.
110
the variable MOZILLA_HOME should be set to point to the root of the Netscape
installation directory
EXAMPLE
For sh or ksh users, if the Netscape installation directory is /opt/netscape, enter the following
commands to set this variable:
MOZILLA_HOME=/opt/netscape
export MOZILLA_HOME
EXAMPLE
For csh users, if the Netscape installation directory is /opt/netscape, enter the following
command to set this variable:
setenv MOZILLA_HOME /opt/netscape

If you resize the installation utility page on computers running Red Hat Linux 7.0, the
page may turn blank.
To fix the problem

Do not resize the installation utility page. Use the scroll bars to navigate the page.
Perl error message is displayed when the -serveronly option is

used
The installation utility displays an error message that the Perl HTTP server could not
be started when the installation utility is launched using the -serveronly command
line option.
To fix the problem

The installation utility may be timing out before the Perl HTTP server is started.
Increase the time out value by using the -timeout command line option with the
-serveronly option as follows:
./setup.sh -serveronly -timeout seconds
For more details on these options, see Command line options on page 65.
Appendix B
111

We were unable to install Perl. At least 1 meg is needed in /tmp.
Explanation
Solution
An incompatible version of the installation utility was

downloaded from the BMC Software product
download or ftp site and therefore cannot be used to
run the utility on some UNIX platforms.
The installation utility product download and ftp

sites consist of several versions based on supported
UNIX platforms. Download either the version that
corresponds to the platform that you are installing to
or the version that is compatible for all UNIX
platforms.
The installation utility cannot write to the $HOME

directory.
See To fix the problem.
To fix the problem

Make sure that
you have write permissions for the $HOME and $HOME/BMCINSTALL

directories.
the umask setting is set to 022.
you have enough disk space on the computer on which you are installing
products.
you do not su to the installation account, because the $HOME environment

variable may not be set properly.
Installation fails or configuration scripts cannot be run after

an installation
You installed products by using the root account. The concatenated installation log
file will show a value of user=root.
To fix the problem

Uninstall the products then reinstall them by using a user account other than the root
account.
112

http://localhost:50001/ 425 HTTP Error Unable to connect with
remote host
The installation utility is unable to connect to the primary IP address of the computer
on which the products are being installed. The installation utility uses the primary IP
address to connect to the Perl HTTP server that it uses to perform a product
installation.
To fix the problem

Launch the installation utility by specifying the following command:
./setup.sh -host_override hostname
This option allows you to specify the host name or IP address that you want the
installation utility to use on computers with multiple IP addresses. For more details
on the -host_override command line option, see Command line options on page 65.
Installation will not proceed past the specify installation

directory page
When you specify the product installation directory that you want to install to and
click Next to proceed to the Select Products and Components to Install page, the
installation utility displays the following error message:
There are no visible products on the image -- nothing to select
for install
Explanation
Solution
The installation utility and a product file downloaded Make sure that the installation utility and product
from either the BMC Software ftp or download sites files reside in the same directory before you extract
are not in the same directory.
the files and start the installation.
You may be installing a component, such as a patch,
that is designed for another operating system.
Verify the system requirements for the products and

components that you are installing as specified in the
product documentation (release notes, technical
bulletins, getting started guides, and so forth).
Appendix B
113
Unable to run root scripts error message is displayed on computers running Red Hat Enterprise Linux AS 3.0
Unable to run root scripts error message is displayed on

computers running Red Hat Enterprise Linux AS 3.0
The installation utility displays an Unable to run root scripts error message
at the end of a product installation and in the product log file on computers running
Red Hat Enterprise Linux AS 3.0 for IBM zSeries, even though the installation was
successful.
The installation utility uses a third party tool called Expect to run root scripts as root
processes in UNIX environment. Expect uses /dev/ttypx pseudo terminal for the
communication layer between the install process and the root process. Red Hat
Enterprise Linux AS 3.0 for IBM zSeries does not have the old-style BSD pseudo
terminals configured by default, therefore, Expect can not run the root scripts during
the installation session.
To fix the problem

Run the root scripts manually after the product installation is complete. The
installation utility creates a root script log that lists the scripts that were to be run
during the installation session and each scripts arguments. You can use this log file
to determine what scripts you will need to run. By default, the script log file is
located in a subdirectory in the $HOME/BMCINSTALL directory and uses the
following naming convention: computername_timestamp.log_rootscripts.
Create a pseudo terminal as follows before you install products in this

environment:
A. Log on as root.
B. Enter the following commands:
mknod /dev/ttyp0 c 3 0
chmod 666 /dev/ttyp0
You need to create only one device for Expect to work correctly. Expect will try to
open /dev/ttyp0 and if it's unsuccessful, will try the next device through the
character set 0123456789abcdef.
114
Mozilla browser renders installation utility pages with extra space
Mozilla browser renders installation utility pages with extra

space
The Mozilla web browser inserts extra space at the bottom of the installation utility
pages, in some cases causing a scroll bar to appear. This is a limitation in the way the
Mozilla browser renders the pages and does not affect the installation.
Cannot extract a compressed installable image that is saved

to a network share on AIX platforms
A compressed installable image created on AIX platforms and saved to a network
share has 0 bytes and cannot be extracted by using the cizip utility.
To fix the problem

Save the image to a local drive instead of a network share.
Installation fails on computers running Red Hat and SuSE

Linux
The installation utility is unable to determine the correct target operating system that
it is installing to and therefore, fails the installation on computers running Red Hat
Linux and SuSE Linux.
To fix the problem

This problem may be the result of edits to the operating system release files. The
installation utility uses information stored in these files to determine the target
operating system. BMC Software recommends that you do not edit the release files,
because the installation utility may be unable to read the edited files, thus causing the
installation to fail. If you must edit the release files, do so by adding additional lines
of text and not by editing the existing information stored in the file.
Appendix B
115
The installation utility is unable to run root scripts and reports an invalid root password on computers running Red Hat
The installation utility is unable to run root scripts and

reports an invalid root password on computers running Red
Hat Enterprise Linux AS 4.0
The installation utility is unable to run root scripts on computers running Red Hat
Enterprise Linux AS 4.0 and reports an invalid password, even though a correct root
password was entered and the installation completed successfully. This problem
occurs because the installation utility cannot find su to switch to root to execute the
script.
The following error message is displayed in the log file:
CI_ROOT_BAD_PASSWD;Unable to run script [scriptName] as user
[root] because of invalid password. The script has to be run
manually later as root.
To fix the problem

After the product installation is complete, run the root scripts manually. The
installation utility creates a root script log that lists the scripts that were to be run
during the installation session and each scripts arguments. You can use this log file
to determine what scripts you will need to run manually. By default, the script log file
is located in the $HOME/BMCINSTALL directory and uses the following naming
convention: computername_timestamp.log_rootscripts.
Error messages are displayed when launching the installation

utility on computers running Red Hat Enterprise Linux AS 4.0
on Itanium
One of the following error messages is displayed when you launch the installation
utility on a computer running Red Hat Enterprise Linux AS 4.0 on Itanium:
Exec format error. Wrong Architecture.
[ERROR]Failed to execute targetos.l22, maybe incompatible

with current platform.
These error messages are displayed when the 32-bit compatibility system libraries
have not been installed on Red Hat Enterprise Linux AS 4.0 systems. These libraries
are required to launch the installation utility.
116
To fix the problem

You must install the 32-bit compatibility packages containing the system libraries
from the Red Hat Enterprise Linux distribution. For details on how to install these
packages, see the Red Hat Enterprise Linux AS 4.0 Release Notes. The system
libraries will be installed into the following directory:
/emul/ia32-linux/lib

This section contains general information on gathering diagnostic information for the
installation utility.
Where to find diagnostic information

The following table lists locations where you can find diagnostic information for
problems with the installation utility.
Type
Location
Description
Installation
logs
$HOME/BMCINSTALL
See Locating log files on page 87.
Status page
This page is displayed in the installation The status page displays the following
utility while products are being installed, information:
an installable image is being created, or
products are being uninstalled.
a message indicating what action the
installation utility is currently taking
the status of that action
the percent complete of the process
You can review this information while the
process is being performed and look for any
potential problems with the installation.

The following table lists tasks for generating debug and other diagnostic information.
Appendix B
117
Task
Reference
page 118
page 118
page 119

To create a trace log file that can be used to help you debug problems with a product
installation, launch the installation utility from a command line and use the -trace
command line option. If you specify this option, the control file and log files created
during the installation are saved. For details on this option, see Command line
options on page 65.
WARNING
Turning on trace mode causes passwords to be recorded in plain text and not encrypted in the

This version of the installation utility might be different from the version included on
another product CD or from a version that you downloaded from the BMC Software
product download site. Review the release notes for the version that you are using to
identify any open issues and workarounds to help you troubleshoot potential
problems. If a call to Customer Support is necessary to help you resolve an issue,
your Support representative will ask you what version of the installation utility you
are using.
To determine the installation utility version number

Perform the following steps:

2 Navigate to the directory where the installation utility is located.
./setup.sh -v
A message box displays the version of the installation utility.
118
Sending diagnostic information to BMC Software support

You can create a control file (.ctl) instead of installing products locally or creating an
installable image. This control file can be used to help debug problems with a product
installation or can be used to identify potential problems with the installation before
you actually install products. To create a control file, launch the installation utility
from a command line and use the -createcontrolfile command line option. For details
on this option, see Command line options on page 65.

If you experience problems that require you to contact Customer Support, email the
following diagnostic information to [email protected] when you open your case. This
will help Customer Support troubleshoot your case more quickly.
Error message generated during the installation
The name of the product CD (or downloaded product image) that you are
installing
The installation logs (located in your users profile directory in the

$HOME/BMCINSTALL directory)
The operating system on which you are installing products, including version and
kernel width (32 or 64 bit)
Any command line options that you specified when you started the installation
Shell environment information (enter env to get this information)
Disk space information (enter df -k to get this information)
Appendix B
119
120
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
B
BMC Software, contacting 2
browser
Internet Explorer
bypassing proxy server definitions 24
removing proxy server definitions 24
setting font size 24
Netscape
setting character sets for Japanese locales 67
requirements for displaying installation utility online
Help
in UNIX environments 68
in Windows environments 25
C
changing the default host name when installing products
on UNIX platforms 75
on Windows platforms 33
character sets, setting in Netscape for Japanese locales 67
command line options
for installing an installable image
for starting the installation utility
control files
definition 47, 85
editing for installable images by using ctltool
using to uninstall products
for UNIX platforms 74
for Windows platforms 32
using to uninstall products
creating an installable image

account requirements for Windows platforms 48
command line options for installing the image
deploying the image for installation
files and directories used for installation
installing
locally on a UNIX computer 88
locally on a Windows computer 51
maintaining permissions when deploying to UNIX
platforms 50, 88
procedure for
Custom installation path 16
customer support 3
D
debugging
using the -trace command line option
Default installation path 15
directories
created as part of an installable image
designating temporary space for multiple CD
installations 18
overview of default installation directory structure
for UNIX environments 94
for Windows environments 57
F
files used to install an installable image
Index
121
H
-h command line option
Help, requirements for displaying in the installation utility
host name
changing the default when installing products
-host_override command line option
I
installable images
account requirements for Windows platforms 48
command line options for installing
creating
deploying before installing
directories. See files and directories used for
installation
editing control files by using ctltool
files and directories used for installation
installing
locally on a UNIX computer 88
locally on a Windows computer 51
maintaining permissions when deploying to UNIX
platforms 50, 88
installation directories
overview of default directory structure
installation log files
location in UNIX environments 93
location in Windows environments 56
installation paths
Custom 16
Default 15
Typical. See Default
122
installation prerequisites
required file for Terminal Services 26
required umask setting for UNIX 69
installation requirements
installing installable images
deploying before installing
how to install
Internet Explorer
bypassing proxy server settings 24
removing proxy server settings 24
requirements for displaying Help 25
IP address
changing the default when installing products
L
launching the installation utility
for multiple CD installations on UNIX platforms 70
-locale command line option
log files
accessing after performing an installation
M
Microsoft Windows
Terminal Services file required to change installation
mode 26
multiple CD installations, launching the installation utility
N
Netscape
bypassing proxy server settings 68
removing proxy server settings 67
requirements for displaying Help 68
network requirements
-no_change_exe command line option for Windows
platforms 35
O
online Help, requirements for displaying in the
installation utility
UNIX platforms 68
Windows platforms 25
-override_file command line option
P
-port command line option
prerequisites
for installing products on Windows platforms 26
required file for Terminal Services 26
setting umask value before installing on UNIX
platforms 69
privileged account, creating with sudo 17
problems, common
product installation directories
overview of default directory structure
product support 3
proxy server settings
bypassing in Internet Explorer 24
bypassing in Netscape 68
removing in Internet Explorer 24
removing in Netscape 67
R
-releaseversion command line option
-repository_designator command line option

requirements
for displaying online Help in the installation utility
for installation
network
root account, using a sudo-privileged account in place of
17
S
selecting products
by using the Custom installation path 16
by using the Default installation path 15
-serveronly command line option
-shutdownservice command line option for Windows
platforms 42
silent installation. See installable images
silent uninstallation
-skipuserright command line option for Windows
platforms 43
starting the installation utility
sudo, installing and configuring 17
support, customer 3
T
technical support 3
Terminal Services, file required to change installation
mode 26
-timeout command line option
-trace command line option
trace mode
Index
123
troubleshooting
UNIX
unable to run root scripts error message is
displayed on computers running Red Hat
Enterprise Linux AS 3.0 120
cannot extract a compressed installable image
that is saved to a network share on AIX
platforms 121
common problems 112
computer does not have a web browser 116
determining installation utility version number
124
display cannot be opened 113
error messages are displayed when launching the
installation utility on computers running Red
Hat Enterprise Linux AS 4.0 on Itanium 122
installation fails on computers running Red Hat
and SuSE Linux 121
installation fails or configuration scripts cannot
be run after installation 118
installation fails with unable to connect to
remote host error 119
installation fails with an unable to install Perl
error message 118
installation utility is unable to run root scripts
and reports an invalid password on computers
running Red Hat Enterprise Linux AS 4.0 122
installation utility will not launch 114
installation utility windows turn blank on Red
Hat Linux 7.0 computers 117
installation will not proceed past the Specify
Installation Directory window 119
javascript error messages are displayed during
installation 115
Mozilla browser renders installation utility pages
with extra space 121
online Help does not display properly 116
Perl HTTP server could not be started when
using the -serveronly command line option 117
sending information to Customer Support 125
setting DISPLAY environment variable 69
typing errors cannot be corrected in an Xemulator 113
using an unsupported UNIX shell causes
problems during installation 115
Windows
after installation, the installation utility cannot
change a Windows Server 2003 Terminal
Server computer from install mode to execute
mode 106
common problems 100
computer does not have a web browser 102
determining installation utility version number
109
installable image installation fails 104
installation fails if change.exe file does not exist
in Terminal Server environments 101
124
installation fails if pop-up blocker software is

enabled 101
installation fails if proxy server is defined for web
browser 101
installation fails with unable to connect to
remote host error 104
installation utility is unable to perform directoryrelated functions 107
installation utility may stop responding if double
quotes and angle brackets are used in a
directory path during a multiple CD
installation 105
installation will not proceed past the Specify
Installation Directory window 105
Internet Explorer 5.0 stops responding and
consumes 99 percent CPU 105
more than one Program directory or file 103
online Help does not display properly 102
sending information to Customer Support 110
turning on trace mode
Typical installation path. See Default installation path
U
umask setting 69
unattended uninstallation
uninstalling products
UNIX
umask setting 69
V
-v command line option
W
web browser
Internet Explorer
Netscape
web browser (continued)
requirements for displaying installation utility online
Help
Windows
Terminal Services file required to change installation
mode 26
Index
125
126
TCL/TK License Terms

This product includes the TCL software product found at http://tcl.sourceforge.net, and the software product is distributed to us pursuant to the following
terms and conditions:
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following
terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing
copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is
required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described
here, provided that the new terms are clearly indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF
THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON
AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software
and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of
the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as
defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf
permission to use and distribute the software in accordance with the terms specified in this license.
Notes
*65067*
*65067*
*65067*
*65067*
*65067*

Installation Utility

Uploaded by

Copyright:

Available Formats

Installation Utility

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Utility

Uploaded by

Copyright:

Available Formats

Installation Utility

Contacting BMC Software

United States and Canada

BMC SOFTWARE INC

713 918 8800 or

(01) 713 918 8000

713 918 8000

Outside United States and Canada

(01) 713 918 8800

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

operating system and environment information

sequence of events leading to the issue

commands and options that you used

product error messages

Installation Utility Reference Manual

About the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing and uninstalling products in a Windows environment

Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing and uninstalling products in a UNIX environment

Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Troubleshooting a Windows environment

Troubleshooting a UNIX environment

Common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Installation Utility Reference Manual

The installation utility will not launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Installation Utility Reference Manual

Chapter 1 Installation overview

About the installation utility

About the installation utility

The installation utility interface

page to the default values.

Show/Hide Advanced - displays or hides optional advanced product

Options for installing products

Installation Utility Reference Manual

Options for selecting products to install

Options for selecting products to install

Selecting products by using the default installation path

Example of a product selection tree view for PATROL productsdefault

You are installing products for the first time.

Selecting products by using the custom installation path

Selecting products by using the custom installation path

Example of a product selection tree view for PATROL productscustom

and all products that belong to the specified

You want to more fully customize your product configuration.

Installation Utility Reference Manual

Installing and configuring sudo to create a privileged account

Installing and configuring sudo to create a

To install and configure sudo

3 Reconfigure sudo to turn off password caching by entering the following

Password caching causes sudo sessions to be on a timer, meaning one sudo

Performing a multiple CD installation

# User alias specification

Performing a multiple CD installation

creates the temporary directory, if necessary

Installation Utility Reference Manual

Gathering product configuration information

Gathering product configuration information