Installing Reflection Products to a Windows Terminal Server

  • 7021751
  • 15-Nov-2001
  • 31-Mar-2018


Reflection for UNIX and OpenVMS version 13.0 through 14.x
Reflection for HP version 13.0 through 14.x
Reflection for ReGIS Graphics version 13.0 through 14.x
Reflection for IBM version 13.0 through 14.x
Reflection X version 13.0 through 14.x
Reflection for Secure IT Windows Client version 7.x
Microsoft Windows 2000 Server with Terminal Services
Microsoft Windows 2003 Server with Terminal Services


This technical note explains how to install and publish Reflection products to a Windows Terminal Server.


Before proceeding, note the following:

  • To evaluate Reflection on your Windows terminal server, obtain an evaluation CD for Reflection, rather than downloading the evaluation software, and install from the CD. The original media may be required during uninstallation of the product. You can obtain a free copy of the evaluation CD from
  • Installation should be completed after normal working hours, when you can easily reboot the Windows server.
  • Obtain and apply the latest Service Pack for Windows server from
  • Be sure you have installed Terminal Services on your Windows server.
  • If you are installing Reflection to one of the multi-user operating systems listed below, see the associated technical note.
KB 7021638—Windows 2000 Terminal Server with Citrix MetaFrame
KB 7021754—Windows Server 2003 with Citrix MetaFrame Presentation Server 4.0

Installing the Executable Files

Before installing Reflection, Attachmate recommends that you close all applications.

Note: If you are installing Reflection from a network location, use a UNC path to access the installation files, not a mapped drive letter.

UNC path syntax: \\<servername>\<path to msi database>

Installing from a mapped drive may generate a Microsoft Windows installation error similar to the following: "Error 2755. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package."

To install the Reflection executable files, follow the steps below:

  1. At your Windows server console, log in as Administrator. From Control Panel, double-click the Add/Remove Programs icon. Click the "Add New Programs" icon, and then click to add a program from "CD or Floppy."
  2. If you are evaluating Reflection:
    1. Browse to and double-click Evaluate.exe on the Reflection Evaluator CD.
    2. To evaluate Reflection X, click PC X-Server Software. To evaluate Reflection for HP, Reflection for UNIX and OpenVMS, Reflection for IBM, or Reflection for ReGIS Graphics, click Windows Based Terminal Emulation. To evaluate Reflection for Secure IT Windows Client, click Secure Shell Technology.
    3. Click "Evaluate Reflection Now," select the product you wish to evaluate, and then click Install.

If you are installing Reflection:

    1. Browse to and double-click Install.exe on the Reflection product CD, and click Next
    2. Click Install Reflection, select the product to install, and then click Workstation Install.

To install Reflection 11.0 or higher, you must have Microsoft Windows Installer version 2.0 or higher on your server. If the Windows Installer service is not found, Reflection alerts you and allows you to install the service.

Note: Reflection 13.0 or higher ships with Microsoft Windows Installer (MSI) 3.x. If you have MSI 2.0 installed, you can optionally upgrade to 3.x during installation.

You must reboot your computer after Windows Installer is installed. After you reboot, restart the Reflection installation program: Browse to the file Install.exe on the Reflection product CD and click Next. (If you are evaluating Reflection, browse to Evaluate.exe.) Click Install Reflection, select the product to install, and then click Workstation Install.

  1. Accept the license agreement.
  2. Accept the default destination folder for Reflection: <Windows server drive>:\Program Files\Attachmate(in version 14.x)\Reflection. If you choose to install it to another drive, make sure the drive is accessible to all of your users.
  3. For installation type, Attachmate recommends "Custom."

Note: The SNA engine was originally designed to run on individual PC workstations. Modifications have been made to enable the SNA engine to function in a Terminal Server environment, but it can handle only a limited number of simultaneous connections (10 or less). For this reason, using Telnet is strongly recommended in the IBM environment.

  1. Accept the default value for user-generated files (such as settings files or scripts):
<Windows server drive>:\Documents and Settings\Administrator\My Documents\Attachmate(in version 14.0 or higher)\Reflection
  1. On the Select Features screen, select the product components you want to install. For each feature, there are usually several subfeatures that may or may not be installed by default. To see which subfeatures will be installed, click the + button to open the tree of a feature box. Clicking the feature box displays the installation options. Note the following:
    • Attachmate recommends that you not install the Virtual Desktop. (Mark this component with an X to avoid installing it.) The Virtual Desktop causes extra network overhead.
    • Choose not to install the Performance Tuner. (In the feature tree, navigate to Reflection > X Window Server > Local X Clients > Performance Tuner. Mark the Performance Tuner component with an X.)

If the Performance Tuner is installed, the first time users run Reflection X they will be prompted to run the Performance Tuner. Attachmate strongly recommends that you not install the Performance Tuner, or that you uninstall it, in the Windows Terminal Server environment. The Performance Tuner offers no value in the Windows Terminal Server environment.

  1. Click Next. Choose the default Reflection folder for shortcut storage, and then click Next.
  2. Click Next when prompted by the message, "Are you ready to start installation?"
  3. Click Finish to exit Setup.

Note: If prompted, reboot to save the registry entries.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 1606.