HP Z620 HP Remote Graphics Software 5.4.7 - Page 214

Usages of the HPRemote log, Troubleshooting, Automatic Remote Application Termination

Page 214 highlights

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. ● Automatic Remote Application Termination-Network outages or loss of connectivity between a Remote and Local Computer can leave a remote desktop session running without supervision. To prevent applications from running unattended, a customer-designed agent can use the HPRemote log to monitor the status of connections to determine if application termination is required. If so, the agent would be designed to take the appropriate action to terminate the application. The Chapter Remote Application Termination on page 200 , describes how to create an agent that uses the HPRemote log to automatically monitor the connection between the Remote and Local Computers-and then take whatever action you require. Sample code is provided to facilitate creation of the agent. ● Other automated actions-The basic principle behind using the HPRemote log to perform automatic Remote Application Termination can be used to create an agent to automatically monitor and process any of the events logged by the RGS Sender. The Section, HPRemote log format on page 200 , lists the events logged by the RGS Sender, and describes their format. Using the sample code provided, you can create an agent to automatically monitor and process any Sender events. 198 Chapter 9 Sender event logging on Windows

  • 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

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.
Automatic Remote Application Termination
—Network outages or loss of connectivity
between a Remote and Local Computer can leave a remote desktop session running without
supervision. To prevent applications from running unattended, a customer-designed agent can use
the HPRemote log to monitor the status of connections to determine if application termination is
required. If so, the agent would be designed to take the appropriate action to terminate the
application.
The Chapter
Remote Application Termination
on page
200
, describes how to create an agent
that uses the HPRemote log to automatically monitor the connection between the Remote and Local
Computers—and then take whatever action you require. Sample code is provided to facilitate
creation of the agent.
Other automated actions
—The basic principle behind using the HPRemote log to perform
automatic Remote Application Termination can be used to create an agent to automatically
monitor and process any of the events logged by the RGS Sender. The Section,
HPRemote log
format
on page
200
, lists the events logged by the RGS Sender, and describes their format.
Using the sample code provided, you can create an agent to automatically monitor and process
any Sender events.
198
Chapter 9
Sender event logging on Windows