This technical note describes how to upgrade an installation of Reflection on multiple Windows Terminal Servers to a higher version.
The following method to upgrade Reflection products can be used in these environments:
As shown in the graphic below, upgrading Reflection on multiple Windows Terminal Servers requires creating an administrative installation. Install the administrative installation to a secure network share point and then use it to deploy workstation installations to your Windows Terminal Servers.
Caution: Do not put the administrative installation on one of your Windows Terminal Servers. Administrative installations and workstation installations must be located on separate machines.
Follow the steps in the sections below to upgrade Reflection on multiple Windows Terminal Servers.
Note: For information about how to deploy Reflection to multiple Windows Terminal Servers, see Technical Note 1558.
From the administrator's workstation, perform an administrative installation of the new Reflection version to a new network share point. Do not install Reflection to the same administrative installation point used for an earlier Reflection installation. For details about upgrading an administrative installation, see Technical 1693. Note the following:
Error 2744. EXE failed called by custom action
you are performing an Administrative installation to a network share point that is not part of your domain or not a trusted domain. Repeat the Administrative installation, but make sure the network share point is on your same domain or a trusted domain.
Perform a workstation installation of the new Reflection version on the administrator's workstation. For Reflection 11.0 or higher, run the installation again and install the Reflection Administrator's Toolkit to the administrator's workstation.
Launch the Install.exe file on the Reflection CD. Click Install Reflection, select Reflection Administrator's Toolkit from the list of products to install, and then click Workstation Install. Follow the instructions in the Wizard to complete the installation.
Run the Install.exe file again to install any Reflection products that require profiling.
You can specify the installation locations for the Reflection product, the end user's folder for their Reflection-generated files, the Start menu location for Reflection, and choose features and properties by setting the installation options in the Customization Manager.
Note: You must redo any product profiling done for an earlier installation. If you do not re-profile the products, the profiling will be lost when upgrading. However, if you install a non-profiled upgrade, the previous profiling will be retained.
To launch Reflection Customization (or Deployment) Manager, use the Windows Start menu shortcut shown below that corresponds to your new version of Reflection.
Reflection 14.x: Start > Programs > Attachmate Reflection > Administrative Tools > Customization Manager
Reflection 11.x 13.x: Start > Programs > Reflection > Administrative Tools > Customization (or Deployment) Manager
For more information about Reflection Customization Manager and installing Reflection onto Windows Terminal Servers, note the following resources:
The Reflection 14.0 Deployment Guide is available from http://docs.attachmate.com/reflection/14.0/deploy.pdf.
If you are using Citrix Presentation Server 4, you can use the Installation Manager tool to deploy packages to the farm.
Or, you may follow the steps below to upgrade the workstation installations on the Windows Terminal Servers.
Note the following:
change user /install
<J:>\<Admininstall>\setup.exe /i <J:>\<Admininstall>\<Package name.msi> TRANSFORMS="<J:>\<AdminInstall>\<Citrix2000.mst>" /qb
change user /execute
In this example,
<J:> is your drive mapping.
<Admininstall> is the location of your Administrative installation on the new network share point.
<Package name.msi> is the name of your .MSI file. (In 10.0 or higher, the name of the .MSI file varies depending on the product, for example, Mp130ilc.msi or Sx140ilc.msi.)
<Citrix2000.mst> is the name of your transform created in "Step 3: Record a Reflection Installation."
Note the following:
If you have Citrix MetaFrame: Use the Published Application Manager (MetaFrame 1.8) or the Citrix Management Console (MetaFrame XP) to publish the batch file created in step 1 to all of the Windows Terminal Servers. Note: Make sure that the batch file is published only to Administrators.
If you do not have Citrix MetaFrame: Distribute the batch file to each Windows Terminal Server by some other means.