Page 1 HP Remote Graphics Software 5.3.0 User Guide Part number: 391829-409 Eighteenth edition: September 2009...
Page 2 © Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Page 3 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.com) log4cplus: This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Page 4: Table Of Contents
Contents 1 Introduction to HP Remote Graphics Software Typical RGS configuration......................12 RGS Sender and Receiver ......................13 RGS features ..........................14 Additional RGS features........................ 14 Tabloid-size page ........................15 Obtaining HP technical support ..................... 15 1-6-1 Software Service Strategy for Non-HP Hardware..............15 2 RGS overview Supported computers and operating systems ...................
Page 5 3-2-2 Uninstalling the Receiver on Linux..................69 3-2-3 Installing audio on the Linux Receiver..................69 3-2-4 Installing the Sender on Linux....................71 4 Pre-connection checklist Local Computer (Receiver) checklist ....................74 Remote Computer (Sender) checklist ....................74 NIC binding on the Sender ......................76 4-3-1 Manual NIC reconfiguration....................
Page 6 Statistics ........................... 135 7 Using Directory Mode 7-1-1 Directory file format......................136 7-1-2 Starting the Receiver in Directory Mode ................137 7-1-3 Selecting Remote Display Windows while in Directory Mode ..........138 8 RGS properties Property syntax.......................... 139 Setting property values in a configuration file ................139 Setting properties on the command line ..................
Page 7 A-2 Using RGS with static HP VDI ......................184 A-2-1 Create a new virtual machine ....................184 A-2-2 Modify the VMware ESX configuration (.vmx file) ............... 185 A-2-3 Installing the RGS Sender on the virtual machine ................ 187 A-3 Using RGS with dynamic HP VDI (based on VMware View)..............187 A-3-1 Create a new virtual machine ....................
Page 8 Figures Figure 1-1 Typical RGS configuration ......................12 Figure 1-2 RGS Sender and Receiver......................13 Figure 1-3 Features of HP RGS ........................14 Figure 2-1 Computers and operating systems that support RGS 5.3.0 ............... 18 Figure 2-2 RGS version numbering ....................... 19 Figure 2-3 Dialog generated when the RGS Sender is unlicensed..............
Page 9 Figure 5-2 Receiver Control Panel ........................ 81 Figure 5-3 Remote Display Window ......................81 Figure 5-4 Dimming of the Remote Display Window in Setup Mode ..............83 Figure 5-5 Remote Display Window selection dialog ..................84 Figure 5-6 Remote Display Window Toolbar ....................85 Figure 5-7 Local Computer warning dialog if the Remote Computer is unable to blank its monitor ......
Page 10 Figure 8-2 The Receiver timeout error IsMutable property is set to 0..............144 Figure 8-3 The Receiver timeout error property menu is grayed out..............144 Figure 8-4 The Receiver maintains a list of the most recently connected Senders..........145 Figure 8-5 Prior to RGS 5.1.3, only one image update would be in-process at any time........
Page 11: Introduction To Hp Remote Graphics Software
1 Introduction to HP Remote Graphics Software This guide provides information that you will need to install, configure, and use HP Remote Graphics Software (RGS). RGS enables you to view and interact with the desktop of a remote computer over a standard TCP/IP computer network.
Page 12: Typical Rgs Configuration
Chapter 12: Troubleshooting RGS—This chapter describes how to troubleshoot issues related to establishing an RGS connection, network timeouts, graphics performance, remote audio, and remote USB. Chapter 13: RGS error messages—This chapter lists each of the errors reported by the RGS Receiver and describes their probable cause.
Page 13: Rgs Sender And Receiver
1-2 RGS Sender and Receiver Figure 1-2 shows the two primary RGS software components, the RGS Sender and RGS Receiver. The RGS Sender runs on the Remote Computer while the RGS Receiver runs on the Local Computer. Figure 1-2 RGS Sender and Receiver RGS Sender RGS Receiver interactive...
Page 14: Rgs Features
1-3 RGS features HP RGS supports a number of features designed to optimize performance, security, and functionality (see Figure 1-3). Figure 1-3 Features of HP RGS Collaboration – Multiple Local Computers can connect to a HP-developed compression algorithms are used single Remote Computer, allowing to minimize data transmission requirements.
Page 15: Tabloid-Size Page
Audio follows focus—The RGS Receiver can be configured to enable audio for the session displayed in the • Remote Display Window that currently has focus, and is muted for all other remote sessions/windows. Directory Mode—Directory Mode enables the Receiver to look up a user’s pre-assigned computers from a •...
Page 16 Telephone support service is for RGS software installation and configuration support. Customer must have a fully functioning system with standard Microsoft Windows software loaded and • running Software patch updates are available through Software Depot at http://software.hp.com under Client Virtualization. Software assurance (enhancement upgrades) are available through separate Software Assurance products 1-6-2 Other RGS Documents Other RGS documents such as the HP Remote Graphics Software Licensing Guide and the HP Remote Graphics...
Page 17: Rgs Overview
2 RGS overview Before exploring how to use RGS, it’s important to first understand the required system environments and security features used and supported by RGS. Supported computers and operating systems • RGS version numbering • RGS licensing • RGS products •...
Page 18: Supported Computers And Operating Systems
2-1 Supported computers and operating systems This section describes the computers and operating systems which support HP RGS 5.3.0 (see Figure 2-1). Any RGS Sender can interoperate with any RGS Receiver. Figure 2-1 Computers and operating systems that support RGS 5.3.0 Receiver Windows Windows XP Professional...
Page 19: Rgs Version Numbering
2-2 RGS version numbering The RGS version (for example, version 5.3.0) contains the following three numbers: Version major number Version minor number Version patch number Figure 2-2 shows the positioning of the three version numbers. RGS 5.3.0 Patch releases are generated for a security major.minor.patch issue or for a major defect in a feature.
Page 20: Rgs Products
purchase, for example, 75 licenses but support a user community of perhaps hundreds of users as long as no more than 75 users ever attempt to establish an RGS connection simultaneously. Floating licenses require a license server, which can be installed on one of the computers running the RGS Sender, or the license server can be installed on a separate computer.
Page 21: Sender And Receiver Interoperability
2-5 Sender and Receiver interoperability RGS provides interoperability between versions of RGS Senders and Receivers that have the same major version number. For example, Sender version 5.0 and Receiver version 5.1 will interoperate together. However, Sender version 4.2 is not guaranteed to interoperate with Receiver version 5.0. Connection between a Receiver and a Sender should only be attempted when their major version numbers are the same.
Page 22: One-To-One Connection
TCP/IP to Local Computer (optional) Remote Computer frame buffer The monitor itself is optional on the Remote Computer. For example, if the Remote Computer is a Personal Workstation, a monitor (plus a keyboard and mouse) would typically be attached. If the Remote Computer is an HP ProLiant Blade Workstation, it is not possible to attach a monitor to view the primary (NVIDIA) frame buffer because the video signal from the NVIDIA graphics adapter is not available on a connector—the contents of the frame buffer can only be viewed remotely using RGS.
Page 23: Figure 2-7 Addition Of Scroll Bars If The Remote Display Window Is Resized Smaller
Figure 2-6 Addition of scroll bars if the Remote Display Window is resized smaller Local Computer (Receiver) Remote Computer (Sender) Scroll bars are created if the Remote Display Window is resized smaller than when it was originally created. NOTE: RGS does not provide a scale-to-fit capability to allow the contents of the Remote Computer frame buffer to be scaled to fit the Local Computer monitor.
Page 24: Many-To-One Connection
2-8-3 Many-to-one connection The RGS Receiver supports a many-to-one connection, allowing a single Local Computer to connect to multiple Remote Computers (see Figure 2-7), each running a desktop session—see Section 2-11, “RGS operating modes,” specifically Directory Mode. The frame buffer of each Remote Computer is displayed in a separate Remote Display Window on the Local Computer.
Page 25: Establishing An Rgs Connection Using Standard Login
The one-to-many configuration is ideal for collaboration because each user can interact with the applications running on the Remote Computer (subject to RGS policies which arbitrate which user is able to provide keyboard and mouse inputs to the Remote Computer at any particular time). As one user interacts with the applications on the Remote Computer, all other users can view these interactions.
Page 26: Single Sign-On And Easy Login
If another user is already logged into the Remote Computer, the second authentication step is replaced by an authorization step, in which the currently logged-in user receives an authorization prompt to allow or disallow the new user to join (connect to) the existing desktop session (see Figure 2-11). The new user is allowed to connect to the existing RGS connection only if the currently logged-in user authorizes the connection.
Page 27: Rgs Operating Modes
2-11 RGS operating modes RGS supports two basic operating modes: Normal Mode—This mode enables RGS to connect to a single Remote Computer, as described in Section 2- 8-2, “One-to-one connection.” Normal Mode is described in Chapter 5, “Using RGS.” Directory Mode—This mode enables RGS to connect to multiple Remote Computers, as described in Section 2-8-3, “Many-to-one connection.”...
Page 28: Multi-Monitor Configurations
2-12 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.
Page 29: Remote Computer Monitor Blanking Overview
Multiple monitors on the Local Computer are also useful in the configuration described in Section 2-8-3, “Many-to- connection.” If the Local Computer is connected to two Remote Computers, each Remote Computer frame buffer can be displayed on its own monitor if the Local Computer has two monitors (see Figure 2-14). Figure 2-14 Each Remote Display Window can be positioned to occupy a single monitor Remote Computer 1...
Page 30: Image Quality
2-15 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. RGS supports setting of the Image quality on a per-Receiver basis.
Page 31: Remote Usb Overview
2-16 Remote USB overview RGS supports remote USB, which allows USB devices connected to the Local Computer (local USB devices) 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 (see Figure 2-16).
Page 32: Install-Time Configuration Of Remote Usb
2-16-3 Install-time configuration of remote USB This section provides an overview of install-time configuration of remote USB—see Chapter 3, “Installing RGS,” for more details. NOTE: The Remote USB configuration cannot be changed after installation of the Sender and Receiver—to select a different USB configuration option, the Sender or Receiver must be uninstalled and reinstalled. During installation of the RGS Receiver, you can select one of three Remote USB Configuration options (see Figure 2-18).
Page 33: Unique Smartcard Handling
Figure 2-19 USB device accessibility for the setting “USB devices are Local/Remote” USB devices are Local/Remote Device #3 will be remotely accessible because it was plugged in during an These devices will only be locally RGS connection. This device will be accessible (never remotely) because remotely accessible during the current they were plugged in while no RGS...
Page 34: Figure 2-22 Smartcard Reader Accessibility Pre- And Post-Rgs Connection For Settings "Usb Devices Are Remote" Or "Usb Devices Are Local/Remote
Figure 2-20 Smartcard reader accessibility pre- and post-RGS connection for settings “USB devices are Remote” or “USB devices are Local/Remote” USB devices are Remote Smartcard reader will USB devices are Local/Remote be locally accessible. Smartcard reader will automatically smartcard reader smartcard become remotely accessible.
Page 35: Computers Supporting Remote Usb
2-16-5 Computers supporting remote USB Remote USB connections are supported by the computers and operating systems shown in Figure 2-21. Figure 2-21 Configurations supporting remote USB Receiver Remote USB Windows Windows XP Professional SP1, SP2, Windows Vista Business, Ultimate and Embedded Support Matrix XPe/WES...
Page 36: Remote Audio On Windows
2-17-1 Remote audio on Windows RGS on Windows supports remote audio, allowing audio generated by the application on the Remote Computer to be captured and transmitted to the Local Computer for playback. In addition, microphone input on the Local Computer running Microsoft Windows XP can be sent to the application running on the Remote Computer also using Microsoft Windows XP.
Page 37 Table 2-1 Windows RGS audio data paths Audio Playback from the Remote Computer to the Local Sending of microphone audio from the Local Computer to Computer the Remote Computer The application-generated audio output. USB devices are Local: If an audio device is installed, the application- The user selects the microphone source, either a USB generated audio is routed through it.
Page 38: Remote Audio On Linux
2-17-2 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 (presuming the Remote Computer has a physical audio device installed). In addition, microphone input on the Local Computer can be sent to the application running on the Remote Computer.
Page 39 Table 2-2 Linux RGS audio data paths Audio Playback from the Remote Computer Sending of microphone audio from the Local to the Local Computer Computer to the Remote Computer The application-generated audio output. USB devices are Local: Linux does not support locally-mounted USB microphones.
Page 40: Support Of Sound Recording Devices On Microsoft Windows Xp Professional
2-17-3 Support of sound recording devices on Microsoft Windows XP Professional NOTE: The Windows Sounds and Audio Devices Properties dialog allows the user to select the “sound recording device”. For simplicity, “microphone” is used below instead of “sound recording device”. Remote microphone is not supported on Microsoft Windows Vista.
Page 41: Computers And Operating Systems Which Support Rgs Audio
2-17-4 Computers and operating systems which support RGS audio Figure 2-24 shows the computers and operating systems that support RGS audio. For further details on Remote Audio, see Section 6-2, “Remote audio operation.” Figure 2-24 Configurations that support remote audio Receiver Audio Windows Windows XP Professional...
Page 42: Remote Clipboard Overview
2-18 Remote Clipboard overview Remote Clipboard was originally supported with RGS 5.1.3, enabling 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 and paste, and copy and paste.
Page 43: Figure 2-28 Enabling Remote Clipboard During Sender And Receiver Installation On Microsoft Windows Systems
In order for Remote Clipboard to be usable, it must be enabled during both the Sender and Receiver installations on Microsoft Windows (see Figure 2-26). See “Manual installation of the Receiver on Windows” and “Manual installation of the Sender on Windows”...
Page 44: Interoperability Of Rgs And Microsoft Remote Desktop Connection
2-19 Interoperability of RGS and Microsoft Remote Desktop Connection This section discusses interoperability considerations for RGS and Microsoft 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.
Page 45: Remote Computer Power Saving States
2-21 Remote Computer power saving states In order for a Local Computer to establish connection to a Remote Computer, the Remote Computer cannot be in a power saving state, such as Windows hibernate or standby. Furthermore, the Remote Computer cannot utilize wake-on-LAN in an attempt to power-up in order to respond to a connection request from the Local Computer—the Remote Computer must be powered-up, and able to respond to an RGS connection request at all times.
Page 46: Rgs Security Features
2-23 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 •...
Page 47: Installing Rgs
3 Installing RGS This chapter describes the following aspects of installing RGS: Installing the RGS Receiver on Windows • Installing the RGS Sender on Windows • Installing the RGS Receiver on Linux • Installing the RGS Sender on Linux • IMPORTANT: RGS licensing applies to the RGS Sender only.
Page 48: Figure 3-1 Receiver Remote Usb Configuration Dialog
During the installation, the Remote USB Configuration dialog is displayed (see Figure 3-1 and Section 2-16, “Remote USB overview”). Additional information can be viewed by selecting I’m not sure, I want more information, and clicking Next. Select the USB configuration option that meets your needs, and click Next. Figure 3-1 Receiver Remote USB configuration dialog NOTE:...
Page 49 Use of this option indicates that the user agrees to the license for use of this software. This option is required when doing an install. /autoremove Remove the Receiver. /folder=<folder> Specifies the destination folder, default is C:\Program Files\Hewlett-Packard\Remote Graphics Receiver. /usb=local Install USB in Local Mode. /usb=remote Install USB in Remote Mode. The system will automatically restart after the install completes.
Page 50 Removes the user specific Receiver settings from the registry. /viewlicense Displays the EULA (End User License Agreement) for use of this software. /help Display usage text. Installing RGS 50...
Page 51 Receiver installation log file Installation of the Receiver creates an installation log file. This log file can be viewed by the user to obtain details about what operations were performed, and view any errors that occurred during the installation process. When Setup.exe for the RGS Receiver is run, the following log file is created: C:\TEMP\rgreceiverInstaller.log The log file is especially useful for automatic installs because installer errors are not displayed on the screen, and...
Page 52: Installing The Sender On Windows
3-1-2 Installing the Sender on Windows IMPORTANT: The Sender can only be installed on the computers and operating systems shown in Figure 2-1. Installing the Sender on a non-supported computer will prevent an RGS connection from being established. This section covers the following topics: Manual installation of the Sender on Windows •...
Page 53: Figure 3-5 Dialog To Enable Single Sign-On Or Easy Login
NOTE: For many USB devices, the Windows operating system provides default USB drivers. While these default drivers may, in fact, work with your USB devices, it is recommended that you install the manufacturer- supplied USB drivers to optimize functionality and performance of your USB devices. The manufacturer- supplied USB driver should be installed on any computer, Local or Remote, where the USB devices will be logically (not necessarily physically) attached.
Page 54: Figure 3-7 Diagnostics Prompt Dialog
Next, the Sender installer will run the rgdiag.exe diagnostics tool. If the tool detects a problem, the dialog shown in Figure 3-6 is displayed. This dialog allows you to run rgdiag.exe directly—refer to the Section “Using the RGS Diagnostics Tool on Windows”...
Page 55 Windows Explorer to display the RGS Sender installation folder, and locate the rgdiag.exe program with the RGS icon. On a 32-bit Windows system, this tool is normally located at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgdiag.exe Note that the rgdiag.exe tool does not run as part of an unattended install.
Page 56: Figure 3-9 Sender Gui
Add the desired process priority command-line option for starting the Remote Graphics Sender service. For example, to increase the process priority to high add the “-high” option to the key “ImagePath” as follows: "C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgsendersvc.exe" -l logSetup –high Restart the Sender service with the new option.
Page 57: Figure 3-10 The Remote Graphics Sender Service
Figure 3-9 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.
Page 58: Figure 3-14 3D Updates Tab
This section describes use of the Sender rgadmin.exe tool. For a normal Sender installation, this tool can be found at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgadmin.exe When run, the rgadmin.exe program displays two tabs. The 3D Updates tab (see Figure 3-10) can be used to enable automatic 3D updates from the application to the Sender.
Page 59: Figure 3-15 Dialog To Enable Or Disable Single Sign-On And Easy Login
The GINA Setup tab on the rgadmin tool can be used to enable Single Sign-on and Easy Login (see Figure 3-11). When rgadmin is brought up, it reports the current status of Single Sign-on and Easy Login. To change the status, check the desired radio button.
Page 60: Figure 3-16 The Dialog Presented During Sender Installation To Enable Single Sign-On Or Easy Login
Installing and enabling Single Sign-on CAUTION: Installing RGS Single Sign-on is for experienced users and IT administrators only. Please read all directions completely before proceeding, and exercise caution when installing. Single Sign-on is only supported on HP blade workstations running the RGS Sender. The RGS shared library, hprgina.dll, enables Single Sign-on.
Page 61: Figure 3-17 Using The Rgadmin Tool To Enable Single Sign-On
2. Using the rgadmin tool to enable Single Sign-on IMPORTANT: The rgadmin tool is only installed and supported on Windows XP. The rgadmin tool can be used to enable Single Sign-on—check the Enable Single Sign-on radio button in Figure 3-13, and click Apply. Enabling Single Sign-on installs the hprgina.dll module. Using the rgadmin tool to enable Single Sign-on is preferred over the manual method, described next.
Page 62: Figure 3-18 Addition Of The Ginadll Key To The Registry
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 To actually enable Single Sign-on, set the value of the GinaDllMode key to the text "HprSso". Confirm the spelling before closing.
Page 63: Installing And Enabling Easy Login
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 Installing RGS 63...
Page 64: Figure 3-20 Addition Of The Ginadllmode Key To The Registry
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 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...
Page 65 3-1-2-1 Setting the Local Security Policy The local security policy "Interactive logon: Do not require CTRL-ALT-DEL" must be disabled to support Easy Login. This can be set in the Windows "Local Security Settings" under "Security Options." The RGS Diagnostics Tool programmatically detects if this local security policy is set correctly.
Page 66 Use of this option indicates that the user agrees to the license for use of this software. This option is required when doing an install. /autoremove Remove the sender. /folder=<folder> Specifies the destination folder, default is C:\Program Files\Hewlett-Packard\Remote Graphics Sender. /usb Enable remote USB. /remotemic Enable remote microphone.
Page 67 /rgslicensefile=<filename> The license to run the RGS Sender is acquired from the specified file. The filename may be omitted by specifying the option as “/rgslicensefile=”, in which case the Sender will be installed without a license, and the license file can be manually copied to the install folder at a later time. Only one of /rgslicenseserver= or /rgslicensefile= may be specified.
Page 68: Installing Rgs On Linux
3-2 Installing RGS on Linux This section describes how to: Install and uninstall the RGS Receiver on Linux • Install audio on the Linux Receiver • Install and uninstall the RGS Sender on Linux. • IMPORTANT: Support of RGS on RHEL 5.2 (or later versions) requires that certain components be installed during the installation of RHEL 5.2.
Page 69: Uninstalling The Receiver On Linux
3-2-2 Uninstalling the Receiver on Linux To uninstall the RGS Receiver on Linux find the name of the RedHat RPM package for the Remote Graphics Receiver, by typing: rpm -q -a | grep -i rgreceiver If the Receiver is installed on the system, you will see rgreceiver_linux_32-5.1-0 or a similar Receiver package.
Page 70 The audio support bundle ships as hp_rgs_4_audiosupport.tar.gz. It is accessed by the RGS install.sh script in /opt/hpremote or may be utilized for manual installations / RPM package building. The install process requires a locally writable directory in which to build. Locate the support bundle in an appropriate directory before installation.
Page 71: Installing The Sender On Linux
3-2-4 Installing the Sender on Linux IMPORTANT: The Linux RGS Sender can only be installed on the computers and Linux operating systems shown in Figure 2-1. Installing the Sender on a non-supported computer will prevent an RGS connection from being established. Like the Windows RGS Sender, the Linux RGS Sender also requires a License Key in order to establish an RGS connection.
Page 72 The Linux Sender uses the Pluggable Authentication Module (PAM) for authentication. If you are using the GNOME Desktop Manager or KDE Desktop Manager, add the following line to the files listed below: session optional pam_rg.so Files (and all related derivatives): /etc/pam.d/gdm /etc/pam.d/kdm /etc/pam.d/xdm...
Page 73 Starting the Sender on Linux The Linux sender is started by the “rge” X server extension whose configuration is described in the previous section. 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).
Page 74: Pre-Connection Checklist
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.
Page 75 you disable Guest logins on the Remote Computer. To disable this policy, open the "Control Panel", selecting "Administrative Tools", selecting "Local Security Policy", expanding the "Local Policies", expanding "Security Options", and setting "Network access: Sharing and security model for local accounts" to "Classic – local users authenticate as themselves".
Page 76: Nic Binding On The Sender
4-3 NIC binding on the Sender If the Remote Computer has multiple NICs, it is possible for the RGS Sender to be “listening” on one NIC while the RGS Receiver is trying to establish a connection to the other NIC. There are three methods to deal with multiple NICs: Manually reconfigure which of the two NICs RGS binds to—see Section 4-3-1, “Manual NIC...
Page 77: Figure 4-3 Determining The First Nic
To determine which NIC is the first NIC, click Advanced > Advanced Setting (see Figure 4-3). The Advanced Settings dialog is displayed (see Figure 4-4). The “first NIC” is listed at the top in the Connections box. In Figure 4-4, the first NIC is Local Area Connection 3, which (from Figure 4-2) has an IP address of 10.10.42.59.
Page 78: Nic Reconfiguration Using The Nic Binding Properties
Figure 4-5 Restarting the RGS Sender 4-3-2 NIC reconfiguration using the NIC binding properties At RGS 5.1, several new Sender properties were added to allow the administrator to configure which NIC(s) the RGS Sender will listen to for connection requests. For a description of these properties, refer to Section 8-6-6, “Sender NIC binding properties.”...
Page 79: Using Rgs Through A Firewall
4-4 Using RGS through a firewall New at RGS 5.1.5 is the ability for the Receiver to use the public IP address of the Sender. This feature has been added to allow RGS to be used through a firewall. To take advantage of this feature, the Sender and Receiver firewalls must both support NAT (Network Address Translation).
Page 80: Using Rgs
5 Using RGS This chapter describes how to use RGS to establish a connection from a Local Computer to a Remote Computer, including: Using RGS in Normal Mode • Functionality and use of the Receiver Control Panel • Setup Mode •...
Page 81: Figure 5-2 Receiver Control Panel
After the Receiver starts, you’ll see the Receiver Control Panel (see Figure 5-2). Figure 5-2 Receiver Control Panel To create an RGS connection, enter the hostname or IP address of the Remote Computer in the Hostname dialog box, and press Enter or click Connect. NOTE: At RGS 5.2.5, the capability was added to specify the port number used by the RGS Sender.
Page 82: Receiver Control Panel
IMPORTANT: If the connection attempt fails, refer to Chapter 4, “Pre-connection checklist,” for a list of conditions which must be met in order for a connection to be established. IMPORTANT: If your RGS Sender is not yet licensed, the error dialog in Figure 2-3 will be displayed in the Remote Display Window.
Page 83: Figure 5-4 Dimming Of The Remote Display Window In Setup Mode
NOTE: In Normal Mode, only a single Remote Display Window can be displayed on the Local Computer. Displaying multiple Remote Display Windows on the Local Computer requires using Directory Mode (see Chapter 7, “Using Directory Mode”). Setup Mode can be activated in two ways: By clicking the Setup Mode button on the Receiver Control Panel (see Figure 5-2).
Page 84: Figure 5-5 Remote Display Window Selection Dialog
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 (see Selecting Remote Display Windows while in Directory Mode).
Page 85: Remote Display Window Toolbar
5-1-3 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-6), and is toggled on and off by pressing the H key while in Setup Mode. In this particular case, Setup Mode can be entered by either method—the Setup Mode button or the hotkey sequence—and the H key can be used to display the toolbar.
Page 86: Remote Computer Monitor Blanking Operation
5-1-4 Remote Computer monitor blanking operation For an overview of Remote Computer monitor blanking, see Section 2-13, “Remote Computer monitor blanking overview.” Monitor blanking on the Remote Computer is provided for security, so that the primary user’s desktop session on the Remote Computer is not visible if a monitor is connected to the Remote Computer. Monitor blanking is supported on all Windows computers that support gamma.
Page 87: Linux Connection Considerations
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 shown in Figure 5-7 will not be displayed.
Page 88: Rgs Login Methods
5-3 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. For an overview of Standard Login, see Section • 2-9, “Establishing an RGS connection using Standard Login.”...
Page 89: Figure 5-10 Standard Login Process
Figure 5-10 Local user Standard Login process and primary user flowchart local user attempt to log in primary user using Standard Login Attempt to connect to Remote Remote Computer Display someone else Window log in with my credentials RGS authentication dialog Windows-to-Windows “authenticating the connection”...
Page 90: Easy Login
5-3-2 Easy Login The Easy Login flowchart is shown in Figure 5-11. If the Easy Login conditions are met, the RGS connection authentication step is skipped, and the local user is presented either with the Welcome to Windows login dialog or the locked screen dialog.
Page 91: Single Sign-On
5-3-3 Single Sign-on The Single Sign-on flowchart is shown in Figure 5-12. If the Single Sign-on conditions are met, the user authenticates the RGS connection, and the Windows log in or unlock step is skipped. The user is presented with the Windows desktop following RGS connection authentication.
Page 92: Changing Your Password
5-4 Changing your password In RGS 5.0 and earlier, attempting to make a connection with an expired password would generate an Authentication failed! error message. In this situation, the user would either need direct access to the Remote Computer to change the password, or would need to call IT to have the password changed. Starting at RGS 5.1, you can change an expired password from the RGS Receiver.
Page 93: Collaborating
5-5 Collaborating RGS enables the primary user to share his or her desktop session with several local users simultaneously (see Section 2-8-4, “One-to-many connection”). This feature can be used in a variety of collaborative scenarios including classroom instruction, design reviews, and technical support. 5-5-1 Creating a collaboration session A collaboration session is created when one or more local users are authorized by the primary user to connect to the primary user’s desktop session.
Page 94: Collaboration Notification Dialog
Connection between a Local Computer and a Remote Computer is permitted only if the primary user allows the connection. A question dialog, stating the domain and user name of the local user attempting a connection, is displayed on the Remote Computer desktop when a local user attempts to connect (see Figure 5-17). All currently- connected local users will also see this dialog because they are currently viewing the Remote Computer desktop.
Page 95: Figure 5-19 Windows Sender Gui To Disconnect Non-Primary Users
All non-primary users can be disconnected using the Sender GUI. Figure 5-19 shows the Windows Sender GUI selection that can be used to disconnect non-primary users. Figure 5-19 Windows Sender GUI to disconnect non-primary users Prior to RGS 5.2.0, the collaboration notification dialog could not be hidden (although it could be moved elsewhere on the desktop by clicking in the dialog and dragging it).
Page 96: Advanced Capabilities
6 Advanced capabilities This chapter discusses the many advanced capabilities of RGS. Click on the Advanced>>> button in the Receiver Control Panel to display the tabs shown in Figure 6-1. Figure 6-1 Tabs to access advanced RGS capabilities The capabilities available under each of these tabs will be described in detail. Unless required for clarity, the portion of the Receiver Control Panel above the tabs will not be shown.
Page 97: General Options
6-1 General options The options available under the General tab are shown in Figure 6-2. Figure 6-2 General tab options The options available under the General tab are: Prompt for username and password—In certain scenarios (such as silent authentication as described in •...
Page 98: Remote Audio Operation
6-2 Remote audio operation For an overview of remote audio, see Section 2-17, “Remote audio overview.” Before describing the RGS audio capabilities available under the Receiver Control Panel Audio tab, Sender audio configuration and calibration are described. 6-2-1 Configuring audio on the Microsoft Windows XP Professional Sender To configure audio on the Microsoft Windows XP Sender, open the Sound and Audio Devices Properties dialog in the Windows Control Panel, and select the Audio tab (see Figure 6-3).
Page 99: Figure 6-4 Microphone Device Selection And Audio Playback Device Selection On The Sender
Figure 6-4 Microphone device selection and audio playback device selection on the Sender If the Remote Computer doesn’t have an audio device installed, RGS will automatically load the HP Remote Audio virtual device (as described in Audio Playback If the Remote Computer has an audio device device selection below)--therefore, HP Remote Audio installed, it will be the default Sound will be listed in the pull-down menu.
Page 100: Figure 6-5 Recording Control Window
The HP Remote Audio device has only the mixer available in the recording control panel and the volume level for this line cannot be adjusted. If an audio device is detected during installation, an attempt is made to select the mixer as the recorder input.
Page 101: Calibrating Audio On The Microsoft Windows Xp Professional Sender
Press the OK button and the Recording Control window should now have the mixer line as one of the controls (see Figure 6-7). Make sure this item is selected, and the volume level is not at the lowest setting. Figure 6-7 Recording Control window After selecting the mixer, the Sender should record audio information and send it to the Receiver.
Page 102: Figure 6-9 Recording Control Window
The next volume control to adjust is the mixer line in the Recording Control window. The name of this line varies with different audio devices. See the Windows Sender Audio Installation section for information on how to determine the name of this control. For our example, the control is called Wave Out Mix. Adjust this volume control while playing a sound.
Page 103: Disabling Audio On The Sender
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 Properties window, and click on the Sounds tab as shown in Figure 6-10. Figure 6-10 Sound and Audio Devices Properties window Select the Critical Battery Alarm program event, and press the play button (the triangle located next to the Browse...
Page 104: Using Audio
6-2-4 Using audio The audio controls in the Receiver Control Panel are shown in Figure 6-11. Figure 6-11 Audio controls Microphone Button: Click to enable and disable microphone input from the Local Computer to audio playback the Remote Computer. volume control Speaker Button: Click to enable and disable remote audio playback...
Page 105: Potential Audio Issues
Quality—This pull-down menu allows the local user to select one of three different audio quality settings: • Low—Specifies a sampling rate of 11 kHz. • Medium—Specifies a sampling rate of 22 kHz. • High—Specifies a sampling rate of 44 kHz, which is equivalent to CD quality audio. •...
Page 106: Remote Usb Operation
6-3 Remote USB operation For an overview of remote USB, see Section 2-16, “Remote USB overview.” This section provides an example of using remote USB. A USB drive key is plugged into the Local Computer, and remote USB is used to attach the drive key to a Remote Computer. This example assumes the Receiver was installed with the remote USB configuration option shown in Figure 6-12.
Page 107: Attaching A Local Usb Device To A Remote Computer
6-3-1 Attaching a local USB device to a Remote Computer The options available under the USB tab in the Receiver Control Panel are shown in Figure 6-13. Figure 6-13 USB tab options The USB options are: Enable Remote USB—This checkbox can be used to dynamically (during an active RGS connection) enable •...
Page 108: Figure 6-14 Prior To Remote Attachment Of The Usb Drive Key
Figure 6-14 shows the presence of the USB drive key on the Local Computer before the remote USB attachment is made. Figure 6-14 Prior to remote attachment of the USB drive key Remote Computer Local Computer To connect the USB drive key to a Remote Computer in Directory Mode, perform the following steps: Click the USB tab on the Receiver Control Panel.
Page 109: Usb Session Switching
6-3-2 USB session switching New with RGS 5.1.3 is the ability to dynamically move USB devices from one Remote Computer to another. This enables USB devices to be detached from one Remote Computer, and made accessible by another Remote Computer without first needing to disconnect the RGS connections. To move USB devices to a different Remote Computer in Directory Mode, simply specify the new Remote Computer (Sender) in the Select sender: dropdown menu (see Figure 6-16).
Page 110: Supported Remote Usb Devices
In the DWORDS created in Step 3, insert the ProductID and VendorID for the USB device that you want auto remoted. To find the ProductID and VendorID of your USB device, perform the following steps: Open Device Manager and find the USB device to be auto-remoted. Right click the USB device and select Properties.
Page 111: Remote Usb Access Control List
Therefore, a deny rule takes precedence over an allow rule. The ACL file is implemented as an XML (Extensible Markup Language) file. The ACL schema file is located at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\hprUsbAcl.xsd For backwards compatibility, the following default ACL file(installed during Sender installation) allows all USB connections to be made: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\hprDefaultUsbAcl.xml...
Page 112 Rules may contain filters based on the 11 parameters listed previously. These parameters are repeated below along with the name of the filter element. Device Class—bDeviceClass Device Subclass—bDeviceSubclass Device Protocol—bDeviceProtocol Vendor ID—idVendor Product ID—idProduct Device BCD—bcdDevice Manufacturer—manufacturer Product Type—product Serial Number—serialNumber CAUTION: Filtering on device strings (manufacturer, product, and serial number) may not be reliable.
Page 113: Determining Usb Device Information
6-3-6 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: Open the device manager.
Page 114: Troubleshooting Remote Usb
The registered classes and subclasses are documented by the USB Device Working Group. The DWG's latest document for 1.0 defined class codes is hosted at: www.usb.org/developers/defined_class 6-3-7 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.
Page 115: Figure 6-17 Checkbox To Enable Remote Usb
Enable Remote USB Verify that Remote USB is enabled under the USB option tab of the Receiver Control Panel (see Figure 6-17). Figure 6-17 Checkbox to enable Remote USB Advanced capabilities 115...
Page 116: Figure 6-18 Hp Remote Virtual Usb Driver
HP Remote Virtual USB Driver Verify that the HP Remote Virtual USB driver is installed and active on the Remote Computer. Open the Windows Device Manager, and verify that HP Remote Virtual USB is listed under Universal Serial Bus Controllers (see Figure 6-18).
Page 117 USB device drivers and program support Verify that the device drivers and programs required by the device are installed and available on the Sender system. Many USB devices require manufacturer-supplied software to work on a system. This software must often be installed before the USB device is connected to the system.
Page 118: Adjusting Network Timeout Settings
6-4 Adjusting Network timeout settings The options available under the Network tab in the Receiver Control Panel are shown in Figure 6-20. Figure 6-20 Options available under the Network tab RGS supports three classes of user-settable timeouts: Receiver network timeout properties—After the Receiver has established a connection to the Sender, the Sender transmits sync pulses (consisting of network messages) to the Receiver every second to permit the Receiver to determine connection integrity.
Page 119: Figure 6-21 Receiver Control Panel
Receiver network timeouts RGS provides two user-settable Receiver timeout properties to allow you to optimize RGS for your particular network conditions (such as low-bandwidth or high-latency conditions). These properties allow you to specify timeout values that, if exceeded, will cause the RGS Receiver to take specific actions, such as displaying a warning dialog or closing the RGS connection.
Page 120: Figure 6-22 Receiver Timeout Sequence
Figure 6-22 shows the sequence of events commencing when sync pulses cease being detected by the Receiver. Figure 6-22 Receiver timeout sequence • TCP/IP stack may detect & resolve problems. • Network disruption may not be noticeable. • Serious network problems may cause the RGS connection to close.
Page 121 Sender network timeout The RGS Sender supports the Sender error timeout property, Rgsender.Network.Timeout.Error. This property can be set only by using the rgsenderconfig file or on a command line—the Sender doesn’t have a dialog to set this property. The Sender error timeout property is independent of the Receiver timeout properties. For legacy reasons, the Sender begins by using the maximum of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.Dialog property (see Section 6-4-2, “Dialog...
Page 122 Network timeout issues Listed below are several timeout-related issues and their potential causes. Remote Display Window repeatedly dims, and displays a connection warning message—This is likely caused • by frequent network disruptions between the Receiver and Sender. The dimming of the display serves as a notification to the user that the Remote Display Window may contain stale information.
Page 123: Dialog Timeouts
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 Section 6-4, “Network timeouts,” for further details on setting timeouts. 6-4-2 Dialog timeouts RGS supports dialog timeouts, which specify how long user interactions between the Local Computer and Remote Computer are allowed to take.
Page 124: Hotkeys
6-5 Hotkeys 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-23).
Page 125: Changing The Setup Mode Hotkey Sequence
Setup Mode Hotkey: The text dialog and the Set and Reset buttons allow you to redefine the Setup Mode • hotkey sequence from its default value. As shown in the Receiver Control Panel of Figure 6-23, the default hotkey sequence to activate Setup Mode is: Press and hold down the Shift key.
Page 126: Remote Clipboard Operation
6-6 Remote Clipboard operation For an overview of Remote Clipboard, see Section 2-18, “Remote Clipboard overview.” Remote Clipboard enables you to cut or copy data between a window on the Local Computer and a Remote Window (provided that the applications being used support cut/copy/paste functionality). Beginning with RGS 5.3.0, Remote Clipboard cut and paste of ANSI text data is supported between Microsoft Windows Receiver systems and Linux Sender systems.
Page 127: Remote Clipboard Data Transfers
6-6-1 Remote Clipboard data transfers Figure 6-25 shows the data transfer that occurs when a cut and paste is performed using Remote Clipboard. In this example, the cut occurs from within the Remote Computer application (as initiated from the Remote Display Window), and the paste occurs into the Local Computer application (via the Local Window).
Page 128: Figure 6-26 Cut And Paste Computer Nomenclature
As we’ve seen, the terms “Remote Computer” and “Local Computer” have very specific meanings in the context of RGS. In the context of Remote Clipboard, however, we use terms that are centric to each computer involved in a Remote Clipboard operation. If a cut and paste is being performed from Computer A to Computer B, Computer A will refer to itself (for example, in the DEBUG LOG) as the local computer, while referring to Computer B as the remote computer.
Page 129: Remote Clipboard Filtering
6-6-2 Remote Clipboard filtering When a cut is performed, applications typically store their data in the clipboard in multiple formats. For a word processing application, the application might store data in the clipboard as both ASCII text and Rich Text Format. This increases the likelihood that, when the paste occurs, there will be a format recognized by the receiving application.
Page 130: Using The Rgs Log To Detect Clipboard Problems
16 (CF_LOCALE)—Locale identifier associated with text in the clipboard • 17 (DIBV5)—Bitmap color space and bitmap data • Ole Private Data—A private application format understood only by the application offering the format. • Object Descriptor—OLE2 object descriptor • Link Source Descriptor—Link to OLE2 object •...
Page 131: Figure 6-30 Transmission Of The Filter String Property From The Rgs Receiver To The Rgs Sender
To demonstrate use of the RGS logs to view Remote Clipboard information on the Receiver and Sender computers, an example is presented in which a copy and paste is performed from a Sender computer to a Receiver computer. The steps in this example are: 1.
Page 132: Figure 6-31 Remote Clipboard Log Entries For Cut And Paste
Now that the filter string has been sent from the Receiver to the Sender, we’ll switch to the Remote Clipboard nomenclature of Figure 6-28. Figure 6-31 shows the Remote Clipboard log entries as the cut and paste is performed. Figure 6-31 Remote Clipboard log entries for cut and paste sending computer, receiving computer,...
Page 133: Receiver And Sender Logging
6-7 Receiver and Sender logging Both the RGS Receiver and the RGS Sender have the ability to log various types of information to files during their operation. Receiver logging can be enabled from the Receiver Control Panel, while Sender logging is controlled by a file on the RGS Sender.
Page 134: Sender Logging
INFO debug level. Unless this command line option is used to change the logSetupFile file, the default logSetup file in the Sender installation folder (C:\Program Files\Hewlett-Packard\Remote Graphics Sender) is used. The first few lines of logSetup are shown in Figure 6-33.
Page 135: Statistics
6-8 Statistics The options available under the Statistics tab in the Receiver Control Panel are shown in Figure 6-34. Figure 6-34 Options available under the Statistics tab The Statistics tab displays aggregate data for all connected sessions. Total network usage (Mbits/sec)—The combined network traffic received from all Remote Computers. •...
Page 136: Using Directory Mode
Remote Computer. The directory file may contain multiple users with a list of Remote Computers assigned to each user. The default directory file used by the Receiver is: C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\directory.txt After the directory file name is determined, the Receiver automatically connects to the Remote Computers specified in this file for the named user.
Page 137: Starting The Receiver In Directory Mode
Starting the Receiver in Directory Mode Alternatively, the Receiver can be started in Directory Mode from a command line, using either of the following: C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\rgreceiver.exe -directory “file” C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\rgreceiver.exe -directory If a file name is specified after -directory, the Receiver will use that file as the directory file. If no file name is specified, the user is prompted by RGS to specify the path and name of the directory file.
Page 138: Selecting Remote Display Windows While In Directory Mode
7-1-3 Selecting Remote Display Windows while in Directory Mode Activate Setup Mode by the hotkey sequence (as opposed to the Setup Mode button), to bring up the Remote Display Window selection dialog to view a thumbnail image of each Remote Display Window Figure 7-3 Remote Display Window selection dialog To display the selection dialog, press the TAB key while in Setup Mode—again, Setup Mode must have been...
Page 139: Rgs Properties
RGS Sender uses the file rgsenderconfig file for its properties. On Windows, these files are located in the directory where the RGS Receiver and Sender are installed, typically: Receiver: C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\rgreceiverconfig Sender: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgsenderconfig...
Page 140: Setting Properties On The Command Line
8-3 Setting properties on the command line Properties can also be set on the command line when the Receiver and Sender are started. Property values entered on the command line override any properties set with other methods. All properties must begin with a "-" on the command line to be recognized as a valid property.
Page 141: Rgs Receiver Properties
8-5 RGS Receiver properties This section describes the RGS Receiver properties. RGS supports two types of Receiver properties: Per-Receiver properties—The per-Receiver properties affect all Remote Display Windows generated by the • Receiver. As noted in Section 2-8-3, “Many-to-one connection,” a Receiver can connect to multiple Remote Computers (and therefore generate multiple Remote Display Windows).
Page 142: Receiver Property Groups
8-5-2 Receiver property groups RGS supports the following groups of Receiver properties. Click on each group name to view the descriptions of the properties in the group. Per-receiver properties • General properties group • • Rgreceiver.IsBordersEnabled • Rgreceiver.IsSnapEnabled • Rgreceiver.IsAlwaysPromptCredentialsEnabled •...
Page 143 Remote Clipboard properties group (see below for the per-session Remote Clipboard property) • • Rgreceiver.Clipboard.IsMutable • Rgreceiver.Clipboard.IsEnabled • Rgreceiver.Clipboard.FilterString Logging properties group • • Rgreceiver.Log.IsMutable • Rgreceiver.Log.IsFileLoggerEnabled • Rgreceiver.Log.IsConsoleLoggerEnabled • Rgreceiver.Log.Filename • Rgreceiver.Log.Level • Rgreceiver.Log.MaxFileSize • Rgreceiver.Log.NumBackupFiles Image codec properties group •...
Page 144: Figure 8-2 The Receiver Timeout Error Ismutable Property Is Set To 0
In Figure 8-2, the Receiver is started with the command line option –Rgreceiver.Network.Timeout.Error.IsMutable=0, which prevents the user from changing the value of the network timeout error property. Figure 8-2 The Receiver timeout error IsMutable property is set to 0 Because the Receiver timeout error property IsMutable property is 0, the Receiver timeout error property cannot be changed by the user in the Receiver Control Panel (see Figure 8-3).
Page 145: Receiver General Properties
8-5-3 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.
Page 146 Rgreceiver.IsMatchReceiverPhysicalDisplaysEnabled=bool Rgreceiver.IsMatchReceiverPhysicalDisplaysEnabled.IsMutable=bool If the following conditions are met: This property is enabled. Rgreceiver.IsMatchReceiverResolutionEnabled is enabled (see previous property). Rgreceiver.Session.<N>.VirtualDisplay.IsPreferredResolutionEnabled is disabled. 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.
Page 147 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 Section 8-5-13, “Windows placement and size properties.” Rgreceiver.RecentWindowPositions=int vector (10 10) Rgreceiver.RecentWindowPositions.IsMutable=bool 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.
Page 148: Figure 8-5 Prior To Rgs 5.1.3, Only One Image Update Would Be In-Process At Any Time
Rgreceiver.IsGlobalImageUpdateEnabled=bool Rgreceiver.IsGlobalImageUpdateEnabled.IsMutable=bool 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.
Page 149: Figure 8-6 Sequence Chart For The Default Property Value Of 4
The sequence chart in Figure 8-6 shows operation for the default property value of 4. In this case, the Receiver can have up to 4 image update requests outstanding at any given time. When image update response #1 is received (meaning that there are now 3 outstanding image update requests), the Receiver can issue image update request #5 (again, up to a maximum of 4 outstanding image update requests at any given time).
Page 150: Receiver Browser Properties
Rgreceiver.IsMouseSyncEnabled=bool Rgreceiver.IsMouseSyncEnabled.IsMutable=bool This property was added with RGS 5.2.5, and allows the RGS Receiver to track a certain type of mouse movement on the RGS Sender when the Sender computer is running Windows. The Sender mouse movement of interest is enabled when the Snap To box is checked in the Mouse Properties Pointer Options dialog on the Sender computer (see Figure 8-7).
Page 151: Receiver Audio Properties
8-5-5 Receiver audio properties Rgreceiver.Audio.IsMutable=bool If set to 1, the user will be able to modify all audio controls in the RGS Receiver. If set to 0, none of the audio controls can be modified by the user. The default value is 1—the audio controls can be modified by the user. Rgreceiver.Audio.IsEnabled=bool Rgreceiver.Audio.IsEnabled.IsMutable=bool If set to 1, the RGS audio subsystem will be enabled.
Page 152: Receiver Network Properties
Rgreceiver.Usb.ActiveSession=int Rgreceiver.Usb.ActiveSession.IsMutable=bool When the Receiver is in Directory Mode, the Local Computer can connect to one or more Remote Computers. This property specifies the Remote Computer that the local USB devices are attached to. To have all local USB devices attached to the first Remote Computer, use value zero.
Page 153: Receiver Remote Clipboard Properties
Rgreceiver.Hotkeys.IsSendFirstKeyInSequenceEnabled=bool Rgreceiver.Hotkeys.IsSendFirstKeyInSequenceEnabled.IsMutable=bool When enabled, the first key in the hotkey sequence is sent to the Remote Computer. The default value is 0—don't send the first key in the hotkey sequence. Rgreceiver.Hotkeys.IsKeyRepeatEnabled=bool Rgreceiver.Hotkeys.IsKeyRepeatEnabled.IsMutable=bool The hotkey sequence is very particular (for example, shift down, space down, space up). The Windows operating system injects key repeats as repeating down events, for example, shift down, shift down, …, shift up.
Page 154: Receiver Logging Properties
(see below for default value) Rgreceiver.Clipboard.FilterString=string IMPORTANT: 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.
Page 155: Receiver Image Codec Properties
This property specifies the path to the log file, and is only used if RgReceiver.Log.IsFileLoggerEnabled is set to 1. The default path on Windows is located in the directory where the RGS Receiver is installed, normally C:/Program Files/Hewlett-Packard/Remote Graphics Receiver/rg.log. The default path on Linux is $HOME/.hpremote/rgreceiver/rg.log.
Page 156: Windows Placement And Size Properties
8-5-13 Windows placement and size properties As described previously, these properties are per-session (per-connection) properties. If, for example, the Receiver connects to two Remote Computers, these properties can be used to specify the properties of each of the two Remote Display Windows on the Local Computer. These properties contain the parameter <N>, which ranges from 0 to N-1 for the creation of N sessions (connections).
Page 157: Rgs Sender Properties
8-6 RGS Sender properties RGS supports the following hierarchy of methods to set the Sender properties (see Figure 8-8). Figure 8-8 Sender properties hierarchy Highest Sender command line properties rgsenderconfig file properties Sender default properties Lowest Properties set by methods higher on the list override properties set by methods lower on the list. For example, a Sender command line property can override a property specified in the rgsenderconfig file.
Page 158: Sender General Properties
USB access control list properties group • • Rgsender.Usb.Acl.RulesetPath • Rgsender.Usb.Acl.SchemaPath • Rgsender.Usb.Acl.RulesetErrorTimeout NIC binding properties group • • Rgsender.Network.IsListenOnAllInterfacesEnabled • Rgsender.Network.Interface.n.IsEnabled • Rgsender.Network.AllowIpAddressSubnet • Rgsender.Network.Port Clipboard property group • • Rgsender.Clipboard.IsEnabled 8-6-2 Sender general properties Rgsender.IsRdpLogoutDetectionEnabled=bool This property only applies to the Windows versions of the RGS Sender. When a user disconnects from a Remote Desktop Protocol (RDP) session, the Windows desktop on the Remote Computer is immediately available for an RGS connection.
Page 159 NOTE: Beginning at RGS 5.2.5, the default value of the following property has been changed from 0 to 30. Rgsender.MaxImageUpdateRate=int (30) This property limits the number of image updates per second transmitted from the Remote Computer to the Local Computer. The value is the maximum number of updates per second. If the image update rate is too high, and using too much network bandwidth, the MaxImageUpdateRate can be set to limit the number of image updates per second.
Page 160: Sender Microphone Property
Rgsender.IsCollaborationNotificationEnabled=bool Introduced at RGS 5.2.0, this property allows the user to enable or disable display of the collaboration notification dialog (see Section 5-5-2, “Collaboration notification dialog”). If set to 1, the collaboration notification dialog is displayed. If set to 0, the collaboration notification dialog is not displayed. The default value is 1— display the collaboration notification dialog.
Page 161: Sender Network Timeout Properties
8-6-4 Sender network timeout properties Rgsender.Network.Timeout.Error=int (30000) The timeout in milliseconds used to detect and disconnect an inactive connection. The default value is 30,000 milliseconds (30 seconds). See Section 6-4, “Network timeouts,” for more details. Rgsender.Network.Timeout.Dialog=int (15000) The timeout in milliseconds used to display and wait on responses from input dialogs, such as the authorization dialog and PAM authentication dialog.
Page 162: Sender Clipboard Property
Rgsender.Network.AllowIpAddressSubnet=string (all IP addresses) This property is used to specify the range of IP addresses that the Sender will listen on for an RGS connection request from the Receiver. A NIC must be enabled, and its IP address must be in the range specified by this property, in order for the Sender to listen on the NIC.
Page 163: Sender Event Logging On Windows
9 Sender event logging on Windows 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 chapter describes the Sender event logging capabilities while the next chapter describes how to use event logging to terminate applications on the Sender.
Page 164: Figure 9-2 Event Properties Window
To view the properties of a particular event, double-click the event of interest—this brings up the Event Properties window. Figure 9-2 shows the Event Properties window for the highlighted event in Figure 9-1. As you can see, the event that has been logged is the Sender connection state. Figure 9-2 Event Properties window The highlighted radio buttons allow viewing of the connection data (in this case, the number of primary and non-...
Page 165: Usages Of The Hpremote Log
Whenever the Local Computer (Receiver) either establishes a connection to the Sender or disconnects from the Sender, the IP address and port number of the Local Computer are logged in the HPRemote log. At RGS 5.2.5, logging of the hostname was added to the HPRemote log. In Figure 9-3, a connection has been established to the Sender from a Local Computer with IP address 16.125.19.100, port number 1069, and hostname HP18009285527.
Page 166: Additional Information On Event Logging
9-3 Additional information on event logging For additional information on Windows event logging, search Microsoft Developer Network (MSDN) as shown in Figure 9-4. Clicking on the first search result will typically display the page shown. Figure 9-4 MSDN event logging information Search criteria: Page typically displayed by the first search result: Sender event logging on Windows 166...
Page 167: Remote Application Termination
10 Remote Application Termination This chapter 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). The sample agent described in this chapter is designed to terminate applications on the Sender when an RGS disconnect occurs.
Page 168 Event Viewer Example: Primary connections: 1 Non-primary connections: 0 A new connection was established with an associated name. If Easy RGSENDER_CONNECT Login is enabled, the name assignment will be deferred until login and the associated name may be “Anonymous”. EventID: 4 Event Viewer Message: Connect %1.
Page 169 A connection with an associated name is assigned to a non-primary RGSENDER_SET_NONPRIMARY status. This may happen as a result of a logout. EventID: 7 Event Viewer Message: Set %1 as non-primary connection. Strings: %1 = name associated with connection Data: None Event Viewer Example: Set MYDOMAIN\myusername as non-primary connection.
Page 170: Sample Agent
Figure 9-4. The sample agent is listed below. Where noted, user-specific code should be added. The agent header file, RGSenderEvents.h, is installed with the RGS Sender and is located at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\include\RGSenderEvents.h #include <windows.h> #include <stdio.h> #include "RGSenderEvents.h"...
Page 171 // Set the pointer to our buffer. Strings and data will get appended // to the EVENTLOGRECORD structure. pevlr = (EVENTLOGRECORD *) &bBuffer; // Read the event specified by dwEventNum result = ReadEventLog(h, // event log handle EVENTLOG_SEEK_READ | // start at specific event EVENTLOG_FORWARDS_READ, // advance forward dwEventNum, // record to read...
Page 172 // 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);...
Page 173: Agent Design Issues
10-4 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. Listed below are several topics to consider when designing application control agents for your environment.
Page 174: Additional Safeguard Features For Windows Systems
Administrator alerts Situation—Instead of shutting down an environment, an agent can be designed to alert an administrator or • operator to determine the status of the user before taking action. This watchdog approach can further be defined to exploit redundant network connection support to a remote system to allow user-directed shutdowns to occur.
Page 175: Figure 10-1 Remote Computer Sender Recovery Options
Figure 10-1 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. Remote Application Termination 175...
Page 176: Optimizing Rgs Performance
11 Optimizing RGS performance This chapter provides suggestions on optimizing RGS performance, including optimizing the Remote Computer display settings and the network configuration. 11-1 Performance tuning for all platforms The following suggestions apply to all platforms: Set the network to full-duplex mode—To obtain the best performance, the network between the RGS Sender •...
Page 177: Troubleshooting Graphics Performance
java SomeApp 11-3 Troubleshooting graphics performance The dominant factor impacting performance on the Sender is the frame buffer read performance of the graphics adapter. Frame buffer read performance of at least ten frames per second is recommended for optimum RGS performance.
Page 178 or network is not configured correctly. Work with your IT organization to optimize your computer and network configuration. Optimizing RGS performance 178...
Page 179: Troubleshooting Rgs
12 Troubleshooting RGS This chapter provides suggestions on troubleshooting potential issues with RGS. Refer also to Chapter 13, “RGS error messages,” which lists the RGS error messages and their potential causes. 12-1 Potential RGS issues and troubleshooting suggestions Table 12-1 lists several potential RGS issues, and provides a number of troubleshooting suggestions. Table 12-1 Potential RGS issues and troubleshooting suggestions Issue...
Page 180: Rgs Error Messages
13 RGS error messages This chapter lists the error messages reported by the RGS Receiver, and describes potential reasons for the error messages. 13-1 Receiver error messages The following table lists the errors that are reported by the RGS Receiver on the Local Computer. Error Description Connection lost!
Page 181 Directory not found or not The directory file is not available. Possible reasons include: accessible! The directory file name or location has been mistyped. The file has been moved or is no longer available. The network is down or experiencing a disruption. The user does not have read permission on the file.
Page 182 Connection denied! The The iLO remote console is enabled on the HP Blade Workstation. The iLO remote console is Blade must be configured in User Mode before connections are enabled. allowed. Unable to connect to This is usually indicative of a DNS error. Sender: The Receiver was unable to resolve the specified...
Page 183: Appendix A: Using Rgs With Hp Vdi
Appendix A: Using RGS with HP VDI This appendix describes how to use RGS with the HP Virtual Desktop Infrastructure (VDI) solution. Using RGS with HP VDI assumes you have a comprehensive working knowledge of VMware’s virtualization products and running Microsoft products within the VMware virtualization environment.
Page 184: Vmware Esx Networking Considerations
Table A-2 shows the VMware View versions that support RGS. Only VMware View 3.1 (and newer versions) support RGS, and only with RGS 5.2.5 (and newer versions), as shown in the green cell. Table A-2 VMware View versions that support RGS RGS 5.2.4 and older RGS 5.2.5 and newer VMware View 3.0 and older...
Page 185: A-2-2 Modify The Vmware Esx Configuration (.Vmx File)
A-2-2 Modify the VMware ESX configuration (.vmx file) The underlying virtual machine configuration file must be modified to support RGS and USB devices over the RGS communication channel. Most values in this file can be set using the Virtual Center GUI. However, a few values must be set by manually editing the .vmx file of the virtual machine.
Page 186 Click the Configuration Parameters button in Figure A-1 to display the configuration parameters shown in Figure A-2. Figure A-2 Configuration Parameters dialog IMPORTANT: Not all configuration parameters can be added using the dialog shown above. Please see VMware View documentation for more details. When adding Svga options, it is recommended that you do this by manually editing the .vmx file.
Page 187: A-2-3 Installing The Rgs Sender On The Virtual Machine
Svga.vramSize = <size in bytes of the VGA screen buffer> This parameter tells the VMware virtual VGA device driver the size of screen buffer to use. This value may only be set by directly editing the .vmx file of the virtual machine and is not propagated by clone and template operations. The default maximum screen resolution for ESX 3.0.1 running XP images is 1180x885 with 16 or 32 bit color depth.
Page 188: A-3-1 Create A New Virtual Machine
Optional: To allow RGS to automatically detect your client screen resolution, follow this procedure on your client computer: Locate the RGS Receiver configuration file, rgreceiverconfig, at “C:\Program Files\Hewlett-Packard\Remote Graphics Receiver”. Right click on the file and remove the Read Only property. Edit the rgreceiverconfig file by un-commenting and modifying the following line to have a value of 1: Rgreceiver.IsMatchReceiverResolutionEnabled=1...
Page 189: Running Rgs Diagnostics
Install the View Client on the client computer. A-4 Running RGS diagnostics You should run the RGS diagnostics utility, rgdiag.exe, following installation of the RGS Sender to determine what additional OS configuration needs to be done to properly support RGS in the VDI environment. OS configuration typically includes the following: Firewall configuration to allow rgsender.exe to pass through.
Page 190: Appendix B: Usb Devices Supported By Rgs
Appendix B: USB devices supported by RGS IMPORTANT: Prior to RGS 5.2.0, this list of USB devices was maintained in a separate document available at www.hp.com/support/rgs_manuals, titled USB Devices Supported by Remote Graphics Software. The list itself was an Excel spreadsheet with an internal description of “Client-attached USB Devices Accessible by the RGS Sender”.
Page 191 Table B-2 Trader keyboards Clients based on Windows XP and USB Devices HP Blade Workstation Clients Windows XPe Notes Bloomberg CTB100 US/UK RGS 4.0.0 RGS 5.0 Support for audio was Bloomberg SEA100 US/UK RGS 5.0 RGS 5.0 added at RGS 5.2.0 Bloomberg FRE100 US/UK RGS 5.2 RGS 5.2...
Page 192 Table B-6 USB keys The following client-attached USB devices can be accessed by a Remote Computer running Windows XP Professional x64 Edition if the RGS Sender version is 5.1.1 or later. Clients based on Windows XP USB Devices HP Blade Workstation Clients and Windows XPe Notes SanDisk...
Page 193 Table B-11 Printers Clients based on Windows USB Devices HP Blade Workstation Clients XP and Windows XPe Notes HP OfficeJet 9110 RGS 5.0 RGS 5.0 HP Photosmart 8750 RGS 5.0 RGS 5.0 HP LaserJet 3000DN RGS 5.0 RGS 5.0 HP Color LaserJet 2820 RGS 5.0 RGS 5.0 HP Business Inkjet 2800...
Page 194 Table B-15 Webcams HP Blade Workstation Clients based on Windows USB Devices Clients XP and Windows XPe Notes Logitech QuickCam Communicate RGS 5.2 RGS 5.2 Deluxe WebCam RGS 5.2 RGS 5.2 Microsoft RoundTable WebCam Logitech QuickCam Pro5000 RGS 5.2 RGS 5.2 WebCam Logitech Pro9000 WebCam RGS 5.2...
Page 195 Table B-19 Character input devices Clients based on Windows USB Devices HP Blade Workstation Clients XP and Windows XPe Notes Elan Crystal Touch Pen Pad RGS 5.2 RGS 5.2 Appendix B: USB devices supported by RGS 195...
Page 196: Appendix C: Linux Remote Audio Device Support
Appendix C: Linux remote audio device support As shown in Figure 2-23, an audio device is required to be installed in Linux-based Remote Computers in order for application-generated 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.

This manual is also suitable for:

Proliant xw2x220c - blade workstation Remote graphics software 5.3.0 Rgs 5.3.0

HP Xw460c - ProLiant - Blade Workstation User Manual

1 Introduction to HP Remote Graphics Software

2 RGS Overview

3 Installing RGS

4 Pre-Connection Checklist

5 Using RGS

6 Advanced Capabilities

7 Using Directory Mode

8 RGS Properties

9 Sender Event Logging on Windows

10 Remote Application Termination

11 Optimizing RGS Performance

12 Troubleshooting RGS

13 RGS Error Messages

Appendix A: Using RGS with HP VDI

Quick Links

Troubleshooting

Related Manuals for HP Xw460c - ProLiant - Blade Workstation

Summary of Contents for HP Xw460c - ProLiant - Blade Workstation