Using Windows Installer, you have the ability to select
exactly which BlueZone components to install. This is accomplished
by using the ADDLOCAL command line switch to control
which BlueZone components get installed.
In order to use the ADDLOCAL feature,
you must know the names of the individual BlueZone components so that
you can include them in the Windows Installer command line. To keep
things as simple as possible, the BlueZone component names use the
same names as their CAB file names.
Refer to Editing the distribution image contents for a complete list of the BlueZone
CAB files.
The following example uses a fictitious company with
the following requirements:
Company XYZ has users who require
the following BlueZone components:
- BlueZone Session Manager
- BlueZone Mainframe Display
- BlueZone Mainframe Printer
- BlueZone VT
- BlueZone Secure FTP
However, company XYZ has no users that require all of
the above BlueZone components.
Table 1 lists company XYZ user groups and
the BlueZone components that they require.
Table 1: Sample user groups and required components
| User group |
Component(s) |
| 1 |
BlueZone Mainframe Display |
| 2 |
BlueZone Session Manager
BlueZone
Mainframe Display
BlueZone Mainframe Printer
BlueZone
Secure FTP |
| 3 |
BlueZone VT |
| 4 |
BlueZone Session Manager
BlueZone
VT
BlueZone Secure FTP |
Step 1: Creating a BlueZone distribution image
The
first step is to create a BlueZone distribution image. It is recommended
that you create one BlueZone distribution image that works with all
of the above situations. In other words, your BlueZone distribution
image contains all of the CAB files necessary to install all four
groups. The advantage to this is that you only have to manage one
BlueZone distribution image and in addition, in the future, if any
of company XYZ's users want to add a BlueZone component to their installation,
this can be accomplished without having to uninstall and reinstall
BlueZone.
Note: You may even want to include additional CAB files
for components that are not being installed now, but you may want
to install in the future, like the BlueZone Mainframe Printer CAB
and the BlueZone Scripting CAB. The advantage to this is that you
do not have to uninstall BlueZone in order to install the new component.
Add
any necessary BlueZone configuration profiles or desktop shortcut
files to this image. Refer to Creating a distribution image for more
information.
Step 2: Creating a command line for each group
To install BlueZone, use standard Windows Installer command line syntax using the
ADDLOCAL feature to install the individual BlueZone Components.
ADDLOCAL is standard Windows Installer syntax. You must know the names of the
individual BlueZone components. They are the same names as the CAB file names.
Note: To run an
MSIEXEC command, you must open the DOS window as an Administrator.
Table 2: Installation command line syntax
| User group |
Command line syntax |
| 1 |
C:\>MSIEXEC /i "BlueZone.msi" ADDLOCAL=bzmdp,common,common2
/qb |
| 2 |
C:\>MSIEXEC /i "BlueZone.msi" ADDLOCAL=bzsm,bzmdp,bzmp,bzftp,common,common2
/qb |
| 3 |
C:\>MSIEXEC /i "BlueZone.msi" ADDLOCAL=bzvt,common,common2
/qb |
| 4 |
C:\>MSIEXEC /i "BlueZone.msi" ADDLOCAL=bzsm,bzvt,bzftp,common,common2
/qb |
Note: You must include the common.cab and common2.cab files
in all cases. Also, these examples assume that the DOS prompt is
already in the same folder as the BlueZone.msi file.
Otherwise, you must include the path to the BlueZone.msi file.
For example, C:\>MSIEXEC /i "C:\Program Files\BlueZone\6.1\BlueZone.msi"
Tip: To execute a Windows Installer command line, one option
is to type the Windows Installer command line at the DOS prompt.
Another option is to place each of the above Windows Installer command
lines into a separate text file that ends in .BAT.
Give each file a name like UserGroup1.bat.
Batch files can be executed from Windows explorer by double-clicking
the file.