HP Remote Graphics Software 6.
© Copyright 2013-2014 Hewlett-Packard Development Company, L.P. Microsoft, Windows, and Windows Vista are U.S. registered trademarks of the Microsoft group of companies. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Acknowledgments HP Remote Graphics Software was developed using several third party products including, but not limited to: OpenSSL: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software written by Tim Hudson (tjh@cryptsoft.com). This product includes cryptographic software written by Eric Young (eay@cryptsoft.
iv Acknowledgments
Table of contents 1 Getting started in Windows ............................................................................................................................... 1 Installation ............................................................................................................................................ 1 Creating a connection .......................................................................................................................... 2 User interface controls ........
Command line options ...................................................................... 19 RGS Sender installation log file on Windows .................................................... 20 Uninstalling the RGS Sender on Windows ........................................................ 20 Installing RGS on Linux ...................................................................................................................... 20 Installing the RGS Receiver on Linux ...................................
Effect of low bandwidth and/or high latency networks on collaboration ............................. 48 Multi-monitor configurations ............................................................................................................... 49 Changing your password .................................................................................................................... 50 Setup Mode ...............................................................................................................
Game Mode ........................................................................................................................................ 86 Auto Launch ....................................................................................................................................... 86 Sender event logging (Windows only) ................................................................................................ 87 The HPRemote log ..........................................................
Receiver property hierarchy ............................................................................................. 115 Restoring Receiver properties default values ................................................. 115 Properties set using the Receiver Control Panel ............................................ 115 Receiver command line properties .................................................................. 116 rgreceiverconfig file properties .....................................................
Receiver network timeouts .............................................................................. 148 Sender network timeout .................................................................................. 150 Network timeout issues ................................................................................... 150 Troubleshooting Remote Audio ....................................................................................... 153 Troubleshooting Remote Clipboard ............................
1 Getting started in Windows The information in this chapter is meant to provide a quick guide for Windows users to install and use RGS in common scenarios. For more detailed information or Linux-specific topics, please see the additional chapters in this document. Installation To install the RGS Receiver on Windows, log in to an account with administrator privileges, and perform the following steps: ▲ Go to the directory where you downloaded RGS, double-click ReceiverSetup.
Creating a connection To start the RGS Receiver in Windows: ▲ Go to Start > HP > HP Remote Graphics Software > HP RGS Receiver. To create an RGS connection: 1. In the Hostname dialog box, type the hostname or IP address of the remote computer that is on the same network and has the RGS Sender installed, and then press Enter or click Connect. Figure 1-1 Receiver Control Panel 2. Type the username and password in the fields, and click OK.
User interface controls Remote Display Window Figure 1-2 Remote Display Window user interface overview 1. Remote Display Window toolbar—Provides easy access to the most frequently used options. For more information about the individual toolbar items, see Remote Display Window toolbar on page 53. 2. Remote Display Window scroll bars—Appear if the Remote Display Window is resized smaller than the remote desktop.
Receiver Control Panel Figure 1-3 Receiver Control Panel UI overview 1. Connection tab—Connection, Remote USB, and Remote Clipboard options. 2. Audio tab—Local and Remote Audio options. 3. Performance tab—Performance, experience, and image options. 4. Network tab—Network timeout and proxy configuration options. 5. Hotkeys tab—Check the index or adjust the behavior of hotkeys. 6. Logging tab—Select the level of logging messages. 7. Statistics tab—View statistics about an active connection. 8.
2 Overview of HP Remote Graphics Software Remote workstations are breaking free of network limitations with HP Remote Graphics Software (RGS). HP RGS is the collaboration and remote desktop solution for serious workstation users and their most demanding applications. All applications run natively on the remote workstation and take full advantage of its graphics resources.
Typical RGS configuration Figure 2-1 Typical RGS configuration 1. Remote computer—Hosts the user's applications and the RGS Sender, which transmits graphics, audio, and USB data to the RGS Receiver on the local computer. The Sender receives and processes keyboard events, mouse events, and USB data from the Receiver. NOTE: The RGS Sender operates independently of whether or not a monitor is actually connected to the remote computer. 6 2.
RGS features RGS supports a number of features designed to optimize performance, security, and functionality: ● 3D application support—Users can interact with OpenGL 3D applications running on the remote computer. Direct3D applications can be used as well, provided they are not in full-screen mode. 3D applications use the full power of graphics acceleration hardware on the remote computer.
● Remote USB—Many USB devices connected to the local computer can be virtually attached to and accessed by the remote computer. Some USB devices, such as webcams, are not supported. NOTE: Remote USB is not supported when the remote computer is running Linux. ● Selective screen updates—When Advanced Video Compression is not selected, only the portions of the screen that change are captured, compressed, and transmitted from the remote computer to the local computer, further improving performance.
Sender and Receiver interoperability RGS provides interoperability between versions of RGS Senders and Receivers that have the same primary version number. A connection between a Receiver and a Sender should only be attempted when their primary version numbers are the same. See below for a description of the RGS version number components. Figure 2-2 RGS version numbering 1.
Connection topologies This section describes the connection topologies supported by RGS, such as how a single local computer may connect to multiple remote computers. After making a connection between a local computer and a remote computer, the remote computer Sender transmits its complete frame buffer to the local computer. The frame buffer is the memory on the remote computer video adapter that holds the bitmapped image that is typically displayed on a monitor.
Figure 2-4 A local computer displaying two remote desktop sessions NOTE: Starting up two (or more) instances of the RGS Receiver to achieve a many-to-one connection is not supported. Achieving a many-to-one connection is only supported by Using RGS in Directory Mode on page 83. The many-to-one connection capability allows implementation of a virtual KVM (keyboard, video, and mouse) switch.
RGS login methods RGS provides three methods for the local user to log into a remote computer: ● Standard Login—supported on Windows and Linux Senders. ● Easy Login—supported on Windows XP, Windows 7, and Linux Senders. ● Single Sign-on—supported on Windows XP and Windows 7 Senders. The login method that is used is dependent on how the Sender was installed. If neither Easy Login nor Single Sign-on was enabled during installation, Standard Login is used.
Easy Login With Easy Login, the user is pre-connected to the system and standard Windows or Linux login screens are used to log in to the desktop or unlock the screen. If authentication is successful, the user will immediately see the desktop session without needing to be first authenticated by the RGS Receiver/Sender. NOTE: There are several Sender setup issues that can prevent an Easy Login connection to the RGS Sender.
3 Installing and activating RGS This chapter describes the following aspects of installing RGS: ● Installing RGS on Windows ● Installing RGS on Linux Installing RGS on Windows This section describes installation of the RGS Receiver and RGS Sender on Windows. See Supported hardware and software on page 142 for a list of the Windows operating systems that support the RGS Receiver and Sender. If you plan to use Advanced Video Compression, see Advanced Video Compression requirements on page 143.
NOTE: The "auto" option described in Auto-remoting on page 74 alters the behavior you select during installation. It will re-enumerate any device marked as auto on connect and disconnect. For instance, you have a USB key device that you have marked "auto". Until the Receiver is started it will be attached to the local system. Once the Receiver is started and makes a connection to a Sender, it will then be taken away from the local system and remoted to the Sender system.
Usage RGS command line options must be preceded by a /z flag and be enclosed in double quotes, with no space before or after the opening double quote and no space before the closing double quote. If using multiple commands, separate them with a single space. See the example below: ReceiverSetup.
Table 3-1 RGS Receiver installation command line options (continued) Command Description /proxy=
: Configures proxy settings to allow RGS to establish an HTTP session during Advanced Features registration. /wanimprovement Installs the HP Velocity network driver.NOTE: Installing the NVIDIA graphics driver after the Sender has been installed may prevent the use of Windows Aero on Windows 7. Manual installation of the RGS Sender on Windows To install the RGS Sender on Windows, log in to an account with administrator privileges, and perform the following steps: 1. Go to the directory where you downloaded RGS, double-click SenderSetup.exe to start the installation, and follow the on-screen instructions. 2.
Usage RGS command line options must be preceded by a /z flag and be enclosed in double quotes, with no space before or after the opening double quote and no space before the closing double quote. If using multiple commands, separate them with a single space. See the example below: SenderSetup.
Table 3-2 RGS Sender installation command line options (continued) Command Description rgslicensefile= may be specified. If neither /rgslicenseserver= nor /rgslicensefile= is specified, the installation will proceed as if this option was specified without a filename. /noreboot Causes the system to not reboot after an installation or uninstallation. /viewlicense Displays the EULA (End User License Agreement) for use of this software. NOTE: Using this option will negate all other options used.
Installing the RGS Receiver on Linux NOTE: The Linux RGS Receiver is available in both 32-bit and 64-bit versions. The Xlib version 1.1.5 is not supported. RGS only supports multi-head displays on Linux systems that have NVIDIA cards in TwinView mode. ATI dual-head is not supported. To install the RGS Receiver on Linux, perform the following steps: 1. Log in as root. 2.
Installing the RGS Sender on Linux NOTE: The Linux RGS Sender can only be installed on the computers and Linux operating systems shown in Supported hardware and software on page 142. Installing the Sender on a non-supported computer will prevent an RGS connection from being established. The RGS Sender requires a license key to establish an RGS connection (except on HP Z series workstations, HP EliteBook mobile workstations, and HP ZBook mobile workstations).
requiring default PAM authentication settings. The rpm can also be run independently of the install script. NOTE: This automated step must be performed after any actions that install their own X server configuration files because, in step (a) above, these files are modified to load the rge module required for proper RGS Sender functionality. If these files are replaced or modified later, the modules modifications described below must be correctly executed. 6.
7. If another desktop manager, such as Enlightenment, is being used, you will need to make similar changes to the PAM configuration file used by it. Consult your Linux and Desktop Manager documentation for further information. 8. If the PAM system has been configured to use custom PAM authentication modules, then you may need to manually configure the PAM module that is used by the RGS Sender. You should consult your Linux documentation when configuring PAM.
4 Pre-connection checklist Establishing an RGS connection from a Receiver to a Sender requires that the Local and remote computers be in the correct state. This chapter provides a checklist of items that should be verified before attempting an RGS connection. NOTE: This chapter can also be used as a troubleshooting aid. If a connection attempt fails, the checklists below can be used to help diagnose the problem. NOTE: The port used by the RGS Receiver is assigned by the local computer OS and can vary.
1. If using Advanced Video Compression, ensure the Sender system meets the requirements described in Advanced Video Compression requirements on page 143 (essential for a quality experience when using this feature). 2. OPTIONAL: Ensure RGS Sender licensing is set up—For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide, available at http://www.hp.com/support/ rgs.
127.0.0.1 localhost localhost.localdomain 88.1.89.122 blade2 blade2.datacenter.com For Linux systems with multiple network interfaces, each IP address must be listed in the /etc/ hosts file for example: 192.168.89.122 blade2 blade2.datacenter.com 192.168.90.111 blade2b blade2b.datacenter.com 10.
Manual Network Interface reconfiguration To manually configure which network interface the Sender binds to, set the Sender property Rgsender.Network.IsListenOnAllInterfacesEnabled=0 overriding the default which is to listen on all interfaces. See Network Interface binding properties on page 140, for more detail. If the Sender property Rgsender.Network.IsListenOnAllInterfacesEnabled=0 then the RGS Sender binds to the network interface specified by the Rgsender.Network.Interface..IsEnabled=1 property.
Figure 4-3 Determining the first network interface Figure 4-4 Advanced Settings dialog The arrows to the right of the Connections box in Figure 4-4 Advanced Settings dialog on page 29 can be used to change the order of the network interfaces and, therefore, which network interface will be used by the RGS Sender. In the above example, the RGS Sender will use Local Area Connection 3 with an IP address of 10.10.42.59.
● Use the Nslookup command to determine the IP address that the hostname resolves to. Then, using the arrow buttons to the right of the Connections box on the Advanced Settings screen (see Figure 4-4 Advanced Settings dialog on page 29) change the first network interface to correspond with the IP address returned by Nslookup. After performing this step, you must either reboot the computer, or restart the RGS Sender (see Figure 4-5 Restarting the RGS Sender on page 30).
Figure 4-6 Network Interface binding order numerical sequence Again, refer to Network Interface binding properties on page 140 for a description of these properties. Using RGS through a firewall The Receiver can use the public IP address of the Sender so that RGS can be used through a simple firewall. To take advantage of this feature, the Sender and Receiver firewalls must both support NAT (Network Address Translation). In addition, the Sender firewall must support port forwarding.
5 Using RGS This chapter discusses the following topics: 32 ● Using the Sender ● Using the Receiver ● Collaborating ● Multi-monitor configurations ● Changing your password ● Setup Mode ● Remote Display Window toolbar Chapter 5 Using RGS
Using the Sender This section discusses the following topics: ● Starting and stopping the Sender on Windows ● Sender command line options on Windows ● Sender GUI on Windows ● Setting the Windows Sender process priority ● Setting the Sender process priority using HP PA ● Using the RGS Diagnostics Tool on Windows ● Using the RGS Admin Tool ● Starting the Sender on Linux ● Sender audio on Linux ● Sender logging Starting and stopping the Sender on Windows The Sender is automatically started
Sender command line options on Windows The Windows Sender is comprised of two processes, one of which runs as a Windows Service. When the remote computer boots, the installed services are typically started. The service process, rgsendersvc.exe will then start the RGS Sender process rgsender.exe. When the RGS Sender is installed, an entry is added in the Windows Registry for the Remote Graphics Sender service. rgsender.exe supports the following options passed to it via registry parameters to rgsendersvc.
1. Start regedit —This can be done by opening a Windows command prompt and executing the command “regedit” or using the "run" command line from the Start menu. 2. Using regedit, navigate to the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rgsender 3. 3. Add the desired process priority command-line option for starting the Remote Graphics Sender service.
Setting the Windows Sender process priority This section discusses adjusting the process priority of the Windows Sender. The default process priority of the Windows Sender is normal. In some cases, increasing the process priority of the Sender will improve interactivity— for example, when the Windows scheduling algorithms does not give the RGS Sender sufficient CPU time to maintain smooth interactivity. Networking performance can also contribute to reduced interactivity.
Using the RGS Diagnostics Tool on Windows During the installation of the Windows Sender, the RGS Diagnostics Tool (rgdiag.exe) is installed. The tool can be used to detect potential issues (such as Windows firewall settings, Guest Account security policies, RDC interoperability, and Easy Login settings) that might prevent a remote connection. The dialog Figure 5-3 Output of the RGS Diagnostics Tool on page 37 shows the output generated by the tool.
Using the RGS Admin Tool The RGS Admin Tool is described for use on Windows 7. For information on using the RGS Admin Tool on Windows XP, see RGS Admin Tool on Windows XP on page 165. NOTE: The RGS Admin Tool is only installed and supported on Windows XP and Windows 7. For a normal Sender installation, this tool can be found at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgadmin.
Starting the Sender on Linux The Linux Sender is started by the “rge” X server extension. The Sender cannot be started manually. Proper configuration and startup of the Sender can be verified by examining the X server log file (Xorg.0.log). The log file will show that the extension is loaded, and that the extension has started the Sender: Log file content should be like: (II) LoadModule: "rge" (II) Loading /usr/lib64/xorg/modules/extensions/librge.so . . . (RG) 10:29:52.654 HP Remote Graphics extension.
Sender logging RGS Sender logging is not controlled by a GUI—instead, Sender logging is controlled by a particular file on the RGS Sender. In Installing the RGS Sender on Windows on page 17, the following command line option for Rgsender.exe is described: -l logSetupFile—Specifies the "logSetupFile" file used to describe various logging parameters for Sender error and informational output.
Using the Receiver RGS supports two basic operating modes: 1. Normal Mode—This mode enables RGS to connect to a single remote computer, as described in One-to-one connection on page 10. 2. Directory Mode—This mode enables RGS to connect to multiple remote computers, as described in Many-to-one connection on page 10. Directory Mode is based on a user-created file which specifies which remote computers the RGS Receiver should connect to.
[-h | -help | -?]—Displays the Receiver command line options that are listed on this page -Rgreceiver.propertyname=value—Can be used to specify one or more RGS Receiver properties. See RGS properties on page 113 for general information on RGS properties. For information specifically on RGS Receiver properties, see RGS Receiver properties on page 115. After the Receiver starts, you’ll see the Receiver Control Panel (see Figure B-1 Receiver Control Panel on page 149).
Receiver Control Panel The Receiver Control Panel is used to perform the following tasks: ● Establish a connection: To establish a connection to a remote computer, enter the hostname or IP address of the computer. Press Enter or click the Connect button to connect to the remote computer. The selector on the right side of the text box displays a history of previously connected computers that can be selected. ● Close a connection: To close a connection, press the Disconnect button.
Figure 5-7 Remote Display Window If you selected to activate HP Velocity, Advanced Video Compression, or both, and your Internet proxy settings are set correctly, a confirmation message will be displayed. If you selected to activate HP Velocity, Advanced Video Compression, or both, and your Internet proxy settings are NOT set correctly, an error message will be displayed.
Collaborating RGS enables the primary user to share his or her desktop session with several users simultaneously (see One-to-many connection on page 11). This feature can be used in a variety of collaborative scenarios including classroom instruction, design reviews, and technical support. Creating a collaboration session A collaboration session is created when one or more users are authorized by the primary user to connect to the primary user’s desktop session.
on page 46). Authorized local users will still be able to view the primary user’s desktop, but will be unable to interact with it. Figure 5-9 Disabling of the local users’ mice and keyboards by the primary user Connection between a local computer and a remote computer is permitted only if the primary user allows the connection and if all users have unique login accounts for the remote computer. Users may not share the same login account.
The Sender desktop icon in the system application tray displays the status of connections. The icon animates when Receivers are connected. All Receivers can be easily disconnected from the HP Remote Graphics icon located in the system tray or from the Sender GUI by right-clicking on the icon or GUI. This is useful when hosting collaborative session, such as in a classroom environment, and the session ends.
CAUTION: Caution is advised in disabling the collaboration notification dialog because neither the Remote User (if present) or the Local Users will be notified who is participating in a collaboration session.
Multi-monitor configurations NOTE: Advanced Video Compression is not supported on multi-monitor configurations. Many computers have a frame buffer that is larger in size (as measured in horizontal pixels by vertical pixels) than what can be displayed on a single monitor. In these situations, the default operation is that a portion of the frame buffer is used, allowing the utilized portion (containing the Windows desktop) to be displayed on a single monitor.
Changing your password You can change an expired password from the RGS Receiver. If you enter an expired password, you will see a dialog stating that the password must be changed (see Figure 5-15 Dialog indicating that the password must be changed on page 50). Figure 5-15 Dialog indicating that the password must be changed After clicking OK, you’ll see the Change Password dialog (see Figure 5-16 Change Password dialog on page 50).
Setup Mode Depending on how you configure RGS on the local computer, the Remote Display Window may cover the entire local computer monitor. Furthermore, the Remote Display Window may be set to borderless —therefore, the window won’t have the title bar and borders that normally allow the window to be moved, minimized, and resized.
Figure 5-17 Dimming of the Remote Display Window in Setup Mode The default hotkey sequence can be changed using the Hotkeys tab in the Receiver Control Panel (see Hotkeys tab on page 62). As long as the Shift key is held down (following the Shift press, space press, and space release hotkey sequence used to enter Setup Mode), Setup Mode remains active. When the Shift key is released, Setup Mode exits.
Remote Display Window toolbar The Remote Display Window toolbar provides information on the RGS connection and allows several RGS parameters to be controlled. The toolbar is positioned at the top of the Remote Display Window (see Figure 5-19 Remote Display Window toolbar on page 53). See the Connection tab on page 56 for more information. Figure 5-19 Remote Display Window toolbar The Remote Display Window toolbar provides the following: 1.
Image quality RGS provides high-quality, high-performance image compression and decompression. Image compression is performed on the remote computer to reduce the network bandwidth requirements— this enables RGS to be used on standard networks. Image decompression is performed on the local computer. Image quality is adjusted using the slide bar in the Remote Display Window toolbar (see Figure 5-20 Image quality slide bar in the Remote Display Window toolbar on page 54).
6 RGS settings This chapter discusses the different tabs available when you select the button from either the Receiver Control Panel or the Remote Display Window toolbar: ● Connection tab ● Audio tab ● Performance tab ● Network tab ● Hotkeys tab ● Logging tab ● Statistics tab Figure 6-1 RGS settings 55
Connection tab The options available under the Connection tab are shown in Figure 6-2 Connection tab options on page 56. Figure 6-2 Connection tab options The options available under the Connection tab are: ● Prompt for username and password—In certain scenarios (such as silent authentication as described in Standard Login on page 12) the Receiver will not prompt the local user for a domain, username, and password.
Receiver physical displays, the Sender will try to just match the Receiver display resolution. For example, if the Receiver has two physical displays in a 1x2 layout and a overall virtual display resolution of 2560x1024 (1280x1024x2), the Receiver will try to set the Sender to the same layout and resolution. If that fails, the Receiver will try to set a single Sender physical display resolution of 2560x1024. If that fails, an error is reported to the local user.
Audio tab The audio controls in the Receiver Control Panel are shown in Figure 6-3 Audio controls on page 58. Figure 6-3 Audio controls The options available under the Audio tab are: ● Don't stream audio from Sender—When selected, the RGS Sender will not send the audio stream along with the video stream to the Receiver. ● Stereo—This checkbox enables or disables stereo audio.
Performance tab The controls available in the Performance tab allow the user to adjust for a better interactive experience. Typically these adjustments will be made when working with highly interactive applications such as a CAD application in low bandwidth and/or high latency network environments. Allowing RGS to degrade the image quality while attempting to maintain a minimum update rate, can smooth the movement of objects on the screen.
When selecting Adaptive image quality, RGS will use this control setting for the target image quality when the updates per second allow. ● Increase text rendering quality—When checked, will improve image quality for images containing significant amounts of text or lines. Because of the high contrast ratio between adjacent pixels, such images often don’t compress well.
Network tab Figure 6-5 Options available under the Network tab The options available under the Network tab in the Receiver Control Panel are: ● Error—If the Receiver fails to detect the Sender after this amount of time in seconds, the Receiver will end the connection. ● Warning—If the Receiver fails to detect the Sender after this amount of time in seconds, the Receiver display a warning message.
Hotkeys tab Hotkeys are key sequences that cause special action to be taken by the Receiver. Such key sequences are processed by the Receiver, and are not sent to the remote computer. However, a hotkey sequence may initiate some type of interaction with the remote computer. The Receiver Control Panel provides a number of options under the Hotkeys tab (see Figure 6-6 The Hotkeys tab options on page 62).
Figure 6-6 The Hotkeys tab options on page 62, the default hotkey sequence to activate Setup Mode is: ● ◦ Press and hold down the Shift key. ◦ At the same time, press then release the space bar—this activates Setup Mode. You will remain in Setup Mode until you release the Shift key. Send First Key: This checkbox controls how the Receiver responds to a key sequence. For example, the default Setup Mode hotkey consists of a Shift Press, Space Press, and Space Release.
Changing the Setup Mode hotkey sequence RGS allows you to change the Setup Mode hotkey sequence from its default value of: Shift Down, Space Down, Space Up In defining a new Setup Mode hotkey sequence, the following keys can be used: ● LCtrl, RCtrl, Ctrl— Specifies a left, right or side-insensitive Ctrl key, respectively. ● LAlt, RAlt, Alt— Specifies a left, right or side-insensitive Alt key, respectively. ● Shift ● Space Every sequence must begin with Ctrl, Alt, or Shift.
Logging tab The RGS Receiver logs various types of information during its operation. The Logging tab allows you to set a number of the logging parameters, such as whether logging is enabled and the location/name of the log file (see Figure 6-7 Options available under the Logging tab on page 65). Figure 6-7 Options available under the Logging tab The options available under the Logging tab are: ● File logging—Enables logging to the specified Log File.
Statistics tab The options available under the Statistics tab in the Receiver Control Panel are shown in Figure 6-8 Options available under the Statistics tab on page 66. Figure 6-8 Options available under the Statistics tab The Statistics tab displays aggregate data for all connected sessions. 66 ● Total network usage (Mbits/sec)—The combined network traffic received from all remote computers. ● Image updates per second—The combined number of image updates per second received from all connections.
7 Advanced capabilities This chapter discusses the following topics: ● Remote Audio ● Remote USB ● Remote Clipboard ● Using RGS in Directory Mode ● Game Mode ● Auto Launch ● Sender event logging (Windows only) ● Remote Application Termination ● Optimizing RGS performance ● Interoperability of RGS and Microsoft Remote Desktop Connection ● RGS security features ● Linux connection considerations 67
Remote Audio This section describes RGS support of Remote Audio on Windows and Linux. Rather than describe all four combinations of remote and local computers running Windows and Linux, the following sections describe Remote Audio when both computers are running Windows, followed by a Remote Audio description when both computers are running Linux.
● USB devices are Remote—If selected, a USB microphone can be accessed anytime by the remote computer.
Remote Audio on Linux RGS on Linux also supports Remote Audio, allowing audio generated by the application on the remote computer to be captured and transmitted to the local computer for playback. Table 7-2 Linux RGS audio data paths on page 70 describes the paths taken by both applicationgenerated audio output and microphone audio in Linux. For a list of audio devices supported on Linux remote computers, see Remote Audio device support on Linux on page 144.
There are two important things. The first is what’s between the “[ ]”. The first number is the “card” (denoted “c” below) and the second number is the “device” (denoted “d” below). The second important thing is the word “capture” in the description. Rgsender.Audio.Linux.DeviceName=plughw:c,d In the example above, depending upon which audio device you would like to capture the audio from, you could specify the device with: Rgsender.Audio.Linux.DeviceName=plughw:0,0 or Rgsender.Audio.Linux.
Remote USB RGS supports Remote USB, which allows USB devices (such as mice and keyboards) connected to the local computer to be attached to a remote computer. Remote USB is supported on remote computers running Windows and enables the remote computer to have direct access to the local USB devices as if they are connected directly to the remote computer. Local USB devices can be collectively attached to a single remote computer.
Attaching a local USB device to a remote computer Figure 7-2 Remote USB options The Remote USB options are: ● Enable Remote USB—This checkbox can be used to dynamically (during an active RGS connection) enable or disable USB connections to the remote computer. When enabled, USB devices plugged into the local computer appear to the remote computer as locally attached devices.
Auto-remoting In addition to the general default settings for Remote USB configurations, RGS supports auto-remote and auto-return of user-specified USB devices when using Windows on both the Sender and Receiver platforms. An auto-remote configuration syntax for the Windows Registry entries allows specified USB devices to be automatically attached to a remote Sender session at RGS connection and then returned to the local client at RGS disconnect.
RGS works very closely with the Windows USB driver stack. Any USB device that exclusively uses the Windows USB driver stack for functionality should work with RGS. The less a USB device's driver complies with the Windows USB driver stack, the less likely it will work with RGS. NOTE: Devices that adhere to the USB standard should work. Because RGS is a remote graphics protocol and is emulating the USB protocol over a network, devices that are sensitive to timing may not work at all.
previously). Because the home RDC login session is still active, RGS will require the user to authenticate the connection (which is not normally required with Easy Login). However, the user may not have a login name and password—the user may be totally relying on smart card readers at home and at work to log into the remote computer.
Remote USB Access Control List RGS supports a per-remote computer access control list (ACL) file that specifies which USB devices are allowed to be remotely attached to the remote computer from a local computer, and which USB devices are denied attachment. The ACL file, which resides on the remote computer, supports allowing/denying USB device attachments based on the following nine USB descriptor fields: 1. Device Class 2. Device Subclass 3. Device Protocol 4. Vendor ID 5. Product ID 6.
Rules may contain filters based on the 11 parameters listed previously. These parameters are repeated below along with the name of the filter element. 1. Device Class— bDeviceClass 2. Device Subclass— bDeviceSubclass 3. Device Protocol— bDeviceProtocol 4. Vendor ID— idVendor 5. Product ID— idProduct 6. Device BCD— bcdDevice 7. Manufacturer— manufacturer 8. Product Type— product 9.
Determining USB device information This section describes how to obtain several of the most-used USB device parameters. Determining USB device information for Windows To obtain the Vendor ID and the Product ID for a USB device on Windows, perform the following steps: 1. Open the device manager. ● Go to the Control Panel and run "System" ● Select the "Hardware" tab ● Select the "Device Manager" button, this runs the device manager program. 2. Double-click the Universal Serial Bus Controllers 3.
Determining USB device information for Linux An open source program called "usbview" is available on the SourceForge website. There are three different programs called "usbview". The one to use is the "original" version. This is the plain usbview that was registered on "1999-12-20" and is administered by "kroah". Do not use "usbview2" or "usbview-1.8". The URL for this software is: http://sourceforge.
Remote Clipboard Remote Clipboard enables the user to cut or copy data between a window on the local computer (the Local Window) and a Remote Display Window (provided that both the remote and local computers are running Windows and the applications being used support cut/copy/paste). Remote Clipboard cut and paste of ANSI text data is supported between Windows Receiver systems and Linux Sender systems. The clipboard can be enabled to work on a limited permissions receiver window for collaboration mode.
NOTE: This property is for advanced users only. The property string should be changed from its default value only if Remote Clipboard doesn’t support the clipboard format required by your application. For more information on clipboard formats, see the Microsoft Developer Network article Clipboard Formats at http://msdn2.microsoft.com/en-us/library/ms649013.aspx. This property contains a list of clipboard formats allowed to be transferred using Remote Clipboard.
Using RGS in Directory Mode Directory Mode enables the local user to automatically open connections to multiple remote computers based on the computers assigned to each user. When the user starts the Receiver in Directory Mode, the Receiver looks for a directory file containing user names and their assigned remote computers. The Receiver reads this file to identify the remote computers assigned to the current user, and then attempts to automatically connect to each specified remote computer.
In the above examples: ● Local user sally is assigned remote computers RC_1, RC_2, and RC_3 ● Local user joe is assigned remote computers RC_4 RC_5, and RC_6 If the domain name, user name, or remote computer contains white-space characters, the name can be enclosed in double-quotes, as follows: "domain 1" "sally user" "RC 1" "RC 2" "RC 3" "domain 1" "joe user" "RC 4" "RC 5" "RC 6" The domain name does not apply when using the directory file for Linux users.
Figure 7-3 The Receiver Control Panel in Directory Mode After clicking Connect All, you’ll need to independently authenticate and log into each remote computer. If Setup Mode is activated by the hotkey sequence (as opposed to the Setup Mode button), and you have multiple Remote Display Windows on your computer, you can bring up the Remote Display Window selection dialog to view a thumbnail image of each Remote Display Window.
Game Mode Game Mode is a feature accessed via Hotkeys tab on page 62. When operating in normal cursor mode, RGS synchronizes the cursor movements of a Sender to a controlling Receiver by placing the senders cursor at the same absolute coordinates of the receivers cursor. Some applications rely on a relative movement of the cursor to interact with a 3D environment. These applications may programmatically readjust the cursor position after a movement is detected.
Sender event logging (Windows only) The RGS Sender on Windows supports event logging. Event logging provides information useful for troubleshooting connection problems, and can also be used to automatically terminate applications on the Sender in case the connection is lost between the Sender and the Receiver. This section describes the Sender event logging capabilities while Remote Application Termination on page 91 describes how to use event logging to terminate applications on the Sender.
Properties window for the highlighted event in Figure 7-5 The HPRemote log on page 87. As you can see, the Sender event that has been logged is the Sender connection state. Figure 7-6 Event Properties window The highlighted radio buttons allow viewing of the connection data (in this case, the number of primary and non-primary connections) in byte and word formats. The Section HPRemote log format on page 91 provides more details on the supported data formats.
Figure 7-7 Reporting of the local computer IP address, port number and hostname when a connection is made to the Sender Usages of the HPRemote log The HPRemote log has several important usages: ● Troubleshooting—The HPRemote log can be used to aid troubleshooting of connection issues between the RGS Sender and Receiver. If you’re unable to view the HPRemote log because of RGS connection difficulties, Remote Desktop can be used to connect to the remote computer to view the HPRemote log.
Using the sample code provided, you can create an agent to automatically monitor and process any Sender events. Additional information on event logging For additional information on Windows event logging, search Microsoft Developer Network (MSDN) at http://msdn.microsoft.com/.
Remote Application Termination This section describes how to create a Windows agent on the Sender that provides Remote Application Termination. “Remote application” refers to user applications that are running on the remote computer (Sender). For a sample agent, see Sample agent on page 99.
Table 7-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description Data: UINT32 numPrimary UINT32 numNonprimary Event Viewer Example: Primary connections:1 Non-primary connections:0 RGSENDER_CONNECT EventID: 4 A new connection was established with an associated name. If Easy Login is enabled, the name assignment will be deferred until login and the associated name may be “Anonymous”. Event Viewer Message: Connect %1.
Table 7-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description None Data: None RGSENDER_SHUTDOWN EventID: 2 Reference event registered to aid in interpretation of the event log by Event Viewer. Signifies proper shutdown of the RGS Sender service. Event Viewer Message: RGS Sender shutdown. Strings: None Data: None RGSENDER_SET_PRIMARY EventID: 6 A connection with an associated name is set as the primary connection. Event Viewer Message: Set %1 as primary connection.
Table 7-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description Strings: %1 = original name of connection %2 = new name of connection Data: None Event Viewer Example: Assign Anonymous connection to MYDOMAIN \myusername. RGSENDER_USB_CONNECT_DEVICE EventID: 9 A new USB device was connected to the Sender via Remote USB.
Table 7-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description Strings: %1 = USB device class %2 = USB device vendor ID %3 = USB device product ID Data: None Agent design issues Designing an agent to provide Remote Application Termination requires consideration of a number of issues in order to minimize data loss and determine when a last-resort shutdown of a disconnected desktop session is required.
require a master semaphore to halt/terminate multiple agents if the user reconnects and wants to stop the shutdown process. Wrapping applications of interest ● Situation—Agents can be launched that supervise only specific applications in a given environment. Tying agents to specific applications is a selective safety net for every user. ● Benefit—Application-specific agents can be implemented as plug-ins or support utilities for a given application.
● Expect the unexpected—where possible, limit your actions to those areas you are certain of the outcomes to minimize loss of data and productivity. ● Always inspect error codes when reading event logs—the reliability of this RGS communication method depends upon the Windows Event Log system. While we have yet to see a failure in this path, we recommend using all information available to its fullest potential.
Figure 7-8 Remote computer Sender recovery options Microsoft Remote Desktop Recovery If the RGS Sender becomes unavailable and the Receiver can no longer connect to the Sender, a Windows system with Remote Desktop services enabled can access the remote computer to diagnose the issue.
Sample agent The sample Windows agent presented below monitors the HPRemote event log and interprets its events. Comments are included in the agent code showing where additional code would be added to determine if the number of primary users has dropped to zero. If so, further code can be added to terminate applications on the Sender. The sample code is a fixed-polling Windows agent that reads and interprets the HPRemote event log. The agent uses two functions: 1. 2.
EVENTLOGRECORD *pevlr; BYTE bBuffer[BUFFER_SIZE]; DWORD dwRead, dwNeeded; BOOL result; // Open, read, close event log =========================================== if ((h = OpenEventLog(eventServer, eventSource)) == NULL) { ... report error status ... return true; } // Set the pointer to our buffer. Strings and data will get appended to the EVENTLOGRECORD structure.
// representing primary and non-primary connections. unsigned int *pData = (unsigned int *) ((LPBYTE) pevlr + pevlr->DataOffset); // Examine state of primary connections here for other // agent response if number drops to zero... ... example only prints out retrieved record to console ... printf ("Event: %u Primary: %u Secondary: %u\n", dwEventNum, pData[0], pData[1]); } ... Process other events here if desired ... } else { ... report unrecognized event here ...
return; } // If an event is added, either the start or count will change. // Get the start and count. Microsoft does not specify what // reasons these functions could fail, so we cannot ensure // success. Check the return value. if (GetOldestEventLogRecord(h, &dwCurrentStart) == false || GetNumberOfEventLogRecords(h, &dwCurrentCount) == false) { CloseEventLog(h); ... report error - unable to obtain event logs ... return; } if (CloseEventLog(h) == false) { ... report error status here ...
if (dwNewIndex) { if (processEvent(eventServer, eventSource, dwCurrentIndex)) { ... event processing error here ... return; } } } else { // No new events. Sleep for 1 second. Sleep(1000); waitedFor += 1; } } return; } main( ... ) { ... setup and initialize agent ... monitorEvents(EVENT_SERVER, EVENT_SRC, seconds); ... cleanup agent here or send alerts ... ... may wish to return status from monitorEvents ...
Optimizing RGS performance This section provides suggestions on optimizing RGS performance, including optimizing the remote computer display settings and the network configuration. Advanced performance features The following features can be used to optimize RGS performance: ● Advanced Video Compression—This option uses a modern video codec to greatly reduce the bandwidth needed for high-quality video streams. You can choose to have the compression done by either the graphics card or the CPU.
● ◦ Select the Control Panel ◦ Bring up the Display Properties window ◦ Select the Settings tab, and set the Color Quality to Highest (32-bit) Lower the Sender display resolution—RGS is an image-based remote visualization technology. Therefore, lowering the display resolution can significantly improve performance.
Performance tuning for Windows This section provides performance tuning tips for RGS on Windows. 1. Lock desktop icons on the remote computer by performing the following steps: ● Select the Control Panel ● Bring up the Display Properties window ● Select the Desktop tab and select Customize Desktop. ● On the Web tab, check Lock desktop items. 2.
● Use the ping command to measure network latency. From a command prompt on Windows or a terminal window on Linux, execute ping hostname. This will report the network latency. Be sure the ping protocol (ICMP) is not blocked by a firewall. Windows may be set up with IPSec filters— be sure there is no IPSec filter policy disabling ICMP traffic. ● Use Traceroute (Linux) or tracert (Windows) to measure the network latency between two computers.
Interoperability of RGS and Microsoft Remote Desktop Connection This section discusses interoperability considerations for RGS and Remote Desktop Connection (RDC). Because RGS and RDC both provide connection to a remote desktop, their interoperation is important to understand. If a local user is connected to a remote computer using RDC and then attempts to establish an RGS connection, the RGS connection only works if the local user credentials match for both connections.
RGS security features Because of the distributed nature of an RGS connection, providing connection security is critically important. RGS implements many features to provide connection security, including: ● Authentication: When a local user attempts to connect to a remote computer, the user credentials are validated using the native authentication method on the remote computer. If the credentials are not authenticated, the connection is closed. On Windows, authentication uses NTLM or Kerberos.
The default behavior is that the remote computer monitor will blank to black when the user connects and logs in. The remote computer monitor will un-blank when the user disconnects or logs out. Below are several additional details on monitor blanking on HP personal workstations: ● The one element on the monitor that does not go blank is the cursor. ● Blanking can take up to two seconds from the time the primary user logs in or reconnects until the time that the monitor is actually blanked.
Figure 7-10 Message Dialog The remote computer monitor blanking feature can be disabled by setting the following Sender property to 0 (false). Rgsender.IsBlankScreenAndBlockInputEnabled If this property is set to 0, monitor blanking will be disabled, meaning that a monitor connected to the remote computer will display the user’s desktop session. Furthermore, because monitor blanking is disabled, the warning dialog will not be displayed.
Linux connection considerations NOTE: The Switch User functionality added to RHEL6 is not supported by RGS. Full-screen crosshair cursors Certain applications that use large crosshair cursors (for example, Dassault Systemes ICEM Surf uses a full-screen crosshair cursor) will not display correctly on the Receiver.
8 RGS properties RGS allows the user to specify many properties of the RGS connection, both on the Sender and Receiver. By specifying properties, the user can modify RGS characteristics such as: ● Display of borders on the Remote Display Window ● Codec quality ● Audio quality ● Connection timeouts This chapter describes each of the RGS properties, their default values, and how they can be changed.
Setting property values in a configuration file RGS property values can be set in a configuration file. The RGS Receiver uses the rgreceiverconfig file for its properties while the RGS Sender uses the file rgsenderconfig file for its properties.
Rgsender.LoggedOutAuthenticators Rgreceiver.AuthenticatorId Rgreceiver.AuthenticatorId.IsMutable CAUTION: The authenticator properties are typically set by 3rd party software modules integrated with RGS, and should not be changed. Changing these properties can have unexpected consequences, including preventing you from establishing an RGS connection from the Receiver to the Sender.
Receiver command line properties See Setting properties on the command line on page 114. rgreceiverconfig file properties See Setting property values in a configuration file on page 114. Archive file properties When the Receiver is run, the user can change a number of properties using menus on the Receiver Control Panel and the Remote Display Window. When the Receiver exits, it saves the state of any properties that were changed by the user—these are known as archive file properties.
● ● ● ◦ Rgreceiver.Experience.IsMutable ◦ Rgreceiver.Experience.Mode ◦ Rgreceiver.Experience.MinImageQuality ◦ Rgreceiver.Experience.MinUpdateRate Browser properties group ◦ Rgreceiver.Browser.IsMutable ◦ Rgreceiver.Browser.Name Audio properties group ◦ Rgreceiver.Audio.IsMutable ◦ Rgreceiver.Audio.IsEnabled ◦ Rgreceiver.Audio.Quality ◦ Rgreceiver.Audio.IsFollowsFocusEnabled ◦ Rgreceiver.Audio.IsInStereo Microphone property group ◦ ● ● ● ● Rgreceiver.Mic.
● ● ◦ Rgreceiver.Clipboard.IsMutable ◦ Rgreceiver.Clipboard.IsEnabled ◦ Rgreceiver.Clipboard.FilterString Logging properties group ◦ Rgreceiver.Log.IsMutable ◦ Rgreceiver.Log.IsFileLoggerEnabled ◦ Rgreceiver.Log.Filename ◦ Rgreceiver.Log.Level ◦ Rgreceiver.Log.MaxFileSize Image codec properties group ◦ Rgreceiver.ImageCodec.IsMutable ◦ Rgreceiver.ImageCodec.Quality ◦ Rgreceiver.ImageCodec.IsBoostEnabled Per-session properties ● ● Auto Launch property set.
in the group. All group IsMutuable properties have a default value of 1, which allows the user to interactively change the other properties in the group. Each of the individual properties has an associated IsMutable Boolean property to control whether each individual property can be interactively changed by the user—this is the individual IsMutable property. For example, the Rgreceiver.Network.Timeout.Error property now has the individual Rgreceiver.Network.Timeout.Error.IsMutable property.
Figure 8-2 The Receiver timeout error property menu is grayed out Receiver general properties The general properties are listed below. After each property, the default value is listed in parenthesis. Rgreceiver.IsBordersEnabled=bool （default=1） Rgreceiver.IsBordersEnabled.IsMutable=bool （default=1） If set to 1, the borders on the Remote Display Window will be enabled (displayed). If set to 0, the borders will be removed creating a borderless windows to display the remote computer desktop.
If set to 1, when connecting to an RGS Sender, the user will always be prompted for the domain, username and password. There will be no attempt to automatically verify the user credentials. The default value is 0—prompting for credentials is off. Rgreceiver.Directory=string （directory.txt） Rgreceiver.Directory.IsMutable=bool （1） Used in Directory Mode to set the name and location of the file that lists the remote computers assigned to the current user. The default value is "directory.txt". Rgreceiver.
Then the Receiver will try to set the layout of the remote computer (Sender) physical displays to have the same display layout and resolution as the Receiver displays. If the Sender is unable to match the layout and resolution of the Receiver physical displays, the Receiver will try to just match the Receiver display resolution.
NOTE: The following property, while supported, has been deprecated. HP recommends using the per-session Remote Display Window X and Y positioning properties described in Window placement and size properties on page 134. Rgreceiver.RecentWindowPositions=int vector （10 10） Rgreceiver.RecentWindowPositions.IsMutable=bool （1） This property can be used to set the positions of the Remote Display Windows. The position of each Remote Display Window is controlled by an (xpos,ypox) 2-tuple.
Rgreceiver.IsGlobalImageUpdateEnabled.IsMutable=bool （1） If set to 1, the Receiver updates the area of the screen with the extents of all the areas of the screen that have changed. If set to 0, the Receiver limits updates of the screen to just the areas that have changed, using individual update rectangles. If image updates in the Remote Display Window show image tearing, setting the value to 1 (enabling global image updates) may reduce the tearing.
Figure 8-4 Pointer Options tab in the Sender Mouse Properties dialog When the Rgreceiver.IsMouseSyncEnabled property is set to 1 on the Receiver and when an automatic snap to action occurs on the Sender, the snap to action will be communicated from the Sender to the Receiver; the RGS Receiver will then move the mouse cursor to reflect the cursor position in the Sender dialog box where the snap to action occurred.
This property allows the user to enable a warning dialog when closing the RGS window while RGS is still connected. This warning dialog will warn the user that disconnecting from RGS while they are still logged in will not log the user out of the remote system. Receiver experience properties Rgreceiver.Experience.IsMutable=bool （1) When set to 1, the default, the user can turn this feature on and off in the Receivers Advanced > General tab, Experience section.
If set to 1, the RGS audio subsystem will be enabled. If set to 0, RGS audio will be disabled and no network bandwidth will be consumed for Remote Audio. The default value is 1—audio is enabled. Rgreceiver.Audio.Quality=int （1） Rgreceiver.Audio.Quality.IsMutable=bool （1） The audio quality property can be set to low (0), medium (1), or high (2) quality. This property is used to adjust the sample rate of the streaming audio.
USB devices attached to the second remote computer, use value one, and so on. The default value is 0—the local USB devices are attached to the first remote computer. The local USB devices can only be attached to one remote computer at a time. To change which remote computer the local USB devices are attached to, all remote computers must be disconnected. Then enter a new value for this property, and reconnect to all remote computers.
Receiver network properties Rgreceiver.Network.Timeout.IsMutable=bool If set to 1, the user can modify all network timeout values in the RGS Receiver Control Panel. If set to 0, the user cannot modify the values. This property can be used to permanently set network timeouts before the RGS Receiver is started. The default value is 1—timeout values are changeable by the user. Rgreceiver.Network.Timeout.
Rgreceiver.Hotkeys.SetupModeSequence=string （“Shift Down, Space Down, Space up”） Rgreceiver.Hotkeys.SetupModeSequence.IsMutable=bool （1） Defines the Setup Mode hotkey sequence. The sequence may only consist of Ctrl, Alt, Shift and Space keys. The sequence must also start with either a Ctrl, Alt or Shift key. The first key must also be held down through the entire hotkey sequence. The default value is "Shift Down, Space Down, Space Up". Rgreceiver.Hotkeys.
If set to 1, the Remote Clipboard setting in the Receiver Control Panel can be changed by the user. If set to 0, the user cannot change the Remote Clipboard settings. The default value is 1—the Remote Clipboard setting can be changed by the user. Rgreceiver.Clipboard.IsEnabled=bool （1） Rgreceiver.Clipboard.IsEnabled.IsMutable=bool （1） This is a per-receiver property. If set to 1, the local user can use Remote Clipboard. If set to 0, the local user cannot use Remote Clipboard.
● Rich Text Format—A text format that includes special formatting features, such as bold, italics, and centering. ● XML Spreadsheet—A format created by Microsoft to allow Excel spreadsheets to be saved in XML (Extensible Markup Language) format. This format is supported by other applications as well. Receiver logging properties Rgreceiver.Log.IsMutable=bool（1） If set to 1, the logging settings in the Receiver Control Panel can be changed by the user.
This property sets the image quality in the Remote Display Window, and can be set to a value from 0 to 100. A value of 100 is the highest quality image while 0 is the lowest image quality. Under most circumstances, the default value of 65 will be sufficient. Lower values of Rgreceiver.ImageCodec.Quality will typically reduce RGS bandwidth requirements on the network. If the Sender property, Rgsender.ImageCodec.Preferred, is set to Rgsender.ImageCodec.Preferred=JPEG-LS, the Rgreceiver.ImageCodec.
The password as a utf8 encoded string, to use if automatically connecting on start-up. Rgreceiver.Session..PasswordFormat=Encrypted | Clear | XOR The format of the password. RGS supports three formats Encrypted, Clear or XOR. Encrypted is only supported on Windows and is the hexadecimal string representation of a password encrypted using the Windows command CryptProtectData. Clear is the password as clear text. XOR is the hexadecimal string representation of a password XORed against the value 129.
is unable to match the resolution preference of the local computer, a warning dialog is displayed on the local computer NOTE: The per-session property Rgreceiver.Session..VirtualDisplay.IsPreferredResolutionEnabled takes precedence over the perReceiver property Rgreceiver.IsMatchReceiverResolutionEnabled. This allows individual sessions to override the global property.
● ◦ Rgsender.MaxImageUpdateRate ◦ Rgsender.ImageCodec.Preferred ◦ Rgsender.IsBlankScreenAndBlockInputEnabled ◦ Rgsender.IsIloRemoteConsoleEnabled ◦ Rgsender.IsAnonymousConnectionForceEnabled ◦ Rgsender.PreferredDisplayMethods ◦ Rgsender.IsCollaborationNotificationEnabled ◦ Rgsender.IsReconnectOnConsoleDisconnectEnabled Microphone properties group ◦ ● ● ● ● Rgsender.Mic.IsEnabled Network timeout property group ◦ Rgsender.Network.Timeout.Error ◦ Rgsender.Network.Timeout.
Sender general properties Rgsender.IsRdpLogoutDetectionEnabled=bool （1） This property only applies to the Windows versions of the RGS Sender. When a user disconnects from a RDC session, the Windows desktop on the remote computer is immediately available for an RGS connection. However, if the user logs out of the RDC session, the RGS Sender will be unable to access the desktop for about 60 seconds. If this property is set to 1, the desktop will be available to RGS almost immediately.
The default value is 1— monitor blanking is enabled. For details on monitor blanking, see Remote computer monitor blanking operation on page 109. Rgsender.IsIloRemoteConsoleEnabled=bool （0） This property is supported only on Linux. If set to 0, the iLO (integrated Lights-Out) console is disabled when an RGS connection is made. This prevents the user’s desktop session from being visible through the iLo remote console.
CAUTION: Caution is advised in disabling the collaboration notification dialog because neither the Remote User (if present) or the Local Users will be notified who is participating in a collaboration session.
Network Interface binding properties The following properties permit control of which network interface the RGS Sender binds to. Use of the network interface binding properties is described in Network Interface reconfiguration using the Sender network interface binding properties on page 30. Rgsender.Network.IsListenOnAllInterfacesEnabled=bool（1） This property can be used to force the Sender to listen for RGS connections on all network interfaces.
If set to 1, Remote Clipboard is enabled—specifically, the copy and cut functionality in the Remote Display Window is enabled. If set to 0, the copy and cut functionality is disabled. The default value is 1 —Remote Clipboard is enabled. Rgsender.Clipboard.IsAlwaysAuthorized=bool （1） If set to 1, Remote Clipboard works on a limited permissions receiver window for collaboration mode.
A Supported hardware and software RGS support matrix Table A-1 RGS support matrix Windows XP Professional (32bit, 64-bit) Windows 7 Professional, Enterprise (32-bit, 64-bit) √ √ Desktop mode only √ √ √ 64-bit √ RGS Receiver (Desktops/ notebooks) Windows 8 Pro, Enterprise RHEL 5.9, 6.4 (32bit, 64-bit) SLED 11.
Advanced Video Compression requirements Table A-2 Advanced Video Compression requirements RGS Sender RGS Receiver CPU encoding—4 cores or more running at 2 GHz (minimum); 8 cores or more running at 2 GHz (recommended) CPU decoding—2 cores or more running at 2 GHz NOTE: If using GPU encoding, the CPU only needs to meet the requirements listed in RGS support matrix on page 142. GPU encoding—NVIDIA Quadro 2000 or better graphics card with driver version 305.
Remote Audio device support on Linux An audio device is required to be installed in Linux-based remote computers in order for applicationgenerated audio to be sent to the local computer. Furthermore, the audio device installed in the remote computer must have the ability to record from a control that is the mix of all audio signals. On a Windows computer, by way of comparison, this control is often called “Stereo Mix”.
Keyboard locale support The following keyboard localizations are supported when connected to a Linux Sender: 1. French 2. German 3. Japanese 4. Norwegian 5. Swedish 6. United Kingdom 7. U.S. English The following keyboard localizations are supported when connected to a Windows Sender: 1. Belgian French 2. Canadian French 3. Chinese (Simplified) – US Keyboard 4. Chinese (Traditional) – US Keyboard 5. Czech 6. Czech (QWERTY) 7. Danish 8. Dutch 9. Finnish 10. French 11.
25. United Kingdom 26. United Kingdom Extended 27. United States-International 28. US Application support RGS supports all applications, except those applications that use full screen exclusive mode. RGS may not be suitable for most full screen games. If a full-screen MS-DOS command prompt window is created on the Sender (using, for example, command.com), the window will be reset to its default size by RGS. Likewise, if a full-screen Windows XP command prompt window is created (using cmd.
B Troubleshooting RGS This appendix provides suggestions on troubleshooting potential issues with RGS and also lists the RGS error messages and their possible causes. Potential issues and suggestions Table B-1 Potential RGS issues and troubleshooting suggestions Issue Suggestion Cannot connect to the RGS Sender Verify that the pre-connection checklist is satisfied as described in Pre-connection checklist on page 25. A connection is established but it appears to time out.
Troubleshooting network timeouts RGS uses TCP/IP over a standard computer network to transmit data. Although TCP/IP is a reliable transport mechanism, it does not guarantee network packet delivery. The TCP/IP network stack performs well on a relatively stable network. However, network issues beyond RGS can affect the probability and timing of network packet delivery.
Figure B-1 Receiver Control Panel If a temporary network disruption occurs for less time than the Receiver warning timeout property, the Receiver will not display a warning, and the user will experience only a brief drop in Remote Display Window interactivity. This means, for example, that a user moving or scrolling a window might see a momentary decrease in interactivity.
potential disruptions greater than two seconds, a higher Receiver warning timeout property may be appropriate to lessen distraction of the user. Experience has demonstrated that 30 seconds is a reasonable Receiver error timeout property, although some users adjust this property lower to force connections to close sooner. Higher settings, such as 60 seconds, are often impractical because they force the user to wait an inordinate amount of time before RGS closes the connection.
◦ The Sender unexpectedly terminated. ◦ The remote computer experienced a failure ◦ The remote computer CPU utilization prevented the Sender from making progress, ◦ The length of this connectivity loss exceeds the Receiver’s error timeout value, controlled by the Receiver’s Rgreceiver.Network.Timeout.Error property so the Receiver disconnected. If this condition persists, it is possible that network disruptions are exceeding the Receiver error timeout value.
Sender’s timeout values are shorter than the Advanced capabilities Receiver’s, the Sender may close the connection sooner than the Receiver, disconnecting the Receiver. If the issue continues, consider increasing the Sender's error timeout value. See Network tab on page 61 for further details on setting timeouts.
Troubleshooting Remote Audio Several potential audio issues are described below along with their potential causes. ● No mixer control available on Windows XP — If a mixer control such as “Wave Out Mix”, “Stereo Mix”, “What U Hear”, or an equivalent control is not available, Remote Audio will not work. Either disable the audio device and reinstall the RGS Sender to get the virtual audio driver, update the audio driver, or use a different audio device.
● ToggleKeys sound not working—The Accessibility control in Windows will play a sound when some control keys are pressed. This sound is not heard on the Receiver because it is played through the PC Speaker. See the section “PC speaker sounds not working” above. ● No audio with multiple audio devices—The Sender will open up the device that is registered as the default audio device. The Sender is a service that is running in a different context.
Troubleshooting Remote USB If you have problems connecting a remote USB device from a local computer to a remote computer, the following checklist may help identify the problem. Computers supporting Remote USB Ensure that both the remote computer and the local computer support Remote USB. Supported USB devices Verify that the USB device you’re using is supported. HP has tested a number of USB devices to verify they work correctly when attached to a remote computer from a local computer.
Check USB cable connections Verify that the USB device is physically connected to the local computer. Check to see that it has power and is turned on. Some devices may require that the user initiate an action before it connects. To further verify your connections, recognized devices on the Receiver system appear in the Proc file system under the /proc/devices/usb_remote directory.
RGS error messages This section lists the error messages reported by the RGS Receiver and describes possible reasons for them. Table B-2 RGS Receiver error messages Error Description Connection lost! The RGS Sender has closed the connection. Possible reasons include: ● The Sender may have explicitly disconnected your connection. For example a user may have selected disconnect all connections from the Sender icon or Sender GUI or the user may have logged off.
Table B-2 RGS Receiver error messages (continued) User not found in directory! The username of the current user of the HP Remote Graphics Software Receiver is not found in the directory file. Possible reasons include: ● The username entered in the directory file does not exactly match the real username. ● The domainName entered in the directory file is incorrect. See Directory file format on page 83 for information about choosing the correct domainName.
C Technical support Obtaining HP technical support If you encounter an issue that requires technical support, please do the following prior to contacting HP for assistance: ● Be in front of the local computer or remote computer, whichever one is appropriate. ● Note the operating system. ● Note any applicable error messages. ● Note the applications you were using when you had the issue. ● Be prepared to spend the time necessary to troubleshoot the problem with the service technician.
D RGS on Windows XP This appendix discusses several topics that apply to Windows XP only. ● Easy Login and Single Sign-on ● RGS Admin Tool on Windows XP ● Audio on the Windows XP Sender Easy Login and Single Sign-on Setting the local security policy in Windows XP The local security policy "Interactive logon: Do not require CTRL-ALT-DEL" must be disabled to support Easy Login or Single Sign-on. This can be set in the Windows "Local Security Settings" under "Security Options.
5. Add the GinaDllMode registry key if does not already exist. This can be done through the use of regedit as well. Create the key as type RGS_SZ (a string type). The full path of the key is: HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\Remote Graphics Sender \GinaDllMode 6. To actually enable Easy Login, set the value of the GinaDllMode key to the text "HprEasyLogin". Confirm the spelling before closing.
1. Create the ChainedGinaDLL registry key. Create the key as type REG_SZ (a string type). The full path of the key is: HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\Remote Graphics Sender \ChainedGinaDLL 2. Set the value of the new ChainedGinaDLL key to the name of the custom GINA module. For example, if the name of the custom GINA module is foogina.dll, then the value of the key should be foogina.dll. The value should match the string originally discovered in the registry key GinaDLL.
1. Install the Sender on the HP workstation. If the RGS Sender is not installed or installs with errors, DO NOT perform the remaining steps. Doing so will put the computer in a state that requires a complete re-installation of the operating system. 2. After the RGS Sender is installed, confirm that hprgina.dll exists in the C:\WINDOWS\system32 directory. The Sender installer copies hprgina.dll directly into the system32 directory. CAUTION: If the hprgina.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon \GinaDll CAUTION: If the value of the GinaDLL key contains the name of a custom GINA DLL, and the file does not exist in C:\WINDOWS\system32, the computer will not start correctly after the next reboot. The computer will then require a complete re-installation of the operating system. GinaDLL key is removed using regedit, the Windows Registry Editor.
RGS Admin Tool on Windows XP When run on Windows XP, the RGS Admin Tool displays two tabs. The 3D Updates tab (see Figure D-4 3D Updates tab on page 165) can be used to enable automatic 3D updates from the application to the Sender. These updates inform the Sender what screen rectangles have been changed by the 3D application. Figure D-4 3D Updates tab NOTE: RGS versions prior to RGS 4.0 required the manual placement of the RGS OpenGL32.dll library into the application directory for each application.
Figure D-5 Dialog to enable or disable Single Sign-on and Easy Login (Windows XP) 166 Appendix D RGS on Windows XP
Audio on the Windows XP Sender Configuring audio on the Windows XP Sender NOTE: It is critical that a mixer control such as “Wave Out Mix”, “Stereo Mix”, or some variation on “Mixer” is available. The Creative Audigy driver calls this the “What U Hear” control. See Figure D-9 Recording Control dialog on page 169 for a mixer example. If a mixer control is not available, see Troubleshooting Remote Audio on page 153 for troubleshooting suggestions.
To select the mixer as the input line, click the Volume button in the Sound recording section of Figure D-6 Sound and Audio Devices Properties dialog on page 167. This brings up the Recording Control window (see Figure D-7 Select Recording Control Properties on page 168). Many audio device drivers do not show all available inputs by default. The mixer line is often one of the control lines that is not visible by default.
Figure D-8 Recording Control Properties dialog Press the OK button and the Recording Control window should now have the mixer line as one of the controls (see Figure D-9 Recording Control dialog on page 169). Make sure this item is selected, and the volume level is not at the lowest setting. Figure D-9 Recording Control dialog After selecting the mixer, the Sender should record audio information and send it to the Receiver. See the following section to improve the audio quality.
Calibrating audio on the Windows XP Sender The audio signal captured by the Sender is modified by two different device driver volume controls, and then the master volume level is artificially inserted into the signal. If these volume controls are too low, you might not hear the audio signal. If they are too high, the signal might be distorted. This section describes a technique to hand tune the volume controls to reduce the amount of distortion.
Figure D-11 Recording Control dialog The best sound to play to calibrate your audio device is a low frequency sound with high amplitude. By default, Windows has a program event that meets these requirements. To play this sound, open up the Sound and Audio Devices window, and click the Sounds tab as shown in Figure D-12 Sound and Audio Devices Properties dialog on page 172.
Figure D-12 Sound and Audio Devices Properties dialog Select the Critical Battery Alarm program event, and press the play button (the triangle located next to the Browse button). The wav file associated with this event is recorded near maximum intensity. If you can play this sound without distortion, most sounds should play without distortion. Some media applications modify their audio signal prior to sending it to the audio device. The Windows Media Player may appear to distort some audio files.
Index A Admin Tool, Windows XP 165 administrator alerts 96 advanced capabilities 67 Advanced Video Compression description 7, 104 enabling 59 requirements 143 agent design guidelines 96 agent design issues 95 application support 146 Audio Receiver requirements on Linux 21 audio calibrating, Windows XP Sender 170 configuring, Windows XP Sender 167 disabling on Sender 71 Linux Sender 39 Receiver properties 126 remote 68 Remote, troubleshooting 153 Windows XP Sender 167 Audio tab 58 authenticator properties 11
L licensing, RGS 9 Linux black or blank connection session with Sender 112 connection considerations 112 full-screen crosshair cursors 112 gamma correction on the Receiver 112 installing 20 installing Receiver 21 installing Sender 22 manually disabling Easy Login 24 Receiver Audio requirements 21 Remote Audio 70 Remote Audio device support 144 Sender audio 39 starting Sender 39 uninstalling Receiver 21 uninstalling the Sender 24 Linux Remote Audio device support 144 local security policy Windows XP 160 log
logging properties 132 manual installation on Windows 14 microphone property 127 network properties 129 network timeout 148 properties 115 property groups 116 property hierarchy 115 Remote Clipboard properties 130 uninstalling on Linux 21 USB properties 127 using 41 Receiver Control Panel 43 Receiver, starting 2 Remote Application Termination 91 Audio 68 Clipboard 81 USB 72 Remote Audio on Linux 70 on Windows 68 support on Linux 144 troubleshooting 153 Remote Clipboard Receiver properties 130 troubleshootin
graphics performance 106 issues, suggestions 147 network timeouts 148 Remote Audio 153 Remote Clipboard 154 Remote USB 155 typical configuration 6 U uninstalling Receiver on Linux 21 Sender on Linux 24 uninstalling Receiver Windows 17 uninstalling Sender on Windows 20 USB Access Control List 77 attaching local device to remote computer 73 determining device information 79 Local/Remote 72 Receiver properties 127 remote 72 remote, troubleshooting 155 Sender access control list properties 139 supported devices
