HP Xw460c Remote Graphics Software 4.2.0 User Guide - Page 111

Additional Safeguard Features for Windows systems

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 111 highlights

Using Remote Graphics Software • Concerns - May require redundant networking channel. Requires administrator or operator availability to support. Anticipating User Disconnects and Reconnection • Issues - Users must first be warned about the consequences of disconnection. Agents that provide protection for a disconnected session can also provide a nuisance for unsuspecting users if they fail to address protective measures in place for their safety. For example, users must know how much time they have to reconnect before safeguards take action. If a remote agent arms itself for application termination, users should be presented with a large, unmistakable disarming "opt-out" panel that, upon login and discovery, they can halt any agent actions before termination. Organizations should carefully discuss and publicize safety measures due to potential data loss. • Concerns - Users should not be able to disable or specify their own timeouts due to potential irreversible data loss. General Design Issues • All active agents should externally log their decisions and actions for post mortem analysis. • Independent agents should provide their own opt-out, disarming dialogs with countdown feedback before taking action. • Expect the unexpected - where possible, limit your actions to those areas you are certain of the outcomes to minimize loss of data and productivity. • Always inspect error codes when reading event logs - the reliability of this RGS communication method depends upon the Windows Event Log system. While we have yet to see a failure in this path, we recommend using all information available to its fullest potential. Additional Safeguard Features for Windows systems The following optional procedures for the RGS Sender service can improve the reliability of your remote agent solution if required in your environment. RGS Sender Service Recovery Settings • By default, most Windows services are installed without any automatic restart/recovery settings. This means that when a service terminates, Windows will, by default, not restart the service unless explicitly set. When RGS Sender software is first installed, it is installed with Windows defaults (do not restart). • Restarting the RGS Sender service can support RGS reconnection with a RGS Receiver client (unless a system error prevents the RGS service from restarting). • Agent designs should take into account whether or not to check for the existence of a running RGS Sender service as an indication of a sufficient 103

  • 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
103
•
Concerns
- May require redundant networking channel. Requires
administrator or operator availability to support.
Anticipating User Disconnects and Reconnection
•
Issues
- Users must first be warned about the consequences of
disconnection. Agents that provide protection for a disconnected session can
also provide a nuisance for unsuspecting users if they fail to address
protective measures in place for their safety. For example, users must know
how much time they have to reconnect before safeguards take action. If a
remote agent arms itself for application termination, users should be
presented with a large, unmistakable disarming "opt-out" panel that, upon
login and discovery, they can halt any agent actions before termination.
Organizations should carefully discuss and publicize safety measures due to
potential data loss.
•
Concerns
- Users should not be able to disable or specify their own timeouts
due to potential irreversible data loss.
General Design Issues
•
All active agents should externally log their decisions and actions for post
mortem analysis.
•
Independent agents should provide their own opt-out, disarming dialogs with
countdown feedback before taking action.
•
Expect the unexpected - where possible, limit your actions to those areas you
are certain of the outcomes to minimize loss of data and productivity.
•
Always inspect error codes when reading event logs - the reliability of this
RGS communication method depends upon the Windows Event Log system.
While we have yet to see a failure in this path, we recommend using all
information available to its fullest potential.
Additional Safeguard Features for Windows systems
The following optional procedures for the RGS Sender service can improve the
reliability of your remote agent solution if required in your environment.
RGS Sender Service Recovery Settings
•
By default, most Windows services are installed without any automatic
restart/recovery settings. This means that when a service terminates,
Windows will, by default, not restart the service unless explicitly set. When
RGS Sender software is first installed, it is installed with Windows defaults (do
not restart).
•
Restarting the RGS Sender service can support RGS reconnection with a RGS
Receiver client (unless a system error prevents the RGS service from
restarting).
•
Agent designs should take into account whether or not to check for the
existence of a running RGS Sender service as an indication of a sufficient