HP Xw9400 Remote Graphics Software 4.2.0 User Guide - Page 99

Remote Application Termination on Windows

Get HP Xw9400 - Workstation - 16 GB RAM PDF manuals and user guides View all HP Xw9400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

Using Remote Graphics Software Remote Application Termination on Windows Remote Application Termination (RAT) is only supported on Windows. Network outages or loss of connectivity between a RGS Receiver and Sender can leave a desktop session running without supervision. To safeguard running applications, customer-designed agents can monitor the status of connections to determine if termination of applications is required. This support is available through the RGS Sender for Windows. This section describes how to interpret RGS connectivity status, decode Windows Event Log messages from the Sender, and create effective control agents for remote application management and termination during disconnects. RGS Connection and User Status The RGS Sender reports status of connections through a custom Windows Event Log called HPRemote. RGS connections normally occur in two phases: • Phase 1: RGS Connection - a connection over a standard computer network between an RGS Sender and RGS Receiver • Phase 2: Desktop Session - a logged-in session that gives access to a desktop workspace on a remote workstation using a RGS connection Desktop Sessions can operate independently of active RGS Connections. This allows the user to disconnect and reconnect to Desktop Sessions as part of a normal workflow. However, when a connection is unintentionally disconnected, a user may require remote applications to be terminated after Desktop Sessions are left unattended for a period of time to prevent them from operating unsupervised. Ownership of a Desktop Session on Windows defines the type of user status in effect for a RGS connection. Events posted to the HPRemote Windows Event Log reflect the following control priorities: • Primary User - The user of a RGS Connection that matches the user logged into the Desktop Session. • Non-primary User (also Collaborating User) - A user of a RGS Connection that does not match the user logged into the Desktop Session. If no one is logged into a Desktop Session, then all connections are non-primary. Primary user status defines control and the need for a monitoring agent to take action against running applications of interest. When the number of primary user connections drops to zero, then the Desktop session may require user-defined actions. HPRemote - the RGS Windows Event Log The RGS Sender posts events in the HPRemote Windows Event Log. Event messages are directly viewable with the Windows Event Viewer or by an application 91

  • 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
Using Remote Graphics Software
91
Remote Application Termination on Windows
Remote Application Termination (RAT) is only supported on Windows.
Network outages or loss of connectivity between a RGS Receiver and Sender can
leave a desktop session running without supervision. To safeguard running
applications, customer-designed agents can monitor the status of connections to
determine if termination of applications is required. This support is available through
the RGS Sender for Windows.
This section describes how to interpret RGS connectivity status, decode Windows
Event Log messages from the Sender, and create effective control agents for remote
application management and termination during disconnects.
RGS Connection and User Status
The RGS Sender reports status of connections through a custom Windows Event Log
called
HPRemote
. RGS connections normally occur in two phases:
•
Phase 1:
RGS Connection
- a connection over a standard computer network
between an RGS Sender and RGS Receiver
•
Phase 2:
Desktop Session
- a logged-in session that gives access to a
desktop workspace on a remote workstation using a RGS connection
Desktop Sessions can operate independently of active RGS Connections. This allows
the user to disconnect and reconnect to Desktop Sessions as part of a normal
workflow. However, when a connection is unintentionally disconnected, a user may
require remote applications to be terminated after Desktop Sessions are left
unattended for a period of time to prevent them from operating unsupervised.
Ownership of a Desktop Session on Windows defines the type of user status in effect
for a RGS connection. Events posted to the
HPRemote
Windows Event Log reflect
the following control priorities:
•
Primary User
- The user of a RGS Connection that matches the user logged
into the Desktop Session.
•
Non-primary User
(also
Collaborating User
) - A user of a RGS Connection
that does not match the user logged into the Desktop Session. If no one is
logged into a Desktop Session, then all connections are non-primary.
Primary user status defines control and the need for a monitoring agent to take
action against running applications of interest. When the number of primary user
connections drops to
zero
, then the Desktop session may require user-defined
actions.
HPRemote - the RGS Windows Event Log
The RGS Sender posts events in the
HPRemote
Windows Event Log. Event
messages are directly viewable with the Windows Event Viewer or by an application