Installing an installable image on a Windows computer

This topic describes how to install an installable image of BMC products on a Windows computer.  

Before you begin

You must have created the installable image and deployed it to the target Windows computer.

To install a product image locally in a Windows environment

  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. 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 the following table.
  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 the following table. 

Installable image command line options for Windows 

Option

Definition

-v

Displays the installation utility version on the command line, and 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 a name and location for the comprehensive log file and the name of the log file to be stored in that location. You can specify a complete path and file name 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. You can use additional command line options to specify a different location and file name for these log files. For example, if you name the comprehensive log file testing.log and store the it 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; all these log files will also be stored in the c:\install\logfiles directory.

-productlog location filename

Lets you specify a name and a location for the product log file and the name of the product log file to be stored in that location. You can specify a complete path and file name 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.

-userlog location filename

Lets you specify a name and a location for the user log file. You can specify a complete path and file name 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.

-output location filename

Lets you specify a name and a location for the standard output log file. You can specify a complete path and file name 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.

-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.

-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.

-no_backupwhen upgrading a PATROL Agent, by default the common installer creates a backup. If this option is enabled, then it does not creates a backup.

The installation utility runs 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. This is followed by a list of messages
    • The product log contains the following non-fatal messages. This is followed by a list of 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 the above table to redirect them to another location. If you use only the -log command line option, 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: 

      C:\Documents and Settings\username\Application Data\BMCinstall 
Was this page helpful? Yes No Submitting... Thank you

Comments