Folder Locations Used By Reflection Desktop

  • 7021416
  • 29-Oct-2015
  • 24-Sep-2018

Environment

Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.0 or higher

Situation

Beginning in Reflection Desktop version 16.0, installation folder locations have changed.  This technical note explains the directory locations used for the application program files, user data files, and application data files on Windows systems.

Cause

Folder Locations

Attachmate is now part of Micro Focus, and the product name has changed to Reflection Desktop. Beginning in version 16.0, folder locations have changed to reflect the new names.

For detailed information about the product installation folders, see the Deployment Guide at https://www.attachmate.com/documentation/reflection-desktop-v16/deployment-guide/data/bookinfo.htm.

Program Files

Beginning with Reflection Desktop version 16.0, the default location for new installations has changed. However, if you are upgrading from an existing installation of Reflection 2014 or Reflection 2011 products, your existing installation folder remains unchanged.

Product
Platform
Default Program Files Location
Reflection Desktop (new install)
64-bit Windows
C:\Program Files (x86)\Micro Focus\Reflection
Reflection Desktop (new install)
32-bit Windows
C:\Program Files\Micro Focus\Reflection
Reflection 2014 or 2011 (upgrade)
64-bit Windows
C:\Program Files (x86)\Attachmate\Reflection
Reflection 2014 or 2011 (upgrade)
32-bit Windows
C:\Program Files\Attachmate\Reflection

When installing the product (using either setup.exe or *.msi methods), the administrator can specify a different folder instead of the default.

User Data Folder

Beginning with Reflection Desktop version 16.0, the default user data location for new installations has changed. However, if you are upgrading from an existing installation of Reflection 2014 or Reflection 2011 products, your existing user data folder remains unchanged.

Product
Default User Data Location
Reflection Desktop (new install)
C:\Users\<username>\Documents\Micro Focus\Reflection
Reflection 2014 or 2011 (upgrade)
C:\Users\<username>\Documents\Attachmate\Reflection

When installing the product (using either setup.exe or *.msi methods), the administrator can specify a different folder instead of the default.

AppData Folder

The AppData folder is used for any changes made to Reflection Workspace settings (application.settings), the VBA project file (vbaproject.bin), the Permission Files (*.access), and other global configuration files.

Beginning with Reflection Desktop version 16.0, the default application data location has changed. When upgrading from an existing installation of Reflection 2014 or Reflection 2011 products, the existing AppData folder contents are copied to the new location. The new location is used by Reflection Desktop going forward. The original files remain in the old location as a backup.

Product
AppData Location
Reflection
Desktop 16.1
C:\Users\<username>\AppData\Roaming\Micro Focus\Reflection\Desktop\v16.1
Reflection Desktop 16.0
C:\Users\<username>\AppData\Roaming\Micro Focus\Reflection\Desktop\v16
Reflection 2014
C:\Users\<username>\AppData\RoamingAttachmate\Reflection\Workspace\R2014
Reflection 2011
C:\Users\<username>\AppData\RoamingAttachmate\Reflection\Workspace\R2011

Upgrading from Reflection 14.1 or Earlier

If you are upgrading from an existing installation of Reflection products version 14.1 or earlier to Reflection Desktop 16, the existing user data folder is not recognized or migrated. After upgrading, manually copy user data files as follows:

From (default): C:\Users\<username>\Documents\Attachmate\Reflection (including subfolders .ssh, .pki, and Logs)

To (default): C:\Users\<username>\Documents\Micro Focus\Reflection

Troubleshooting Reflection Desktop Folder Issues

Problems may occur if a customer’s application, user-specific settings files, VBA code, etc. are manually copied from a Reflection 2014 or Reflection 2011 installation to a system with new installation of Reflection Desktop 16.  Files may need to be manually edited so that folder and path information is correct and points to the appropriate product installation folders.

Possible symptoms for this type of situation includes messages such as “File Not Found” when attempting to load custom keyboard maps, mouse maps, themes, QuickPads, hotspots, or ribbon files.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 2831.