HP Remote Graphics Software 5.4.
© Copyright 2010-2012 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
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 Introduction to HP Remote Graphics Software ................................................................... 1 Typical RGS configuration ......................................................................................................... 3 RGS Sender and Receiver ......................................................................................................... 4 RGS features ..................................................................................................
Remote Computer monitor blanking overview ............................................................................ 28 Video overlay surfaces ............................................................................................................ 28 Image quality ........................................................................................................................ 29 Remote USB overview .................................................................................................
Manually enabling Single Sign-on (Windows XP Professional only) .. 68 Setting the local security policy (Windows XP Professional only) ...... 69 Disabling Single Sign-on ........................................................................... 69 Using the rgadmin tool to disable Single Sign-on ........................... 69 Manually disabling Single Sign-on (Windows XP Professional only) ........................................................................................
Network Interface binding on the Sender .................................................................................. 94 Manual Network Interface reconfiguration ................................................................. 94 Network Interface reconfiguration using the Sender network interface binding properties .............................................................................................................. 97 Using RGS through a firewall .............................................
Attaching a local USB device to a Remote Computer ................................................. 138 USB session switching ............................................................................................ 139 Local/Remote USB Device Management .................................................................. 140 Supported remote USB devices ............................................................................... 141 Remote USB Access Control List .......................................
Setting properties on the command line .................................................................................. 175 Authenticator properties ........................................................................................................ 176 RGS Receiver properties ....................................................................................................... 176 Receiver property hierarchy ....................................................................................
Agent design issues .............................................................................................................. 217 Desktop session logout ........................................................................................... 217 Selective environment shutdown .............................................................................. 217 Wrapping applications of interest ........................................................................... 218 Administrator alerts .........
List of tables Table 2-1 Computers and operating systems that support RGS 5.4.8 Receiver ............................................ 10 Table 2-2 Computers and operating systems that support RGS 5.4.8 Sender .............................................. 11 Table 2-3 RGS support requirements ..................................................................................................... 12 Table 2-4 Receiver remote USB support ...................................................................
List of figures Figure 1-1 Typical RGS configuration ...................................................................................................... 3 Figure 1-2 RGS Sender and Receiver ...................................................................................................... 4 Figure 1-3 Features of RGS .................................................................................................................... 5 Figure 2-1 RGS version numbering ...........................
Figure 3-3 Dialog to enable or disable Remote USB in the Sender ............................................................ 59 Figure 3-4 Dialog to enable Single Sign-On or Easy Login ....................................................................... 60 Figure 3-5 Configuration of the RGS Sender license ................................................................................ 61 Figure 3-6 The Remote Graphics Sender service ................................................................
Figure 5-14 Multiple local users can view and interact with the primary user's desktop .............................. 114 Figure 5-15 Disabling of the local users’ mice and keyboards by the primary user .................................... 115 Figure 5-16 Primary user dialog to authorize a local user to connect to the primary user’s desktop ............. 115 Figure 5-17 Collaboration notification dialog displayed on the Sender and in each Remote Display Window .........................................
Figure 6-35 logSetup file ................................................................................................................... 168 Figure 6-36 Options available under the Statistics tab ........................................................................... 169 Figure 7-1 Starting the Receiver in Directory Mode ............................................................................... 172 Figure 7-2 The Receiver Control Panel in Directory Mode .................................
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.
Chapter 6: Advanced capabilities on page 118—This chapter describes the RGS advanced capabilities that are provided by each of the tabs in the Receiver Control Panel. Chapter 7: Using Directory Mode on page 170—Establishing RGS connections using Directory Mode is described in this chapter. Chapter 8: RGS properties on page 174—This chapter describes each of the RGS Sender and Receiver properties.
Typical RGS configuration The following illustration shows a typical RGS configuration, consisting of a remote computer (sender) and a local computer (receiver). In this example, the sender is the personal workstation on the left and the receiver is the mobile workstation on the right. The user’s applications run on the sender while the user interacts with these applications from the receiver.
RGS Sender and Receiver Figure 1-2 RGS Sender and Receiver on page 4 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 The Sender and Receiver provide the following functionality: ● Sender—Runs on the Remote Computer, and transmits graphics updates, audio, and USB data to the RGS Receiver on the Local Computer.
RGS features RGS supports a number of features designed to optimize performance, security, and functionality (see Figure 1-3 Features of RGS on page 5). Figure 1-3 Features of RGS ● Application transparency—RGS supports application transparency, which enables applications to be run on the Remote Computer, and accessed from the Local Computer, without modifications.
Additional RGS features RGS provides many additional features, including: ● 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 attached to and accessed by the Remote Computer.
Tabloid-size page The PDF version of this guide contains a tabloid-size page that is best viewed either on your computer monitor or by printing it on size B (11 inches by 17 inches) or ISO A3 (297 mm by 420 mm) paper. The tabloid page is included to permit a complex diagram (the diagram on the last page) to be documented on a single page while maintaining readability. The tabloid page from the PDF document may be printed individually if you have access to a tabloidcapable printer.
Software service strategy for non-HP hardware RGS 5.4.8 and later is designed for and compatible with the following Microsoft® Windows operating systems on hosted OS Virtual Machine and physical machine environments: ● Windows® XP Professional 32- and 64-bit ● Windows 7 Professional and Enterprise 32- and 64-bit ● Red Hat Enterprise Linux V5 and V6.
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.
● Interoperability of RGS and Microsoft Remote Desktop Connection on page 48 ● Remote Computer power saving states on page 48 ● Supported keyboard locales on page 49 ● RGS security features on page 50 This chapter provides an overview of each of these features. For a description of new features and other late-breaking topics, see the README.txt file in the installation directory of either the RGS Receiver or RGS Sender. The file is best viewed using Wordpad, Microsoft Word or Openoffice swriter.
Table 2-2 Computers and operating systems that support RGS 5.4.8 Sender Sender Platforms Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows 7 Professional and Enterprise 32-bit and 64-bit RHEL V5.2 or later; V6.
RGS support requirements Table 2-3 RGS support requirements Operating System Bare Metal Citrix XenServer v6 VMWare vSphere (ESX) v5.
Figure 2-1 RGS version numbering on page 13 shows the positioning of the three version numbers. Figure 2-1 RGS version numbering RGS version description 1. Major – A major release contains sufficient changes such that interoperability with the prior primary release is not guaranteed. For example, Sender version 5.4.0 is not guaranteed to interoperate with Receiver version 4.2.0. A major release introduces significant new RGS features and functionality.
RGS licensing NOTE: RGS licensing applies to the RGS Sender only. The RGS Receiver is a free download and can be used on any number of computers. Therefore, the following discussion of RGS licensing applies only to the RGS Sender. For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide, available at http://www.hp.com/support/rgs_manuals. Two types of licenses are supported by the RGS Sender: 1.
RGS products HP offers these RGS products : 1. HP RGS Desktop Trial Edition — HP offers a free, 60-day trial version of RGS Desktop; no license purchase is required. 2. HP RGS VDI local license — This RGS product runs on Citrix XenDesktop and VMware VDI (Virtual Desktop Infrastructure) platforms. RGS VDI uses a local license file key. A separate RGS VDI license is required for each virtual machine using RGS. 3.
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 Professional command prompt window is created (using cmd.exe or the command prompt icon), the window will also be reset to its default size by RGS.
Remote Computer video adapter that holds the bitmapped image that is typically displayed on a monitor—the frame buffer below contains the familiar Windows desktop (see Figure 2-3 The Remote Computer frame buffer containing the Windows desktop on page 17). Figure 2-3 The Remote Computer frame buffer containing the Windows desktop The monitor itself is optional on the Remote Computer.
size of the Local Computer monitor (as measured in horizontal pixels by vertical pixels). As before, the Remote Display Window will be the size of the Remote Computer frame buffer. If the Remote Display Window is larger than the Local Computer monitor, the window will extend off the monitor.
Directory Mode. The frame buffer of each Remote Computer is displayed in a separate Remote Display Window on the Local Computer. Figure 2-6 A Local Computer displaying two 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 Directory Mode on page 170 . The many-to-one connection capability allows implementation of a virtual KVM (keyboard, video, and mouse) switch.
Remote Computer, and two local users who are viewing the primary user’s desktop session on the Remote Computer. Figure 2-7 Multiple users can access the desktop of a Remote Computer 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).
from the Remote Computer. RGS can be used by local users 1 and 2 to connect to the primary user’s desktop. NOTE: One-to-many (collaboration) requires a unique login account with credentials on the sender for each participant. Establishing an RGS connection using Standard Login In normal operation, users are required to authenticate twice when establishing an RGS connection from a Local Computer to a Remote Computer. This is the Standard Login process—the two steps are: 1.
Figure 2-10 RGS connection process if another user is already logged into the Remote Computer There are a number of variations of the Standard Login process, as detailed in the diagram of the Standard login process on the tabloid page (the last page of the PDF version) of this guide.
Single Sign-on and Easy Login RGS supports two additional login methods in certain circumstances. These two methods allow users to enter their credentials only once in connecting to a Remote Computer—these methods are described below, along with which authentication process is used: Single Sign-on Single Sign-on—Supported only for Windows-based senders.
to be first authenticated by the RGS Receiver/Sender. Easy Login is described further in Easy Login on page 111. Deciding between Single Sign-on and Easy Login If neither Single Sign-on nor Easy Login is selected, the default Standard Login will be used.
● Windows 7 Easy Login on Windows 7 uses Credential Providers to allow the user to be authenticated through their standard username/password mechanism or using smart card or activkey technologies. Single Sign-on does not support smart card or activkey technologies. The only Credential Providers supported when using Easy Login are the Microsoft Password Credential Provider and the Microsoft Smartcard Credential Provider.
RGS operating modes 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 17, Normal Mode is described in Using RGS in Normal Mode on page 101. 2. Directory Mode — This mode enables RGS to connect to multiple Remote Computers, as described in Many-to-one connection on page 18.
desktop of the Remote Computer, the Local Computer must have a comparably-sized frame buffer, which will typically require two monitors to view (see Figure 2-15 A Remote Display Window spanning two monitors on page 27). Figure 2-15 A Remote Display Window spanning two monitors Multiple monitors on the Local Computer are also useful in the configuration described in Many-to-one connection on page 18.
Remote Computer monitor blanking overview New in RGS 5.0, this feature blanks the Remote Computer monitor (if one is connected) when the local user establishes an RGS connection to the Remote Computer and logs in—in other words, becomes the primary user. This feature is provided for security, to ensure that the primary user’s desktop session on the Remote Computer is not visible on a monitor connected to the Remote Computer.
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.
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-18 Remote Computer can access the local USB devices on page 30). For details on remote USB, see Remote USB operation on page 136.
Figure 2-19 The local USB devices can be attached to only one Remote Computer at a time. USB session switching At RGS 5.1.3, the ability to dynamically move USB devices from one Remote Computer to another was added. Prior to RGS 5.1.3, it was necessary to first disconnect all RGS connections (sessions) to the Remote Computers, and then re-establish connections while specifying a new Remote Computer to attach the USB devices to. With RGS 5.1.
away from the local system and remoted to the Sender system. Upon disconnect it will be given back to the local system. Figure 2-20 Receiver installation dialog to specify the Remote USB Configuration The three Remote USB Configuration options are: 1. USB devices are Local—All USB devices will remain local, and will be accessible only by the Local Computer—none of the USB devices will be accessible by a Remote Computer. 2.
For information on how to modify the Registry to support auto-remoting. (see Local/Remote USB Device Management on page 140 Figure 2-21 USB device accessibility for the setting “USB devices are Local/Remote” As can be seen in Figure 2-21 USB device accessibility for the setting “USB devices are Local/Remote” on page 33, USB device accessibility depends on when the USB device is plugged into the Local Computer.
establishing a connection to a Remote Computer. This is to allow the smart card reader to be used by the Local Computer prior to using the smart card to authenticate access to the Remote Computer. ● Figure 2-22 Smart card reader accessibility pre- and post-RGS connection for settings “USB devices are Remote” or “USB devices are Local/Remote” on page 34 shows the local and remote accessibility of the smart card reader for USB configuration settings USB devices are Remote and USB devices are Local/Remote.
the interoperability of RGS and RDC, see Interoperability of RGS and Microsoft Remote Desktop Connection on page 48. This situation can arise as follows: 1. The user uses a smart card reader to log into the Remote Computer with RDC. Assume that this login session is established from the user’s home. 2. Assume further that the user inadvertently leaves the RDC login session established, and departs for work. 3.
Computers supporting remote USB Remote USB connections are supported by the computers and operating systems shown in the tables below.
Supported USB devices The information in this section supersedes any previous supported USB device information. Starting with the 5.2.0 release, RGS supports all USB transfer types (bulk, isochronous, interrupt and control). This support means that a wide range of USB devices will work remotely with RGS. 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.
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.
Table 2-6 Windows RGS audio data paths Audio Playback from the Remote Computer to the Local Computer Sending of microphone audio from the Local Computer to the Remote Computer 1. The application-generated audio output. USB devices are local: 2. If an audio device is installed, the application-generated audio is routed through it. 1. 3.
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 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. Figure 2-24 RGS audio subsystem on Linux on page 41 shows the RGS audio subsystem (green boxes), and the audio data paths for Linux—these data paths are described in Table 2-7 Linux RGS audio data paths on page 42.
Table 2-7 Linux RGS audio data paths Audio Playback from the Remote Computer to the Local Computer Sending of microphone audio from the Local Computer to the Remote Computer 1. The application-generated audio output. 2. If an audio device is installed, the application-generated audio is routed through it. USB devices are Local: RGS on Linux does not support locally-mounted USB microphones. 3. If the Virtual Audio Device is installed, the application generated audio is routed through it. 4.
If USB devices are Remote is selected, a USB microphone can be accessed anytime by the Remote Computer. If USB devices are Local/Remote is selected, how the USB microphone can be accessed by the Remote Computer depends on when the microphone is connected to the Local Computer relative to establishment of the RGS connection.
Table 2-8 Receiver Remote Audio support (continued) Receiver Platforms Windows XPe/ WES 2009/WES 7 HP gt7720 WES 2009 Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows 7 Professional and Enterprise 32-bit and 64bit HP gt7725 HP 6360t Embedded Linux RHEL V5.2 or later; V6.2, 32bit, 64-bit HP ThinPro WES 7, WES 2009 Table 2-9 Sender remote Audio Support Sender Platforms Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows 7 Professional and Enterprise 32-bit and 64-bit RHEL V5.
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. Beginning with RGS 5.3.0, Remote Clipboard cut and paste of ANSI text data is supported between Windows Receiver systems and Linux Sender systems.
NOTE: Not all data formats can be transferred using cut and paste between Windows applications. See Remote Clipboard operation on page 159 for detailed information on the supported formats. In order for Remote Clipboard to be usable, it must be enabled during both the Sender and Receiver installations on Windows (see the Manual installation of the Receiver on Windows on page 53” and the Manual installation of the Sender on Windows on page 59) for further information on Remote Clipboard installation.
For details on using Remote Clipboard, see Remote Clipboard operation on page 159 Following installation, Remote Clipboard on Windows can be enabled or disabled via a toggle in the Receiver's controls.
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.
request from the Local Computer—the Remote Computer must be powered-up, and able to respond to an RGS connection request at all times. Supported keyboard locales 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.
18. Portuguese (Brazilian ABNT) 19. Russian 20. Spanish 21. Swedish 22. Swiss French 23. Swiss German 24. Turkish Q 25. United Kingdom 26. United Kingdom Extended 27. United States-International 28. US RGS security features Because of the distributed nature of an RGS connection, providing connection security is critically important.
● Connection status: A desktop icon in the application tray animates when other users are connected. ● Collaboration notification: See Collaboration notification dialog on page 116. ● Connections are not allowed when an iLO remote console is enabled: If the iLO remote console is enabled on a HP Blade Workstation, connections to the blade using RGS are denied. ● Disconnect Everyone: All Receivers can be easily disconnected using the Sender GUI.
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 NOTE: RGS licensing applies to the RGS Sender only. The RGS Receiver is a free download and can be used on any number of computers.
Installing RGS on Windows This section describes installation of the RGS Receiver and Sender on Windows. See Supported computers and operating systems on page 10 for a list of the Windows operating systems that support the RGS Receiver and Sender. Installing the Receiver on Windows This section describes manual and automatic installation of the RGS Receiver on Windows.
3. During the installation, the Remote USB Configuration dialog is displayed (see Figure 3-1 Receiver Remote USB configuration dialog on page 54 and Remote USB overview on page 30). To see additional information, select I’m not sure, I want more information, and click Next. Select the USB configuration option that meets your needs, and click Next. Figure 3-1 Receiver Remote USB configuration dialog NOTE: For many USB devices, the Windows operating system provides default USB drivers.
4. The Remote Clipboard Configuration dialog is displayed next (seeFigure 3-2 Remote Clipboard Configuration dialog on page 55 and Remote Clipboard overview on page 45). To see additional information, select I’m not sure, I want more information, and click Next. Select the desired Remote Clipboard Configuration option, and click Next. Figure 3-2 Remote Clipboard Configuration dialog NOTE: Selecting “Yes” will cause the hprclipboard.dll library to be installed with the RGS Receiver.
Usage Setup.exe /autoinstall /agreetolicense [/folder=] [/usb=local | /usb=remote | /usb=localRemote] [/clipboard] [/noreboot] Setup.exe /autoremove [/noreboot] Setup.exe /viewlicense Setup.exe /help Command line options /autoinstall This option performs one of the following: ● Installs the Receiver if it is not currently installed. ● Updates the Receiver if a prior version of the Receiver is currently installed.
/usb=remote Install USB in Remote Mode. The system will automatically restart after the install completes. /usb=localRemote Install USB in Local/Remote Mode. The system will automatically restart after the install completes. This is the default if none of /usb=local, /usb=remote, and /usb=localRemote are specified. /clipboard Enable remote clipboard. /noreboot Do not reboot the system when the setup requires a reboot to complete.
Uninstalling the RGS Receiver on Windows To uninstall the RGS Receiver, use the Windows Add or Remove Programs feature from the Control Panel. Select Remote Graphics Receiver, and click Remove. A dialog box will open with choice of REMOVE or Exit without changes. Choose REMOVE to uninstall the RGS Receiver. On certain client computers simply re-run the setup.exe program that you used to originally install the Receiver in place of using the Windows Add or Remove Programs feature.
Manual installation of the Sender on Windows To install the Sender on Windows, log into an account with administrator privileges, and perform the following steps: 1. Go to the directory where you downloaded RGS, and change to the directory win32\sender. 2. Double-click Setup.exe to start the Sender installation, and follow the instructions on the screen. 3.
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. 4.
5. Next, the Sender installer will prompt you for the Sender license. If you have a Sender license file, click the appropriate radio button, click Next, and provide the requested information. If you don’t yet have a license file, click I do not yet have a license file, and click Next. You can install your license file later.
stopped, started, or resumed. Additionally, the properties of the service can be controlled such as the start-up type and the recovery mode. Figure 3-6 The Remote Graphics Sender service 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.
-nocollab—Disables collaboration. When specified, only the primary user can connect to the Sender. -timeout value—The timeout in milliseconds used to detect and disconnect an inactive connection. This option sets the property Rgsender.Network.Timeout.Error. See Adjusting Network timeout settings on page 148 for more details. -authtimeout value—The timeout in milliseconds used to detect and notify the user of a network disruption. This option sets the property Rgsender.Network.Timeout.Dialog.
The Sender GUI on Windows The Sender displays the HP Remote Graphics Software icon in the application tray. The icon animates when Receivers are connected to the Sender. Right-click the icon to display the Sender GUI (see Figure 3-7 Sender GUI on page 64).
There are two ways to set the process priority of the Windows Sender: ● Use regedit to modify the rgsender service start up parameters in the Windows Registry.
If Single Sign-on is enabled and the computer is running Windows XP Professional, the computer must be restarted before Single Sign-on is operational. Figure 3-8 The dialog presented during Sender installation to enable Single Sign-on or Easy Login Using the rgadmin tool to enable Single Sign-on NOTE: The rgadmin tool is only installed and supported on Windows XP and Windows 7. The rgadmin tool can be used to enable Single Sign-on—check the Enable Single Sign-on radio button and click Apply.
Figure 3-9 Using the rgadmin tool to enable Single Sign-on (Windows XP Professional) Figure 3-10 Using the rgadmin tool to enable Single Sign-on (Windows 7) Installing RGS on Windows 67
Manually enabling Single Sign-on (Windows XP Professional only) Although the manual method is not the preferred method to enable Single Sign-on, it is provided so that administrators will know exactly what parts of the operating system are being modified. To manually enable Single Sign-on, perform the following steps: 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.
Summary—If the GinaDLL key does not currently exist in the registry, the Microsoft default GINA DLL (msgina.dll) is loaded by WinLogon. Adding the GinaDLL registry key, and setting its value to hprgina.dll, informs WinLogon to load hprgina.dll instead of the default msgina.dll. Setting the local security policy (Windows XP Professional only) The local security policy "Interactive logon: Do not require CTRL-ALT-DEL" must be disabled to support Single Sign-on.
Figure 3-14 Using rgadmin to disable Single Sign-on (Windows 7) Manually disabling Single Sign-on (Windows XP Professional only) To disable Single Sign-on without using the rgadmin tool, delete or rename the value of the GinaDLL registry key. If there is no other custom GINA module on the computer, simply removing the GinaDLL key definition from the registry entry below disables Single Sign-on.
Installing and Enabling Easy Login CAUTION: Installing RGS Easy Login is for experienced users and IT administrators only. Please read all directions completely before proceeding, and exercise caution when installing. Easy Login is only supported on HP blade workstations running the RGS Sender. The RGS shared library, hprgina.dll, enables Easy Login for Windows XP Professional. The file hprgina.
RGS ELO Credential Providers for Windows 7. Using the rgadmin tool to enable Easy Login is preferred over the manual method, described next for Windows XP Professional.
Manually enabling Easy Login (Windows XP Professional only) Although the manual method is not the preferred method to enable Easy Login, it is provided so that administrators will know exactly what parts of the operating system are being modified. To manually enable WinLogon to load the hprgina.dll module, perform the following steps: 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.
Chaining custom GINA modules for Easy Login (Windows XP Professional only) If it is determined in step 3 above that the GinaDLL registry key does exist, and the value of the key is not msgina.dll, then a custom GINA module is currently loaded and being used by WinLogon. Custom GINA modules provide custom authentication dialogs or even custom user authentication methods. If it is determined that functionality of both the RGS Easy Login and a custom GINA module is required, the hprgina.
Setting the Local Security Policy (Windows XP Professional) 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. See Using the RGS Diagnostics Tool on Windows on page 80 for more information.
Figure 3-19 Using rgadmin to disable Easy Login (Windows 7) Manually disabling Easy Login (Windows XP Professional only) To disable Easy Login without using the rgadmin tool, delete or rename the value of the GinaDLL registry key. If there is no other custom GINA module on the system, simply removing the GinaDLL key definition from the registry entry below disables Easy Login.
Manually disabling Easy Login (Linux only) In RGS 5.4.8 and later, Easy Login can be disabled on Linux by adding the following properties to the rgsenderconfig file: Rgsender.IsAnonymousConnectionForceEnabled=0 Rgsender.IsClassicEasyLogonEnabled=0 Automatic installation of the RGS Sender on Windows The RGS Sender can be installed or removed in automatic mode. Automatic mode allows the Sender to be installed or removed without any user interaction.
Command line options /autoinstall This option performs one of the following: ● Installs the Sender if it is not currently installed. ● Updates the Sender if a prior version of the Sender is currently installed. ● Exits without changes if the version being installed is the same as the version that is currently installed. The Sender will not be reinstalled if the version of the Sender being installed is older than the version of the Sender currently installed.
/sso Enable Single Sign-on, only one of /sso and /el can be used. /el Enable Easy Login, only one of /sso and /el can be used. /gina= Chaining GINA module to use, default is "msgina.dll", can only be specified if /el is used. /rgslicenseserver= The license to run the RGS Sender is acquired from a license server listening on the specified port and host. The port/host must be in the form of port@host.
Sender installation log file on Windows As with installation of the Receiver, installation of the Sender also 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.
dialog Figure 3-20 Output of the RGS Diagnostics Tool on page 81 shows the output generated by the tool. Figure 3-20 Output of the RGS Diagnostics Tool The Test Name left panel shows the list of tests that have been run. Selecting a test with the mouse will display additional information in the Results right panel. The Rerun Tests button on the bottom left reruns all tests. The example window shows that all tests have passed.
updates from the application to the Sender. These updates inform the Sender what screen rectangles have been changed by the 3D application. Figure 3-21 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. For RGS 4.0 and later, this library may cause applications to fail on startup. Because automatic updates of OpenGL applications are now supported, the OpenGL32.
Figure 3-22 Dialog to enable or disable Single Sign-on and Easy Login (Windows XP Professional) rgadmin tool on Windows 7 Beginning with RGS 5.4.
When rgadmin is started, it reports the current status of Single Sign-on and Easy Login. To change the status, check the desired radio button. After clicking Apply, Single Sign-on or Easy Login are immediately available on Windows 7.
To install the RGS Receiver on Linux, perform the following steps: 1. Login as root. 2. Go to the directory where you downloaded RGS, and change to the directory lin32/receiver (32bit version) or lin64/receiver (64-bit version). 3. Execute the following command: ./install.sh 4. The Receiver will be installed into /opt/hpremote/rgreceiver. To start the Receiver, execute the following command: /opt/hpremote/rgreceiver/rgreceiver.
Installing the Sender on Linux NOTE: The Linux RGS Sender can only be installed on the computers and Linux operating systems shown in Supported computers and operating systems on page 10. Installing the Sender on a nonsupported 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.
The rgsender_config_64-*.rpm provides an automated way to handle the standard customizations described below. This is especially useful for network or unattended installations requiring default PAM authentication settings. The rpm can also be run independently of the install script.
types of pam_unix*.so, pam_env*.so, common-auth, and pam_stack.so may apply to your configuration for the /etc/pam.d/rgsender configuration file. If you choose to do all of your own customizations manually, please run the rgsender_config_64*-rpm at least once on a test system to determine an example of any customizations that you might need in your current environment. 7.
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. Build date : Jul 15 2009 (RG) 10:29:53.002 Listening for RG connections at /var/opt/hpremote/rgsender/sockets/rgsenderrge:0 (RG) 10:29:53.
rpm. If you are upgrading your system from a previous version of RGS, it is suggested that you remove both packages, and then apply the new software rpms for supported results.
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.
Remote Computer (Sender) checklist Modification and verification of the Sender state can be performed either by connecting a keyboard, mouse, and monitor directly to the Remote Computer, or by using Remote Desktop Protocol to log in remotely to the Remote Computer. In either case, verify each of the following items: 1. OPTIONAL: Ensure RGS Sender licensing is set up—Beginning at RGS 5.2.0, HP implemented licensing for the RGS Sender. For an overview of RGS licensing, see RGS licensing on page 14 .
7. Network Interface binding—Beginning with RGS 5.4.0 the Sender defaults to listening to multiple network interfaces if the computer is so equipped. If the Remote Computer has multiple network interfaces, the Sender will dynamically add or remove network interfaces without restarting the Sender. This topic is expanded considerably in Network Interface binding on the Sender on page 94 . 8.
Network Interface binding on the Sender If the Remote Computer has multiple network interfaces, beginning with RGS 5.4.0 the Sender defaults to “listening” on all network interfaces. If this is undesirable, the previous behavior can be restored by manually configuring the network interface binding properties. There are four methods to deal with multiple network interfaces: 1.
2. Double-click each LAN icon and the Support tab, which displays the network interface IP address (see Figure 4-2 Network Interface IP addresses on page 95). While this provides the IP address of each network interface, it does not indicate which network interface is considered the “first network interface”. Figure 4-2 Network Interface IP addresses 3.
Figure 4-4 Advanced Settings dialog The arrows to the right of the Connections box in Figure 4-4 Advanced Settings dialog on page 96 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 96) 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 97).
requests on network interface 1 (corresponding to Local Area Connection 4), even though network interface 1 is the second network interface in binding order. Figure 4-6 Network Interface binding order numerical sequence Again, refer to Network Interface binding properties on page 204 for a description of these properties. 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.
NOTE: The port used by the RGS Receiver is assigned by the Local Computer OS and can vary. The RGS Sender listens on TCP/IP port 42966. At RGS 5.2.5, the capability was added to specify the port number used by the RGS Sender. The default Sender port number is 42966, as noted above. The Sender port number can be changed using the Rgsender.Network.Port property as described in Network Interface binding properties on page 204.
5 Using RGS This chapter describes how to use RGS to establish a connection from a Local Computer to a Remote Computer, including: 100 ● Using RGS in Normal Mode ● Functionality and use of the Receiver Control Panel ● Setup Mode ● Remote Display Window Toolbar ● Remote Computer monitor blanking ● Linux connection considerations ● RGS login methods ● Receiver command line options ● Collaborating Chapter 5 Using RGS
Using RGS in Normal Mode Normal Mode is one of the two RGS operating modes—see RGS operating modes on page 26. Normal Mode is the simplest means of establishing a connection—you enter the IP address or hostname of the Remote Computer in the Local Computer Receiver Control Panel, and click Connect. NOTE: The second RGS operating mode, Directory Mode, is described in Using Directory Mode on page 170 . NOTE: The RGS Sender listens on TCP/IP port 42966.
[-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 174 for general information on RGS properties. For information specifically on RGS Receiver properties, see RGS Receiver properties on page 176. After the Receiver starts, you’ll see the Receiver Control Panel (see Figure 5-2 Receiver Control Panel on page 102).
Figure 5-3 Remote Display Window NOTE: If the connection attempt fails, refer to the Pre-connection checklist on page 91 , for a list of conditions which must be met in order for a connection to be established. NOTE: If your RGS Sender is not yet licensed, the error dialog in Section RGS licensing on page 14 will be displayed in the Remote Display Window. For information on Sender licensing, see the HP Remote Graphics Software Licensing Guide, available at http://www.hp.com/support/rgs_manuals.
the mouse and keyboard to interact with local Remote Display Windows. See Setup Mode on page 104 for more information. ● View advanced operations: Click Advanced>>> to view the tabs which provide access to many of the advanced capabilities of RGS. ● Display help: Click Help to display the online help. On Linux, the online help is displayed separately in a web browser, such as Mozilla. On Windows, the online help is displayed using the CHM file viewer hh.exe.
Setup Mode can be activated in two ways: 1. By clicking the Setup Mode button on the Receiver Control Panel (see Figure 5-2 Receiver Control Panel on page 102). This presumes, of course, that the Receiver Control Panel is visible. 2. By typing a special key sequence on the keyboard, called a hotkey sequence.
Figure 5-5 Remote Display Window selection dialog The Remote Display Window selection dialog is only displayed in Directory Mode—this is the mode that supports multiple Remote Display Windows. Remote Display Window Toolbar The Remote Display Window Toolbar provides information on the RGS connection, and allows several RGS parameters to be controlled.
● Borders button—Adds or removes window borders and decorations on the Remote Display Window. ● Snap button—When selected, this option causes the Remote Display Window to snap to the edges of the monitor whenever the boundaries of the window are within 30 pixels of any edge of the monitor. ● Image quality slide bar—Sets the image quality and, therefore, the amount of compression. Higher image quality reduces the amount of compression, and therefore consumes greater network bandwidth.
If monitor blanking is enabled but the Remote Computer is unable to blank the display (because, for example, the computer is not one of the supported computers listed previously), a warning dialog is displayed on the Local Computer (see Figure 5-7 Local Computer warning dialog if the Remote Computer is unable to blank its monitor on page 108). NOTE: Linux screen blanking functionality is not supported on Dual-Monitor systems unless NVIDIA TwinView is in use.
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. Full-screen crosshair cursors can be disabled by typing the following in a terminal window: X11xprop -root -remove _SGI_CROSSHAIR_CURSOR This will force the application to use an X cursor, which will display correctly on the Receiver.
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 Establishing an RGS connection using Standard Login on page 21. ● Easy Login—supported on Windows XP Professional and Windows 7 Senders on HP blade workstations. Beginning with RGS 5.4.8, Easy Login is also supported on Linux Senders.
Standard Login Standard Login is the process by which a local user attempts to connect to a Remote Computer that has neither Single Sign-on nor Easy Login enabled. See the tabloid page (the last page of the PDF version) of this guide for a diagram of the Standard login process. Easy Login The Easy Login flowchart is shown in Figure 5-10 Easy Login process on page 111.
NOTE: There are several Sender setup issues that can prevent an Easy Login connection to the RGS Sender. The RGS Diagnostics Tool programmatically detects several of these issues, and suggests possible solutions. See Using the RGS Diagnostics Tool on Windows on page 80 for more details. Single Sign-on The Single Sign-on flowchart is shown in Figure 5-11 Single Sign-on process on page 112.
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.
Collaborating RGS enables the primary user to share his or her desktop session with several users simultaneously (see One-to-many connection on page 19). 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.
Figure 5-15 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.
Collaboration notification dialog The Windows Sender displays a collaboration notification dialog when collaboration users are connected. This Sender-created dialog appears in each Remote Display Window that is connected to the Sender. The dialog displays a list of domain\usernames for each user connected to the Remote Computer (see Figure 5-17 Collaboration notification dialog displayed on the Sender and in each Remote Display Window on page 116).
Effect of low bandwidth and/or high latency networks on collaboration The update rates of all collaborators is limited by the lowest update rate of any one collaborator. This is required for content synchronization. When collaborating with highly interactive content any one collaborator connected via a low bandwidth and/or high latency network can cause all collaborators to have a less than satisfactory experience. This experience can be improved for all collaborators.
6 Advanced capabilities This chapter discusses the many advanced capabilities of RGS. Click the Advanced>>> button in the Receiver Control Panel to display the tabs shown in Figure 6-1 Tabs used to access advanced RGS capabilities on page 118.
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. General options General tab The options available under the General tab are shown in Figure 6-2 General tab options on page 119.
The options available under the General tab are: ● Prompt for username and password—In certain scenarios (such as silent authentication as described in Standard Login on page 111) the Receiver will not prompt the local user for a domain, username, and password. If the local user desires a prompt in order to enter an alternate domain, username, and password, the user can check this box. If checked, the authentication dialog is always displayed when the Connect button is clicked.
When the user stops interacting, RGS will return the image quality to the level set by the Maximum image quality slider if the update rate will allow. These controls will also improve the viewing of video by degrading the image quality to a point where the update rate can be maintained thereby smoothing the video.
122 ● Maximum image quality—This is the original user quality adjustment. The quality slider adjusts the maximum image quality desired. When selecting Fixed image quality RGS will maintain the image quality specified by this control setting. When selecting Adjust image quality RGS will use this control setting for the target image quality when the updates per second allow. ● Fixed image quality—RGS maintains the image quality specified by the Maximum image quality slider described above.
Auto Launch On Windows beginning with RGS 5.4.0, the RGS Receiver supports file association. The user can create property files with the extension ".rgreceiver" using the same format as the RGS Receiver configuration file. See Setting property values in a configuration file on page 174 for more details. For example, the file "hostname.rgreceiver" could be used for creating a property configuration file for connecting to the system with name "hostname". If the user double-clicks or opens a file with the ".
Game Mode Game Mode is a feature accessed via Hotkeys on page 156 introduced in RGS 5.4.0. 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.
Figure 6-4 Sound and Audio Devices Properties dialog The first step is to configure the Sound playback device (if used) and the Sound recording device (if used). As shown in Figure 2-23 RGS audio subsystem on Windows on page 38, the Sender contains audio components for both Sound playback and Sound Recording (microphone input).
Figure 6-5 Microphone device selection and audio playback device selection on the Sender NOTE: Remote Microphone can be enabled/disabled using the Rgsender.Mic.IsEnabled property, as described in the section Microphone property group on page 203. 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.
To select the mixer as the input line, click the Volume button in the Sound recording section of Figure 6-4 Sound and Audio Devices Properties dialog on page 125. This brings up the Recording Control window (see Figure 6-6 Select Recording Control Properties on page 127). 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 6-7 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 6-8 Recording Control dialog on page 128). Make sure this item is selected, and the volume level is not at the lowest setting. Figure 6-8 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 Professional 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 6-10 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 6-11 Sound and Audio Devices Properties dialog on page 131.
Figure 6-11 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.
Configuring audio on Windows 7 Sender When a connection is established between a Receiver and Sender, an audio session is created on the Sender. When audio is enabled in the Receiver GUI, audio will be captured from the default playback device. The master volume level on the Sender should have the expected impact on the remote audio volume level. Windows 7 also allows application specific volume controls through the Volume Mixer. This can be opened through the volume control in the taskbar.
The Audigy2ZS and Audigy 4 audio devices require the controls labeled "PCM Capture" to have a non-zero volume. Other volume controls will not impact the volume of the signal captured through RGS. Since the Master control does not impact RGS, the volume of the speakers on the sender system can be muted without preventing RGS from capturing an audio signal. The Sound Blaster Live! needs to have recording enabled on the Wave control in addition to having a non-zero volume level.
Using audio The audio controls in the Receiver Control Panel are shown in Figure 6-13 Audio controls on page 134. Figure 6-13 Audio controls The Speaker Button on the Receiver Control Panel enables and disables remote audio playback. When remote audio playback is enabled, the Sender records and transmits audio to the Receiver for playback. Audio controls in the Receiver Control Panel allow you set the audio volume, quality, and stereo/mono format.
The options available under the Audio tab are: ● Audio follows focus—This checkbox determines how audio is handled when the Receiver is connected to multiple Remote Computers in Directory mode. Checking this box enables playback of the audio stream from the Remote Computer whose Remote Display Window currently has the keyboard focus. When unchecked, the Receiver combines the audio from all Remote Computers into a single audio stream.
If all of the audio devices on a system are configured as not plugged in, the audio device cannot be opened. Some programs, such as Windows Media Player, will display an error indicating that an audio device is not available. Something will need to be plugged into one of the unplugged devices to allow audio to work on these devices. ● Audio not continuous—Low bandwidth connections can cause discontinuities in the audio stream. Reducing the quality and turning off stereo may improve the audio quality.
NOTE: Hewlett-Packard RGS supports remote USB. 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. This includes USB devices with security and encryption mechanisms built into them. The additional network delay could be looked at as a threat. Other devices that are known to break the USB standard, such as WEB CAMS, may also not function at all.
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-15 USB tab options on page 138. Figure 6-15 USB tab options The 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.
Figure 6-16 Prior to remote attachment of the USB drive key To connect the USB drive key to a Remote Computer in Directory Mode, perform the following steps: 1. Click the USB tab on the Receiver Control Panel. 2. Click the Enable Remote USB checkbox to enable the remote USB connection. 3. Select the IP address (or hostname) of the Remote Computer, and click Connect. 4.
another Remote Computer on page 140). The USB devices will be detached from the current computer and attached to the selected computer. Figure 6-18 Dynamically moving USB devices to another Remote Computer Local/Remote USB Device Management In addition to the general default settings for remote USB configurations, RGS 5.2.6 and higher releases support auto-remote and auto-return of user-specified USB devices when using Windows on both the Sender and Receiver platforms. RGS 5.4.
where xxxx is the VendorID and yyyy is the ProductID The VendorID and ProductID are reported in hexadecimal format, and should be entered in hexadecimal format in the new key created below. 2. Create the following Registry key: HKLM\System\CurrentControlSet\Services\hprpusbh\Parameters\Device 3.
8. Product Type 9. Serial Number USB device mounting can also be allowed/denied based on the following two parameters: 1. IP address of the Local Computer 2. The domain group of the local user The ACL file supports two rule types: “allow” and “deny”. The rules are evaluated by the Remote Computer for each USB connection request from a Local Computer as follows: ● If any rule indicates the USB connection should be denied, the connection is denied, regardless of any other rule.
6. Device BCD— bcdDevice 7. Manufacturer— manufacturer 8. Product Type— product 9. Serial Number— serialNumber CAUTION: Filtering on device strings (manufacturer, product, and serial number) may not be reliable. Device vendors are not required to add data to these fields, and many do not. Before deploying a solution that depends on a string-based filter, ensure that the devices you wish to use implement the appropriate device strings. 10. IP address of the Local Computer—peerAddress 11.
3. Double-click the specific device, which brings up a separate window. 4. Select the Details tab and select one of the following properties from the pull down menu: ● "Hardware Ids" property—This property shows the Vendor ID, Product ID and Revision for the device. The Vendor ID is the 4 hex digits after "Vid_". The Product ID is the 4 hex digits after "Pid_". The Revision is the 4 hex digits after "Rev_".
http://www.linux-usb.org/usb.ids The registered classes and subclasses are documented by the USB Device Working Group (DWG). The latest document from DWG for 1.0 defined class codes is hosted at: http://www.usb.org/developers/defined_class 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.
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.
If the HP Remote Virtual USB driver is not reported, reinstall the RGS Sender software. During installation, verify that the Remote USB box is checked in the Configuration window (see Figure 6-21 Enable installation of remote USB on page 147). Figure 6-21 Enable installation of remote USB 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.
Adjusting Network timeout settings The options available under the Network tab in the Receiver Control Panel are shown in Figure 6-22 Options available under the Network tab on page 148. Figure 6-22 Options available under the Network tab RGS supports three classes of user-settable timeouts: 1.
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.
timeout properties are specified in milliseconds. Figure 6-23 Receiver Control Panel on page 150 shows the default Receiver timeout periods and the corresponding timeout properties. Figure 6-23 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.
Figure 6-24 Receiver timeout sequence After the Receiver warning timeout property has been exceeded (two seconds, in this case), the Receiver Remote Display Window will dim and display a warning message to the user. The dimmed window and warning message notify the user of the potentially stale contents in the Remote Display Window. During this time, the Remote Display Window will appear unresponsive to the user.
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. The Sender begins by using the maximum of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.Dialog property (see Dialog timeouts on page 154).
again—Most likely the network connectivity between the Receiver and Sender was temporarily lost. Other possible problems include: ◦ 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.
seconds. See Adjusting Network timeout settings on page 148 for further details on setting the Receiver timeouts. ● Increasing the Receiver error dialog timeout doesn’t appear to have an effect and the Receiver still disconnects—This is likely caused by either: ◦ A network failure resulting in detecting lost connectivity by the Receiver (resulting in a disconnected connection) ◦ The Sender timeouts are shorter than the Receiver’s timeouts, and the Sender disconnects the Receiver.
Rgreceiver.Network.Timeout.Dialog property. If this timeout expires without the local user entering a username and password, the Receiver will remove the dialog. NOTE: The property Rgreceiver.Network.Timeout.Dialog does not control the duration of all dialogs displayed by the Receiver.
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-25 The Hotkeys tab options on page 156).
Figure 6-25 The Hotkeys tab options on page 156, 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.
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. Two actions are associated with each key: ● Down: Specifies a key press. ● Up: Specifies a key release.
Remote Clipboard operation For an overview of Remote Clipboard, see Remote Clipboard overview on page 45. 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 Windows Receiver systems and Linux Sender systems.
Remote Clipboard data transfers Figure 6-27 Transfer of data when a cut and paste is performed from a Remote Display Window to a Local Window on page 160 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).
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.
Figure 6-29 Cutting and pasting between Remote and Local Computers 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.
filtering of cut and paste data on page 163, which expands on Figure 6-28 Cut and paste computer nomenclature on page 161 to show receiving-side filtering. Figure 6-30 Receiving-side filtering of cut and paste data The filter parameter is specified by this RGS Receiver Remote Clipboard property: Rgreceiver.Clipboard.FilterString NOTE: This property is for advanced users only.
● 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 ● HTML Format—Text is in Hypertext Markup Language format ● 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.
Clipboard information. In this section, the text preceding the Remote Clipboard information will not be shown. 11-08-08 00:26:14 DEBUG - (format filter) ...Remote Clipboard information... 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. Set the Rgreceiver.Clipboard.
Figure 6-33 Remote Clipboard log entries for cut and paste on page 166 shows the Remote Clipboard log entries as the cut and paste is performed. Figure 6-33 Remote Clipboard log entries for cut and paste NOTE: If the clipboard on either the Local or Remote Computer already contains content at the time the RGS connection is established, a sending formats entry will appear in the log file of that computer preceding the setting filter log entry.
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. Both types of logging are described below. Receiver logging The RGS Receiver logs various types of information during its operation.
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 Sender on Windows on page 58, 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.
Statistics The options available under the Statistics tab in the Receiver Control Panel are shown in Figure 6-36 Options available under the Statistics tab on page 169. Figure 6-36 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. ● Image updates per second—The combined number of image updates per second received from all connections.
7 Using 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.
where: ● The domainName on a Windows computer depends upon the environment the currently logged-in user is operating within. If the user is logged onto their domain account, this means they have logging onto an account specified by Microsoft Active Directory directory services. If the domain account is worldwide\sally, the name of the Windows domain is “worldwide” and will be used as the domainName for directory mode.
Starting the Receiver in Directory Mode Before attempting a connection in Directory Mode for the first time, HP recommends that you verify that RGS can connect to each computer individually in Normal Mode (see Using RGS in Normal Mode on page 101). The Pre-connection checklist on page 91 can be used to verify that the computer and network parameters are set correctly.
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. 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 previously activated by the hotkey sequence.
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.
Receiver: C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\rgreceiverconfig Sender: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgsenderconfig On Linux, these files are located as follows: Receiver: /etc/opt/hpremote/rgreceiver/rgreceiverconfig Sender: /etc/opt/hpremote/rgsender/rgsenderconfig The configuration files contain property name/value pairs, with only one property per line. Empty lines (containing only whitespace characters) are ignored.
Authenticator properties The following Sender and Receiver properties affect how the user authenticates an RGS connection: Rgsender.LoggedInAuthenticators 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.
Restoring Receiver properties default values Receiver property default values can be reset by uninstalling and reinstalling the Receiver. Properties set using the Receiver Control Panel The Receiver Control Panel enables the user to modify the values of many Receiver properties. For example, as described in Remote Clipboard operation on page 159, the user can enable/disable Remote Clipboard using the Receiver Control Panel. This affects the Rgreceiver.Clipboard.
● ● ● ● ◦ Rgreceiver.IsMatchReceiverPhysicalDisplaysEnabled ◦ Rgreceiver.RecentWindowPositions(deprecated） ◦ Rgreceiver.ConnectionWarningColor ◦ Rgreceiver.IsGlobalImageUpdateMutable（deprecated） ◦ Rgreceiver.IsGlobalImageUpdateEnabled ◦ Rgreceiver.MaxImageUpdateRequests ◦ Rgreceiver.IsMouseSyncEnabled ◦ Rgreceiver.IsMenubar.Enabled ◦ Rgreceiver.IsAutoMenubarEnabled.IsMutable ◦ Rgreceiver.IsAutoMenubarEnabled ◦ Rgreceiver.
● ● ● ● ● USB properties group ◦ Rgreceiver.Usb.IsMutable ◦ Rgreceiver.Usb.ActiveSession ◦ Rgreceiver.Usb.IsEnabled Network properties group ◦ Rgreceiver.Network.Timeout.IsMutable ◦ Rgreceiver.Network.Timeout.IsGuiEnabled ◦ Rgreceiver.Network.Timeout.Warning ◦ Rgreceiver.Network.Timeout.Error ◦ Rgreceiver.Network.Timeout.Dialog Hotkey properties group ◦ Rgreceiver.Hotkeys.IsMutable ◦ Rgreceiver.Hotkeys.IsSetupModeEnabled ◦ Rgreceiver.Hotkeys.SetupModeSequence ◦ Rgreceiver.
● ◦ 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. (Windows only) See Auto Launch on page 123 for general details. ◦ Rgreceiver.Session..IsConnectOnStartup ◦ Rgreceiver.Session..Hostname ◦ Rgreceiver.Session..Username ◦ Rgreceiver.Session..Password ◦ Rgreceiver.Session..
Rgreceiver.Network.Timeout.Error property now has the individual Rgreceiver.Network.Timeout.Error.IsMutable property. If this RGS properties individual IsMutable property is true, the user is allowed to interactively change the associated property, that is, the Rgreceiver.Network.Timeout.Error property. NOTE: For clarity, the individual IsMutable properties are not shown in the previous list; however, they are included in the following detailed description of each property.
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. The default value is 1— the borders are enabled. Rgreceiver.
Receiver will keep the most recently connected Remote Computers on its list, up to the maximum number specified by this property. Minimum useful value is 1. Figure 8-4 The Receiver maintains a list of the most recently connected Senders. Rgreceiver.IsMatchReceiverResolutionEnabled=bool （0） Rgreceiver.IsMatchReceiverResolutionEnabled.
NOTE: As noted earlier, Rgreceiver.Session..VirtualDisplay.IsPreferredResolutionEnabled takes precedence over Rgreceiver.IsMatchReceiverResolutionEnabled. Therefore, if the former property is enabled (as listed in paragraph 2 above), the latter property is a “don’t care”, and its setting is ignored. If the above conditions are met, the Receiver will determine the physical displays that are contained within the Receiver Remote Display Window specified by these properties: ● Rgreceiver.Session..
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. The following example contains two 2tuples, one for each of two Remote Display Windows: Rgreceiver.RecentWindowPositions=0 0 1280 0 This property will set the coordinates (upper left corner) of the first Remote Display Window to (0, 0) and the second Remote Display Window to (1280, 0).
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.
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). Figure 8-6 Sequence chart for the default property value of 4 The sequence can vary considerably from that shown in Figure 8-6 Sequence chart for the default property value of 4 on page 187. For example, image update response #1 might be received prior to issuance of image update request #4.
Figure 8-7 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.
When the Rgreceiver.IsAutoMenubarEnabled.IsMutable property is set to 0, the user cannot turn Auto show toolbar feature on in the Receivers Advanced > General tab. Rgreceiver.IsDisconnectWarningEnabled=bool (0) This property was added with RGS 5.4.5 and 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.
For the Windows Receiver, the Help system is based on a CHM file. Receiver audio properties Rgreceiver.Audio.IsMutable=bool （1） 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 （1） Rgreceiver.Audio.IsEnabled.IsMutable=bool （1） If set to 1, the RGS audio subsystem will be enabled.
Receiver USB properties Rgreceiver.Usb.IsMutable=bool （1） If set to 1, the user can modify all USB controls in the Receiver Control Panel. If set to 0, none of the USB controls can be changed by the user. This property can be used to permanently enable or disable remote USB before the RGS Receiver is started. The default value is 1—the user can modify all USB controls. Rgreceiver.Usb.IsEnabled=bool （1） Rgreceiver.Usb.IsEnabled.IsMutable=bool （1） If set to 1, remote USB will be enabled.
Rgreceiver.Network.Timeout.Error.IsMutable=int （1） The timeout in milliseconds used to detect and disconnect an inactive connection. The default value is 30,000 milliseconds (30 seconds). Rgreceiver.Network.Timeout.Dialog=int （15000） Rgreceiver.Network.Timeout.Dialog.IsMutable=bool （1） This property specifies the timeout in milliseconds used to display, and wait on responses from, input dialogs, such as the authorization dialog and the PAM authentication dialog.
Rgreceiver.Hotkeys.IsKeyRepeatEnabled.IsMutable=bool （1） 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. By default, the Receiver ignores these key repeats in the hotkey state machine. The Local Computer may be set up to process key repeats in the hotkey state machine, which may be necessary for certain types of applications.
Rgreceiver.Clipboard.FilterString=string（see below for the default value） 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.
enable or disable logging settings before the RGS Receiver is started. The default value is 1—logging settings can be changed. Rgreceiver.Log.IsFileLoggerEnabled=bool （1） Rgreceiver.Log.IsFileLoggerEnabled.IsMutable=bool （1） If set to 1, logging output from the RGS Receiver will be sent to a file. The default value is 1 —log to a file. Rgreceiver.Log.Filename=string （rg.log） Rgreceiver.Log.Filename.IsMutable=bool （1） This property specifies the path to the log file, and is only used if RgReceiver.Log.
NOTE: Even with an image quality of 100, RGS still performs image compression to reduce the network bandwidth requirements. While the image on the Receiver will usually appear visually lossless to the user at an image quality of 100, the actual image data sent over the network from the Sender to the Receiver will be “lossy” to a limited extent. The exception is the Sender codec JPEG-LS which is mathematically lossless. See Sender general properties on page 200 for more information. Rgreceiver.ImageCodec.
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. See http://msdn.microsoft.com/enus/library/aa380261(VS.85).
This property and the above property specify the preferred resolution of the Remote Display Window (in pixels). This resolution is communicated to the Remote Computer Sender, which will attempt to adapt its resolution to match the resolution preference of the Local Computer. If the Remote Computer 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.
RGS Sender properties RGS supports the following hierarchy of methods to set the Sender properties (see Figure 8-8 Sender properties hierarchy on page 199). Figure 8-8 Sender properties hierarchy 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. Similarly, an rgsenderconfig file property can override a Sender default property.
● ◦ Rgsender.IsDisconnectOnLogoutEnabled ◦ 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.
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 RGS Sender will monitor the RDC session for a logout, and begin the process of making the desktop available as soon as the logout is detected. If set to 0, the RGS Sender will not monitor the RDC session for a logout. The default is 1— allow quick access to the Windows desktop after Remote Desktop logout. Rgsender.
mouse that are directly connected to the Remote Computer. If set to 0, monitor blanking is disabled. The default value is 1— monitor blanking is enabled. For details on monitor blanking, see Remote Computer monitor blanking operation on page 107. 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.
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.
This property is used by the Sender remote USB code while monitoring the ACL file (hprDefaultUsbAcl.xml). If this file disappears or otherwise becomes inaccessible while the Sender is running, this property controls how long the Sender waits for the file to be restored. If the timeout expires, all currently connected USB devices are disconnected. If the file is restored prior to expiration of the timeout period, the USB devices remain connected. The default timeout value is 5,000 milliseconds (5 seconds).
If Rgsender.Network.IsListenOnAllInterfacesEnabled=0, the Sender will listen on any network interface “n” where Rgsender.Network.Interface.n.IsEnabled=1, and the Receiver IP address is in the range specified by this property. Rgsender.Network.Port=int (42966) This property controls the port used for communications with the RGS Sender. If this property is not specified, the Sender will listen on port 42966, which is the default port used by the Receiver in establishing a connection to the Sender.
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.
Then, in the left pane, select System Tools followed by Event Viewer—the HPRemote Event Viewer is highlighted. The HPRemote log reflects recent RGS connection activity. The log entries are in "Last In, First Out" (LIFO) order. By default, the most recent events are listed first. NOTE: RGS event logging is supported only on the RGS Sender on Windows. It is not supported on the RGS Receiver. NOTE: The HPRemote log allows you to implement a capability called Remote Application Termination.
of the Local Computer IP address, port number and hostname when a connection is made to the Sender on page 208, 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.
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.
Additional information on event logging For additional information on Windows event logging, search Microsoft Developer Network (MSDN) as shown in Figure 9-4 MSDN event logging information on page 210. Clicking on the first search result will typically display the page shown.
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.
Table 10-1 RGS Sender events logged in the HPRemote log Message ID Description RGSENDER_CONNECT_STATE The connection state consists of zero or more primary connections and zero or more non-primary connections. Each event entry records the current number of active connections in each category. Events appear when the connection status of these users changes. The first field represents the number of primary connections. The second field represents the number of non-primary connections.
Table 10-1 RGS Sender events logged in the HPRemote log (continued) RGSENDER_DISCONNECT EventID 5 NOTE: Parameter %2 is new in the RGS 5.1.5 release. A receiver has disconnected. The message will contain the name associated with the connection. If Easy Login is enabled and the Receiver disconnects prior to a login, the associated name may be “Anonymous”. Event Viewer Message: Disconnect %1.
Table 10-1 RGS Sender events logged in the HPRemote log (continued) 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. Strings: %1 = name associated with connection Data: None Event Viewer Example: Set MYDOMAIN\myusername as primary connection. RGSENDER_SET_NONPRIMARY EventID: 7 A connection with an associated name is assigned to a nonprimary status. This may happen as a result of a logout.
Table 10-1 RGS Sender events logged in the HPRemote log (continued) RGSENDER_USB_CONNECT_DEVICE EventID: 9 A new USB device was connected to the Sender via remote USB.
Table 10-1 RGS Sender events logged in the HPRemote log (continued) RGSENDER_USB_DISCONNECT_DEVICE EventID: 10 A new USB device was disconnected to the Sender via remote USB.
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. The topics are not exhaustive—use them as a starting point for a more complete design that meets your business requirements.
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. In the future, certain software providers may provide custom interfaces for safe shutdown messages from an agent or the operating system.
● 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.
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. A number of design issues for the Windows agent are described in the previous section.
#define EVENT_SERVER NULL // remote server = "\\\\nodename"; local = NULL #define EVENT_SRC "rgsender" // specifies specific event name source in // HPRemote BOOL processEvent(LPCTSTR eventServer, LPCTSTR eventSource, DWORD dwEventNum) { HANDLE h; 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 ...
{ ... report error status ... return true; } // Process event (example: print out event) ============================== if (result) { // We only know how to process specific events if (pevlr->EventID == RGSENDER_CONNECT_STATE) { // Retrieve the two UINT32 fields of this message // 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... ...
{ DWORD dwCurrentIndex = 0; DWORD dwCurrentStart; DWORD dwCurrentCount; DWORD dwNewIndex; int waitedFor; // This function will monitor the log for the specified number of // seconds. If seconds is less than zero, we will wait forever. for (waitedFor = 0; seconds < 0 || waitedFor < seconds; ) { HANDLE h; // Open, read status of log, close event log ========================= if ((h = OpenEventLog(eventServer, eventSource)) == NULL) { ... report error status here ...
... report error status here ... return; } // Determine state of log change ===================================== // Compute the index of the last event. If the count is zero, then // there are no events and the index is 0. if (dwCurrentCount == 0) { dwNewIndex = 0; } else { dwNewIndex = dwCurrentStart + dwCurrentCount - 1; } // If the new index is different than the current, update the current // and process the current event. Otherwise, we sleep for a while.
{ // 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 ... } Additional features for Windows systems The following optional procedures for the RGS Sender service can improve the reliability of your remote agent solution.
● To set the RGS Sender service for automatic restart, you must adjust its Recovery Property through the Administrative Tools and Services control panel options. ● Actions to take for the first failure, second failure, and subsequent failures are available in the properties menu (see Figure 10-1 Remote Computer Sender recovery options on page 226).
11 Optimizing RGS performance This chapter provides suggestions on optimizing RGS performance, including optimizing the Remote Computer display settings and the network configuration. 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 and RGS Receiver should operate in full-duplex mode.
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.
On Windows, use BltTest to test the frame buffer read performance of the Remote Computer. This tool is available at: http://www.stereopsis.com/blttest/ Configuring your network for optimal performance RGS depends on low network latency and reasonably high network bandwidth. There are several methods to test and measure the network bandwidth, latency, and the number of hops between Sender and Receiver computers: ● Use the ping command to measure network latency.
To set the LAN characteristics for a 100 Mb/sec connection running full-duplex mode, as root, type: $ /usr/local/sbin/ethtool -s eth0 speed 100 duplex full autoneg off If you are not satisfied with your network performance, look at the log files on your network switch (if the Local Computer is connected to one). A significant number of errors on the switch port may indicate that the computer or network is not configured correctly.
12 Troubleshooting RGS This chapter provides suggestions on troubleshooting potential issues with RGS. Refer also to RGS error messages on page 232 which lists the RGS error messages and their potential causes. Potential RGS issues and troubleshooting suggestions Table 12-1 Potential RGS issues and troubleshooting suggestions on page 231 lists several potential RGS issues, and provides a number of troubleshooting suggestions.
13 RGS error messages This chapter lists the error messages reported by the RGS Receiver, and describes potential reasons for the error messages. Receiver error messages Error Description Connection lost! The RGS Sender has closed the connection. Possible reasons include: Unable to connect to Sender! 232 Chapter 13 RGS error messages ● The Sender may have explicitly disconnected your connection.
Authentication failed! Directory not found or not accessible! User not found in directory! The RGS Sender has refused to allow a connection. Possible reasons include the following: ● The authentication credentials that you entered, such as domain name, user name and password, are not valid or recognized by the Sender system. ● The Sender's authentication is not configured appropriately. Please consult the User's manual and README.
234 A space may only be entered after Ctrl, Alt or Shift is pressed. The Setup Mode hotkey sequence cannot start with a space. Setup Mode hotkey sequence is invalid. The sequence has been reset to the default. The Setup Mode hotkey sequence specified using a property either on the command-line or in the property configuration file is invalid, and has been reset to the default. Setup Mode hotkey sequence is invalid. The sequence has been disabled.
A Linux remote audio device support As shown in Figure 2-24 RGS audio subsystem on Linux on page 41, 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. On a Windows computer, by way of comparison, this control is often called “Stereo Mix”.
Index A Advanced capabilities 118 Authenticator properties 176 Auto Launch 123 Auto Launch session properties 196 M Many-to-one connection 18 Microphone property group 203 monitor blanking operation 107 monitor blanking overview 28 Multi-monitor configurations 26 C Collaborating 114 N Network Interface binding properties 204 Network timeout settings 148 Normal Mode 26 D Directory Mode 26 E Easy Login 111 G Game Mode 124 General options 119 H Hotkeys 156 I Image quality 29 Installing RGS 52 Interactive
Using RGS 100 V Video overlay surfaces 28 W Window placement and size properties 197 Index 237
Local user Standard Login process and primary user flowchart local user attempt to log in using Standard Login primary user N Attempt to connect to Remote Computer Remote Display Window did someone else log in with my credentials ? RGS authentication dialog Windows-to-Windows connection AND local user credentials match any credentials on Remote Computer ? Y If another user attempts to connect to the Remote Computer with the same credentials as the local user, the local user Remote Display Window be
