HP Remote Graphics Software (RGS) Instrukcja Użytkownika Pobierz pdf (Strona 91)

100

101

Desktop session logout

●

Situation—In some circumstances, loss of a primary user connection should trigger a full shutdown of

all applications and force a logout of the desktop session (perhaps after a specied time limit for

reconnection has expired). This action would drop all connections to the remote session.

●

Benet—Implementing a full desktop session shutdown/logout ensures that all connection activity

ceases immediately and ensure that applications are prevented from further unattended actions.

Shutdown of a remote session frees the workstation for connection by other users. This approach is the

most absolute and secure solution for desktop session management. Agent relies upon Windows logout

routines to terminate environment—simple in design and result.

●

Issue—Forcing a desktop session shutdown/logout can result in data loss for any open applications on

the desktop session. Forcing session logouts can result in application alert prompts requiring user

interaction to save altered data. These prompts can delay or halt an interactive logout. Session

termination also destroys memory of window placement on the desktop, and requires user intervention

at restart.

Selective environment shutdown

●

Situation—Partial shutdown of an environment only terminates specic applications of interest. It does

not implement a full desktop session logout. It selectively protects only the most critical applications

requiring oversight and control.

●

Benet—Preserves the active desktop session for connection at a later time. Selectively terminates the

applications of interest. Preserves data not governed by an automated shutdown policy. Supports

session recovery with an arbitrary connection time. If done in layers (giving some applications more

time to live than others), then a gradual "soft landing" shutdown can occur that ultimately results in a

full logout. Idle resources over a specic amount of time can be returned to a remote server pool.

●

Issue—Potentially more complicated to implement. Can require coordination of multiple agents to

handle layered shutdown. May still result in data loss for specic applications. May also require a master

semaphore to halt/terminate multiple agents if the user reconnects and wants to stop the shutdown

process.

Wrapping applications of interest

●

Situation—Agents can be launched that supervise only specic applications in a given environment.

Tying agents to specic applications is a selective safety net for every user.

●

Benet—Application-specic 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 specic application releases for greater support exibility. Independent agent design supports

unit testing and decouples environmental dependencies.

●

Issue—Users need specic 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

Agent design guidelines 81

1 2 ... 86 87 88 89 90 91 92 93 94 95 96 ... 100 101

Komentarze do niniejszej Instrukcji

Brak uwag

HP Remote Graphics Software (RGS) Instrukcja Użytkownika Strona 91

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Nie HP Remote Graphics Software (RGS)