Package Configuration Files
Create a companion installer package (also called a "companion database") to install any custom files you created when you customized Reflection. A companion installer package is a standalone MSI file that is independent of any Reflection installer package.
You can deploy companion installer packages separately or you can add them to a customized installation, so that the companion installer packages are automatically installed when the Reflection installer package completes.
You can also create and install packages at any time after the initial installation. Because companion installer packages are installed independently of Reflection, you can upgrade the product without removing these support files and you can deploy additional support files without re-installing the product.
If you support several business units that require their own customized configuration files, you can create a companion installer package for each business unit.
Companion installer packages have no built-in user interface except a standard progress bar. They are displayed as independent entries in the Windows Add\Remove Programs list and can be installed or uninstalled independently of Reflection.
If you use centralized management, you can also use Use Central Management to Deploy MSI Packages.
|Package Sessions and Custom Settings Files
|How to bundle configuration files into Microsoft MSI files that you can deploy using standard Windows deployment tools.
|Create and Automatically Package Workspace and Access file Settings
|How you can use the Installation Customization Tool to create and automatically package workspace settings that customize the Reflection workspace and .access files that lock down Reflection.
|Walkthrough to Create a Package with the Installation Customization Tool
|An example that shows how to create and deploy a companion installer package to install a keyboard map file and a session document file.
|Customized Files that Must be Deployed to Specific Locations
|Directory locations for custom configuration files that you create when you customize Reflection sessions or other settings. Reflection cannot find these files unless they are in these specific locations.
|Other Customized Files and Supported Files from Other Products
|Customized files that Reflection doesnRSQUOt look for in the user data directory, other supported files that you would most likely not deploy, and files that can be imported from Extra!, legacy Reflection, and other products.