Sequencing Reflection 2011 as a Virtual Application with Microsoft Application Virtualization 4.6 (App-V) on Windows 7

  • 7021523
  • 20-Jul-2010
  • 01-Apr-2018

Environment

Reflection for IBM 2011
Reflection for UNIX and OpenVMS 2011
Reflection X 2011
Reflection Standard Suite 2011
Reflection Suite for X 2011

Situation

This technical note includes a recipe to sequence Reflection 2011 so that it can run as a virtual application streamed from a Virtual Application Server or deployed with installer technology using Microsoft Application Virtualization 4.6 (App-V).

Note: Other methods not described in this technical note can be used to successfully sequence and deploy Reflection 2011 as a virtual application.

Resolution

Known Issue with App-V Version 4.6 SP1 Client and Sequencer

There is a known issue with Microsoft's Application Virtualization version 4.6 SP1 and Attachmate's emulation products. If you are running App-V 4.6 SP1, download and apply the hotfix package provided by Microsoft:

App-V 4.6 SP1 Client – http://support.microsoft.com/?kbid=2549352
App-V 4.6 SP1 Sequencer – http://support.microsoft.com/?kbid=2571168

Steps to Create an Application to Run as a Virtual Application

There are three main phases to create an application to run as a virtual application:

Phase I. Document the application's installation requirements for sequencing—determine your sequencing requirements by documenting which Reflection 2011 components and features are installed, the location of installation files, and the location of any configured user data, such as session documents.

Phase II. Sequence the application using the Application Virtualization Sequencer, and then copy the sequenced package files to the Distribution Point or Virtual Application Server.

Phase III. Publish and assign the virtual application package to users.

Phase I. Document a Customized Reflection 2011 Installation Before Sequencing

Before you use the Sequencer Package Configuration Wizard to sequence Reflection 2011, you should document your sequencing requirements and steps. Some Reflection application components may not be needed. To determine your requirements for sequencing, install Reflection on another PC to help identify and document the sequencing steps.

Note the following:

  • The sequencing steps described in this document were performed on 32-bit Windows 7 with .NET Framework 3.5. If Reflection has any service packs, ensure that the service pack installer file, *.msp, is available for installation during the sequencing process.
  • Reflection Productivity Microsoft Office Tools have not been tested to work with Microsoft Office streamed as a virtual application.

Follow these best practices:

  • Always use a clean sequencing PC that has not yet been used for sequencing an application.
  • Install as a User with local administrator rights on the PC used for sequencing.
  • Turn off Windows Defender, Anti-virus software, Automatic Windows Update, and Windows Security Alerts. If User Account Control is used on the client PC, then it should be turned on during the sequencing process.
  • Sequence on the same operating system type, version, and patch level as the App-V Desktop Client systems.

Creating Companion Packages, Permissions Files, and Transforms

Use the Attachmate Customization Tool to create companion packages, to define permissions files, and to create transforms; the basic steps are listed below. Refer to the Install and Deployment Guide as a resource, which is available from the Documentation page: http://support.microfocus.com/manuals/reflection2011.html.

Note: In the section below, the steps for using the Attachmate Customization Tool assume that you have set up a Reflection Administrative Installation. If you do not plan to use an Administrative Install to automate parts of the installation and add user session documents, then proceed to Phase II. Sequence Reflection 2011 Using the Sequencer Package Configuration Wizard.

Create a Companion *.MSI File Using the Attachmate Customization Tool

Use the Attachmate Customization Tool to create a companion .msi file.

  1. Navigate to your Reflection Administrative Installation and run Setup.exe /Admin to launch the Attachmate Customization Tool.
  2. Select "Create a new Companion installer." Click OK.
  3. In the left pane, click "Specify install locations."

Note: It is important to perform steps a and b in order.

    1. Under Installation type, select the "Installs only for the user who installs it" option.
    2. In the Default installation folder drop-down list, select [AppDataFolder].
  1. In the left pane, click Add files to add files to [AppDataFolder]. Click the Add button to add files that you may want to include, such as your pre-configured Reflection session documents (.rd3x, .rd5x, .rdox, .rfw, or .rwsp settings files, for example).
  2. Click File > Save As. Save the companion.msi file in the same location as Setup.exe.

Define Permissions Files

Use the Attachmate Customization Tool to define permissions files.

  1. If the companion file that you created in the previous section is no longer open, open the companion.msi file.
  2. In the left pane, click "Specify install locations" and verify that "Installs only for the user who installs it" is selected. (This option may be dimmed; as long as it is selected, there is no cause for concern.)
  3. In the left pane, click "Modify user settings" to define *.access permission files. For example, you may want to define .rd3x.access to restrict TN3270Basic or TN3270Advanced settings.
    1. Select the Application – Settings to modify and click the Define button.
    2. Select the Group from the Groups drop-down list. You can allow or restrict accessibility for each item listed.
    3. Repeat steps a and b until you have configured the permissions for your environment. Click Next.
    4. Optional: Select Additional security options for Session file encryption.
    5. Click Finish.
  4. Click File > Save and save the companion.msi in the same location as Setup.exe.

Use the Attachmate Customization Tool to Create a Custom Transform File

To prepare Reflection 2011 as a virtual application, you can use the Attachmate Customization Tool to create a custom transform file.

  1. Use the Attachmate Customization Tool to create a new custom.mst transform file by navigating to your Reflection installation and running Setup.exe /Admin.
  2. Select "Create a new Setup customization file for the following product."
  3. In the Welcome pane, under Setup, click "Install location and organization name." In the Default installation folder field, enter a location on Q:\ (for example, Q:\R2011SE).
  4. Under Setup, click "Licensing and session metering." Complete the licensing agreement and accept the Session Metering setting defaults.
  5. Under Setup, click "User interface." Select the "Use this customization with interactive installs using setup.exe" option. Also, verify that the user interface level is Full, the default.
  6. To add a chained companion.msi to your installation, under Setup, click "Add installations and run programs." Add a companion.msi file (using the UNC path) to the installation command. For example:
msiexec.exe /i \\hostname\R2011adminstall\companion.msi

Or, you can install the companion.msi file by clicking it after Reflection 2011 is installed.

  1. Under Setup, click "Modify setup properties." INSTALLDIR_Custom should display with a Value of Q:\R2011SE (step 3 above).
  2. Under Features, click "Set feature installation states." Select the Reflection 2011 features you will install. Since user interface level is set at Full (step 5 above), you should be able to also select or de-select features during installation while in the sequencing process.
  3. Save the custom.mst file in the same location as Setup.exe.

Phase II. Sequence Reflection 2011 Using the Sequencer Package Configuration Wizard

Use the Application Virtualization Sequencer to start the sequencing process.

  1. Create a new Package; click File > New Package and enter a Package Name.
  2. If you select "Show Advanced Monitoring Options," then accept the default 32K Block Size on the next screen.
  3. Click Next; click Begin Monitoring.
  4. Create the primary install directory, for example: Q:\Refl2011, and click OK.

Note: Microsoft recommends that you select a unique 8-character folder name.

  1. Wait for the Virtual Environment to load.
  2. When the "Install the application, and then click Stop Monitoring " option displays above the status bar, navigate to Reflection 2011 and install it by clicking Setup.exe.
  3. On the Install Attachmate Reflection 2011 screen, click Continue.
  4. Read and accept the License Agreement; then click Continue.
  5. Personalize the installation by completing the Full name, Organization, and VPA number fields on the User Information tab.
  6. On the File Location tab, change the File Location by clicking the Browse button. Following the example in this technical note, File Location is specified as Q:\Refl2011.
  7. On the Feature Selection tab, de-select any features not needed so that they will not install. For example, de-select the following:
Utilities\Kerberos Manager
Utilities\Key Agent
Compatibility\IBM Personal Communications
Compatibility\NetManage\RUMBA
Application Programmer Interface
  1. On the Advanced tab verify that "Install to this PC" is enabled. Then click the Install Now button.
  2. When the Installation has completed successfully, click the Close button.
  3. If you have a chained companion .msi package, allow the package to install.
  4. If you have a Reflection 2011 .msp update file, then click the file to install the patch. If there is no .msp update to install, then click Stop Monitoring.
  5. When the virtual environment is downloaded and monitoring is finished, click Next. The Configure Application screen displays.

Working with Microsoft Office Tools Integration

If you are using Microsoft Office Tools Integration features, complete these required steps.

  1. Navigate to C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\1033
  2. Copy VBE6INTL.DLL and paste it into the new location, if it's not already there. For example,
Q:\Refl2011\VFS\CSIDL_PROGRAM_FILES_COMMON\Microsoft Shared\VBA\VBA6\1033

Note: You may have given the <Q:\Refl2011> folder a different name.

  1. To test the Office Integration features, run the Workspace and create a session.

Configure and Launch the Sequenced Applications

Launch the Reflection sequenced application to create the virtualization .osd files, which are used for streaming the application.

  1. Remove any applications that are not needed, but were captured during the sequencing process.

Typical application components to remove include Reflection ‘No Open’ Handler, Reflection IBM Printer, and Macro execution utility.

  1. Click the Add button to add any Reflection 2011 session documents that were installed by the companion .msi file. To find the files, browse to the Q:\Refl2011 \VFS\CSIDL_CCMMON _APPDATA folder.
  2. After adding any session documents, click Next to Launch Applications. (Do not click Launch All.) Then launch Reflection Workspace.
  3. If you need to create any additional session documents, you can use the Create New Document wizard. Save the session in, for example, Q:\Refl2011\VFS\CSIDL_COMMON _APPDATA.
  4. If you create any new Reflection 2011 session documents, you must click the Back button to add them to the application package, as in step 2 above.
  5. Launch and then close each session document to create .osd files that will be used for streaming.

Note: If you launch Reflection Workspace, Reflection FTP client, or any session document, and a Sequencer error displays: “The Sequencer could not stop the MSIServer service,” click OK and try again.

  1. Once you have completed launching the session document applications, you can click Back to remove any applications that will not be published to users. For example, you can remove Reflection Workspace and Reflection FTP Client since users have pre-configured session documents while Reflection is running in the App-V Desktop Client environment.
  2. After all the applications and Reflection Session documents have been launched and closed, click Next to complete the sequencing.
  3. Click Finish when sequencing is completed.
  4. Enter deployment information on the Deployment Tab of the Sequencer, including operating systems.
  5. Create the path location for package contents to be saved.
  6. Click Package > Save.

Note: Instead of using a Virtual Application Server to deploy the application, you could also creat an .msi package when you save Reflection sequenced as a virtual application to run in a standalone environment. Instead of streaming the virtualized application, this method uses .msi installer technology to load and configure virtual applications onto PCs running the App-V Desktop Client.

Phase III. Publish Reflection 2011 with Virtual Application Management Console

Once Reflection has been sequenced and configured for streaming, copy the sequenced package files to the Virtual Application Server content folder, and then prepare Reflection for publishing.

Note: Before publishing Reflection X 2011 or Reflection Suite for X 2011, delete from the virtual file system the .attachmate folder that is generated during the sequencing process.

  1. When moving the package of Reflection 2011 files to the Virtual Application Server content folder, include the following files:
    • Saved session .osd files
    • Reflection .ico icon files
    • Project .sft asset files
    • Manifest XML and .sprj files
  1. Use the Application Virtualization Management Console to create and configure the Reflection Package and Application.
  2. Publish Reflection for users running the Application Virtualization Desktop Client software.

Verify that Reflection 2011 Streams Correctly

From the client computer, double-click the shortcut icon for Reflection 2011. If a Launch Failed dialog box opens, click the box for details, and troubleshoot as appropriate.

For Reflection X 2011 and Reflection Suite for X 2011, configure the following environment variable on each App-V client machine:

SFT_SOFTGRIDSERVER=<App-V Server hostname>)

Accessing APIs

If an emulator is running in a virtual environment, APIs (like COM and HLLAPI) cannot be accessed by client applications that are running on the desktop outside of the virtual environment. Client applications like these that depend on components found in the directory where the emulator is installed will not work unless they are also installed on the server where the emulator software is located.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 2514.