Best practices for Administrators when deploying Reflection Desktop host session files

  • 7023390
  • 27-Sep-2018
  • 23-Oct-2018

Environment

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

Situation

This article outlines a few suggestions and some best practices for Administrators to use when deploying Reflection Desktop host session files to end-users.

Resolution

1. Save Host session information in Compound documents by using Reflection Desktop 16.0 and higher.
Host connection and configuration information, along with Keyboard Maps, Mouse Maps, Custom UI, Hotspot Maps, Quickpads, and Theme information can all be stored in one host session file (RD3X, RD5X, RDOX) keeping all related and interconnected session information in one location.  This makes for ease of deployment and prevents error messages from appearing due to a component being missing.


2. Don’t save Host session files automatically.
Set Reflection Desktop to discard the users changed settings to prevent the users from automatically saving changes they have made to their configuration.  When using shared host session files for multiple users, preventing changes to the host session is important to present a common user-experience each time the connection to the host is made.


3. Deploy Host session files as Read Only.
Lock down the users configuration by making the Host session files Read Only.  This prevents users from permanently saving changes they might have made while running a host session and thus when using shared host session files across multiple users, will provide a common user-experience each time the connection to the host is made.

4. Deploy *.access files to lock down features of Reflection Desktop.
Access files can be used to prevent users from accessing features of the Reflection software that they should not be using.


5. Deploy shortcuts on the end-users desktop to load the host sessions via a command line.
To make it easy and quick for users to launch their host session(s), Windows shortcuts can be added to the users desktop.


6. Deploy common session files.
There are a number of ways to deploy common host session files to be shared among multiple users or for a single user.

    a. Use the Installation Customization Tool (ICT) and deploy Companion Install files.
        The ICT can be used to create Companion Install files that contain customized configurations such as application.settings, frame.settings, Host sessions, and Access files.


    b. Manually store files on network server or other shared location.
        Store Host session files in a common location for ease of update and access by the users and the administrators.

7. See additional suggestions under "Best Practices" in the "Getting Started with Reflection Desktop Deployment" at: