HP Remote Graphics Software 7.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Microsoft, Windows, and Windows Vista are U.S. registered trademarks of the Microsoft group of companies. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Acknowledgments HP Remote Graphics Software was developed using several third party products including, but not limited to: OpenSSL: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software written by Tim Hudson (tjh@cryptsoft.com). This product includes cryptographic software written by Eric Young (eay@cryptsoft.
iv Acknowledgments
About this guide This guide uses the following styles to distinguish elements of text: Style Definition Variables or placeholders are enclosed in angle brackets. For example, replace with the appropriate path, such as C:\Windows\System. When typing the actual value for the variable, omit the brackets. [optional parameters] Optional parameters are enclosed in square brackets. When specifying the parameters, omit the brackets.
vi About this guide
Table of contents 1 Getting started in Windows ............................................................................................................................... 1 2 RGS overview ................................................................................................................................................... 2 Typical RGS deployment ...................................................................................................................... 3 User interface overview ..
Installing RGS on Linux ...................................................................................................................... 19 Installing the RGS Receiver on Linux ................................................................................ 19 RGS Receiver audio requirements on Linux ..................................................... 19 Uninstalling the RGS Receiver on Linux ........................................................... 20 Installing the RGS Sender on Linux ..........
Setting the RGS Sender process priority (Windows only) .................................................................. 41 Using the RGS Diagnostics Tool (Windows only) .............................................................................. 41 Using the RGS Admin Tool (Windows only) ....................................................................................... 42 RGS Sender logging (Windows only) ..............................................................................................
Agent design issues ........................................................................................................... 65 Desktop session logout ..................................................................................... 65 Selective environment shutdown ...................................................................... 65 Wrapping applications of interest ...................................................................... 66 Administrator alerts ...................................
Clipboard properties (per-session) .................................................................... 86 RGS Sender properties ...................................................................................................................... 87 Appendix A Supported hardware and software ................................................................................................. 91 RGS support matrix ..................................................................................................
xii
1 Getting started in Windows The chapter provides a quick guide for Windows users to install and use HP Remote Graphics Software (RGS) in common scenarios. To install RGS: IMPORTANT: Be sure you are logged in to an account with administrator privileges before performing installation: 1. Install the RGS Sender on the remote computer using the default options. 2. Install the RGS Receiver on the local computer using the default options.
2 RGS overview This chapter discusses the following topics: 2 ● Typical RGS deployment ● User interface overview ● RGS features ● RGS Sender and RGS Receiver interoperability ● RGS licensing ● Connection types ● Multi-monitor configurations ● RGS login methods Chapter 2 RGS overview
Typical RGS deployment RGS is the collaboration and remote desktop solution for serious workstation users and their most demanding applications. All applications run natively on the remote workstation and take full advantage of its graphics resources. The desktop of the remote workstation is transmitted over a standard network to a window on a local computer using advanced image compression technology specifically designed for digital imagery, text, and high frame rate video applications.
User interface overview RGS Receiver Control Panel 1 In this field, enter the hostname or IP address of the remote computer running the RGS Sender. You can also click the down arrow to display a list of recent entries. 2 Initiates the RGS connection. 3 Displays advanced options. NOTE: 4 Displays the RGS version number, technical information, and the End User License Agreement (EULA). 5 Displays the HP Remote Graphics Software User Guide (this document).
Remote Display Window NOTE: The Remote Display Window might look slightly different on touch displays. 1 The Remote Display Window toolbar provides easy access to the most frequently used options. For more information about the individual toolbar items, see Remote Display Window toolbar on page 6. 2 Scroll bars appear if the resolution of the remote computer is larger than the size of the Remote Display Window.
Remote Display Window toolbar Non-touch displays Touch displays 1 Sets the image quality and the amount of compression. Higher image quality reduces the amount of compression and therefore consumes greater network bandwidth. NOTE: This control is duplicated in the Performance tab of the RGS Receiver settings. 2 Displays the current network bandwidth consumed by the connection. 3 Displays the number of image updates in frames per second for the connection. 4 Shows or hides the toolbar.
RGS features The following tables describe many of the RGS features that are designed to optimize functionality, performance, and security. Table 2-1 RGS functionality features Feature Description 3D application support OpenGL 3D applications can be run on the remote computer. Direct3D applications are also supported if they are not in full-screen mode.
Table 2-2 RGS performance features (continued) Feature Description HP Velocity This option improves performance over poor network connections. See Advanced performance features on page 45 for more information. Selective screen updates When Advanced Video Compression is not selected, only the portions of the screen that change are captured, compressed, and transmitted from the remote computer to the local computer, further improving performance.
RGS Sender and RGS Receiver interoperability RGS provides interoperability between an RGS Sender and RGS Receiver that have the same primary version number. A connection should only be attempted when their primary version numbers are the same. See below for a description of the RGS version number components. 1 Primary release number—A primary release contains sufficient changes such that interoperability with the prior primary release is not guaranteed. For example, RGS Sender version 5.
Multi-monitor configurations NOTE: Advanced Video Compression is not supported on multi-monitor configurations. Many computers have a frame buffer that is larger in size (as measured in horizontal pixels by vertical pixels) than what can be displayed on a single monitor. During an RGS connection, the remote computer transmits its entire frame buffer.
In normal operation, users are required to authenticate twice when establishing an RGS connection from a local computer to a remote computer. The two steps are as follows: 1. The first authentication step is from the RGS Receiver to the RGS Sender. The dialog for this authentication step is generated and displayed by the RGS Receiver on the local computer. 2. The second authentication step is when logging in to or unlocking the remote computer desktop session.
3 Installing and activating RGS This chapter describes the following aspects of installing RGS: ● Installing RGS on Windows ● Installing RGS on Linux Installing RGS on Windows This section describes installation of the RGS Receiver and RGS Sender on Windows. See Supported hardware and software on page 91 for a list of the Windows operating systems that support the RGS Receiver and Sender. If you plan to use Advanced Video Compression, see Advanced Video Compression requirements on page 92.
NOTE: The "auto" option described in Auto-remoting on page 51 alters the behavior you select during installation. It will re-enumerate any device marked as auto on connect and disconnect. For instance, you have a USB key device that you have marked "auto". Until the local computer is started, it will be attached to the local system. Once the local computer starts and makes a connection to a remote computer, it will be remoted to the remote system. Upon disconnect, it will be given back to the local system.
Command line syntax RGS command line options must be preceded by a /z flag and be enclosed in double quotes, with no space before or after the opening double quote and no space before the closing double quote. If using multiple commands, separate them with a single space. See the example below: ReceiverSetup.
Table 3-1 RGS Receiver installation command line options (continued) Command Description NOTE: /help Displays usage text. NOTE: /proxy=
: Example: /proxy=123.456.78.90:4321 /wanimprovement Using this option will negate all other options used. Using this option will negate all other options used. Configures proxy settings to allow RGS to establish an HTTP session during Advanced Features registration. Installs HP Velocity.NOTE: For some features, it is recommended to have an NVIDIA Quadro 2000 or better graphics card with driver version 305.29 or greater. Install the NVIDIA graphics driver following the instructions in the download package. NOTE: Installing the NVIDIA graphics driver after the RGS Sender has been installed may prevent the use of Windows Aero on Windows 7.
If an illegal combination of command line options is specified or another error occurs during the installation, the installation will abort and the error will be logged to the RGS Sender installation log file. Setup will exit without making any changes if automatic installation of the same version currently installed is attempted.
Table 3-2 RGS Sender installation command line options (continued) Command Description NOTE: Only one of /el or /sso can be specified. If neither is specified, the Standard Login method will be used. /gina=\"\" Specifies the chaining GINA module to use and can only be specified if /el is used. The default is msgina.dll. /rgslicenseserver=@ Specifies the listening port and host of the license server where RGS should acquire a license during installation.
IMPORTANT: After the RGS Sender is uninstalled, you will be prompted to restart your computer. This restart is very important—if it is not performed, installation of a later version of the RGS Sender may not succeed. Installing RGS on Linux This section describes installation of the RGS Receiver and RGS Sender on Linux. See Supported hardware and software on page 91 for a list of the Linux operating systems that support the RGS Receiver and RGS Sender.
the JACK RPM package. If the RGS Receiver is being removed from the system, JACK can also be removed using the following command: rpm -e jack-audio-connection-kit Uninstalling the RGS Receiver on Linux To uninstall the RGS Receiver on Linux find the name of the RedHat RPM package for the RGS Receiver by typing the following: rpm -q -a | grep -i rgreceiver If the RGS Receiver is installed on the system, you will see rgreceiver_linux_32-5.1-0 or a similar package.
● /etc/X11/xorg.conf—The configuration file for the X Server will be modified to load the rge extension. ● /etc/pam.d/rgsender—This configuration file will be modified to allow the RGS Sender to interact with the currently supported PAM authentication. ● /etc/pam.d/gdm*, /etc/pam.d/kdm*, /etc/pam.d/xdm*—These configuration files will be modified to ensure proper PAM authentication window manager support for the RGS Sender process.
rgsender to specify the PAM authentication module to be used by the RGS Sender. For example, you might need to add the following line to the file:. auth optional /lib/security/pam_custom.1 The RGS Sender will not accept remote connections when a DNS name inquiry does not resolve to a valid/active IP address—it 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.
4 Pre-connection checklist Establishing an RGS connection from an RGS Receiver to an RGS 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.
1. If using Advanced Video Compression, make sure that the remote computer system meets the requirements described in Advanced Video Compression requirements on page 92 (essential for a quality experience when using this feature). 2. OPTIONAL: Ensure RGS Sender licensing is set up—For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide, available at http://www.hp.com/support/ rgs.
88.1.89.122 blade2 blade2.datacenter.com For Linux systems with multiple network interfaces, each IP address must be listed in the /etc/ hosts file, for example: 192.168.89.122 blade2 blade2.datacenter.com 192.168.90.111 blade2b blade2b.datacenter.com 10. User-started X environments do not reliably support outside connections—Users who manually start X desktops (such as with startx) from the console command line will find that outside access attempts may not properly connect or be authenticated.
If the hostname resolves to the IP address of an incorrect network interface, do one of the following: ● Enter the IP address that the RGS Sender is bound to instead of the hostname when establishing an RGS connection. ● Reconfigure your DHCP and DNS servers so that the hostname resolves to the correct IP address.
Using RGS through a firewall The RGS Receiver can use the public IP address of the remote computer so that RGS can be used through a simple firewall. To take advantage of this feature, the remote and local computer firewalls must both support Network Address Translation (NAT). In addition, the remote computer firewall must support port forwarding. NOTE: For more information on how to set up port forwarding on your firewall, see the documentation for your firewall.
5 Using the RGS Receiver This chapter discusses the following topics: ● Starting the RGS Receiver ● Creating an RGS connection ● Using touch features (Windows 8 only) ● Setup Mode (non-touch displays only) Starting the RGS Receiver To start the RGS Receiver on Windows: ▲ Windows 7: Select Start > All Programs > HP > HP Remote Graphics Software > HP RGS Receiver. Windows 8: Select the HP RGS Receiver tile on the Start screen. To start the RGS Receiver on Linux: ▲ Run the executable rgreceiver.sh.
Creating an RGS connection NOTE: Before attempting to connect to a particular remote computer for the first time, HP recommends that you verify that the remote and local computers satisfy the Pre-connection checklist on page 23. The checklist can also be used as a troubleshooting aid if a connection attempt fails. To create an RGS connection: 1.
Using touch features (Windows 8 only) RGS supports the following touch features: ● Gestures—See Table 5-2 RGS touch gestures on page 30 for more information. ● Virtual keyboard and virtual mouse—The virtual keyboard and virtual mouse can be accessed using the Remote Display Window toolbar. The virtual mouse provides a visual indication of the remote cursor position, which is normally not present in tablet mode. The virtual mouse is useful when precise cursor positioning or hovering is required.
Setup Mode (non-touch displays only) If the Remote Display Window is configured to cover the entire local monitor and also has its title bar and borders hidden, than a number of questions arise, including the following: ● How do you move or resize the window absent a title bar and borders? ● In Directory Mode, if multiple Remote Display Windows are covering each other, how do you select a particular Remote Display Window to view? Complicating the situation is that all keyboard and mouse events in the Re
6 RGS Receiver Control Panel settings This chapter discusses the advanced settings available in the RGS Receiver Control Panel: 32 ● Connection settings ● Performance settings ● Gesture settings (Windows 8 only) ● Audio settings ● Network settings ● Hotkey settings ● Logging settings ● Statistics Chapter 6 RGS Receiver Control Panel settings
Connection settings The following table describes the settings available in the Connection tab. Table 6-1 Connection settings Setting Description Prompt for username and password Forces the authentication prompt to display when starting an RGS connection. In certain scenarios, RGS will not prompt you to enter a domain, username, and password when starting an RGS connection. If you need to enter a domain, username, and password, then check this box.
Performance settings The performance settings allow you to improve the interactive experience. Typically, these adjustments will be made when working with highly interactive applications (such as a CAD application) in a low-bandwidth or high-latency network environment. The following table describes the settings available in the Performance tab. Table 6-2 Performance settings Setting Description Force full screen image updates Forces the entire screen to update when any part of it changes.
Gesture settings (Windows 8 only) NOTE: The Gestures tab is only available if the local computer is running Windows and has a touch display. You can use the gesture settings to map hotkey sequences to the gestures that are not used by RGS by default. For a list of the gestures that can be customized, see Using touch features (Windows 8 only) on page 30. To map a hotkey sequence to a gesture: 1. Select the pencil icon in the row of the desired gesture. 2. Enter the key sequence. 3.
Network settings The following table describes the settings available in the Network tab. Table 6-4 Network settings Setting Description Error Sets the time in seconds that the RGS Receiver will wait before ending the connection after failing to detect the RGS Sender. Warning Sets the time in seconds that the RGS Receiver will wait before displaying a warning dialog to the local user after failing to detect the RGS Sender.
Table 6-5 Hotkey settings (continued) Setting Description TIP: The Ctrl+Alt+Del sequence can also be sent using the Remote Display Window toolbar. Key Repeat Enables the processing of key repeats for when the Shift key is held down. By default, key repeat processing is disabled by RGS, but some remote applications might require this functionality. NOTE: If this option is enabled, the default Setup Mode hotkey sequence will not trigger unless it is typed fast enough.
Logging settings The RGS Receiver logs various types of information during its operation. The logging settings allow you to set a number of parameters, such as whether logging is enabled and the location and name of the log file. The following table describes the settings available in the Logging tab. Table 6-6 Logging settings Setting Description Enable message logging Enables logging. Log file path Specifies the path of the log file. Log level Determines the level of information that is logged.
7 Using the RGS Sender This chapter discusses the following topics: ● Starting and stopping the RGS Sender on Windows ● Starting the RGS Sender on Linux ● RGS Sender GUI (Windows only) ● Setting the RGS Sender process priority (Windows only) ● Using the RGS Diagnostics Tool (Windows only) ● Using the RGS Admin Tool (Windows only) ● RGS Sender logging (Windows only) Starting and stopping the RGS Sender on Windows The Windows version of the RGS Sender is comprised of two processes, one of which
Table 7-1 RGS Receiver command line options (Windows) (continued) NOTE: This option sets the value of the property Rgsender.Network.Timeout.Error and overrides the Error value set in the RGS Receiver network settings. -authtimeout Example: -authtimeout 15000 Specifies the timeout in milliseconds used to detect and notify the user of a network disruption. NOTE: This option sets the value of the property Rgsender.Network.Timeout.
The rgsender.sh command has two options that can be executed from the command line. The rgsender.sh command does not start the RGS Sender if either of these options are used. The options are described in the following table. Table 7-2 RGS Receiver command line options (Linux) -v | -ver | -version Displays the RGS Sender version information. -h | -help | -? Displays the command line options that are listed in this section.
details in the Results panel. This information can be used to determine what the test looked for, why it failed, whether the failure will prevent connections, and suggestions on how to fix the problem. The RGS Diagnostics Tool can be run any time after RGS Sender installation. To run the RGS Diagnostics Tool, use Windows Explorer to display the RGS Sender installation folder, and locate rgdiag.exe. This tool is normally located at: C:\Program Files\Hewlett-Packard\Remote Graphics Sender\rgdiag.
8 Advanced RGS features This chapter discusses the following topics: ● Collaboration ● Optimizing RGS performance ● Remote Audio ● Remote Clipboard ● Remote USB ● Using RGS in Directory Mode (non-touch displays only) ● Game Mode (non-touch displays only) ● Auto-launching connections ● RGS Sender event logging (Windows only) ● Remote application termination ● Interoperability of RGS and Microsoft Remote Desktop Connection ● RGS security features ● Linux connection considerations 43
Collaboration RGS enables the primary user to share their desktop session with several users simultaneously. This feature can be used in a variety of collaborative scenarios including classroom instruction, design reviews, and technical support. Creating a collaboration session A collaboration session is created when one or more users are authorized by the primary user to connect to the primary user’s desktop session. This allows all users to view and interact with the primary user’s desktop.
The primary user can disable collaborator input using the RGS Sender GUI. Authorized local users will still be able to view the primary user’s desktop but will be unable to interact with it. To disable collaborator input: ▲ Right-click the RGS Sender icon in the notification area and select Collaborator Input > Disable. All collaboration users can be disconnected simultaneously using the RGS Sender GUI.
NOTE: HP Velocity may increase network bandwidth usage. NOTE: These features will be activated during the first RGS connection, and this activation will require Internet access. Please make sure your proxy settings are correctly configured (see Network settings on page 36). Performance tuning for all operating systems The following suggestions apply to all operating systems: ● Set the network to full-duplex mode ● Do not use color or animated cursors on the remote computer.
settings, however. If the network interface and switch settings don’t complement each other, the network will have poor performance. To configure a network interface to force a particular network speed on Windows: 1. Open Device Manager in the Windows Control Panel. 2. Expand Network adapters. 3. Right-click the network adapter you want to configure, and then select Properties. 4. Click the Advanced tab. 5. In the list of properties, locate the property that controls the speed and duplex setting.
Table 8-1 Windows RGS audio data paths (continued) 8. The audio device drives an audio output device, such as a speaker. Remote Audio on Linux The following table describes the paths taken by both application-generated audio output and microphone audio on Linux. Table 8-2 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. An application on the remote computer generates audio output. 2.
48: [ 1- 0]: digital audio playback 56: [ 1- 0]: digital audio capture There are two important things. The first is the content between the “[ ]”. The first number is the “card” (denoted “c” below) and the second number is the “device” (denoted “d” below). The second important thing is the word “capture” in the description. Rgsender.Audio.Linux.DeviceName=plughw:c,d In the example above, depending upon which audio device you would like to capture the audio from, you could specify the device with: Rgsender.
device should not be enabled at the same time. The remote computer will connect to the first audio device it detects, which might not be the device that is selected by the user. Remote Clipboard Remote Clipboard allows you to cut, copy, and paste data between the local and remote computers or between two different remote computers.
Auto-remoting In addition to the general default settings for Remote USB configurations, RGS supports auto-remote and auto-return of user-specified USB devices when using Windows on both the RGS Sender and Receiver platforms. An auto-remote configuration syntax for the Windows Registry entries allows specified USB devices to be automatically attached to a remote computer at RGS connection and then returned to the local computer at RGS disconnect.
RGS works very closely with the Windows USB driver stack. Any USB device that exclusively uses the Windows USB driver stack for functionality should work with RGS. The less a USB device's driver complies with the Windows USB driver stack, the less likely it will work with RGS. NOTE: Devices that adhere to the USB standard should work. Because RGS is a remote graphics protocol and is emulating the USB protocol over a network, devices that are sensitive to timing may not work at all.
evidenced by the smart card reader being locally accessible prior to establishment of an RGS connection. Similarly, the USB devices are Local/Remote setting is ignored as evidenced by the locally-accessible smart card reader automatically becoming remotely accessible once an RGS connection is established. ● If a smart card reader is plugged in after an RGS connection is established, it will be available remotely.
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: 1. IP address of the local computer 2. The domain group of the local user The ACL file supports two rule types: “allow” and “deny.
6. Device BCD—bcdDevice 7. Manufacturer—manufacturer 8. Product Type—product 9. Serial Number—serialNumber IMPORTANT: Filtering on device strings (manufacturer, product, and serial number) may not be reliable. Device vendors are not required to add data to these fields, and many do not. Before deploying a solution that depends on a string-based filter, ensure that the devices you wish to use implement the appropriate device strings. 10. IP address of the local computer—peerAddress 11.
after "Pid_". The Revision is the 4 hex digits after "Rev_". For example, an iPod has a "Hardware Ids" property that looks like this: USB\Vid_05ac&Pid_120a&Rev_0001 This gives us the following values: iPod Vendor ID： 0x05AC iPod Product ID： 0x120A iPod Revision： 0x0001 ● "Compatible Ids" property—This property shows the class code, subclass code and protocol code for the device. The class code is the 2 hex digits after "Class_". The subclass code is the 2 hex digits after the "SubClass_".
C:\Program Files\Hewlett-Packard\Remote Graphics Receiver\directory.txt After the directory file name is determined, the RGS Receiver automatically connects to the remote computers specified in this file for the named user. Directory file format Often, the directory file is a common file for a group, department, organization, or an entire company. The directory file can manage and administer the remote computer assignments for any number of users.
The domain name does not apply when using the directory file for Linux users. Instead, use the keyword UNIX in place of the domain name. For example: UNIX sally RC_1 RC_2 RC_3 Comment lines in the directory file are preceded by the “#” character in the first column. Starting the RGS Receiver in Directory Mode Before attempting a connection in Directory Mode for the first time, HP recommends that you verify that RGS can connect to each computer individually (see Creating an RGS connection on page 29).
Figure 8-1 Remote Display Window selection dialog To display the selection dialog, press the Tab key while in Setup Mode—again, Setup Mode must have been previously activated by the hotkey sequence. The selection dialog is displayed as long as the initial Setup Mode hotkey (normally the Shift key) remains pressed. The currently-selected Remote Display Window is highlighted with a red border.
repositioned without leaving Game Mode. When a connection is terminated, Game Mode will be disabled. RGS may not be suitable for full screen games. The techniques used by games to quickly draw to the screen will often prevent RGS from being able to extract the contents of the remote frame buffer for display. This is often seen as partially rendered scene or a completely scrambled scene. A game that works in a windowed mode may be able to be controlled when Game Mode is enabled.
To view the properties of a particular event, double-click the event of interest to open the Event Properties window. This window displays the connection data in byte and word formats. The section HPRemote log format on page 61 provides more details on the supported data formats. Additional information on event logging For additional information on Windows event logging, search Microsoft Developer Network (MSDN) at http://msdn.microsoft.com/.
Table 8-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description UINT32 numNonprimary Event Viewer Example: Primary connections:1 Non-primary connections:0 RGSENDER_CONNECT EventID: 4 A new connection was established with an associated name. If Easy Login is enabled, the name assignment will be deferred until login and the associated name may be Anonymous. Event Viewer Message: Connect %1.
Table 8-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description None RGSENDER_SHUTDOWN EventID: 2 Reference event registered to aid in interpretation of the event log by Event Viewer. Signifies proper shutdown of the RGS Sender service. Event Viewer Message: RGS Sender shutdown. Strings: None Data: None RGSENDER_SET_PRIMARY EventID: 6 A connection with an associated name is set as the primary connection. Event Viewer Message: Set %1 as primary connection.
Table 8-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description %2 = new name of connection Data: None Event Viewer Example: Assign Anonymous connection to MYDOMAIN \myusername. RGSENDER_USB_CONNECT_DEVICE EventID: 9 A new USB device was connected to the remote computer via Remote USB.
Table 8-3 RGS Sender events logged in the HPRemote log (continued) Message ID Description %1 = USB device class %2 = USB device vendor ID %3 = USB device product ID Data: None Agent design issues Designing an agent to provide Remote Application Termination requires consideration of a number of issues in order to minimize data loss and determine when a last-resort shutdown of a disconnected desktop session is required.
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.
Additional features for Windows systems The following optional procedures for the RGS Sender service can improve the reliability of your remote agent solution. RGS Sender Service Recovery Settings This section discusses restart options for the RGS Sender and possible interactions of the agent with the remote computer. By default, most Windows services are installed without any automatic restart/recovery settings.
● for a finite number of seconds (or infinite if seconds <= 0) do ● open event log, read log length, close event log ● if log has changed, processEvent(), else sleep for X ms. To properly use the function monitorEvents(...
// Set the pointer to our buffer. Strings and data will get appended to the EVENTLOGRECORD structure. pevlr = (EVENTLOGRECORD *) &bBuffer // Read the event specified by dwEventNum result = ReadEventLog(h, // event log handle EVENTLOG_SEEK_READ | // start at specific event EVENTLOG_FORWARDS_READ, // advance forward dwEventNum, // record to read pevlr, // pointer to buffer BUFFER_SIZE, // size of buffer &dwRead, // number of bytes read &dwNeeded); // bytes in next record if (CloseEventLog(h) == false) { ...
} else { ... report unrecognized event here ... return true; } return false; } void monitorEvents(LPCTSTR eventServer, LPCTSTR eventSource, int seconds) { DWORD dwCurrentIndex = 0; DWORD dwCurrentStart; DWORD dwCurrentCount; DWORD dwNewIndex; int waitedFor; // This function will monitor the log for the specified number of // seconds. If seconds is less than zero, we will wait forever.
return; } if (CloseEventLog(h) == false) { ... report error status here ... return; } // Determine state of log change ===================================== // Compute the index of the last event. If the count is zero, then // there are no events and the index is 0. if (dwCurrentCount == 0) { dwNewIndex = 0; } else { dwNewIndex = dwCurrentStart + dwCurrentCount - 1; } // If the new index is different than the current, update the current // and process the current event. Otherwise, we sleep for a while.
// No new events. Sleep for 1 second. Sleep(1000); waitedFor += 1; } } return; } main( ... ) { ... setup and initialize agent ... monitorEvents(EVENT_SERVER, EVENT_SRC, seconds); ... cleanup agent here or send alerts ... ... may wish to return status from monitorEvents ... } Interoperability of RGS and Microsoft Remote Desktop Connection This section discusses interoperability considerations for RGS and Remote Desktop Connection (RDC).
Under reverse circumstances for the above, RGS connections will not log out an existing RDC user, regardless of authority. RGS will report an authorization failure message concerning a different user owning the desktop When RGS displaces an existing RDC session on Windows 7, the desktop may enter into a temporary logged in and unlocked state due to these operations. The user should exercise caution in situations where even a temporarily unlocked desktop is a security concern.
● Remote Keyboard/Mouse: The RGS Sender GUI can enable or disable mouse and keyboard input for all collaboration users. ● Single user connection: A user, identified by a username, is only allowed one connection to a RGS Sender. If the same username connects more than once to a RGS Sender, the previous connection drops and the new connection continues on. If several users attempt to share a username, only one connection is active at a time.
Full-screen crosshair cursors Certain applications that use large crosshair cursors (for example, Dassault Systemes ICEM Surf uses a full-screen crosshair cursor) will not display correctly on the local computer. Full-screen crosshair cursors can be disabled by typing the following in a terminal window: X11xprop -root -remove _SGI_CROSSHAIR_CURSOR This will force the application to use an X cursor, which will display correctly on the local computer.
9 RGS properties RGS properties provide you with another way to customize RGS settings. Some properties correspond to settings that are also available in the GUI, while other properties correspond to settings that can only be set via a configuration file or the command line.
Property syntax The following example shows the RGS property syntax: Rgreceiver.Network.Timeout.Warning=10000 In this example, the name of the property is Rgreceiver.Network.Timeout.Warning, and the value of the property is 10000. This setting specifies that the RGS Receiver will wait 10,000 milliseconds (10 seconds) before displaying a warning dialog that indicates that it is no longer able to communicate with the RGS Sender.
Setting properties on the command line Properties can be set on the command line like in the following examples: Windows: rgreceiver.exe -Rgreceiver.Network.Timeout.Warning=10000 Linux: rgreceiver.sh -Rgreceiver.Network.Timeout.Warning=10000 NOTE: Properties of the type int vector cannot be set on the command line. RGS Receiver properties There are two types of RGS Receiver properties: ● Global properties—The global properties affect all RGS connections.
Table 9-1 Remote Display Window properties (continued) Rgreceiver.ImageCodec.IsMutable 1=The image quality slider can be adjusted by a user, either in the RGS Receiver Control Panel or on the Remote Display Window toolbar (default). 0=The image quality slider is disabled and cannot be adjusted by a user. Rgreceiver.ImageCodec.Quality The image quality can be set from a minimum of 0 to a maximum of 100. The default is 65. Rgreceiver.ImageCodec.
Table 9-1 Remote Display Window properties (continued) Rgreceiver.IsDisconnectWarningEnabled 1=The RGS Receiver will display a warning that disconnecting an RGS connection will not automatically log them out of the remote computer. 0=This warning is disabled. Rgreceiver.IsAlwaysPromptCredentialsEnabled 1=The RGS Receiver will always prompt for the domain, username, and password when establishing a connection.
Browser properties Table 9-3 Browser properties Rgreceiver.Browser.IsMutable NOTE: This property only applies to Linux. 1=A user can use the RGS Receiver Control Panel to specify the name of the browser that is used to display this document. 0=The browser name cannot be changed by a user. Rgreceiver.Browser.Name NOTE: This property only applies to Linux. This property specifies the name of the browser that is used to display this document. The default is mozilla.
USB properties Table 9-6 USB properties Rgreceiver.Usb.IsMutable 1=A user can modify the Remote USB settings in the RGS Receiver Control Panel (default). 0=A user cannot modify the Remote USB settings in the RGS Receiver Control Panel. Rgreceiver.Usb.IsEnabled 1=Remote USB is enabled (default). 0=Remote USB is disabled. Rgreceiver.Usb.ActiveSession This property specifies which remote computer to attach USB devices to for Directory Mode.
Table 9-7 Network properties (continued) NOTE: See HP Velocity documentation for more information. Rgreceiver.Network.HPVelocity.TargetLossRate 3=The target loss rate used by HP Velocity is 0.04% (default). 2=The target loss rate used by HP Velocity is 0.1%. 1=The target loss rate used by HP Velocity is 0.2%. 0=The target loss rate used by HP Velocity is 0.4%. NOTE: See HP Velocity documentation for more information. Rgreceiver.Network.HPVelocity.NetworkInterface NOTE: This property only applies to Linux.
Table 9-8 Hotkey properties (continued) 0=Disables Game Mode. Clipboard properties NOTE: For per-session clipboard properties, see Clipboard properties (per-session) on page 86. Table 9-9 Clipboard properties Rgreceiver.Clipboard.IsMutable 1=A user can modify the Remote Clipboard setting in the RGS Receiver Control Panel (default). 0=A user cannot modify the Remote Clipboard setting in the RGS Receiver Control Panel. Rgreceiver.Clipboard.IsEnabled 1=Enables Remote Clipboard (default).
Table 9-10 Logging properties (continued) Windows: C:/Program Files/Hewlett-Packard/Remote Graphics Receiver/rg.log Linux: $HOME/.hpremote/rgreceiver/rg.log Rgreceiver.Log.MaxFileSize This property sets the maximum size of the log file in kilobytes (KB). The default is 1024 (1 MB). Registration properties Table 9-11 Registration properties Rgreceiver.Registration.IsEnabled 1=Enables registration to the HP registration server, which is required to use advanced RGS features (default).
Table 9-13 Auto-launch properties (per-session) (continued) Rgreceiver.Session..Password This property sets the password for session number n as a UTF-8 encoded string. Rgreceiver.Session..PasswordFormat Encrypted=Sets the password format for session number n. This format is only supported on Windows and is the hexadecimal string representation of the password encrypted using the Windows command CryptProtectData. See http://msdn.microsoft.com/en-us/library/aa380261(VS.85).aspx for more information.
Table 9-15 Clipboard properties (per-session) NOTE: For Remote Clipboard to be enabled for any session, the general clipboard property Rgreceiver.Clipboard.IsEnabled must also be set to 1. RGS Sender properties In this hierarchy, properties set by methods higher on the list override properties set by methods lower on the list (with 1 being the highest and 3 being the lowest): 1. Properties set on the command line 2. Properties set in the RGS Sender configuration file 3.
Table 9-16 RGS Sender properties (continued) Rgsender.IsCollaborationNotificationEnabled 1=Enables the collaboration notification dialog (default). 0=Disables the collaboration notification dialog. IMPORTANT: This property should normally remain enabled. When disabled, neither remote users or local users will be notified who is participating in a collaboration session. The warning dialog that is displayed when the remote computer is unable to blank its monitor will also be prevented from being displayed.
Table 9-16 RGS Sender properties (continued) 0=HP Velocity is disabled. NOTE: See HP Velocity documentation for more information. Rgsender.Network.HPVelocity.TargetLossRate 3=The target loss rate used by HP Velocity is 0.04% (default). 2=The target loss rate used by HP Velocity is 0.1%. 1=The target loss rate used by HP Velocity is 0.2%. 0=The target loss rate used by HP Velocity is 0.4%. NOTE: See HP Velocity documentation for more information. Rgsender.Network.HPVelocity.
Table 9-16 RGS Sender properties (continued) This property sets the amount of time in milliseconds that the RGS Sender will wait before disconnecting all USB devices if the USB ACL file disappears or becomes inaccessible. The default is 5000 milliseconds (5 seconds). If the file is restored prior to expiration of the timeout period, the USB devices remain connected. Rgsender.Clipboard.IsEnabled 1=Enables Remote Clipboard (default). 0=Disables Remote Clipboard. Rgsender.
A Supported hardware and software RGS support matrix Table A-1 RGS support matrix Windows 7 Windows 8.1 Professional, Enterprise Pro, Enterprise √ √ RHEL 5.9, 6.5 SLED 11.
Advanced Video Compression requirements Table A-2 Advanced Video Compression requirements Remote computer (RGS Sender) Local computer (RGS Receiver) CPU encoding—4 cores or more running at 2 GHz (minimum); 8 cores or more running at 2 GHz (recommended) CPU decoding—2 cores or more running at 2 GHz NOTE: If using GPU encoding, the CPU only needs to meet the requirements listed in RGS support matrix on page 91. GPU encoding—NVIDIA Quadro 2000 or better graphics card with driver version 305.
IMPORTANT: The Linux virtual audio driver is the only supported audio device for RHEL 6. Hardware audio devices are not supported. NOTE: The Linux virtual audio driver is not supported in a virtual machine. Timing information from the kernel in a virtual machine may not be precise enough to ensure consistent audio quality. Keyboard locale support The following keyboard localizations are supported when connected to a RGS Sender on Linux: 1. French 2. German 3. Japanese 4. Norwegian 5. Swedish 6.
21. Swedish 22. Swiss French 23. Swiss German 24. Turkish Q 25. United Kingdom 26. United Kingdom Extended 27. United States—International 28. U.S. Application support RGS supports all applications, except those applications that use full screen exclusive mode. RGS may not be suitable for most full screen games. If a full-screen MS-DOS command prompt window is created on the remote computer (using, for example, command.com), the window will be reset to its default size by RGS.
B Troubleshooting This appendix provides suggestions on troubleshooting potential issues with RGS and also lists the RGS error messages and their possible causes. Potential issues and suggestions Table B-1 Potential RGS issues and troubleshooting suggestions Issue Suggestion Cannot connect to the RGS Sender. Verify that the pre-connection checklist is satisfied as described in Pre-connection checklist on page 23. A connection is established but it appears to time out.
RGS Receiver network timeout RGS provides two user-settable RGS Receiver timeout properties to allow you to optimize RGS for your particular network conditions (such as low-bandwidth or high-latency conditions). These properties allow you to specify timeout values that, if exceeded, will cause the RGS Receiver to take specific actions, such as displaying a warning dialog or closing the RGS connection.
independent of the RGS Receiver timeout properties. The RGS Sender begins by using the maximum of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.Dialog property. When the RGS Receiver negotiates its connection to the RGS Sender, it notifies the RGS Sender of its error timeout property. For sync pulse timeout purposes, the RGS Sender adopts the minimum of: Rgreceiver.Network.Timeout.Error and the maximum of { Rgsender.Network.Timeout.Error AND Rgsender.Network.Timeout.
timeout of the RGS Receiver to reduce RGS Receiver disconnection. Additionally, the RGS Sender timeout might need to be increased too. See Network settings on page 36 for further details. ● When connecting to a Linux remote computer, the PAM authentication dialog displayed by the local computer does not appear long enough to enter the user’s credentials such as username and password—This is likely caused by the RGS Receiver’s dialog timeout value being too small.
Troubleshooting graphics performance The dominant factor impacting performance on the remote computer is the frame buffer read performance of the graphics adapter. Frame buffer read performance of at least ten frames per second is recommended for optimum RGS performance. RGS uses the remote computer’s graphics adapter to accelerate rendering of the image.
computer. This may occur when something is connected to the "Line In" port of the audio device. Reducing volume levels or disconnecting any external devices may help reduce the interference. ● ToggleKeys sound not working—The Accessibility control in Windows will play a sound when some control keys are pressed. This sound is not heard on the local computer because it is played through the PC Speaker.
Troubleshooting Remote USB If you have problems connecting a remote USB device from a local computer to a remote computer, the following checklist may help identify the problem. Computers supporting Remote USB Ensure that both the remote computer and the local computer support Remote USB. Supported USB devices Verify that the USB device you’re using is supported. HP has tested a number of USB devices to verify they work correctly when attached to a remote computer from a local computer.
RGS error messages This section lists the error messages reported by the RGS Receiver and describes possible reasons for them. Table B-2 RGS Receiver error messages Error Description Connection lost! The RGS Sender has closed the connection. Possible reasons include: ● The RGS Sender might have explicitly disconnected your connection. For example a user might have selected disconnect all connections from the RGS Sender icon or RGS Sender GUI or the user might have logged off.
Table B-2 RGS Receiver error messages (continued) User not found in directory! The username of the current user of the HP Remote Graphics Software Receiver is not found in the directory file. Possible reasons include: ● The username entered in the directory file does not exactly match the real username. ● The domainName entered in the directory file is incorrect. See Directory file format on page 57 for information about choosing the correct domainName.
C HP support Obtaining HP support If you encounter an issue that requires support, please do the following prior to contacting HP for assistance: ● Be in front of the local computer or remote computer, whichever one is appropriate. ● Note the operating system. ● Note any applicable error messages. ● Note the applications you were using when you had the issue. ● Be prepared to spend the time necessary to troubleshoot the problem with the service technician.
Index A advanced performance features, activation 13 Advanced Video Compression activation 13 description 45 enabling 34 requirements 92 application support 94 audio disabling on remote computer 49 Remote Audio. See Remote Audio RGS Receiver requirements on Linux 19 RGS Receiver settings. See RGS Receiver settings C collaboration 44 command line options RGS Receiver 28 RGS Sender on Windows 39 connections auto-launching 60 creating 29 creating in Directory Mode 56 pre-connection checklist 23 settings.
pre-connection checklist local computer 23 remote computer 23 properties RGS Receiver 78 RGS Sender 87 setting in a configuration file 77 setting on the command line 78 syntax 77 R Remote application termination overview 61 sample agent 67 Remote Audio on Linux 48 on Windows 47 overview 47 support on Linux 92 troubleshooting 99 Remote Clipboard 50 troubleshooting 100 Remote Display Window toolbar 6 Remote Microphone on Linux 48 on Windows 47 Remote USB Access Control List 53 auto-remoting 51 determining dev
