You can use the Attachmate Customization Tool to create a Microsoft transform file (MST file) to modify the installation of Reflection when you deploy it to users.

Audio Transcript:

0:05 - 0:10 You can use the customization tool to create a Microsoft transform that changes how Reflection is installed. 0:13 - 0:19 The tool provides options for a number of customizations. Among other things, you can specify the installation directory or modify which features are installed. 0:26 - 0:30 You could also chain the install to run other MSIs. After you create a transform, you can deploy it with a base installation package. 0:30 - 0:36 We'll create a transform that adds a feature to our install then starts an MSI for another application after the primary install runs. 0:44 - 0:54 To create a transform, you'll need an administrative installation point that you can install from and a workstation that has Reflection installed on it. 0:54 - 1:03 And it's a good idea to create a desktop shortcut on your workstation that opens the customization tool on the server. 1:03 - 1:05 We'll use a desktop shortcut that we created earlier to open the customization tool. 1:09 - 1:15 When the tool opens, we'll select to create a new customization file. 1:15 - 1:23 Before we do anything else, we need to accept the license terms on behalf of users. 1:24 - 1:27 Now we need to select whether we want to use this transform with the MSI command line or with the setup tool. 1:31 - 1:34 If you're using a command line install or a deployment tool... 1:34 - 1:38 You'll need to add the transform to the command line. 1:38 - 1:44 If you're using the setup tool, the transform is automatically added for you. 1:44 - 1:49 Now we need to chain the installation to add the MSI for our other application. 1:49 - 1:56 To do this, we just browse to the file we want to run on the administrative installation point. 1:58 - 2:04 Now let's say we need to deploy to users who need to use macros developed on the Extra! product. 2:05 - 2:15 To support these macros, we need to add the legacy Extra! compatibility feature to the install. 2:18 - 2:23 Now we'll save the transform on the administrative installation point. 2:23 - 2:26 When we deploy this transform with a primary MSI... 2:26 - 2:33 the legacy Extra! compatibility feature is installed along with the default features... 2:33 - 2:36 and the MSI that we chained in our transform runs after the primary install. 2:39 - 2:47 for more about transforms, see the Reflection Deployment Guide.