approach can further be dened to exploit redundant network connection support to a remote system to
allow user-directed shutdowns to occur.
●
Benet—System agents are not required to take destructive action—they serve only as alarms and
monitors for alternative human intervention.
●
Issue—May require redundant networking channel. Requires administrator or operator availability to
support.
Anticipating user disconnects and reconnects
●
Situation—Users must rst be warned about the consequences of disconnection. Agents that provide
protection for a disconnected session may become 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.
●
Issue— Users should not be able to disable or specify their own timeouts due to potential irreversible
data loss.
General agent design guidelines
In developing an agent, HP recommends following these guidelines:
●
The agent should externally log its decisions and actions for postmortem 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.
Recovery settings for the RGS Sender service
This section discusses restart options for RGS Sender and possible interactions of the agent with the sender.
By default, most Windows services are installed without any automatic restart or recovery settings. The same
is true for the RGS Sender service.
Restarting the RGS Sender service can help reconnect a lost RGS connection (unless a system error prevents
the RGS Sender service from restarting).
When designing the agent, you should consider whether to check for the existence of a running RGS Sender
service as an indication of a suicient primary user connection. If service restarts are programmed for your
environment, this test may be unnecessary.
To set the RGS Sender service to restart automatically, you must change its recovery settings on the Recovery
panel of its properties (right-click the service and select Properties).
Actions to take for the rst failure, second failure, and subsequent failures are available in the properties
menu. The Recovery options include:
82 Appendix B Creating an agent for remote application termination (Windows only)
Comentarios a estos manuales