HP Remote Graphics Software 5.4.
© Copyright 2011 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. The HP Remote Graphics Sender for Windows uses Microsoft Detours Professional 2.
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 ...................................................................................................
Install-time configuration of remote USB ..................................................................... 29 Unique smartcard handling ...................................................................................... 31 Computers supporting remote USB ............................................................................ 34 Supported USB devices ............................................................................................ 35 Remote audio .......................................
Enabling Easy Login during installation ........................................ 66 Using the rgadmin tool to enable Easy Login ................................ 66 Manually enabling Easy Login (Windows XP Professional only) ....... 68 Chaining custom GINA modules for Easy Login (Windows XP Professional only) ....................................................................................................... 69 Install time specification of the custom GINA module .....................
Receiver Control Panel ............................................................................................. 96 Setup Mode ........................................................................................................... 96 Remote Display Window Toolbar .............................................................................. 98 Remote Computer monitor blanking operation ............................................................ 99 Linux connection considerations ...................
Verifying the USB data ............................................................................ 134 Troubleshooting remote USB .................................................................... 135 Computers supporting remote USB ............................................ 135 Supported USB devices ............................................................ 135 Check USB cable connections ................................................... 135 Reset the USB device ...................................
Archive file properties ............................................................................. 168 Receiver default properties ...................................................................... 168 Receiver property groups ....................................................................................... 168 Receiver general properties .................................................................................... 172 Receiver experience properties ......................................
Additional features for Windows systems ................................................................................ 213 RGS Sender Service Recovery Settings ..................................................................... 213 Microsoft Remote Desktop Recovery ........................................................................ 214 11 Optimizing RGS performance ...................................................................................... 215 Performance tuning for all platforms .......
List of tables Table 2-1 Computers and operating systems that support RGS 5.4.7 Receiver ............................................ 10 Table 2-2 Computers and operating systems that support RGS 5.4.7 Sender .............................................. 10 Table 2-3 Receiver Remote USB Support ................................................................................................ 34 Table 2-4 Sender 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 HP RGS ............................................................................................................... 5 Figure 2-1 RGS version numbering ..............................
Figure 3-6 The Remote Graphics Sender service ..................................................................................... 57 Figure 3-7 Sender GUI ........................................................................................................................ 59 Figure 3-8 The dialog presented during Sender installation to enable Single Sign-on or Easy Login ............... 61 Figure 3-9 Using the rgadmin tool to enable Single Sign-on (Windows XP Professional) ......................
Figure 5-17 Collaboration notification dialog displayed on the Sender and in each Remote Display Window ............................................................................................................................................ 108 Figure 5-18 Windows Sender GUI to disconnect collaboration users ....................................................... 108 Figure 6-1 Tabs used to access advanced RGS capabilities ....................................................................
Figure 7-2 The Receiver Control Panel in Directory Mode ....................................................................... 163 Figure 7-3 Remote Display Window selection dialog ............................................................................. 163 Figure 8-1 Receiver property hierarchy ................................................................................................ 167 Figure 8-2 The Receiver timeout error IsMutable property is set to 0 ................................
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 7: Using Directory Mode on page 161—Establishing RGS connections using Directory Mode is described in this chapter. Chapter 8: RGS properties on page 165—This chapter describes each of the RGS Sender and Receiver properties. Chapter 9: Sender event logging on Windows on page 195—This chapter describes the Windows Event Logging capability of RGS.
Typical RGS configuration Figure 1-1 Typical RGS configuration on page 3 shows a typical RGS configuration, consisting of a personal workstation and a thin client. The user’s applications run on the personal workstation while the user interacts with these applications from the thin client. Figure 1-1 Typical RGS configuration The remote Personal Workstation desktop image is transmitted over the network to the thin client, which displays the desktop image locally in a window.
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.
NOTE: Local user refers to the person physically located at the Local Computer. Remote user refers to the person physically located at the Remote Computer (if, in fact, a person is present at the Remote Computer). A local user who establishes an RGS login to the Remote Computer is known as the primary user. Once a primary user has been established, another local user can view the Remote Computer desktop session using RGS only if allowed by the primary user.
● HP compression/decompression algorithms—Proprietary, high-performance HP image compression/decompression algorithms enable real-time remote visualization that is visually lossless and highly interactive. ● Selective screen updates—Only those portions of the screen which change are captured, compressed, and transmitted from the Remote Computer to the Local Computer, further improving performance.
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 patch updates are available through Software Depot at http://software.hp.com under Client Virtualization. Other RGS Documents Other RGS documents such as the HP Remote Graphics Software Licensing Guide can be found at: http://www.hp.
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.
Table 2-1 Computers and operating systems that support RGS 5.4.
NOTE: Desktop Sender systems require 1.5 GHz or greater processor with SSE2 multi-media instruction extension, 32-bit color display adapter and 512 MB minimum RAM. Microsoft Windows Vista or Windows 7 Aero theme desktop running on a Sender requires an nVidia graphics card and a compatible nVidia driver that has native DX10 support. Windows Vista systems require driver version 182.61 or 191.56 and later. Windows 7 systems require driver version 191.56 and later.
RGS version numbering The RGS version (for example, version 5.4.0) contains the following three numbers: 1. Version primary number 2. Version major number 3. Version minor/patch number Figure 2-1 RGS version numbering on page 12 shows the positioning of the three version numbers. Figure 2-1 RGS version numbering RGS Version Description 1. primary – A primary release contains sufficient changes such that interoperability with the prior primary release is not guaranteed. For example, Sender version 5.
Two types of licenses are supported by the RGS Sender: 1. Local license file—With local licenses, each system running the RGS Sender requires a license file. ◦ 2. A license must be purchased and the license file installed for each RGS Sender computer. Floating licenses—With floating licenses, a pool of RGS licenses is purchased, which are dynamically allocated on a first-come, first-serve basis whenever an RGS Receiver first attempts to connect to an RGS Sender.
workstations. In addition, this key will also run on VMware VDI and HP Blade PC platforms that are supported by the RGS VDI license key. 4. HP RGS Desktop floating license — This RGS product runs on all RGS supported platforms, including: notebooks, desktop PCs, mobile workstations, personal workstations and HP blade workstations. In addition, this key will also run on VMware VDI and HP Blade PC platforms that are supported by the RGS VDI license key.
On Remote Computers running Linux, OpenGL-based applications can only be remoted if the Remote Computer is using NVIDIA graphics. RGS 5.2.6 and newer Sender and Receiver executables are signed for compatibility with strict antivirus programs. Networking support RGS uses TCP/IP over a standard computer network, and supports Ethernet connection speeds of 10/100/1000BASE-T (Gigabit). The RGS Sender listens on TCP/IP port 42966.
monitor—for Windows XP, the frame buffer contains the familiar Windows desktop (see Figure 2-3 The Remote Computer frame buffer containing the Windows desktop on page 16). Figure 2-3 The Remote Computer frame buffer containing the Windows desktop The monitor itself is optional on the Remote Computer. For example, if the Remote Computer is a Personal Workstation, a monitor (plus a keyboard and mouse) would typically be attached.
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 161 . 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 on certain Windows-based Remote Computers. These login methods are currently supported on Windows XP, Windows Vista and Windows 7 Sender platforms.
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. In terms of selecting between Single Sign-on and Easy Login, two factors to consider are: ● Single Sign-on If Single Sign-on is used with HP Session Allocation Manager (SAM), the user will only need to enter their credentials once to connect to multiple Remote Computers.
◦ Windows Vista and Windows 7 Easy Login on Windows Vista and Windows 7 uses Credential Providers to allow the user to be authenticated through their standard username/password mechanism or using smartcard or activkey technologies. Single Sign-on does not support smartcard 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 16, Normal Mode is described in Using RGS in Normal Mode on page 93. 2. Directory Mode — This mode enables RGS to connect to multiple Remote Computers, as described in Many-to-one connection on page 17. Directory Mode is based on a user-created file which specifies which Remote Computers the RGS Receiver should connect to.
complete 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 26). 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 17.
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.
NOTE: Even with an image quality of 100, RGS still performs some image compression to reduce the network bandwidth requirements. While the image quality on the Receiver will usually appear visually lossless to the user, the actual image data sent over the network 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 189 for more information. Beginning in RGS 5.4.
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.
The "auto" option described in Local/Remote USB Device Management on page 130 alters this behavior. It will re-enumerate any device marked as auto on connect and disconnect. For instance, you have a USB key device that you have marked "auto". Until the Receiver is started it will be attached to the local system. Once the Receiver is started and makes a connection to a Sender it will then be taken away from the local system and remoted to the Sender system.
CAUTION: Enabling auto-remoting of specific USB devices requires modifications to the Windows Registry. Registry modifications should only be made by experienced personnel. Because an incorrect Registry setting can cause serious problems, you should always make a backup of the Registry prior to making any changes. For information on how to modify the Registry to support auto-remoting.
devices, as described above. With RGS 5.1.3, smartcard readers are now handled in a unique manner, as follows: ● Unique smartcard handling requires, on the Sender, that Easy Login be enabled. Windows XP Professional – The chaining GINA module msgina.dll will be utilized. Windows Vista and Windows 7 – The HP ELO Credential Provider will be utilized. ● Unique smartcard handling also requires that the Local and Remote Computers both be running Windows.
● If a smartcard reader is plugged in after an RGS connection is established, it will be available remotely. ● If there is a break in the RGS connection, the smartcard reader will become locally accessible.
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. See USB devices supported by RGS on page 223 for a list of devices that have been tested with RGS. 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 Microsoft Windows USB driver stack.
on page 36 shows the RGS audio subsystem (green boxes) for Windows, and the audio data paths —these data paths are described in Table 2-5 Windows RGS audio data paths on page 37. Figure 2-23 RGS audio subsystem on Windows Table 2-5 Windows RGS audio data paths on page 37 describes each of the audio data paths. The numbering and lettering in the table correspond to the numbering and lettering in Figure 2-23 RGS audio subsystem on Windows on page 36.
Table 2-5 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.
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 38 shows the RGS audio subsystem (green boxes), and the audio data paths for Linux—these data paths are described in Table 2-6 Linux RGS audio data paths on page 39.
Table 2-6 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 Sender remote Audio Support Sender Platforms Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows Vista Business, Ultimate and Enterprise 32-bit, 64-bit RHEL V4 (update 5 or later), V5 (update 2 or later), V6 32 bit, 64 bit Windows 7 Professional and Enterprise 32 bit and 64 bit Blade Clients HP Blade Workstations X X 32–bit only X X X Personal Workstations X X Mobile Workstations X X Desktop PCs X X Notebook PCs X X HP Blade PCs VDI Servers X Desktops HP only (custom
Figure 2-25 Remote Clipboard operation Cut and paste are supported in the following scenarios. 1. Between a Local Window and a Remote Display Window (in both directions)—The Remote Computer may be running Windows or Linux. The Local Computer must be running Windows. 2. Between two Remote Display Windows (in both directions)—In this case, the Local Computer can be running either Windows or Linux; the Remote Computers may be running Windows or Linux.
Figure 2-26 Enabling Remote Clipboard during Sender and Receiver installation on Microsoft Windows systems.
For details on using Remote Clipboard, see Remote Clipboard operation on page 149 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 Microsoft Remote Desktop Connection (RDC). Because RGS and RDC both provide connection to a remote desktop, their interoperation is important to understand.
Remote Computer power saving states In order for a Local Computer to establish connection to a Remote Computer, the Remote Computer cannot be in a power saving state, such as Windows hibernate or standby. Furthermore, the Remote Computer cannot utilize wake-on-LAN in an attempt to power-up in order to respond to a connection request from the Local Computer—the Remote Computer must be powered-up, and able to respond to an RGS connection request at all times.
17. Portuguese 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.
● Collaboration notification: See Collaboration notification dialog on page 107. ● 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. This is useful when hosting a collaboration session, such as in a classroom environment, and the session ends. The Sender GUI is an icon in the system tray.
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.
3. During the installation, the Remote USB Configuration dialog is displayed (see Figure 3-1 Receiver Remote USB configuration dialog on page 49 and Remote USB overview on page 28). Additional information can be viewed by selecting I’m not sure, I want more information , and clicking Next. Select the USB configuration option that meets your needs, and click Next. Figure 3-1 Receiver Remote USB configuration dialog NOTE: 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 50 and Remote Clipboard overview on page 41). Additional information can be viewed by selecting I’m not sure, I want more information, and clicking 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.
-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 139 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. See Adjusting Network timeout settings on page 139 for more details.
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 on the icon to display the Sender GUI (see Figure 3-7 Sender GUI on page 59).
CAUTION: Adjusting the process priority of the Sender to a level higher than –normal can cause other normally privileged processes to receive fewer CPU cycles than normal. Therefore, caution should be observed in adjusting the priority of the Sender. Setting the Sender process priority using HP PA The HP Performance Advisor (HP PA) can be used adjust the priority of the Sender without having to use regedit. HP PA is available for HP Workstations only from this location: http://www.hp.
or Easy Login on page 61). 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, Windows Vista and Windows 7.
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 Vista and Windows 7) 62 Chapter 3 Installing RGS
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, Microsoft's 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 Vista and 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.
HP RGS ELO Credential Providers for Windows Vista and 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 75 for more information.
Figure 3-19 Using rgadmin to disable Easy Login (Windows Vista and 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.
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. Automatic mode will also restart the computer, if required, after the installation process completes. Should an illegal combination of command line options be specified, or if an error occurs during the install process, the install will abort and the error will be logged to the Sender installation log file.
/autoremove Remove the Sender. /folder= Specifies the destination folder, default is C:\Program Files\Hewlett-Packard\Remote Graphics Sender. /usb Enable remote USB. /remotemic Enable remote microphone. /clipboard Enable remote clipboard. /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.
/rgslicensefile= The license to run the RGS Sender is acquired from the specified file. The filename may be omitted by specifying the option as “/rgslicensefile=”, in which case the Sender will be installed without a license, and the license file can be manually copied to the install folder at a later time. Only one of /rgslicenseserver= or /rgslicensefile= may be specified.
Using the RGS Diagnostics Tool on Windows During the installation of the Windows Sender, the RGS Diagnostics Tool (rgdiag.exe) is installed. The tool can be used to detect potential issues (such as Windows firewall settings, Guest Account security policies, RDC interoperability, and Easy Login settings) that might prevent a remote connection. The dialog Figure 3-20 Output of the RGS Diagnostics Tool on page 75 shows the output generated by the tool.
rgadmin tool on Windows XP Professional When run on Windows XP Professional, the rgadmin.exe program displays two tabs. The 3D Updates tab (see Figure 3-21 3D Updates tab on page 76) can be used to enable automatic 3D updates from the application to the Sender. These updates inform the Sender what screen rectangles have been changed by the 3D application. Figure 3-21 3D Updates tab NOTE: RGS versions prior to RGS 4.0 required the manual placement of the RGS OpenGL32.
Figure 3-22 Dialog to enable or disable Single Sign-on and Easy Login (Windows XP Professional) rgadmin tool on Windows Vista and 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 Vista and Windows 7.
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.sh To start the Receiver in directory mode, execute the following command: /opt/hpremote/rgreceiver/rgreceiver.sh -directory 5. Optionally, add the directory /opt/hpremote/rgreceiver to your PATH environment variable.
To install the Sender on Linux, perform the following steps: A fully functional Linux install is required prior to beginning the RGS Sender install. 1. Log in as root. 2. Install the accelerated nVidia graphics driver. This is required prior to installing the RGS Sender. The nVidia driver install creates the file /etc/X11/xorg.conf used by the RGS Sender installation. The minimum nVidia driver version for RHEL6 is 256.53. The latest nVidia driver for your product is available at http://www.hp.
6. If you choose not to use the customization described in step 5, perform the following steps to update the respective configuration: a. Add the "rge" extension to the X Server configuration file (/etc/X11/xorg.conf). In the Modules section of this file, add the following line: Load "rge" The Module section should now read as follows: Section "Module" ... Load "rge" ...
active network connection IP. To test this, the command hostname -i should report an active IP address for the qualified hostname. Failure to resolve this address from a qualified hostname may result in remote connection errors. One way to address the hostname/IP name resolution is to edit the /etc/hosts file, and bind the machine name to its proper IP address as follows: 127.0.0.1 localhost localhost.localdomain 88.1.89.122 blade2 blade2.datacenter.com 10.
The functionality of each option is as follows: [-v | -ver | -version] —Displays the Sender version information. [-h | -help | -?] —Displays the rgsender.sh command line options that are listed on this page. Uninstalling the Sender on Linux To uninstall the RGS Sender on Linux, perform the following steps: 1. Log in as root. 2. If the default install.sh was used, then the following command should report some variation of the following packages: # rpm -qa | grep -i rgsender rgsender_linux_64-5.4.
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 12 .
restarting the Sender. This topic is expanded considerably in Network Interface binding on the Sender on page 86 . 8. Linux Sender machine name and IP address—The default on Linux is to bind the machine name to the following loopback interface in the /etc/hosts file: 127.0.0.1 blade2 localhost.localdomain The RGS Sender will not accept remote connections with this configuration. Edit the /etc/hosts file and bind the machine name to its proper IP address as follows: 127.0.0.1 localhost localhost.
There are four methods to deal with multiple network interfaces: 1. Allow the Sender to listen on all network interfaces and dynamically add and remove network interfaces, the default behavior of RGS 5.4.0 and beyond. See the Networking support on page 15 section for more detail. 2. Manually reconfigure which of the two network interfaces RGS binds to—see Manual Network Interface reconfiguration on page 87. 3. Use the RGS Sender network interface binding properties (introduced at RGS 5.
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 88). 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. To determine which is the first network interface, click Advanced > Advanced Setting (see Figure 4-3 Determining the first network interface on page 88).
Figure 4-4 Advanced Settings dialog The arrows to the right of the Connections box in Figure 4-4 Advanced Settings dialog on page 89 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 89) 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 90).
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 193 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 193.
5 Using RGS This chapter describes how to use RGS to establish a connection from a Local Computer to a Remote Computer, including: ● Using RGS in Normal Mode ● Functionality and use of the Receiver Control Panel ● Setup Mode ● Remote Display Window Toolbar ● Remote Computer monitor blanking ● Linux connection considerations ● RGS login methods ● Receiver command line options ● Collaborating Using RGS in Normal Mode Normal Mode is one of the two RGS operating modes—see RGS operating modes
The RGS Receiver supports the following command line options for the Windows executable, rgreceiver.exe, and the Linux executable, rgreceiver.sh: [-config [filename]] [-directory [file]] [-nosplash] [-v | -ver | -version] [-h | -help | -?] -Rgreceiver.propertyname=value -config filename—Specifies the name of a RGS Receiver configuration file to use. -directory [file]—Starts the Receiver in Directory Mode.
NOTE: 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. The Sender port number can be changed using the Rgsender.Network.Port property. If this property is used to change the Sender port number from its default value of 42966, the Sender port number must then be specified in the above Hostname dialog box, in either of the following formats: hostname:port number IP address:port number For example, if the Rgsender.Network.
In Normal Mode, the Local Computer can connect to only one Remote Computer at a time, as described in One-to-one connection on page 16 If an attempt is made to connect to a second Remote Computer using the Receiver Control Panel, the connection to the first Remote Computer is terminated. Receiver Control Panel Now that a connection has been established, the Receiver Control Panel is described in more detail.
interact with the Remote Display Window on the Local Computer. In Setup Mode, you can perform a number of operations, including: ● Move a borderless Remote Display Window ● Raise a particular Remote Display Windows that is being obscured by another Remote Display Window NOTE: In Normal Mode, only a single Remote Display Window can be displayed on the Local Computer. Displaying Multiple Remote Display Windows on the Local Computer requires using Directory Mode (see Using Directory Mode on page 161).
The default hotkey sequence can be changed using the Hotkeys tab in the Receiver Control Panel (see Hotkeys on page 147). As long as the Shift key is held down (following the Shift press, space press, and space release hotkey sequence used to enter Setup Mode), Setup Mode remains active. When the Shift key is released, Setup Mode exits. In contrast, the Setup Mode button on the Receiver Control Panel toggles the state of Setup Mode each time the user clicks on the button.
The Remote Display Window Toolbar provides the following: ● hostname—The hostname or IP address of the Remote Computer ● disconnect button—Disconnects the current RGS session ● CTRL-ALT-DEL button—Sends the CTRL-ALT-DEL key sequence to the Remote Computer. Some key sequences, such as CTRL-ALT-DEL, are trapped by the Local Computer, and therefore are not forwarded to the Remote Computer. This button allows the user to send a CTRL-ALT-DEL sequence to the Remote Computer without using the keyboard.
Computer, the monitor will enter the display powersave mode, and the cursor will be blanked as a result. ● An exception to input blocking is the CTRL-ALT-DEL key sequence. When this sequence is received by the Remote Computer from a directly-connected keyboard, the Remote Computer desktop will display the login dialog on the Local Computer.
Linux connection considerations NOTE: The Switch User functionality added to RHEL6 is not supported by RGS. Full-screen crosshair cursors Certain applications that use large crosshair cursors (for example, PTC ICEM Surf uses a full-screen crosshair cursor) will not 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 20. ● Easy Login—supported on Windows XP Professional, Windows Vista and Windows 7 Senders on HP blade workstations.
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 103. If the Easy Login conditions are met, the RGS connection authentication step is skipped, and the local user is presented either with the Welcome to Windows login dialog or the locked screen dialog.
Single Sign-on The Single Sign-on flowchart is shown in Figure 5-11 Single Sign-on process on page 104. If the Single Sign-on conditions are met, the user authenticates the RGS connection, and the Windows log in or unlock step is skipped. The user is presented with the Windows desktop following RGS connection authentication. Figure 5-11 Single Sign-on process Changing your password In RGS 5.
Starting at RGS 5.1, you can change an expired password from the RGS Receiver. If you enter an expired password, you will see a dialog stating that the password must be changed (see Figure 5-12 Dialog indicating that the password must be changed on page 105). Figure 5-12 Dialog indicating that the password must be changed After clicking OK, you’ll see the Change Password dialog (see Figure 5-13 Change Password dialog on page 105).
interact with the primary user’s desktop (see Figure 5-14 Multiple local users can view and interact with the primary user's desktop on page 106). Figure 5-14 Multiple local users can view and interact with the primary user's desktop The user currently controlling the mouse and keyboard is called the floor owner. Only one user, the floor owner, can interact with the desktop at a time.
NOTE: One-to-many (collaboration) requires a unique login account with credentials on the sender for each participant. Figure 5-16 Primary user dialog to authorize a local user to connect to the primary user’s desktop The different cases for establishing a collaborative session are: ● If no one is logged into the Remote Computer desktop (in other words, there is no primary user), all authenticated users are connected, and can view the Windows login desktop.
Computer (see Figure 5-17 Collaboration notification dialog displayed on the Sender and in each Remote Display Window on page 108). Figure 5-17 Collaboration notification dialog displayed on the Sender and in each Remote Display Window When the collaboration notification dialog is displayed, it indicates there are multiple connections to the Remote Computer desktop. Primary and collaboration users are identified using different fonts in the notification dialog.
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 on 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 110. Figure 6-1 Tabs used to access advanced RGS capabilities The capabilities available under each of these tabs will be described in detail. Unless required for clarity, the portion of the Receiver Control Panel above the tabs will not be shown.
General options General tab The options available under the General tab are shown in Figure 6-2 General tab options on page 111. Figure 6-2 General tab options The options available under the General tab are: ● Prompt for username and password—In certain scenarios (such as silent authentication as described in Standard Login on page 102) the Receiver will not prompt the local user for a domain, username, and password.
● Match receiver display resolution—When checked, the Receiver will negotiate with the Remote Computer Sender to have the Sender adjust its display resolution to match the Receiver display resolution. If the Sender is unable to match the resolution of the Receiver, a warning dialog is issued to the local user. ● Match receiver display layout—This checkbox is new with RGS 5.1.3.
TIP: Certain Microsoft Windows user environment configuration adjustments can improve the user interactive experience by minimizing the bandwidth required. Mute the audio on the Receiver if it is not needed using the Receiver's mute button, not the system mute function, or adjust the audio in the Receiver Advanced->Audio tab to use mono with a the quality at 11 or 22 KHz. See an example of these controls in the Using audio on page 124 section.
aggressive quality reduction. The Minimum update rate is a target. The available bandwidth may be too low to maintain the target rate. Valid settings are 0 to 30 updates per second. Auto Launch On Microsoft 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 165 for more details.
Remote audio operation For an overview of remote audio, see Remote audio on page 35. Before describing the RGS audio capabilities available under the Receiver Control Panel Audio tab, Sender audio configuration and calibration are described. Configuring audio on the Microsoft Windows XP Professional Sender NOTE: It is critical that a mixer control such as “Wave Out Mix”, “Stereo Mix”, or some variation on “Mixer” is available. The Creative Audigy driver calls this the “What U Hear” control.
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 192. 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 115. This brings up the Recording Control window (see Figure 6-6 Select Recording Control Properties on page 117). 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 118). 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 Microsoft 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 on the Sounds tab as shown in Figure 6-11 Sound and Audio Devices Properties dialog on page 121.
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 Microsoft Windows Vista and 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 Vista and Windows 7 also allow application specific volume controls through the Volume Mixer.
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 124. 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. 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.
● 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. Some high priority CPU intensive tasks may disrupt the audio stream. The Windows Task Manager may help you identify such a task. Another possible problem may be a bad network setup. ● PC speaker sounds not working—The Sender captures all audio information sent through the mixer.
configuration during Receiver installation —USB devices are Local or Remote on page 127. For a discussion of the USB installation options, see Installing the Receiver on Windows on page 48.
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 128. 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 130). 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.
9. Serial Number USB device mounting can also be allowed/denied based on the following two parameters: 10. IP address of the Local Computer 11. 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.
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 on 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_".
The registered classes and subclasses are documented by the USB Device Working Group. The DWG's latest document for 1.0 defined class codes is hosted at: 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.
Enable Remote USB Verify that Remote USB is enabled under the USB option tab of the Receiver Control Panel (see Figure 6-19 Checkbox to enable Remote USB on page 136).
HP Remote Virtual USB Driver Verify that the HP Remote Virtual USB driver is installed and active on the Remote Computer. Open the Windows Device Manager, and verify that HP Remote Virtual USB is listed under Universal Serial Bus Controllers (see Figure 6-20 HP Remote Virtual USB driver on page 137). Figure 6-20 HP Remote Virtual USB driver If the HP Remote Virtual USB driver is not reported, reinstall the RGS Sender software.
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. Many USB devices require manufacturer-supplied software to work on a system. This software must often be installed before the USB device is connected to the system.
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 139. 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 141 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. For legacy reasons, the Sender begins by using the maximum of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.
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 139 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 147).
The options available under the Hotkeys tab are: ● Send CTRL-ALT-END key sequence as CTRL-ALT-DEL: On some computers, the operating system will intercept the CTRL-ALT-DELETE key sequence, and will not forward it to the Receiver. For example, assume that the Local Computer is running Windows, and that the local user enters the key sequence CTRL-ALT-DELETE in a Remote Display Window for the purpose of logging into the Remote Computer.
◦ “C”—Closes the Remote Display Window, which terminates the RGS connection ◦ “G”—Toggles “Game Mode.” Game Mode enables relative cursor movements instead of absolute cursor movements. See Game Mode on page 114 for more details.
applications, you will need to perform cut or copy actions by Highlighting the text of interest and selecting the Cut or Copy action normally found in the application's "Edit" menu. Following installation, Remote Clipboard on Windows can be enabled or disabled via a toggle in the Receiver's controls. Remote Clipboard on Linux is installed by default and is enabled or disabled via a toggle in the Receiver's controls. Both cut and paste, and copy and paste, are supported in the following scenarios at RGS 5.3.
the clipboard data is transferred from the Remote Computer clipboard to the Local Computer clipboard, and then pasted into the Local Computer application. Figure 6-27 Transfer of data when a cut and paste is performed from a Remote Display Window to a Local Window The above demonstrates delayed rendering. Instead of transferring data from the Remote Computer to the Local Computer when the cut occurs, the data transfer is delayed until the paste occurs.
Continuing with the example of a cut and paste from Computer A to Computer B, Computer A is also referred to as the sending computer or cut computer, while computer B is referred to as the receiving computer or paste computer. Figure 6-28 Cut and paste computer nomenclature on page 152 shows this nomenclature. When discussing Remote Clipboard operation, we’ll generally use this nomenclature because it is independent of which computers are the Remote or Local Computers.
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 154, which expands on Figure 6-28 Cut and paste computer nomenclature on page 152 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 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. The sending formats log entry is due to the clipboard contents being sent to the Remote Computer when the RGS connection is first established.
enabled and the location/name of the log file(see Figure 6-34 Options available under the Logging tab on page 158). Figure 6-34 Options available under the Logging tab The options available under the Logging tab are: ● File logging—Enables logging to the specified Log File. The spinbox for Max logfile size limits the maximum logfile size. ● Log level—Determines the level of information that is logged.
Unless this command line option is used to change the logSetup file, the default logSetup file in the Sender installation folder (C:\Program Files\Hewlett-Packard\Remote Graphics Sender) is used. The first few lines of logSetup are shown in Figure 6-33 Remote Clipboard log entries for cut and paste on page 157. Figure 6-35 logSetup file The highlighted, uncommented line specifies that INFO-level logging is used.
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 160. Figure 6-36 Options available under the Statistics tab The Statistics tab displays aggregate data for all connected sessions. 160 ● 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.
worldwide joe RC_4 RC_5 RC_6 In the next example, the directory file specifies the Remote Computers for users Sally and Joe in a standalone or WORKGROUP environment.
specify a different directory file. The Connect All button is used to establish a connection to the Remote Computers listed in the directory file. Figure 7-2 The Receiver Control Panel in Directory Mode After clicking Connect All, you’ll need to independently authenticate and log into each Remote Computer.
The Remote Display Window selection dialog is only displayed in Directory Mode—this is the mode that supports multiple Remote Display Windows. While the Remote Display Window selection dialog is active, navigate between windows (thumbnails) by: ● Pressing TAB to select the next window. ● Clicking on the number displayed beneath the thumbnail. ● Clicking directly on a thumbnail. ● Double clicking the mouse on a thumbnail (this will also immediately close the selection dialog).
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.
The configuration files contain property name/value pairs, with only one property per line. Empty lines (containing only whitespace characters) are ignored. The "#" character begins a comment on the line, extending to the end of the line. If a property is listed more than once, the value of the last entry is used. NOTE: All properties in the configuration files are initially commented out with the “#” character.
RGS Receiver properties This section describes the Receiver properties. RGS supports two types of Receiver properties: ● Per-Receiver properties—The per-Receiver properties affect all Remote Display Windows generated by the Receiver. As noted in Many-to-one connection on page 17 a Receiver can connect to multiple Remote Computers (and therefore generate multiple Remote Display Windows). ● Per-session properties—New in RGS 5.
Archive file properties When the Receiver is run, the user can change a number of properties using menus on the Receiver Control Panel and the Remote Display Window. When the Receiver exits, it saves the state of any properties that were changed by the user—these are known as archive file properties. Receiver default properties The Receiver has a set of default properties that are built into the Receiver.
● ● ● ◦ Rgreceiver.Experience.MinImageQuality ◦ Rgreceiver.Experience.MinUpdateRate Browser properties group ◦ Rgreceiver.Browser.IsMutable ◦ Rgreceiver.Browser.Name Audio properties group ◦ Rgreceiver.Audio.IsMutable ◦ Rgreceiver.Audio.IsEnabled ◦ Rgreceiver.Audio.Quality ◦ Rgreceiver.Audio.IsFollowsFocusEnabled ◦ Rgreceiver.Audio.IsInStereo Microphone property group ◦ ● ● ● Rgreceiver.Mic.IsEnabled USB properties group ◦ Rgreceiver.Usb.IsMutable ◦ Rgreceiver.Usb.
● ● ● Remote Clipboard properties group (see below for the per-session Remote Clipboard property) ◦ Rgreceiver.Clipboard.IsMutable ◦ Rgreceiver.Clipboard.IsEnabled ◦ Rgreceiver.Clipboard.FilterString Logging properties group ◦ Rgreceiver.Log.IsMutable ◦ Rgreceiver.Log.IsFileLoggerEnabled ◦ Rgreceiver.Log.Filename ◦ Rgreceiver.Log.Level ◦ Rgreceiver.Log.MaxFileSize Image codec properties group ◦ Rgreceiver.ImageCodec.IsMutable ◦ Rgreceiver.ImageCodec.Quality ◦ Rgreceiver.ImageCodec.
Rgreceiver.Audio.IsMutable=1 When the group IsMutable property is 1 (true), the user is allowed to interactively change the other properties in the audio group—by using, for example, the Receiver Control Panel. When the group IsMutable property is 0 (false), the user is prevented from interactively changing the other properties in the group. All group IsMutuable properties have a default value of 1, which allows the user to interactively change the other properties in the group. With RGS 5.
Figure 8-3 The Receiver timeout error property menu is grayed out Receiver general properties The general properties are listed below. After each property, the default value is listed in parenthesis. Rgreceiver.IsBordersEnabled=bool （default=1） Rgreceiver.IsBordersEnabled.IsMutable=bool （default=1） If set to 1, the borders on the Remote Display Window will be enabled (displayed). If set to 0, the borders will be removed creating a borderless windows to display the Remote Computer desktop.
Rgreceiver.Directory=string （directory.txt） Rgreceiver.Directory.IsMutable=bool （1） Used in Directory Mode to set the name and location of the file that lists the Remote Computers assigned to the current user. The default value is "directory.txt". Rgreceiver.MaxSenderListSize=int （5） Rgreceiver.MaxSenderListSize.IsMutable=bool （1） In Normal Mode, the Receiver keeps a list of the Senders that it has most recently connected to. Figure 8-4 The Receiver maintains a list of the most recently connected Senders.
layout and resolution of the Receiver physical displays, the Receiver will try to just match the Receiver display resolution. For example, if the Receiver has two physical displays in a 1x2 layout and a overall virtual display resolution of 2560x1024 (1280x1024x2), the Receiver will try to set the Sender to the same layout and resolution. If that fails, the Receiver will try to set a single physical display resolution of 2560x1024. If that fails, an error is reported. If the following conditions are met: 1.
NOTE: The following property, while supported, has been deprecated. HP recommends using the per-session Remote Display Window X and Y positioning properties described in Window placement and size properties on page 186. Rgreceiver.RecentWindowPositions=int vector （10 10） Rgreceiver.RecentWindowPositions.IsMutable=bool （1） This property can be used to set the positions of the Remote Display Windows. The position of each Remote Display Window is controlled by an (xpos,ypox) 2-tuple.
used to permanently enable or disable global image updates in the Receiver. The default value is 1— global image updates can be configured by the user. Rgreceiver.IsGlobalImageUpdateEnabled=bool （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.
The sequence chart in Figure 8-6 Sequence chart for the default property value of 4 on page 177 shows operation for the default property value of 4. In this case, the Receiver can have up to 4 image update requests outstanding at any given time. When image update response #1 is received (meaning that there are now 3 outstanding image update requests), the Receiver can issue image update request #5 (again, up to a maximum of 4 outstanding image update requests at any given time).
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.
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.
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. If set to 0, remote USB will be disabled. The default value is 1 —remote USB is enabled. Rgreceiver.Usb.ActiveSession=int （0） Rgreceiver.Usb.ActiveSession.IsMutable=bool （1） When the Receiver is in Directory Mode, the Local Computer can connect to one or more Remote Computers.
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. The default value is 15,000 milliseconds (15 seconds). Receiver hotkey properties Rgreceiver.Hotkeys.IsMutable=bool （1） If set to 1, all Hotkey settings in the Receiver Control Panel can be changed by the user. If set to 0, none of the hotkey settings can be changed by the user.
Rgreceiver.Hotkeys.IsCtrlAltDeletePassThroughEnabled.IsMutable=bool （1） When a Windows Local Computer detects a Ctrl-Alt-Delete key sequence, it does not send the sequence to the Remote Computer—only the Local Computer processes the key sequence. Setting this property to 1 will result in both the Remote and Local Computers processing the key sequence. Note that some third party software tools or OS configurations may be available to disable the Ctrl-Alt-Delete sequence on the Local Computer. Rgreceiver.
The default clipboard formats are: ● 1 (CF_TEXT)—Text format. Each line ends with a carriage return/linefeed (CR-LF) combination. A null character signals the end of the data. Use this format for ANSI text. ● 2 (CF_BITMAP)—Bitmap format. ● 7 (CF_OEMTEXT)—Text format containing characters in the OEM character set. Each line ends with a carriage return/linefeed (CR-LF) combination. A null character signals the end of the data.
Rgreceiver.Log.Level.IsMutable=bool （1） RGS supports five logging levels: DEBUG, INFO, WARN, ERROR, and FATAL. If DEBUG is chosen, all level of output from DEBUG to FATAL will be output to the log file. If WARN level is chosen, all levels from WARN to FATAL will be output. The default value is INFO—all DEBUG output is turned off. Rgreceiver.Log.MaxFileSize=int （1024） Rgreceiver.Log.MaxFileSize.IsMutable=bool （1） This sets the maximum size of the log file in kilobytes (Kbytes).
Auto Launch session properties These properties are per-session (per-connection) properties. If, for example, the user wants to auto connect to various Remote Computers, these properties can be used to specify the properties of each of the various Remote Display Windows on the Local Computer. A .rgreceiver file is required for each Remote Computer. These properties contain the parameter which currently must be set to 0 in the .rgreceiver file. The .
Rgreceiver.Session..RemoteDisplayWindow.X.IsMutable=bool （1） This property specifies the X position of the session N Remote Display Window, as measured from the left side of the Local Computer display. Rgreceiver.Session..RemoteDisplayWindow.Y=int （0） Rgreceiver.Session..RemoteDisplayWindow.Y.IsMutable=bool （1） This property specifies the Y position of the session N Remote Display Window, as measured from the top of the Local Computer display. 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 188). 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.
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.IsCopyRegionEnabled=bool （1） If set to 1, RGS Copy Regions are sent from the Sender to the Receiver. If set to 0, RGS Copy Regions are turned off and will be sent to the Receiver as Image Update Regions. This is for advanced use and should not be set. The default value is 1—send RGS Copy Regions. Rgsender.
This property is supported only on Linux. If set to 0, the iLO (integrated Lights-Out) console is disabled when an RGS connection is made. This prevents the user’s desktop session from being visible through the iLo remote console. When set to one, the user’s desktop session will be viewable through the iLO remote console. The default is 0—disable viewing of the user’s desktop session through iLO. Rgsender.
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.
of the timeout period, the USB devices remain connected. The default timeout value is 5,000 milliseconds (5 seconds). Network Interface binding properties The following properties permit control of which network interface the RGS Sender binds to. Use of the network interface binding properties is described in Network Interface reconfiguration using the Sender network interface binding properties on page 90. Rgsender.Network.
user will need to specify the same port number on the Receiver to establish a connection with the Sender, as described in Using RGS in Normal Mode on page 93. Sender clipboard property Rgsender.Clipboard.IsEnabled=bool （1） If set to 1, Remote Clipboard is enabled—specifically, the copy and cut functionality in the Remote Display Window is enabled. If set to 0, the copy and cut functionality is disabled. The default value is 1 —Remote Clipboard is enabled.
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.
NOTE: The HPRemote log allows you to implement a capability called Remote Application Termination. Remote Application Termination enables applications on the Sender (Remote) Computer to be automatically terminated if the RGS connection to the Receiver is lost. See Remote Application Termination on page 200 for details. To view the properties of a particular event, double-click on the event of interest—this brings up the Event Properties window.
Figure 9-3 Reporting of the Local Computer IP address, port number and hostname when a connection is made to the Sender The HPRemote log 197
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, Microsoft 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 199. 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 (continued) RGSENDER_CONNECT_STATE EventID: 3 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.
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_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 ... return true; } // Set the pointer to our buffer.
// 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... ...
// 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 ... return; } // If an event is added, either the start or count will change. // Get the start and count. Microsoft does not specify what // reasons these functions could fail, so we cannot ensure // success.
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. if (dwNewIndex != dwCurrentIndex) { // We have at least one new event. Print out the last event. dwCurrentIndex = dwNewIndex; if (dwNewIndex) { if (processEvent(eventServer, eventSource, dwCurrentIndex)) { ... event processing error here ... return; } } } else { // No new events. Sleep for 1 second.
... 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. RGS Sender Service Recovery Settings This section discusses restart options for the RGS Sender and possible interactions of the agent with the Sender. ● By default, most Windows services are installed without any automatic restart/recovery settings.
◦ Run a Program ◦ Restart the Computer Figure 10-1 Remote Computer Sender recovery options Microsoft Remote Desktop Recovery If the RGS Sender becomes unavailable and the Receiver can no longer connect to the Sender, a Windows system with Remote Desktop services enabled can access the Remote Computer to diagnose the issue.
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.
● Select the Desktop tab and select Customize Desktop. ● On the Web tab, check Lock desktop items. 2. Sender process priority—Occasionally, an activity such as rotating a model in a 3D design program may appear slow and erratic, and image update may appear inconsistent. If the Sender is running on Windows, OS scheduling may be an issue. This can often be resolved by increasing the process priority of the Sender. See the Setting the Windows Sender process priority on page 59 for further details. 3.
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. From a command prompt on Windows or a terminal window on Linux, execute ping hostname. This will report the network latency. Be sure the ping protocol (ICMP) is not blocked by a firewall.
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. Work with your IT organization to optimize your computer and network configuration.
12 Troubleshooting RGS This chapter provides suggestions on troubleshooting potential issues with RGS. Refer also to RGS error messages on page 220 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 219 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 220 Error Description Connection lost! The RGS Sender has closed the connection. Possible reasons include: ● The Sender may have explicitly disconnected your connection. For example a user may have selected disconnect all connections from the Sender icon or Sender GUI or the user may have logged off.
Directory not found or not accessible! User not found in directory! The directory file is not available. Possible reasons include: ● The directory file name or location has been mistyped. ● The file has been moved or is no longer available. ● The network is down or experiencing a disruption. ● The user does not have read permission on the file. The username of the current user of the HP Remote Graphics Software Receiver is not found in the directory file.
222 Connection denied! The iLO remote console is enabled. The iLO remote console is enabled on the HP Blade Workstation. The Blade must be configured in User Mode before connections are allowed. Unable to connect to Sender: The Receiver was unable to resolve the specified hostname or IP Address. Verify that you entered the value correctly. This is usually indicative of a DNS error. Unable to connect to Sender: The Receiver resolved the specified hostname or IP address, but cannot connect to the Sender.
A USB devices supported by RGS NOTE: Prior to RGS 5.2.0, this list of USB devices was maintained in a separate document available at http://www.hp.com/support/rgs_manuals, titled USB Devices Supported by Remote Graphics Software. The list itself was an Excel spreadsheet with an internal description of “Client-attached USB Devices Accessible by the RGS Sender”. Beginning at RGS 5.2.0, the supported USB devices are now listed in this appendix, which supersedes the above document.
Table A-1 PDA devices (continued) Blackberry 7290 RGS 3.0 RGS 5.0 Desktop Manager 3.6 RGS 5.0 RGS 5.0 Desktop Manager 4.0 Blackberry 8100 RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8300 RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8310 RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8320 RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8700c RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8700g RGS 5.0 RGS 5.0 Desktop Manager 4.2 Blackberry 8800 RGS 5.0 RGS 5.
Table A-4 Security devices USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Axalto smartcard reader RGS 4.0.2 RGS 5.0 Digital Persona Keyboard RGS 5.0 RGS 5.0 Digital Persona Fingerprint reader RGS 5.0 RGS 5.0 HP Smart Card keyboard Notes RGS 5.0 Access Biometrics RGS 4.0.0 RGS 5.0 ActivIdentity smart card reader V2 RGS 5.0 RGS 5.0 ActivIdentity smart card reader V3 RGS 5.1.3 Keytronic USB Smartcard keyboard RGS 5.1.3 SCM SCR331 USB reader RGS 5.
Table A-6 USB keys (continued) HP 128M RGS 5.0 RGS 5.0 Memorex RGS 5.0 RGS 5.0 USB Device HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Memorex DVD/R - CD/RW RGS 5.0 RGS 5.0 USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Pioneer DVR-111D DVD-RW RGS 5.0 RGS 5.0 HP DVD300e RGS 5.0 RGS 5.0 Sony External Multiformat DVD Recorder RGS 5.0 RGS 5.
Table A-11 Printers USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe HP OfficeJet 9110 RGS 5.0 RGS 5.0 HP Photosmart 8750 RGS 5.0 RGS 5.0 HP LaserJet 3000DN RGS 5.0 RGS 5.0 HP Color LaserJet 2820 RGS 5.0 RGS 5.0 HP Business Inkjet 2800 RGS 5.0 RGS 5.0 HP Officejet Pro L7680 RGS 5.0 RGS 5.0 Epson Stylus R800 RGS 5.0 RGS 5.0 HP 2015dn RGS 5.0 RGS 5.0 HP 3005x RGS 5.0 RGS 5.
Table A-14 Enclosure USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Notes Adaptec USB 2.0 enclosure for IDE hard drives RGS 5.0 RGS 5.0 The enclosure works, but the behavior can differ depending on the drive used inside the enclosure. USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Notes Plantronics USB Audio 470 Headset RGS 5.2 RGS 5.2 Plantronics USB Audio 500 Headset RGS 5.2 RGS 5.
Table A-17 Sound recording devices (continued) Philips SpeechMike Pro Plus RGS 5.2 RGS 5.2 Logitech USB Desktop Microphone 980186-0403 RGS 5.2 RGS 5.2 Table A-18 Character input devices USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Elan Crystal Touch Pen Pad RGS 5.2 RGS 5.
B Linux remote audio device support As shown in Figure 2-24 RGS audio subsystem on Linux on page 38, 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 110 Authenticator properties 166 Auto Launch 114 Auto Launch session properties 186 C Collaborating 105 D Directory Mode 25 E Easy Login 103 G Game Mode 114 General options 111 H Hotkeys 147 I Image quality 27 Installing RGS 48 Interactive Experience controls 112 Introduction to HP Remote Graphics Software 1 K keyboard locales 45 L Linux remote audio device support 230 Logging 157 login methods 102 M Many-to-one connection 17 Microphone property group 192 monitor blanking ope
