Deployment Options for Reflection 14.x

  • 7021653
  • 20-Sep-2002
  • 01-Apr-2018


Reflection for HP version 14.x
Reflection for IBM version 14.x
Reflection for UNIX and OpenVMS version 14.x
Reflection X version 14.x
Reflection Suite for X version 14.x


Reflection supports several methods for deploying Reflection to users. This technical note describes how to perform a simple Reflection deployment and lists resources you can refer to for more information about other deployment options.


Deployment Options

There are many ways you can deploy Reflection to your users—with or without customizations, from a file or a web server, and using a variety of deployment software packages. The following lists a few of the common ways Reflection is deployed in work environments:

  • Simple Reflection Deployment (No customizations or added files)
  • Custom Reflection Deployment
  • Reflection Web Server Deployment

The following section lists the steps to follow to perform a simple Reflection deployment without customizations. To customize your deployment, see the Preparing to Deploy Reflection Guide 14.1, (The Reflection 14.0 Deployment Guide is available from The topics covered in the guide are listed below. For information about deploying Reflection from a web server, see the product help.

Simple Reflection Deployment

If you do not want to customize the Reflection installation or to make additional files available to your users, installing and deploying Reflection to your users is a simple two-step process. First, you must perform an administrative installation to a file server, then have users install Reflection by pointing them to the Setup.exe file on the network installation point.

Follow these steps to perform an administrative installation:

  1. On the product CD, double-click Install.exe.
  2. Click Install Reflection.
  3. Select the product to install, and then click Administrative Install.
  4. Enter the Network installation point and complete the installation.

Once you have completed the administrative installation, have users install Reflection to their machines by pointing them to the Setup.exe file located in the administrative install folder on the file server. Or you can install Reflection by using any deployment method that is compatible with standard Windows installer packages, such as Active Directory or SMS.

Custom Reflection Deployment

If you want to customize the Reflection installation or make additional files (such as settings files, client files, text files, or document files) available to your users, see the Preparing to Deploy Reflection Guide,, for detailed instructions. The topics covered in the deployment guide are listed below:

Overview of the Installation and Deployment Process

Phase 1—Preparation

Install Reflection to the administrator's workstation
Install the Reflection Administrator's Toolkit
Create new settings or client files
Preset Reflection FTP settings for export
Locate existing settings files
Prepare for installation access

Phase 2—Customization

Open the installation (Reflection Installer Package)
Set installation options
Edit product shortcuts
Add files to the installation
Define profiles and default settings for Reflection
Profile Reflection
Export FTP settings
Set client metering options
Make additional files available for your users
About Companion Packages
Create a companion package for added files
Add files to a companion package
Install a companion package
View customization details

Phase 3—Deployment

Create a deployment shortcut
Deploy silently, without user intervention
Assign and publish with Active Directory
Other deployment methods

Reflection Web Server Deployment

For information about deploying Reflection from a web server, see the product help.

Important Security Note:

If installing Reflection from a web server, firewalls, proxy servers and settings, and external access to your site are issues that can both prevent installation of Reflection to the end user and/or permit an unauthorized user to gain access to the product and your site. For more information see Microsoft Knowledge Base Article 328748.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 1686.