Sequencing Reflection 14.x as a Virtual Application with Microsoft Application Virtualization 4.5 (App-V)

This technical note describes one way to sequence Reflection 14.x 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.5 (App-V).

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

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 a Customized Reflection 14.x Installation Before Sequencing

Before you use the Sequencer Package Configuration Wizard to sequence Reflection 14.x, 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 sequencing steps described in this document were performed on 32-bit Windows Vista SP2 with .NET Framework 3.5 SP1. If Reflection 14.x has any service packs, ensure that the service pack installer file, .MSP, is available for installation during the sequencing process.

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 Reflection Administrator's Toolkit to create companion packages, to define permissions files, and to create transforms. Refer to KB 7021653, Deployment Options for Reflection 12.0 through 14.x, as a resource.

Phase II. Sequence Reflection 14.x 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:\WIX14.001, and click OK.
5. Wait for the Virtual Environment to load.
6. When "Please begin installation" displays above the status bar, navigate to Reflection 14.x and install it by clicking Setup.exe.
7. On the Attachmate Reflection Welcome screen, click Next.
8. Read and accept the License Agreement; then click Next.
9. Personalize the installation by completing the Full name, Organization, and VPA number fields. Click Next.
10. On the Destination Folder screen, change the Destination folder by clicking the Browse button. Following the example in this technical note, it is specified as Q:\WIX14.001.

11. If you chose Custom, on the Select Features screen, de-select any features not needed so that they will not install. For example, de-select the following:

12. On the Start Installation screen, click Next.
13. When the Installation has completed successfully, click Finish.
14. If you have a chained companion *.msi package, allow the package to install.

15. When the virtual environment is downloaded and monitoring is finished, click Next.
16. Click Next on Additional Files to Map to Virtual File System (VFS).

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.

2. Click the Add button to add any Reflection 14.x files that were installed by the companion file. Click Next.
3. After adding any additional files, click Next to Launch Applications. (Do not click Launch All.) Then launch Reflection.
4. Click Finish when sequencing is completed.
5. Enter deployment information on the Deployment Tab of the Sequencer. For example, change the protocol to RTSP and enter your host name.
6. Click File > Save.

Note: Instead of using a Virtual Application Server to deploy the application, you could also create an .MSI package when you save Reflection 14.x sequenced as a virtual application. 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 14.x 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.

1. When moving the package of Reflection 14.x 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

2. Use the Virtual Management Console to create and configure the Reflection 14.x Package and Application.
3. Publish Reflection 14.x for users running the Application Virtualization Desktop Client software.

Verify that Reflection 14.x Streams Correctly

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

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.

Legacy KB ID