This technical note lists Reflection products and components that can be run in Windows Terminal Server environments (with or without Citrix MetaFrame).
Most of the Reflection products, and some of the Reflection components, have been designed so that they can be installed on and run from a Windows Terminal Server (with or without Citrix MetaFrame).
Note: Windows Terminal Server (with or without Citrix MetaFrame) is abbreviated as WTS in the remainder of this technical note.
No Reflection splash screen is displayed on product startup.
Cursor blink is disabled by default.
Connection time is not displayed by default.
Beginning in version 9.x of Reflection X and Reflection Suite for X, the performance tuner is not run because the product is not installed on the end user's PC.
For additional information about configuring and using Reflection with Windows Terminal Server or Citrix MetaFrame, see Technical Note 1097.
Which Reflection Products and Components Run on WTS?
A Windows Terminal Server enables clients to run Reflection products remotely when logged into the server. The tables below detail which Reflection products and components will run in this environment.
Reflection for the Web is not recommended for, nor is it tested in WTS environments.
Use the following table to determine which Reflection windows-based products can be run in a WTS environment.
Important: All of these products contain components that may or may not be compliant with the WTS environment. The components that are installed on the WTS depend on which features were selected during installation or added after installation. After verifying that your product runs in this environment, make sure to check the table in Reflection Components to determine the status of each additional component you may have installed.
Yes; however, certain components included with this product may not. See Reflection Components.
Yes, with exceptions. This product includes transport types that run in this environment only with restrictions.
The SNA engine was designed to run on individual PC workstations. Modifications have been made to enable the SNA engine to function in a Terminal Server environment, but it can handle only a limited number of simultaneous connections (10 or less). For this reason, using Telnet is strongly recommended in the IBM environment.
Telnet and Telnet Extended do work in this environment.
DLC is a network protocol that is not designed for, and does not work in this environment.
Additionally, certain components included with this product may not work in a WTS environment. See Reflection Components.
Yes; Reflection NFS Client version 11.0 or higher, with some restrictions.
No; All versions of Reflection NFS Client prior to 11.0.
Certain components included with the NFS Client product may also run in this environment. See Reflection Components.
After using the table above to determine if your Reflection product runs in a WTS environment, use the following table to determine the status of any Reflection components you installed during the Reflection product installation process.
No. Reflection LPR/LPD is a network service and does not run in this environment.
Yes. If using the Find Route feature, keep in mind that the ping is being initialized from the WTS, not the client PC.
No. Reflection Timesync is a network service and does not run in this environment.
No. Reflection LAT is a network protocol and does not run in this environment.
No. The Reflection Virtual Desktop adds unnecessary overhead to the WTS or Citrix Server; therefore, this component has not been developed for the WTS environment.
Note: This document is provided for informational purposes only and may be updated if additional information becomes available. The information in this document does not constitute a warranty by Attachmate or extend the terms of any existing warranty. Warranties for Attachmate products, if any, are set forth in the end-user license agreements that accompany the products or the terms of the license agreement under which you make use of an Attachmate product.
This document was originally published as Attachmate Technical Note 1626.