HP Remote Graphics Software User Guide 5.4.
© Copyright 2010 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 ENWW
Table of contents 1 Introduction to HP Remote Graphics Software ................................................................... 1 1.1 Typical RGS configuration ................................................................................................... 3 1.2 RGS Sender and Receiver ................................................................................................... 4 1.3 RGS features ...................................................................................................
2.18 2.19 2.20 2.21 2.22 2.23 2.17.1 Remote audio on Windows ........................................................................... 32 2.17.2 Remote audio on Linux .................................................................................. 34 2.17.3 Support of sound recording devices on Microsoft Windows .............................. 35 2.17.4 Computers and operating systems which support RGS audio ............................. 36 Remote Clipboard overview .....................................
3.1.2.12.3 3. Manually enabling hprgina.dll to load a custom GINA module ........................................................................... 67 3.1.2.12.4 Setting the Local Security Policy .................................. 67 3.1.2.13 Disabling Easy Login .................................................................. 68 3.1.2.13.1 1. Using the rgadmin tool to disable Easy Login ........... 68 3.1.2.13.2 2. Manually disabling Easy Login ............................... 68 3.1.
5.5 Collaborating .................................................................................................................. 98 5.5.1 Creating a collaboration session ...................................................................... 98 5.5.2 Collaboration notification dialog .................................................................... 100 6 Advanced capabilities ................................................................................................... 102 6.1 General options ..
6.8.2 Remote Clipboard filtering ............................................................................. 141 6.8.3 Using the RGS log to detect clipboard problems .............................................. 143 6.9 Receiver and Sender logging ........................................................................................... 145 6.9.1 Receiver logging .......................................................................................... 145 6.9.2 Sender logging ..........................
8.6.7 Sender clipboard property ............................................................................ 180 9 Sender event logging on Windows ............................................................................... 181 9.1 The HPRemote log .......................................................................................................... 181 9.2 Usages of the HPRemote log ............................................................................................ 184 9.
A.3.2 Install the RGS Sender on View Master/Parent VM and modify the configuration file to optimize for VMware View environment ...................................... 215 A.3.3 Install View Agent on View Master/Parent VM ....................................... 216 A.3.4 Install the RGS Receiver and View Client on the client computers .............. 216 A.4 Running RGS diagnostics .......................................................................................... 216 A.
List of tables Table Table Table Table 2-1 Computers and operating systems that support RGS 5.4.0 ........................................................ 10 2-2 Computers and operating systems that support RGS 5.4.0 ........................................................ 11 2-3 Receiver Remote USB Support ................................................................................................ 30 2-4 Sender Remote USB Support ........................................................................
List of figures Figure Figure Figure Figure 1-1 1-2 1-3 2-1 Typical RGS configuration ...................................................................................................... 3 RGS Sender and Receiver ...................................................................................................... 4 Features of HP RGS ............................................................................................................... 5 RGS version numbering ...................................
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 3-11 3-12 3-13 3-14 3-15 3-16 3-17 4-1 4-2 4-3 4-4 4-5 4-6 4-7 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 3D Updates tab ................................................................................................................
Figure 6-12 Audio controls ................................................................................................................ 113 Figure 6-13 USB configuration during Receiver installation —USB devices are Local or Remote .................. 116 Figure 6-14 USB tab options .............................................................................................................. 116 Figure 6-15 Prior to remote attachment of the USB drive key ..................................................
xvi ENWW
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 149—Establishing RGS connections using Directory Mode is described in this chapter. Chapter 8: RGS properties on page 153—This chapter describes each of the RGS Sender and Receiver properties. Chapter 9: Sender event logging on Windows on page 181—This chapter describes the Windows Event Logging capability of RGS.
1.1 Typical RGS configuration Figure 1-1 Typical RGS configuration on page 3 shows a typical RGS configuration, consisting of a blade workstation and a thin client. The user’s applications run on the blade workstation while the user interacts with these applications from the thin client. Figure 1-1 Typical RGS configuration The blade workstation desktop image is transmitted over the network to the thin client, which displays the desktop image locally in a window.
1.2 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.
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. Go to the last page, select Current Page in the print dialog, and select Properties to view the paper size and orientation options. Depending on your printer, paper size may be listed as tabloid, size B, or size A3.
1.8 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.
Table 2-2 Computers and operating systems that support RGS 5.4.
2.2 RGS version numbering The RGS version (for example, version 5.4.0) contains the following three numbers: 1. Version major number 2. Version minor number 3. Version 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. major – A major release contains sufficient changes such that interoperability with the prior major release is not guaranteed. For example, Sender version 5.4.
connect to an RGS Sender. In licensing terminology, a floating license is checked-out when a connection is established to the RGS Sender, and is checked-in when the connection terminates. Floating licenses allow a company to purchase, for example, 75 licenses but support a user community of perhaps hundreds of users as long as no more than 75 users ever attempt to establish an RGS connection simultaneously.
NOTE: Except for the 60-day HP RGS Desktop Trial Edition, the above RGS products never expire once they are installed and licensed. When you purchase RGS, you are entitled to free upgrades to all future patch releases. For example, if you purchase RGS 5.4.0, you are entitled to a free upgrade to patch release 5.4.1, if available. In order to upgrade to new enhancement releases, you must purchase RGS Software Assurance or repurchase a new license at upgrade time.
2.7 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. The port used by the RGS Receiver is assigned by the Local Computer OS and can vary. HP recommends full-duplex operation between the Sender and Receiver. For information on using RGS through a firewall, see Using RGS through a firewall on page 84. Beginning in RGS 5.4.
The monitor itself is optional on the Remote Computer. For example, if the Remote Computer is a Personal Workstation, a monitor (plus a keyboard and mouse) would typically be attached. If the Remote Computer is an HP ProLiant Blade Workstation, it is not possible to attach a monitor to view the primary (NVIDIA) frame buffer because the video signal from the NVIDIA graphics adapter is not available on a connector—the contents of the frame buffer can only be viewed remotely using RGS.
Figure 2-5 Addition of scroll bars if the Remote Display Window is resized smaller NOTE: RGS does not provide a scale-to-fit capability to allow the contents of the Remote Computer frame buffer to be scaled to fit the Local Computer monitor. If the Remote Computer frame buffer is larger than the Local Computer monitor, the Remote Display Window will simply extend beyond the edges of the monitor. If the Remote Display Window is resized to fit on the monitor, scroll bars will be added. 2.8.
The many-to-one connection capability allows implementation of a virtual KVM (keyboard, video, and mouse) switch. The virtual KVM switch emulates the functionality of a standard KVM switch in software to provide a convenient method to connect a single monitor, keyboard, and mouse (all on the Local Computer) to multiple Remote Computers. Using the RGS Setup Mode (see Setup Mode on page 89) you can switch the local monitor to display each of the Remote Computer frame buffers.
Figure 2-8 Sharing between workstations In Figure 2-8 Sharing between workstations on page 19, the primary user is directly logged into the Remote Computer using its attached keyboard, mouse and monitor. In other words, the primary user is physically present at the Remote Computer, while local user 1 and local user 2 are physically separate from the Remote Computer. RGS can be used by local users 1 and 2 to connect to the primary user’s desktop. 2.
If another user is already logged into the Remote Computer, the second authentication step is replaced by an authorization step, in which the currently logged-in user receives an authorization prompt to allow or disallow the new user to join (connect to) the existing desktop session (see Figure 2-10 RGS connection process if another user is already logged into the Remote Computer on page 20).
For example, a 3rd party fingerprint reader will typically install a custom GINA module. The GINA module will allow the user to be authenticated through their standard username/password mechanism (because the GINA modules are chaining) or with their fingerprint. The fingerprint reader would be physically attached to the Local Computer but would be logically connected to the Remote Computer using remote USB.
Computer, which, for this particular Remote Computer, requires two monitors to display the Windows desktop. Figure 2-11 Remote Computer frame buffer requires two monitors to view the Windows desktop When a Local Computer establishes an RGS connection to the Remote Computer of Figure 2-11 Remote Computer frame buffer requires two monitors to view the Windows desktop on page 22, the Remote Computer will, as usual, transmit its complete frame buffer.
Figure 2-13 Each Remote Display Window can be positioned to occupy a single monitor As always, each Remote Computer (Sender) frame buffer is displayed in its own Remote Display Window. In Figure 2-13 Each Remote Display Window can be positioned to occupy a single monitor on page 23, the user has positioned each Remote Display Window to occupy a single monitor, achieving the result that the left monitor is dedicated to Remote Computer 1 while the right monitor is dedicated to Remote Computer 2. 2.
this enables RGS to be used on standard networks. Image decompression is performed on the Local Computer. RGS supports setting of the Image quality on a per-Receiver basis. Image quality is adjusted using the slide bar in the Remote Display Window Toolbar (see Figure 2-14 Image quality slide bar in the Remote Display Window Toolbar on page 24). As the image quality is increased toward 100, the amount of compression decreases, and the required network bandwidth increases.
In Figure 2-15 Remote Computer can access the local USB devices on page 24, two USB devices are connected to the Local Computer. Using RGS, the local USB devices can be attached to the Remote Computer. The keyboard and mouse always remain connected to the Local Computer, and cannot be attached to the Remote Computer. The local USB devices can be collectively attached to a single Remote Computer (see Figure 2-16 The local USB devices can be attached to only one Remote Computer at a time. on page 25).
NOTE: The Remote USB configuration cannot be changed after installation of the Sender and Receiver—to select a different USB configuration option, the Sender or Receiver must be uninstalled and reinstalled. During installation of the RGS Receiver, you can select one of three Remote USB Configuration options, local, remote or local then remote. This is referred to as legacy mode. The local/remote in legacy mode does not re-enumerate. It supports what was called "captureOnConnect".
NOTE: 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.0 introduced a new auto-remote configuration syntax for the Windows Registry entries. Auto-remote allows specified USB devices to be automatically attached to a remote Sender session at RGS connection and then returned to the local client at RGS disconnect.
devices, as described above. With RGS 5.3.0, smartcard readers are now handled in a unique manner, as follows: ● Unique smartcard handling requires, on the Sender, that Easy Login be enabled and that the chaining GINA module msgina.dll 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.
Table 2-3 Receiver Remote USB Support Receiver Remote USB Support Matrix Windows XPe/WES Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows Vista Business, Ultimate and Enterprise 32bit, 64-bit Embedded Linux Windows 7 Professional and Enterprise 32 bit and 64 bit Desktops Personal Workstations X X Mobile Workstations X X Desktop PCs X X Notebook PCs X X Performance Thin Clients HP GT7725 HP GT7720 HP GT7720w HP ThinPro GT XPe WES HP dc73 Blade WS Client HP Blade WS Client HP dc7
Table 2-4 Sender Remote USB Support Sender Remote USB Support Matrix Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows Vista Business, Ultimate and Enterprise 32-bit, 64-bit Windows 7 Professional and Enterprise 32 bit and 64 bit Blade Clients HP Blade Workstations X X 32–bit only 32–bit non-aero only 32–bit hosted desktop 32–bit non-aero only Personal Workstations X X Mobile Workstations X X Desktop PCs X X Notebook PCs X X HP Blade PCs VDI Servers Desktops 2.16.
2.17.1 Remote audio on Windows RGS on Windows supports remote audio, allowing audio generated by the application on the Remote Computer to be captured and transmitted to the Local Computer for playback. In addition, microphone input on the Local Computer running Microsoft Windows XP can be sent to the application running on the Remote Computer also using Microsoft Windows XP. Remote microphone is not supported on Microsoft Windows Vista and Windows 7.
Table 2-5 Windows RGS audio data paths ENWW 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.
2.17.2 Remote audio on Linux RGS on Linux also supports remote audio, allowing audio generated by the application on the Remote Computer to be captured and transmitted to the Local Computer for playback (presuming the Remote Computer has a physical audio device installed). In addition, microphone input on the Local Computer can be sent to the application running on the Remote Computer. However, unlike Windows, microphone input on Linux can be provided only via the remote USB driver.
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: Linux does not support locallymounted USB microphones. NOTE: HP Blade Workstations do not contain audio devices.
To remotely attach USB microphones to the Remote Computer, either of these Remote USB Configuration settings can be selected: ● USB devices are Remote ● USB devices are Local/Remote 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-7 Computers and operating systems that support RGS audio (continued) Receiver Audio Support Matrix Windows XPe/ WES Windows XP Professional SP1, SP2, SP3 32-bit, x64 Windows Vista Business, Ultimate and Enterprise 32bit, 64-bit Embedded Linux RHEL V4 (update 5 or later) V5 (update 2 or later) 32-bit, 64-bit Windows 7 Professional and Enterprise 32 bit and 64 bit Notebook PCs X X Performance Thin Clients HP GT7725 HP GT7720 HP GT7720w HP ThinPro GT XPe WES HP dc73 Blade WS Client HP Blade
Table 2-8 Computers and operating systems that support RGS 5.4.
Figure 2-22 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-23 Enabling Remote Clipboard during Sender and Receiver installation on Microsoft Windows systems. For details on using Remote Clipboard, see Remote Clipboard operation on page 137 Following installation, Remote Clipboard on Windows can be enabled or disabled via a toggle in the Receiver's controls.
2.19 Interoperability of RGS and Microsoft Remote Desktop Connection This section discusses interoperability considerations for RGS and Microsoft Remote Desktop Connection (RDC). Because RGS and RDC both provide connection to a remote desktop, their interoperation is important to understand. If a local user is connected to a Remote Computer using RDC, and then attempts to establish an RGS connection, the RGS connection only works if the local user credentials match for both connections.
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. 2.22 Supported keyboard locales The following keyboard localizations are supported when connected to a Linux Sender: 1. French 2. German 3. Japanese 4. Norwegian 5. Swedish 6. United Kingdom 7. U.S.
21. Swedish 22. Swiss French 23. Swiss German 24. Turkish Q 25. United Kingdom 26. United Kingdom Extended 27. United States-International 28. US 2.23 RGS security features Because of the distributed nature of an RGS connection, providing connection security is critically important.
44 ● 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. Simply rightclick on the GUI and select Disconnect->Everyone. ● Remote Keyboard/Mouse: The Sender GUI can enable or disable mouse and keyboard input for all collaboration users.
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 46 and Remote USB overview on page 24). 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. If USB devices are Remote or USB devices are Local/Remote is chosen on Windows Vista or Windows 7, the following certificate installation dialog will be presented. Installation of the certificate is required for installation of the RGS remote USB driver. Select Yes, install the certificate to continue installing the Receiver.
5. The Remote Clipboard Configuration dialog is displayed next (seeFigure 3-3 Remote Clipboard Configuration dialog on page 48 and Remote Clipboard overview on page 38). 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-3 Remote Clipboard Configuration dialog NOTE: Selecting “Yes” will cause the hprclipboard.dll library to be installed with the RGS Receiver.
3.1.1.2.1 Usage Setup.exe /autoinstall /agreetolicense [/folder=] [/usb=local | /usb=remote | /usb=localRemote] [/clipboard] [/noreboot] [/removesettings] Setup.exe /autoremove [/noreboot] Setup.exe /viewlicense Setup.exe /help 3.1.1.2.2 Command line options /autoinstall This option performs one of the following: ● Installs the Receiver if it's not already installed. ● Updates the Receiver if a prior version of the Receiver is already 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.
3.1.1.4 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 Change/Remove. A dialog box will open with choices for: Repair or Remove. 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.
● Enable Remote Clipboard—Check this box if your Local Users will need Remote Clipboard capability. For further information, see Remote Clipboard overview on page 38 ● I’m not sure, I want more information—For further information, check this box, and click Next. Figure 3-4 Dialog to enable or disable Remote USB in the Sender NOTE: For many USB devices, the Windows operating system provides default USB drivers.
4. On Windows Vista and Windows 7, the following dialog for installing the RGS driver certificate is presented. Installation of the certificate is required to install the RGS Sender drivers. Select Yes, install the certificate to continue installing the Sender.
5. If you are installing the Sender on HP blade workstations or HP personal workstations running Windows XP Professional, you will be presented with a dialog to enable either Single Sign-On or Easy Login. If you’re not sure, you will be able to configure them later using the rgadmin.exe tool.
6. 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.
dialog Figure 3-8 Output of the RGS Diagnostics Tool on page 56 shows the output generated by the tool. Figure 3-8 Output of the RGS Diagnostics Tool The Test Name left panel shows the list of tests that have been run. Selecting a test with the mouse will display additional information in the Results right panel. The Rerun Tests button on the bottom left reruns all tests. The example window shows that all tests have passed with the exception of the Service dependencies test.
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-9 The Remote Graphics Sender service 3.1.2.4 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 127 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 127 for more details.
3.1.2.5 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-10 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. 3.1.2.7 Setting the Sender process priority using PTF The HP Performance Tuning Framework (PTF) can be used adjust the priority of the Sender without having to use regedit. PTF is available for HP Workstations only from this location: http://www.hp.
The GINA Setup tab on the rgadmin tool can be used to enable Single Sign-on and Easy Login (see Figure 3-12 Dialog to enable or disable Single Sign-on and Easy Login on page 61). When rgadmin is brought up, it reports the current status of Single Sign-on and Easy Login. To change the status, check the desired radio button. After clicking Apply, you’ll be requested to restart your computer—this is required in order for the new setting to take affect.
on or Easy Login on page 62). If Single Sign-on is enabled, the computer must be restarted before Single Sign-on is operational. Figure 3-13 The dialog presented during Sender installation to enable Single Sign-on or Easy Login 3.1.2.9.2 Using the rgadmin tool to enable Single Sign-on NOTE: The rgadmin tool is only installed and supported on Windows XP.
Figure 3-14 Using the rgadmin tool to enable Single Sign-on 3.1.2.9.3 Manually enabling Single Sign-on 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.
4. Set the value of the GinaDLL key to the text "hprgina.dll". Confirm the spelling before closing. Figure 3-15 Addition of the GinaDLL key to the registry on page 64 shows the registry key contents. Figure 3-15 Addition of the GinaDLL key to the registry 5. Add the GinaDllMode registry key if does not already exist. This can be done through the use of regedit as well. Create the key as type RGS_SZ (a string type).
CAUTION: If the value of the GinaDLL key contains the name of a custom GINA DLL, and the file does not exist in C:\WINDOWS\system32, the computer will not start correctly after the next reboot. The computer will then require a complete re-installation of the operating system. GinaDLL key is removed using regedit, the Windows Registry Editor. Be sure to actually remove the key by selecting the GinaDLL key in regedit, and select the Delete entry in the Edit menu.
3.1.2.11.3 3. Manually enabling Easy Login 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.
GINA module rather than the default msgina.dll as described above. There are three ways to enable the hprgina.dll module to load a custom GINA module: 3.1.2.12.1 1. Install time specification of the custom GINA module A custom GINA module can be chained by the hprgina.dll at install time. This is the preferred method. The installer will bring up a GUI that allows the Easy Login GINA module (hprgina.dll) to be enabled, as well as provides a text box to enter the name of the custom GINA module.
3.1.2.13 Disabling Easy Login There are two methods to disable Easy Login: 3.1.2.13.1 1. Using the rgadmin tool to disable Easy Login The rgadmin tool shown in Figure 3-12 Dialog to enable or disable Single Sign-on and Easy Login on page 61 can be used to disable Easy Login. Using the rgadmin tool to disable Easy Login is preferred over the manual method, described next. 3.1.2.13.2 2.
3.1.3.1 Usage Setup.exe /autoinstall /agreetolicense [/folder=] [/usb] [/remotemic] [/clipboard] [/sso | [/el [/gina=]]] [/rgslicenseserver= | /rgslicensefile=] [/noreboot] [/removesettings] Setup.exe /autoremove [/noreboot] Setup.exe /viewlicense Setup.exe /help 3.1.3.2 Command line options /autoinstall This option performs one of the following: ● Installs the Sender if it's not already installed.
/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. /rgslicenseserver= The license to run the RGS Sender is acquired from a license server listening on the specified port and host.
/noreboot Do not reboot the system when the setup requires a reboot to complete. /removesettings Removes the user specific Sender settings from the registry. /viewlicense Displays the EULA (End User License Agreement) for use of this software. /help Display usage text. 3.1.4 Sender installation log file on Windows As with installation of the Receiver, installation of the Sender also creates an installation log file.
3.2 Installing RGS on Linux This section describes how to: ● Install and uninstall the RGS Receiver on Linux ● Audio requirements for the Linux Receiver ● Install and uninstall the RGS Sender on Linux. NOTE: The RGS Sender uses TCP/IP port 42966. 3.2.1 Installing the Receiver on Linux NOTE: Beginning with RGS 5.1.3, the Linux RGS Receiver is available in both 32-bit and 64-bit versions. To install the RGS Receiver on Linux, perform the following steps: 1. Login as root. 2.
RGS Receiver installer is the version that is expected to be started by the script in /opt/hpremote/ rgreceiver/hprgsaudio. A different version may require adjustments to this script to provide different options for the JACK daemon. The JACK Audio Connection Kit is installed as an RPM package. The RGS Receiver will run on systems without audio hardware, but the Receiver will not run without the libraries provided by the JACK RPM package.
5. If you choose not to use the customization described in step 5, or have a different configuration file that needs to be updated, perform the following steps to update the respective configuration: a. Add the "rge" extension to the X Server configuration file. Edit the /etc/X11/XF86Config, / etc/X11/XF86Config-4 or the appropriate XF86Config file on your system for XFree86 X servers. Edit the xorg.conf file for X.Org X Servers.
auth optional /lib/security/pam_custom.1 8. 8. The RGS Sender will not accept remote connections when a DNS name inquiry does not resolve to a valid/active IP address—the Sender expects to fully resolve the machine name to an 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.
3.2.4.2 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.1.0-1 rgsender_config_64-5.1.0-1 3. To remove the rgsender package (and corresponding configuration rpm if used), execute the command: rpm -e --allmatches rgsender_linux_64 rgsender_config_64 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.
4.2 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 79 . 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 80. 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 81). 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 81).
Figure 4-4 Advanced Settings dialog The arrows to the right of the Connections box in Figure 4-4 Advanced Settings dialog on page 82 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 82) 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 83).
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 179 for a description of these properties. 4.4 Using RGS through a firewall New at RGS 5.1.5 is the ability for the Receiver to use the public IP address of the Sender.
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 179.
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 5.
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. 5.1.1 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 149).
The default hotkey sequence can be changed using the Hotkeys tab in the Receiver Control Panel (see Hotkeys on page 135). 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.
● 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. ● Borders button—Adds or removes window borders and decorations on the Remote Display Window.
display the login dialog on the Local Computer. The Remote Computer monitor will remain blank while this occurs but the monitor will exit its powersave mode, and keyboard input will become unblocked until this dialog is dismissed.
/usr/contrib/bin/X11xprop -root -remove _SGI_CROSSHAIR_CURSOR /usr/contrib/bin/X11xprop -root -remove _HP_CROSSHAIR_CURSOR This will force the application to use an X cursor, which will display correctly on the Receiver. 5.2.2 Gamma correction on the Receiver The color on a 3D application on the Sender can look incorrect when displayed on a Receiver. This is because the gamma of the Local Computer monitor may not match the gamma of the Remote Computer monitor.
5.3 RGS login methods RGS provides three methods for the local user to log into a Remote Computer: ● Standard Login—supported on Windows and Linux Senders. For an overview of Standard Login Establishing an RGS connection using Standard Login on page 19. ● Easy Login—supported on Windows XP Professional Senders on HP blade workstations. ● Single Sign-on—supported on Windows XP Professional Senders on HP blade workstations and HP personal workstations.
See the tabloid page (the last page of the PDF version) of this guide for a diagram of the Standard login process. 5.3.2 Easy Login The Easy Login flowchart is shown in Figure 5-10 Easy Login process on page 96. 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.
5.3.3 Single Sign-on The Single Sign-on flowchart is shown in Figure 5-11 Single Sign-on process on page 97. 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 5.4 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 98). 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 98).
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 99). 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. To transition the floor owner, the current floor owner must cease using the keyboard or mouse for a short period of time (0.
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.
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. The primary user is italicized and listed first. Collaboration usernames follow, and are displayed using a normal font. The figure above shows three active connections, one a primary user and the other two collaboration users.
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 102. 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.
6.1 General options The options available under the General tab are shown in Figure 6-2 General tab options on page 103. Figure 6-2 General tab options The options available under the General tab are: ENWW ● Prompt for username and password—In certain scenarios (such as silent authentication as described in Standard Login on page 95) the Receiver will not prompt the local user for a domain, username, and password.
single Sender physical display resolution of 2560x1024. If that fails, an error is reported to the local user. For information on the properties associated with the above two checkboxes, see Receiver general properties on page 159—specifically, see the Rgreceiver.IsMatchReceiverResolutionEnabled and Rgreceiver.IsMatchReceiverPhysicalDisplaysEnabled properties. ● Select help browser—Enables the user to specify a web browser, such as mozilla, to display online help.
possible with the current RGS protocol. See Application support on page 14 for the official description of supported applications. 6.4 Remote audio operation For an overview of remote audio, see Remote audio on page 31. Before describing the RGS audio capabilities available under the Receiver Control Panel Audio tab, Sender audio configuration and calibration are described. 6.4.
Figure 6-4 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 178. 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-3 Sound and Audio Devices Properties dialog on page 105. This brings up the Recording Control window (see Figure 6-5 Select Recording Control Properties on page 107). 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-6 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-7 Recording Control dialog on page 108). Make sure this item is selected, and the volume level is not at the lowest setting. Figure 6-7 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.
6.4.2 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-9 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-10 Sound and Audio Devices Properties dialog on page 111.
Figure 6-10 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.
6.4.3 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.
6.4.5 Using audio The audio controls in the Receiver Control Panel are shown in Figure 6-12 Audio controls on page 113. Figure 6-12 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 116. For a discussion of the USB installation options, see Installing the Receiver on Windows on page 45. Figure 6-13 USB configuration during Receiver installation —USB devices are Local or Remote 6.5.1 Attaching a local USB device to a Remote Computer The options available under the USB tab in the Receiver Control Panel are shown in Figure 6-14 USB tab options on page 116.
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. Because remote USB supports hot plug connections, it is not necessary to disable remote USB before plugging or unplugging USB devices on the Local Computer.
6.5.2 USB session switching New with RGS 5.1.3 is the ability to dynamically move USB devices from one Remote Computer to another. This enables USB devices to be detached from one Remote Computer, and made accessible by another Remote Computer without first needing to disconnect the RGS connections.
To specify auto-remoting of a particular USB device, perform the following steps: 1. Get the vendor id and device id for your usb device using the following steps. For this example assume that you found the vendor id is 0x1234 and device id is 0x5678. a. Open Device Manager and find the USB device to be auto-remoted. b. Right click the USB device and select Properties. c. Select the Details tab and select Hardware Ids in the dropdown menu.
devices are denied attachment. The ACL file, which resides on the Remote Computer, supports allowing/denying USB device attachments based on the following nine USB descriptor fields: 1. Device Class 2. Device Subclass 3. Device Protocol 4. Vendor ID 5. Product ID 6. Device BCD 7. Manufacturer 8. Product Type 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.
Rules may contain filters based on the 11 parameters listed previously. These parameters are repeated below along with the name of the filter element. 1. Device Class— bDeviceClass 2. Device Subclass— bDeviceSubclass 3. Device Protocol— bDeviceProtocol 4. Vendor ID— idVendor 5. Product ID— idProduct 6. Device BCD— bcdDevice 7. Manufacturer— manufacturer 8. Product Type— product 9.
6.5.6.1 Determining USB device information for Windows To obtain the Vendor ID and the Product ID for a USB device on Windows, perform the following steps: 1. Open the device manager. ● Go to the Control Panel and run "System" ● Select the "Hardware" tab ● Select the "Device Manager" button, this runs the device manager program. 2. Double click on the Universal Serial Bus Controllers 3. Double click on the specific device, which brings up a separate window. 4.
that contain most of the registered Vendor IDs and Device IDs. There are different documents that contain the different registered classes and subclasses. By comparing the values of the device to these documents, the user can verify that they are looking at the correct device and not some other device that is also plugged into the system. The linux-usb group keeps an up-to-date list of registered USB Vendor IDs and Device IDs. This document resides on the http://www.linux-usb.org site at: http://www.
6.5.6.4.5 Enable Remote USB Verify that Remote USB is enabled under the USB option tab of the Receiver Control Panel (see Figure 6-18 Checkbox to enable Remote USB on page 124).
6.5.6.4.6 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-19 HP Remote Virtual USB driver on page 125). Figure 6-19 HP Remote Virtual USB driver If the HP Remote Virtual USB driver is not reported, reinstall the RGS Sender software.
Figure 6-20 Enable installation of remote USB 6.5.6.4.7 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.
6.6 Adjusting Network timeout settings The options available under the Network tab in the Receiver Control Panel are shown in Figure 6-21 Options available under the Network tab on page 127. Figure 6-21 Options available under the Network tab RGS supports three classes of user-settable timeouts: 1.
6.6.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-22 Receiver Control Panel on page 129 shows the default Receiver timeout periods and the corresponding timeout properties. Figure 6-22 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-23 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.
have a dialog to set this property. The Sender error timeout property is independent of the Receiver timeout properties. For legacy reasons, the Sender begins by using the maximum of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.Dialog property (see Dialog timeouts on page 133). When the Receiver negotiates its connection to the Sender, it notifies the Sender of its error timeout property. For sync pulse timeout purposes, the Sender adopts the minimum of: Rgreceiver.Network.
◦ The Remote Computer CPU utilization prevented the Sender from making progress, ◦ The length of this connectivity loss exceeds the Receiver’s error timeout value, controlled by the Receiver’s Rgreceiver.Network.Timeout.Error property so the Receiver disconnected. If this condition persists, it is possible that network disruptions are exceeding the Receiver error timeout value.
computer determines that network connectivity is lost and an error returns by the network stack to the Receiver, then the connection will disconnect sooner than the error timeout setting. If the Sender’s timeout values are shorter than the Advanced capabilities Receiver’s, the Sender may close the connection sooner than the Receiver, disconnecting the Receiver. If the issue continues, consider increasing the Sender's error timeout value.
The Sender dialog timeout property, Rgsender.Network.Timeout.Dialog, can only be set using the rgsenderconfig file and from a command line—there is no dialog on the Sender for setting this property. The default value of this property is also 15 seconds. The 15 second Receiver and Sender dialog timeouts should support most authorization and authentication scenarios. For more complex scenarios requiring additional time, the user should adjust both the Receiver and Sender dialog timeouts appropriately.
6.7 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-24 The Hotkeys tab options on page 135).
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 104 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-26 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.
computer or paste computer. Figure 6-27 Cut and paste computer nomenclature on page 140 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-27 Cut and paste computer nomenclature Figure 6-28 Cutting and pasting between Remote and Local Computers on page 141 show a system consisting of three Remote Computers connected by RGS to the Local Computer.
Figure 6-28 Cutting and pasting between Remote and Local Computers 6.8.2 Remote Clipboard filtering When a cut is performed, applications typically store their data in the clipboard in multiple formats. For a word processing application, the application might store data in the clipboard as both ASCII text and Rich Text Format. This increases the likelihood that, when the paste occurs, there will be a format recognized by the receiving application.
filtering of cut and paste data on page 142, which expands on Figure 6-27 Cut and paste computer nomenclature on page 140 to show receiving-side filtering. Figure 6-29 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.
● 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. This format is supported by other applications as well.
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.FilterString="|1|2|13|Object Descriptor|HTML Format|" 2. Establish an RGS connection from the Receiver to the Sender. 3. Open Notepad on the Receiver computer. 4.
Figure 6-32 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. 6.
enabled and the location/name of the log file(see Figure 6-33 Options available under the Logging tab on page 146). Figure 6-33 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-32 Remote Clipboard log entries for cut and paste on page 145. Figure 6-34 logSetup file The highlighted, uncommented line specifies that INFO-level logging is used.
6.10 Statistics The options available under the Statistics tab in the Receiver Control Panel are shown in Figure 6-35 Options available under the Statistics tab on page 148. Figure 6-35 Options available under the Statistics tab The Statistics tab displays aggregate data for all connected sessions. 148 ● Total network usage (Mbits/sec)—The combined network traffic received from all Remote Computers.
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.
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. If Setup Mode is activated by the hotkey sequence (as opposed to the Setup Mode button), and you have multiple Remote Display Windows on your computer, you can bring up the Remote Display Window selection dialog to view a thumbnail image of each Remote Display Window.
● Clicking directly on a thumbnail. ● Double clicking the mouse on a thumbnail (this will also immediately close the selection dialog). When the initial Setup Mode hotkey is released, the selected Remote Display Window is brought to the forefront and displayed.
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. 8.
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.
8.5 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.
8.5.1.5 Receiver default properties The Receiver has a set of default properties that are built into the Receiver. These are identical to the property values in the Receiver configuration file (rgreceiverconfig) that is installed with the RGS Receiver. However, as noted previously, the properties in both the Receiver and Sender configuration files are initially commented out. 8.5.
● Microphone property group ◦ ● ● ● ● ● ENWW Rgreceiver.Mic.IsEnabled USB properties group ◦ Rgreceiver.Usb.IsMutable ◦ Rgreceiver.Usb.ActiveSession ◦ Rgreceiver.Usb.IsEnabled Network properties group ◦ Rgreceiver.Network.Timeout.IsMutable ◦ Rgreceiver.Network.Timeout.IsGuiEnabled ◦ Rgreceiver.Network.Timeout.Warning ◦ Rgreceiver.Network.Timeout.Error ◦ Rgreceiver.Network.Timeout.Dialog Hotkey properties group ◦ Rgreceiver.Hotkeys.IsMutable ◦ Rgreceiver.Hotkeys.
● ◦ Rgreceiver.Log.MaxFileSize ◦ Rgreceiver.Log.NumBackupFiles Image codec properties group ◦ Rgreceiver.ImageCodec.IsMutable ◦ Rgreceiver.ImageCodec.Quality ◦ Rgreceiver.ImageCodec.IsBoostEnabled Per-session properties ● ● Auto Launch property set. (Microsoft Windows only) See Auto Launch on page 104 for general details. ◦ Rgreceiver.Session..IsConnectOnStartup ◦ Rgreceiver.Session..Hostname ◦ Rgreceiver.Session..Username ◦ Rgreceiver.Session..Password ◦ Rgreceiver.
property is true, the user is allowed to interactively change the associated property, that is, the Rgreceiver.Network.Timeout.Error property. NOTE: For clarity, the individual IsMutable properties are not shown in the previous list; however, they are included in the following detailed description of each property. NOTE: In order for the user to be able to interactively change a property, the group IsMutable property and the individual IsMutable property must both be 1 (true).
Rgreceiver.IsBordersEnabled=bool （default=1） Rgreceiver.IsBordersEnabled.IsMutable=bool （default=1） If set to 1, the borders on the Remote Display Window will be enabled (displayed). If set to 0, the borders will be removed creating a borderless windows to display the Remote Computer desktop. The default value is 1— the borders are enabled. Rgreceiver.IsSnapEnabled=bool （1） Rgreceiver.IsSnapEnabled.
Rgreceiver.IsMatchReceiverResolutionEnabled.IsMutable=bool （1） If this property is enabled, the Local Computer (Receiver) will attempt to set the resolution of the Remote Computer to the same full-screen resolution of the Local Computer. If the Local Computer display resolution is not supported by the Remote Computer, the connection occurs at the existing Remote Computer (Sender) resolution, and a warning dialog is issued to the user.
● Rgreceiver.Session..RemoteDisplayWindow.Y = 0 ● Rgreceiver.Session..VirtualDisplay.PreferredResolutionWidth = 1280 ● Rgreceiver.Session..VirtualDisplay.PreferredResolutionHeight = 1024 Then the Receiver will determine that one physical display with a resolution of 1280x1024 is contained within the window. The Receiver will try to set the layout of the Remote Computer Sender to a single physical display and a resolution of 1280x1024. If the following conditions are met: 1.
The default value of the warning color is 0x80b40000, representing the following: ● The alpha component is 0x80 (128 decimal. This is 50% transparent. ● The red component is 0xb4 (180 decimal). This is about 70% of full red (0xFF). ● The green component is 0x00. There is no green component. ● The blue component is 0x00. There is no blue component. NOTE: The following property, while supported, has been deprecated. HP recommends that the subsequent properties, Rgreceiver.
Figure 8-5 Prior to RGS 5.1.3, only one image update would be in-process at any time The Rgreceiver.MaxImageUpdateRequests property was added to enable performance optimization in high-latency network environments. For example, setting this property to 2 will allow the Receiver to issue a second image update request to the Sender prior to receiving the previous image update response.
issuance of image update request #4. Also, TCP will temporarily block the Sender from sending further data if the Receiver network buffer becomes full. Nonetheless, the sequence shown in Figure 8-6 Sequence chart for the default property value of 4 on page 164 serves to parallelize local display updates that otherwise would occur serially. The default property value of 4 was determined empirically as a good compromise for both low and high-latency network environments.
This property was added with RGS 5.4.0 and allows the user to disable the Remote Display Window Toolbar functionality. When the Rgreceiver.IsMenubarEnabled property is set to 1 the user will be able to display the Remote Display Window Toolbar by pressing the Hotkey-H. When the Rgreceiver.IsMenubarEnabled property is set to 0 the user will be unable to access the Remote Display Window Toolbar by pressing Hotkey-H. In other words, when the property is disabled the Hotkey-H command is turned off.
Rgreceiver.Audio.IsInStereo=bool （1） Rgreceiver.Audio.IsInStereo.IsMutable=bool （1） If set to 1, stereo is enabled, and both the left and right channels are transmitted. The highest quality audio (2) with stereo enabled is equivalent to CD quality audio but consumes more network bandwidth. The default value is 1—stereo is enabled. 8.5.6 Receiver microphone property Rgreceiver.Mic.IsEnabled=bool （0） Rgreceiver.Mic.IsEnabled.IsMutable=bool （1） This property is new with the RGS 5.1.3 release.
This property was added with RGS 5.4.0 and allows the user to disable a visual notification when the network has timed out. When the Rgreceiver.Network.Timeout.IsGuiEnabled property is set to 1 the network timeout is shown. When the Rgreceiver.Network.Timeout.IsGuiEnabled property is set to 0 the visual network timeout notification is not shown. See Receiver network timeouts on page 128 for more details. Rgreceiver.Network.Timeout.Warning=int （2000） Rgreceiver.Network.Timeout.Warning.
Rgreceiver.Hotkeys.IsSendFirstKeyInSequenceEnabled=bool （0） Rgreceiver.Hotkeys.IsSendFirstKeyInSequenceEnabled.IsMutable=bool （1） When enabled, the first key in the hotkey sequence is sent to the Remote Computer. The default value is 0—don't send the first key in the hotkey sequence. Rgreceiver.Hotkeys.IsKeyRepeatEnabled=bool （0） Rgreceiver.Hotkeys.IsKeyRepeatEnabled.IsMutable=bool （1） The hotkey sequence is very particular (for example, shift down, space down, space up).
This is a per-session property. If set to 1, Remote Clipboard is enabled for the session N Remote Display Window. In order for Remote Clipboard operation to be enabled for session N, the perreceiver property Rgreceiver.Clipboard.IsEnabled must also be 1. The default value for both properties (per-receiver and per-session) is 1—Remote Clipboard is enabled. Rgreceiver.Clipboard.FilterString=string（see below for the default value） NOTE: This property is for advanced users only.
If set to 1, the logging settings in the Receiver Control Panel can be changed by the user. If set to 0, the user will not be able to change any of the logging settings. This property can be used to permanently enable or disable logging settings before the RGS Receiver is started. The default value is 1—logging settings can be changed. Rgreceiver.Log.IsFileLoggerEnabled=bool （1） Rgreceiver.Log.IsFileLoggerEnabled.IsMutable=bool （1） If set to 1, logging output from the RGS Receiver will be sent to a file.
Rgreceiver.ImageCodec.Quality=int （65） Rgreceiver.ImageCodec.Quality.IsMutable=bool （1） This property sets the image quality in the Remote Display Window, and can be set to a value from 0 to 100. A value of 100 is the highest image while 0 is the lowest image quality. Under most circumstances, the default value of 65 will be sufficient. Lower values of Rgreceiver.ImageCodec.Quality will typically reduce RGS bandwidth requirements on the network. If the Sender property, Rgsender.ImageCodec.
Rgreceiver.Session..Username=string The username as a utf8 encoded string, to use if automatically connecting on start-up. Rgreceiver.Session..Password=string The password as a utf8 encoded string, to use if automatically connecting on start-up. Rgreceiver.Session..PasswordFormat=Encrypted | Clear | XOR The format of the password. RGS supports three formats Encrypted, Clear or XOR.
This property and the above property specify the preferred resolution of the Remote Display Window (in pixels). This resolution is communicated to the Remote Computer Sender, which will attempt to adapt its resolution to match the resolution preference of the Local Computer. If the Remote Computer is unable to match the resolution preference of the Local Computer, a warning dialog is displayed on the Local Computer NOTE: The per-session property Rgreceiver.Session..VirtualDisplay.
8.6.1 Sender property groups RGS supports the following groups of Sender properties: ● ● General properties group ◦ Rgsender.IsRdpLogoutDetectionEnabled ◦ Rgsender.IsCopyRegionEnabled ◦ Rgsender.IsRegionLimitEnabled ◦ Rgsender.IsDisconnectOnLogoutEnabled ◦ Rgsender.MaxImageUpdateRate ◦ Rgsender.ImageCodec.Preferred ◦ Rgsender.IsBlankScreenAndBlockInputEnabled ◦ Rgsender.IsIloRemoteConsoleEnabled ◦ Rgsender.IsAnonymousConnectionForceEnabled ◦ Rgsender.
8.6.2 Sender general properties Rgsender.IsRdpLogoutDetectionEnabled=bool （1） This property only applies to the Windows versions of the RGS Sender. When a user disconnects from a Remote Desktop Protocol (RDP) session, the Windows desktop on the Remote Computer is immediately available for an RGS connection. However, if the user logs out of the RDP session, the RGS Sender will be unable to access the desktop for about 60 seconds.
Rgsender.IsBlankScreenAndBlockInputEnabled=bool （1） If set to 1, this property enables monitor blanking on certain Remote Computers when a primary user logs in from a Local Computer. This property also enables blocking of input from a keyboard and mouse that are directly connected to the Remote Computer. If set to 0, monitor blanking is disabled. The default value is 1— monitor blanking is enabled. For details on monitor blanking, see Remote Computer monitor blanking operation on page 92. Rgsender.
Introduced at RGS 5.2.0, this property allows the user to enable or disable display of the collaboration notification dialog (see Collaboration notification dialog on page 100 ). If set to 1, the collaboration notification dialog is displayed. If set to 0, the collaboration notification dialog is not displayed. The default value is 1—display the collaboration notification dialog.
This property is used by the Sender remote USB code while monitoring the ACL file (hprDefaultUsbAcl.xml). If this file disappears or otherwise becomes inaccessible while the Sender is running, this property controls how long the Sender waits for the file to be restored. If the timeout expires, all currently connected USB devices are disconnected. If the file is restored prior to expiration of the timeout period, the USB devices remain connected. The default timeout value is 5,000 milliseconds (5 seconds).
Rgsender.Network.Port=int (42966) This property controls the port used for communications with the RGS Sender. If this property is not specified, the Sender will listen on port 42966, which is the default port used by the Receiver in establishing a connection to the Sender. If this property is used to modify the Sender port number, the 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 86. 8.6.
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. 9.
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 186 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 ENWW The HPRemote log 183
9.2 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.
9.3 Additional information on event logging For additional information on Windows event logging, search Microsoft Developer Network (MSDN) as shown in Figure 9-4 MSDN event logging information on page 185. 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. 10.
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.
10.3 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. 10.3.
10.3.3 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.
ENWW ● 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.
10.4 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.
{ 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. Strings and data will get appended to the EVENTLOGRECORD structure.
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... ... example only prints out retrieved record to console ... printf ("Event: %u Primary: %u Secondary: %u\n", dwEventNum, pData[0], pData[1]); } ...
// 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. Check the return value.
// 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. Sleep(1000); waitedFor += 1; } } return; } main( ... ) { ...
10.5 Additional features for Windows systems The following optional procedures for the RGS Sender service can improve the reliability of your remote agent solution. 10.5.1 RGS Sender Service Recovery Settings This section discusses restart options for the RGS Sender and possible interactions of the agent with the Sender. ENWW ● 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 10.5.2 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. 11.1 Performance tuning for all platforms The following suggestions apply to all platforms: ● Set the network to full-duplex mode—To obtain the best performance, the network between the RGS Sender 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.
11.4 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 206 which lists the RGS error messages and their potential causes. 12.1 Potential RGS issues and troubleshooting suggestions Table 12-1 Potential RGS issues and troubleshooting suggestions on page 205 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. 13.1 Receiver error messages 206 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! ENWW 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.
208 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 Appendix A: Using RGS with HP VDI This appendix describes how to use RGS with the HP Virtual Desktop Infrastructure (VDI) solution. Using RGS with HP VDI assumes you have a comprehensive working knowledge of VMware’s virtualization products and running Microsoft products within the VMware virtualization environment. For general information on HP VDI, please visit the website http://www.hp.com/go/vdi. For an overview of using RGS with HP VDI, see Using RGS with desktop virtualization on page 41.
ESX 3.0.2 RGS 5.2 and newer. Note that, unlike the other versions of VMware ESX, this version of VMware ESX requires RGS 5.2 or newer. ESX 3.0.2 Update1 RGS 5.1 or newer ESX 3.0.3 RGS 5.1 or newer. See NOTE. ESX 3.5 RGS 5.1 or newer ESX 3.5 Update 1, 2, 3, and 4 RGS 5.1 or newer ESX 4 RGS 5.1 or newer NOTE: During installation of Windows XP Professional on these versions of VMware, the USB driver file usbd.sys will not be installed.
A.2 Using RGS with static HP VDI Static HP VDI is a one-for-one replacement of a desktop computer by a virtual machine directly connected to a user on a client computer. To install RGS in a static HP VDI environment, perform the following three steps—these steps are expanded on subsequently. 1. Create a new virtual machine complete with Windows XP Professional and applications. 2. Modify the ESX configuration file for the virtual machine to support RGS. 3.
display the machine's properties. To edit the configuration parameters, click the Options tab and select the Advanced line item. Figure A-1 Virtual Infrastructure Client GUI Click the Configuration Parameters button inFigure A-1 Virtual Infrastructure Client GUI on page 212 to display the configuration parameters shown in Figure A-2 Configuration parameters dialog on page 213.
Figure A-2 Configuration parameters dialog NOTE: Not all configuration parameters can be added using the dialog shown above. Please see VMware View documentation for more details. When adding Svga options, it is recommended that you do this by manually editing the .vmx file. The Configuration Parameters that affect RGS functionality are: SMBIOS.reflectHost = TRUE NOTE: This parameter is needed for RGS versions prior to 5.2.0. It is no longer needed for RGS 5.2.0 and later versions.
This parameter tells the VMware virtual VGA device driver the maximum height of screen to support. This value may be set by GUI or by directly editing the .vmx file of the virtual machine. Svga.maxWidth = This parameter tells the VMware virtual VGA device driver the maximum width of screen to support. This value may be set by GUI or by directly editing the .vmx file of the virtual machine. Svga.
A.3 Using RGS with dynamic HP VDI (based on VMware View) In this document, dynamic HP VDI is based on using the VMware View manager. The following steps assume you are familiar with VMware View, and have read the View installation and configuration documentation—that information is not repeated here. To install RGS in a VMware View environment, perform the following four steps; these steps are expanded on subsequently. 1. Create a new virtual machine complete with OS and applications.
NOTE: Ensure that you remove the “#” from all lines you wish to activate in the rgsenderconfig file. 5. Save the rgsenderconfig file. Restart the RGS Sender or the Sender computer in order to have the new configuration file settings take effect. A.3.3 Install View Agent on View Master/Parent VM The VMware View Agent must be installed after RGS is installed. 1. Launch the View Agent install executable. 2. Install according to View Agent installation instructions. A.3.
A.5 Disabling the RGS warning popup RGS alerts the user when the main console is still viewable. The hardware feature used for screen blanking is not available in VMware ESX virtual machines. Therefore, by default, this warning message appears on the user’s desktop. The persistent “Sender Monitor is Viewable” popup can be removed by editing the rgsenderconfig file in the RGS Sender directory. This can be done by un-commenting the following line, and setting it as shown: Rgsender.
B Appendix B: 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 B-1 PDA devices (continued) Blackberry 7230 RGS 3.0 RGS 5.0 Desktop Manager 3.6 RGS 5.0 RGS 5.0 Desktop Manager 4.0 RGS 3.0 RGS 5.0 Desktop Manager 3.6 RGS 5.0 RGS 5.0 Desktop Manager 4.0 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.
Table B-3 Trader keypads (continued) RBS Greenwich Capital gSpeed RGS 4.2.0 RGS 5.0 Brokertech model 1 RGS 4.2.0 RGS 5.0 Table B-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.
Table B-6 USB keys (continued) PNY 1G RGS 5.0 RGS 5.0 Geek Squad 0.5 G RGS 5.0 RGS 5.0 Cruzer Mini 4G RGS 5.0 RGS 5.0 Lexar JumpDrive 256M RGS 5.0 RGS 5.0 HP 2G RGS 5.0 RGS 5.0 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.
Table B-10 Floppy drives USB Device HP Blade Workstation Clients Clients based on Windows XP and Windows XPe HP 3.5 inch RGS 5.0 RGS 5.0 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.
Table B-13 Human Interface Devices (continued) USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Notes HP Spaceball 5000 RGS 4.0.2 RGS 5.0 Magellan Spacemouse RGS 4.0.2 RGS 5.0 HP SpacePilot RGS 4.0.2 RGS 5.0 LLC504 Penpower HID device RGS 5.2.2 RGS 5.2.2 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.
Table B-16 Headsets USB Devices HP Blade Workstation Clients Clients based on Windows XP and Windows XPe Plantronics USB Audio 470 Headset RGS 5.2 RGS 5.2 Plantronics USB Audio 500 Headset RGS 5.2 RGS 5.2 Plantronics USB Audio 625 Headset RGS 5.2 RGS 5.2 Jabra GN8120 Headset RGS 5.2 RGS 5.2 Cyber Acoustics AC-840 Headset RGS 5.2 RGS 5.
C Appendix C: Linux remote audio device support As shown in Figure 2-21 RGS audio subsystem on Linux on page 34, 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”.
Local user Standard Login process and primary user flowchart local user attempt to log in using Standard Login primary user N Attempt to connect to Remote Computer Remote Display Window did someone else log in with my credentials ? RGS authentication dialog Windows-to-Windows connection AND local user credentials match any credentials on Remote Computer ? Y If another user attempts to connect to the Remote Computer with the same credentials as the local user, the local user Remote Display Window be
Index A Advanced capabilities 102 Auto Launch 104 Auto Launch session properties 172 C Collaborating 98 D Directory Mode 21, 149 E Easy Login 96 error messages 206 G Game Mode 104 General options 103 H Hotkeys 135 I Image quality 23 Installing RGS 45 K keyboard locales 42 L Logging 145 login methods 95 M Many-to-one connection 17 Microphone property group 178 monitor blanking operation 92 monitor blanking overview 23 Multi-monitor configurations 21 N Network Interface binding properties 179 Network timeou
