HP Remote Graphics Software 6.0 User Guide

Remote Application Termination
This section 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).
For a sample agent, see
Sample agent on page 99.
RGS connection and user status
As described in Standard Login on page 12, an RGS connection normally require two authentication
steps:
●
The first authentication step is from the RGS Receiver to the RGS Sender—this is called
authenticating the RGS connection. The dialog for this authentication step is generated and
displayed by the RGS Receiver on the local computer.
●
The second authentication step is when logging into or unlocking the remote computer desktop
session—this is called logging into the remote computer. The login or unlock dialog is generated
by the remote computer, and is displayed in the Remote Display Window on the local computer.
A desktop session can operate independently of the RGS connection. This allows a user to
disconnect and reconnect to desktop sessions as part of a normal workflow. However, when an RGS
connection is unintentionally disconnected, the user may require remote applications to be terminated
to prevent them from operating unsupervised.
HPRemote log format
Data in the HPRemote log consists of a Message ID followed by optional data in both character string
and binary data formats. Binary data provides direct access to data without requiring application
parsing. Character strings format the binary data into human-readable messages compatible with the
Windows Event Viewer.
Table 7-3 RGS Sender events logged in the HPRemote log on page 91
shows the events logged in the HPRemote log. The Message IDs are defined in the header file
RGSenderEvents.h, and are 32-bit values. The EventID is from the Code field within the Message ID
and, for the HPRemote log, ranges from 1 to 13.
Table 7-3 RGS Sender events logged in the HPRemote log
Message ID Description
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.
Each state field provides a text string and binary, 32-bit
unsigned integer for application use.
Event Viewer Message:
Primary connections:%1.
Non-primary connections:%2.
Strings:
%1 = number of primary connections
%2 = number of non-primary connections
Remote Application Termination 91