Create a Companion Install Package
Create a companion install package (also called a "companion database") to install any files that are not installed with Reflection.
Note: Files that are opened by Reflection, such as settings files, must be installed in trusted locations. Before you add these files to the companion database, make sure you know which folders on user workstations are designated as trusted locations.
To create a companion install package
- On a workstation on which you have installed Reflection, open the Attachmate Customization Tool from a desktop shortcut or from a command line as follows:
path_to_setup\setup.exe /admin
- From the Select Customization dialog box, select Create a new Companion installer (or open an existing MSI), and then click OK.
- From the navigation pane, select Specify package information.
- In the Add/Remove name box and the Organization name box, type a name for the installation and the publisher that you want to be displayed in the Microsoft Windows "Uninstall or change a program" panel.
Note: The Windows Vista and Windows 7 Uninstall or change a program list is similar to the Windows Add or Remove Programs List for previous versions of Windows. It is accessed by selecting Programs and Features from the Control Panel.
- From the navigation pane, select Specify install locations.
- Under Installation type, select whether to install the files for all users or for only one user:
Select
|
To set up the companion installer package to
|
Installs to all users of a machine
|
Make files available for every user who logs onto the computer.
Use this option for settings files, macros, and other configuration files that you want to be available to all users.
|
Installs only for the user who installs it
|
Make files available only for the user who installs it.
Important! If you are deploying files that must be installed in the user’s personal data folders, you must select this option.
|
- In the Default installation folder list, select the folder in which to install the files. (Files are deployed to this folder unless you specify another folder when you add a file.)
Note: The folders available in this list depend on which Installation type you chose. Installation Type folder options specify the access for the files (after the installation). These options affect only the folders to which you can install — you cannot change these options after you add a file.
- In the Default shortcut folder list, select the folder in which to install program shortcuts. (Shortcuts are deployed to this folder unless you specify another folder when you add a file.)
Note: List items that refer to folders (for example, [ProgramMenuFolder]) are pre-defined folder keywords. You can create customized directories by adding new folder names with typical directory syntax (such as, [ProgramFilesFolder]\My Folder). Alternatively, you can enter a fully qualified path (for example, C:\Program Files\My Folder), as long as that location is known to exist on the target machine.
- From the navigation pane, select Add files and then click Add and browse to the files you want to include.
- Specify the destination directory for each file as follows:
- In the table of files that you added, select the file.
- In the Add files to list (at the bottom of the panel), enter the destination directory. (You can choose a location from the list or edit the path by typing.)
- Click Update. (The destination directory for the file is displayed in the table’s Location column.)
- (Optional) To create a shortcut for the file, select Include shortcut.
- When you have finished creating your companion installer package, choose File > Save. (If Save is grayed out, click Exit and you will be prompted to save the file.)
- The companion file can now be deployed by itself or with Reflection (by chaining the installation).
- To deploy the companion file independently, enter the following command:
msiexec –i path_to_administrative_installation_point\ myConfigFiles.msi
- To deploy the companion file with your main installation, see Add a Companion Installer to your Installation.
Note: The package remains on the end user's computer until it is removed with the Microsoft Uninstall or change a program utility (or Add/Remove Programs for Windows XP.)
|