HP Z620 HP Remote Graphics Software 5.4.7 - Page 216

Remote Application Termination, RGS connection and user status, HPRemote log format

Page 216 highlights

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. RGS connection and user status As described in Establishing an RGS connection using Standard Login on page 20, 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. The sample agent described in this chapter monitors the number of primary users connected to the Remote Computer. When the number of primary users drops to zero, the agent terminates all applications on the Remote Computer. To determine the number of primary users, the agent reads and interprets the HPRemote log. 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 10-1 RGS Sender events logged in the HPRemote log on page 200 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 10-1 RGS Sender events logged in the HPRemote log Message ID Description 200 Chapter 10 Remote Application Termination

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

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.
RGS connection and user status
As described in
Establishing an RGS connection using Standard Login
on page
20
, 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.
The sample agent described in this chapter monitors the number of primary users connected to the
Remote Computer. When the number of primary users drops to zero, the agent terminates all
applications on the Remote Computer. To determine the number of primary users, the agent reads and
interprets the HPRemote log.
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
10
-
1
RGS Sender events logged in the HPRemote log
on page
200
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 10-1
RGS Sender events logged in the HPRemote log
Message ID
Description
200
Chapter 10
Remote Application Termination