Administrator QuickStart for Upgrading from Extra! to Reflection

This guide includes key issues for system administrators to consider when you are preparing to deploy Reflection Desktop to an Extra! install base.

  • What’s Similar? describes similar features and capabilities of Reflection and Extra!. The process for customizing sessions is similar and many of the custom files you created in Extra! can be imported into Reflection. You can also run and edit Extra! macros.

  • What’s Changed compares the new Reflection tools and processes with those of Extra! This includes packaging and deploying with the Reflection Installation and Customization Tool, locking down and changing the interface with Reflection’s Permissions Manager tool, and using compound session document files that include many of your settings in a single file.

  • What’s New? shows new capabilities of Reflection including flexibility in setting application (workspace) settings, new security features, and installer improvements. It also highlights other features, including the ability to decorate the screen with controls, map actions to events, and create Visual Basic for Applications (VBA) and Express Macro Language (EML) macros.

  • Best Practices lists some things to check to make sure you avoid common problems and mistakes when you deploy Reflection.

For other information about upgrading from Extra! to Reflection Desktop, see the following documents and videos:

1.0 What’s Similar?

Micro Focus has put forth a lot of effort to make it easier for you to upgrade to Extra!

  • Reflection uses many of the same types of settings as Extra! and you’ll find that many of the settings you configured for Extra! can be easily imported into Reflection, including session files, Hotspots, QuickPads, and keyboard maps.

  • You can heavily customize Reflection, just as you can with Extra!. Although the terminology for settings is a little different, you can configure most of the same types of custom settings you set in the Extra! Settings window in the Reflection Settings window.

  • You can use Reflection group policy templates to lock down Reflection, similar to how you use templates to lock down Extra!.

  • You can run and edit Extra! macros, although more modern languages and APIs are available, including: the Reflection Microsoft Visual Basic for Applications API, a .NET API, and the Express Macro Language.

  • You can deploy Reflection using group policy, MSI commands or deployment tools.

  • Although Reflection is configured by default to use a modern ribbon interface, you can configure it to use an alternate interface that is similar to Extra! to ease adoption for your users.

  • Some of the settings in the Extra! Global Preferences dialog box are available in the Reflection Workspace settings.

2.0 What’s Changed?

Reflection provides comparable tools with additional and enhanced capabilities:

  • The Installation Customization Tool is used to modify the install and package files. This tool replaces the Custom Installation Wizard (CIW).

  • Permissions Manager is used to lock down access to settings and controls. This tool provides many benefits over the Extra! Security Editor.

  • Compound Session Documents allow you to save many of your custom settings (such as keyboard maps) in a Reflection session file.

2.1 The Installation Customization Tool

Instead of the Installation Customization Wizard, Reflection provides the Installation Customization Tool that you can use to package your customized files in companion MSI files or to create transforms that you deploy with the Reflection MSI.

For your production deployment, you’ll need to install this tool on an administrative installation point on a server and then run it from your workstation.

For more information about setting up and using the Installation Customization Tool, see:

Setting up the Reflection Administration Tools

Package Configuration Files

Modify the Installation

2.2 Permissions Manager

Instead of using the Security Editor to remove controls or settings you don’t want to be available to users, you’ll use the Reflection Permissions Manager administrative tool or Microsoft Group Policy to restrict access to these controls. These methods allow Reflection to leverage the Microsoft User Access Control (UAC) to restrict access to the interface.

Restricting access through the UAC offers significant advantages over simply removing the controls that improve your ability to manage the product after it is deployed. If you need to change a setting for a user, you can make the change without deploying (or redeploying) any files.

For example, in the settings dialog box shown below, the User interface mode setting is restricted.

A shield is displayed, indicating this dialog box contains restricted controls and the restricted control is grayed out.

NOTE:Restricted controls are grayed out or disabled for all Reflection interfaces. In the Reflection ribbon interface and on Reflection dialog boxes, a shield indicates controls are restricted.

If a user selects Change the currently disabled settings, the User Account Control dialog box is displayed.

The user must contact an administrator (such as a Help desk administrator) and ask them to change the setting. The administrator can then enter their credentials and change the setting without logging on to the machine. After the setting is changed, the control remains restricted.

If you want to completely remove controls from the interface, use the UI Designer to modify the Toolbars or menus as shown in QuickStart for Extra! Users who are setting up Sessions in Reflection (for Classic interface mode) or Customize the Ribbon.

Permissions Manager (accessconfig.exe) and Reflection Group Policy templates are installed in the Reflection installation directory. Permissions Manager settings are saved as .access files and can be packaged and deployed to users in MSI files created with the Installation Customization Tool.

For more information, see:

Control Access to Settings and Controls

Control Access to Settings and Controls with Reflection Administration Tools

Control Access to Settings and Controls with Microsoft Group Policy

2.3 Compound Session Documents

You can set up and customize session files that use custom keyboard maps, controls, themes, and other settings. To customize these settings, see Create and Customize Session Documents.

You can save these session settings as compound session files or standard session document files (the default).

Compound Session Document files include all of the customized settings for Quick-pads, keyboard maps, themes, mouse maps, Hotspots, and ribbons. These files allow you to deploy your sessions without having to deploy dependent files for these settings.

Session Document files save these settings in separate files. If you save sessions using this default, you’ll need to make sure that you deploy the custom files to the correct locations as shown in Customized Files and Where to Deploy Them in the Deployment Guide.

Compound files are easier to deploy because you don’t have to deploy the supporting files. This can be especially useful when deploying to a centralized environment, such as a Citrix server. Regular session files offer more flexibility for sharing common configurations. For example, you can share one keyboard map file in several regular session files. With compound session documents, you have to recreate the custom settings in each file.

3.0 What’s New?

You'll find many new features in Reflection Desktop. These features combine the best emulation features of Reflection and Extra! into a single solution, optimized for Microsoft Windows 7, Windows 10, and Microsoft Office.

  • Installation Improvements include the advantages of using the Reflection.setup program and the Reflection Installation Customization tool.

  • Workspace Settings allow you to set many global application settings that are not available in Extra!.

  • The Trust Center is used to protect sensitive data (such as credit cards), specify secure locations for opening files, and control programmatic access to Reflection.

  • User Interface Options include a number of alternate interfaces. The most commonly used interfaces can be heavily customized.

  • Other Features include features for customization and automation that are not available in Extra!.

3.1 Installation Improvements

The Reflection Setup program (setup.exe) is the recommended tool for installing and deploying Reflection. This tool uses the primary Reflection MSI file to install Reflection but it also installs prerequisite software (if needed) and has several other features that provide a smoother deployment than installing directly with the primary Reflection MSI file. When the Setup Program installs Reflection, it determines whether each workstation has the required .NET Framework and Microsoft Windows Installer version and automatically installs them if necessary. It also automatically uses the correct language for the installation and removes previous versions of Reflection. (This is required to install the new version.) If the Visual Basic feature is selected, it also installs the Visual Basic core MSI, along with the appropriate Visual Basic language MSI.

The Reflection Installation Customization Tool allows you to customize settings that apply to the application and automatically sets the correct location for these files in the MSI.

3.2 Workspace Settings

Global settings that apply to the Reflection application are configured in Reflection Workspace Settings. Most of these Workspace settings are not available in Extra!.

Workspace configuration settings affect all terminal session and Web page documents opened in Reflection. These settings include security, user interface options, file locations, and other settings related to Reflection.

Configure Workspace Defaults

Configure the actions to perform when the Reflection workspace opens (such as startup macros) or closes and preferences for automatically saving session document files.

Configure Workspace Attributes

Configure options for logging, running remote sessions, and displaying Help. You can also specify the user data directory, in which session documents and other related files are saved.

Configure User Interface

Configure which type of user interface to use (Reflection provides a number of alternate interfaces), its look and feel, and other user interface options.

Configure Centralized Management

Set up the workspace to access sessions from a centralized management server.

Configure Usage Data

Choose whether to participate in the Product Experience Improvement program.

Workspace settings are saved in the Application.Settings file or the Frame.Settings file in your AppData directory.

3.3 The Trust Center

Use the Trust Center to protect your working environment from information theft, and your data from potential damage caused by opening documents from non-trusted sources. The trust center is a reflection Desktop feature that is not available in Extra!.

The Trust Center includes three types of global security settings.

Specify Trusted Locations

Set up trusted locations (directories that are designated as secure sources for opening files). By default, Reflection allows you to open documents only in directories that are specified as trusted locations in the Reflection settings.

Set Up Information Privacy

Configure Information Privacy features to protect sensitive data so that it is not displayed on the screen or in productivity features, such as Screen History.

Set Up API and Macro Security

Enable the Reflection .NET API, and specify corresponding settings.

Trusted Locations

A trusted location is a directory that is designated as a secure source for opening files. By default, Reflection Desktop allows users to open documents only in directories specified as trusted locations in the Reflection settings.

NOTE: Reflection Desktop specifies three trusted locations in the workspace Application.settings file in the program directory. If you want users to be able to open or save documents in a location other than one of these default directories, you’ll need to configure and deploy the trusted location settings.

When you add other locations, these locations are saved in a custom Application.settings file in the user data directory folder. If you add trusted locations, you will need to deploy this file.

For more information, see Add Trusted Locations

Information Privacy

In Extra!, you can set privacy filters to mask patterns of data, such as Social Security numbers or phone numbers.

Reflection expands this capability to automatically recognize and redact credit card numbers as they are entered on the screen and allows you to use regular expressions for advanced pattern recognition.

Reflection Information Privacy settings are global and are configured in the Information Privacy dialog box.

API and Macro Security

If you plan to use Extra! macros, make sure that Extra! is selected in the Set up API and Macro Security dialog box.

See Configure API and Macro Security

3.4 User Interface Options

The Ribbon is the default interface for Reflection but you can configure Reflection to use the Classic interface, which is very similar to Extra!.

NOTE:Reflection provides a number of alternate interfaces: the Ribbon is the modern interface used for many Windows products, Classic is similar to Extra!, Classic MDI, Browser, and TouchUx for mobile look and feel.

Reflection’s UI Designer allows you to heavily customize the interfaces used for the Ribbon, Classic, and Classic MDI modes.

3.5 Other Features

You'll find many new features in Reflection Desktop that combine the best emulation features of Reflection and EXTRA! into a single solution, optimized for Microsoft Windows 7, Windows 8.1, Windows 10, and Microsoft Office.

You can customize sessions to set up custom controls for your program screens, configure Reflection to initiate actions when events occur in a session, choose from several user interfaces to address different preferences and needs, and configure many other new settings to improve the user experience.

Using the Reflection object-oriented API model, you can add functionality to terminal sessions and Web pages using .NET, Visual Basic for Applications (VBA), or HLLAPI programming. You can also use the Express Macro Language to develop macros that can be used in multiple Micro Focus products.

4.0 Best Practices

  • Set up Trusted Locations. The Trusted Locations feature provides a way to differentiate safe files from potentially harmful files. When a file is in a trusted location, it’s files are assumed to be safe. Reflection enforces trusted locations by default, so if you want to save sessions in directories that are not default trusted locations, you’ll have to define these directories or disable trusted locations. See Add Trusted Locations in the Reflection Deployment Guide.

  • If you plan to run legacy Extra! macros, set up API and Macro Security to use Extra! for the Legacy API preference.

  • Make sure that the Legacy Extra! compatibility feature is selected in the installer.

  • If you deploy to custom user data or machine data folders, make sure that you test your settings with a user account instead of just your administrator account.

  • Determine whether to set up Reflection with a Classic user interface that is very similar to Extra! or with a more modern Ribbon interface (the default). (Reflection provides optional interfaces designed to meet different needs and preferences.)

  • If you are deploying to Citrix or another centralized environment, consider saving sessions and related files in compound session document files.

  • Follow Best Practices for Planning a Reflection Deployment

  • Follow additional Best practices for Deploying Reflection

6.0 Legal Notices

Copyright © 2017 Attachmate Corporation, a Micro Focus company. All RightsReserved. Micro Focus, the Micro Focus symbol, Extra!, and Reflection are registeredtrademarks of Micro Focus in the USA. All other trademarks, trade names, orcompany names referenced herein are used for identification only and are theproperty of their respective owners.