Skip to content

Deploying Settings

Options for deploying customized settings to end users include:

Install settings in a companion package

Deploy using the Windows Installer. Use the The Installation Customization Tool to deploy your custom settings.

Features

  • Create a companion installer to add templates or definition files to your installation.

  • Create different companion packages for different users or groups in your organization.

  • Configure the companion installer to run automatically with your product installation.

  • Install shortcuts to launch Reflection X using custom command lines.

  • Supported in standalone and domain mode.

  • Create additional companion installers to add new settings and deploy these separately from the product installation.

Requirements and limitations

  • Deploys to Windows systems only.

  • Although you can deploy additional companion packages, you cannot modify settings you have already deployed.

Share settings in a Reflection X domain

Set up a Reflection X domain to support centralized session configuration. See Domain Setup for Centralize Session Configuration.

Features

  • The domain administrator can provide preconfigured, public definitions for users.

  • Updates to centralized definitions are automatically available to users.

  • Users can configure and save personal definitions in addition to using public sessions.

  • Supported on both Windows and Linux systems.

  • By setting up a domain, you can take advantage of other domain services; such as session suspend/resume, and improved performance in high-latency or low bandwidth networks.

Requirements and limitations

  • The domain controller and any required nodes must be installed and configured.

  • Supported in domain mode only. X Manager for Domains must be installed on user workstations.

Install custom templates

Use templates to install default definitions on user workstations. See Deploying Sessions Using a Custom Template.

Features

  • Create custom definitions and export them to definition files (.rxd). Definition files installed to the templates subfolder in the program installation directory are automatically available to users on initial startup.

  • Configure templates to import automatically or provide users with a choice of templates to install the first time they run the application.

  • Supported in standalone and domain mode.

  • Supported on both Windows and Linux systems.

  • On Windows systems, you can use the Installation Customization Tool to create a companion package to install your templates.

Requirements and limitations

  • Template settings are imported only on first run. They cannot be used to update existing settings, and are not available for upgrading users.

Import settings using the command line

Start Reflection X using rxmgr or rxmgrdomains, and use the -import option to specify a definition file to be imported.

Features

  • A definition file with custom settings can be made available from a shared network drive or a web server.

  • Supported in standalone mode (using rxmgr) and domain mode (using rxmgrdomains).

  • Supported on both Windows and Linux systems.

  • Changes to the definition file are imported each time the command line is executed.

Requirements and limitations

  • The administrator must configure and deploy a shortcut or command-line script for end users.

  • Restarting using the import option overrides end-user modifications to imported settings. (The -execOnly option can be used in combination with -import to prevent user edits.)

Distribute settings using Management and Security Server

Configure and launch client connections using the Management and Security Server Administrative Console. See Deploying Sessions with Host Access Management and Security Server.

Features

  • Manage sessions for multiple Reflection products from a single console.

  • Configure sessions that launch X clients directly, without displaying the X Manager window.

  • Provide updated settings to users as needed.

  • Connections go through the Management and Security Server Security Proxy server, which provides SSL/TLS encryption to the proxy. The Security Proxy server can also restrict the visibility of your hosts over the network, which enables you to limit host access to authorized users and members of LDAP groups.

Requirements and limitations

  • You must have Management and Security Server, which is sold and licensed separately from Reflection X.

  • A Management and Security Server proxy server must be configured, clients must connect using Secure Shell, and Reflection PKI Services Manager must be installed and configured to validate the Security Proxy certificate.

  • Administrator and user workstations must be Windows systems, and X Manager (standalone) must be installed on these computers.

  • Users who launch sessions from Management and Security Server can't save X Manager settings.

More information

Back to top