HP Z620 HP Remote Graphics Software 5.4.7 - Page 222
Wrapping applications of interest, Administrator alerts, Anticipating user disconnects
View all HP Z620 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 222 highlights
Wrapping applications of interest ● Situation-Agents can be launched that supervise only specific applications in a given environment. Tying agents to specific applications is a selective safety net for every user. ● Benefit-Application-specific agents can be implemented as plug-ins or support utilities for a given application. In the future, certain software providers may provide custom interfaces for safe shutdown messages from an agent or the operating system. Custom agents can be independently maintained and tied to specific application releases for greater support flexibility. Independent agent design supports unit testing and decouples environmental dependencies. ● Issue-Users need specific recourse to disarm an agent if they reconnect. Applications may not interact well with a dedicated agent (and only shutdown due to a global shutdown request). Dedicated agents could possibly be compromised. Administrator alerts ● Situation-Instead of shutting down an environment, an agent can be designed to alert an administrator or operator to determine the status of the user before taking action. This watchdog approach can further be defined to exploit redundant network connection support to a remote system to allow user-directed shutdowns to occur. ● Benefit-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 first 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 "optout" 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. 206 Chapter 10 Remote Application Termination