Skip to Content
Information
Space banner This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Packages configuration

The Configuration node provides access to different aspects available for the configuration of the different packages. Depending on the type of package some of the tabs might not be available.

The following topics provide more information about different configuration aspects available for different packages:

Overwrite

The Overwrite tab defines which files the package can overwrite when installing on the target and which it is not to touch.

Warning

Note:

This tab is only available for custom packages.

Modifying the overwrite options

To modify any of the previously listed options proceed as follows:

  1. Select either one of the lines in the table of the right window pane.
  2. Select Edit > Propertiesproperties.png.
    The Properties window appears.
  3. Make the required modifications in the two drop-down boxes.
  4. Click OK to confirm the modifications and to close the window.

The Installation tab

The Installation tab provides information about the execution of the installation of the package on the target(s).

MSI Package

The options provided in this tab depend on which type of installation you selected in the General tab. The possible values for most of these options are true and false, true meaning the entry will be applied, false not applied or you might have to provide data in a text field. Following you will a selection of possible options. For more information about these and other options not mentioned here refer to the Microsoft MSI documentation.

Files to be present

The Files to be Present tab for all types of packages is concerned with the definition of files that must absolutely be already installed on the target computer. If these files are not there, the installation or later execution of the installed software will fail. This tab is not available for MSI packages. 

An example of files required for successful operation might be the OLE 2.0 DLLs, which are resident in the Windows directory but are used by most large applications. Such files are not usually added to the system if already present, so it is vital that the console detects the software dependencies on them.

Adding a file to the list of the files to be present

To add a file to the list of files to be present on the target, proceed as follows:

  1. Select the Configuration node in the left window pane and the Files to be Present tab in the right pane.
  2. Select Edit> Add Filefile_add.png.
    The "configuration" window appears.
  3. Select the required file from the file hierarchy displayed in the list window.
  4. Click OK to confirm the addition and to close the window.

Files to be absent

The Files to be Absent tab is concerned with files which must absolutely not be found anywhere on the target computer for the installation to proceed. Examples for such files might be the largest executable files to ensure that the same software will not be installed twice. This tab is not available for MSI packages.

As with the required present files, these files will be automatically added to the list of files, which must be absent from the client system. Same as with the present files, you can specify additional files, which will be required to be absent by the client agent before the installation starts, or you can remove files from the list.

Adding a file to the list of files to be absent

o add a file to the list of files to be absent on the target, proceed as follows:

  1. Select the Configuration node in the left window pane and the Files to be Absent tab in the right pane.
  2. Select Edit> Add Filefile_add.png .
    A configuration window appears.
  3. Select the required file from the file hierarchy displayed in the list window.
  4. Click OK to confirm the addition and to close the window.

Run as

The Run as tab defines which login the script is to use and what to do if the login fails. This tab is not available for RPM packages.

Editing the Run as definitions

To modify the definitions of the run as function proceed as follows:

  1. Select any line in the table in the right window pane.
  2. Click Edit > Propertiesproperties.png.
    The Properties pop-up menu appears.
  3. Make the appropriate modifications to the individual values.
    The new definitions will be taken into account immediately.

Mapping

This tab allows you to define specific mappings for files and directories. It is only available if mapping was selected as an option when the package was created.

Mapping a file or a directory to another path

  1. In the Mapping tab select Edit > Map mapping_add.png.
    The Mapping window opens on the screen.
  2. Enter the source and destination paths into the respective text boxes or modify them.
    You can enter the path as a relative or complete path and it is possible to use environment variables as well.
  3. Click OK at the bottom of the window to confirm the mapping or Cancel to stop and close the window.

Dependencies

The tab displays installation and execution information recovered from the RPM package. This information is view only and cannot be modified.

Package installation options 

The Installation Options tab provides information about the execution of the installation of the package on the target(s).

The options provided in this tab depend on which type of installation you selected in the Installation tab. The possible values for most of these options are true and false, true meaning the entry will be applied, false not applied.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Client Management 12.8