HP Remote Graphics Software 7.0

Additional features for Windows systems
The following optional procedures for the RGS Sender service can improve the reliability of your
remote agent solution.
RGS Sender Service Recovery Settings
This section discusses restart options for the RGS Sender and possible interactions of the agent with
the remote computer.
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 the Windows default (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).
In designing the agent, you should consider whether or not to check for the existence of a running
RGS Sender service as an indication of a sufficient primary user connection. If service restarts are
programmed for your environment, this test may be unnecessary.
To set the RGS Sender service for automatic restart, you must adjust its Recovery Property through
the Administrative Tools and Services control panel options.
Actions to take for the first failure, second failure, and subsequent failures are available in the
properties menu. The Recovery options include:
●
Take No Action
●
Restart the Service
●
Run a Program
●
Restart the Computer
Microsoft Remote Desktop Recovery
If the RGS Sender becomes unavailable and the RGS Receiver can no longer connect to the RGS
Sender, a Windows system with Remote Desktop services enabled can access the remote computer
to diagnose the issue.
Sample agent
The following sample Windows agent monitors the HPRemote event log and interprets its events.
Comments are included in the agent code showing where additional code would be added to
determine if the number of primary users has dropped to zero. If so, further code can be added to
terminate applications on the remote computer.
The sample code is a fixed-polling Windows agent that reads and interprets the HPRemote event log.
The agent uses two functions:
1.
processEvent(eventServer, eventSource, dwEventNum)
●
open event log, read event dwEventNum, close event log
●
if a valid read, process recognized EventIDs, then return
2.
monitorEvents(eventServer, eventSource, seconds)
Remote application termination 67