Using Remote Graphics Software
monitorEvents(EVENT_SERVER, EVENT_SRC, seconds);
... cleanup agent here or send alerts ...
... may wish to return status from monitorEvents ...
}
NOTE: The parameter EVENT_SRC above defines the name of an event generator here, not necessarily the Windows Event Log name HPRemote as suggested by external documentation. Supported event source names include:
RGS Event Source Name | Description |
(LPCTSTR) |
|
|
|
"rgsender" | Events generated by the RGS |
| Sender service |
|
|
More information and examples for Event Log readers is available at:
http://msdn.microsoft.com/library
Search on the topic OpenEventLog for a function description and additional examples.
Agent Design Issues
Windows Application Agents for RGS remote session require careful design to maximize their effectiveness. Issues and tradeoffs can minimize data loss and determine when a last resort shutdown of a disconnected Windows session is required.
The following list introduces topics of interest to consider when designing application control agents for your environment. The topics are not exhaustive. Use them as a starting point for a more complete design that meets your business requirements. In general, remote administration of an arbitrary application environment will require some pioneering work.
Desktop Session Logout
∙Issues - 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 specific time allowance for reconnection has expired). This action would drop all connections to the remote session.
∙Benefits - Implementing a full session shutdown / logout ensures that all connection activity ceases immediately and 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 session management. Agent relies upon Windows logout routines to terminate environment - simple in design and result.
∙Concerns - Forcing a 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
101