Home » HP Manuals » Desktops » HP Z620 » Manual Viewer

HP Z620 HP Remote Graphics Software 5.4.7 - Page 221

Agent design issues, Desktop session logout, Selective environment shutdown, Situation, Benefit, Issue - workstation memory

Add to My Manuals
Save this manual to your list of manuals

Page 221 highlights

Agent design issues Designing an agent to provide Remote Application Termination requires consideration of a number of issues in order to minimize data loss and determine when a last-resort shutdown of a disconnected desktop session is required. Listed below are several topics 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. 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 specified time limit for reconnection has expired). This action would drop all connections to the remote session. ● Benefit-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 specific applications of interest. It does not implement a full desktop session logout. It selectively protects only the most critical applications requiring oversight and control. ● Benefit-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 specific 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 specific applications. May also require a master semaphore to halt/terminate multiple agents if the user reconnects and wants to stop the shutdown process. Agent design issues 205

Section	Page
Introduction to HP Remote Graphics Software	17
Typical RGS configuration	19
RGS Sender and Receiver	20
RGS features	21
Additional RGS features	22
Tabloid-size page	23
Obtaining HP technical support	23
Software Service Strategy for Non-HP Hardware	23
Other RGS Documents	24
RGS overview	25
Supported computers and operating systems	25
RGS version numbering	28
RGS licensing	28
RGS products	29
Sender and Receiver interoperability	30
Application support	30
Networking support	31
Connection topologies	31
The Remote Computer frame buffer	31
One-to-one connection	32
Many-to-one connection	33
One-to-many connection	34
Establishing an RGS connection using Standard Login	36
Single Sign-on and Easy Login	38
Single Sign-on	38
Easy Login	38
Deciding between Single Sign-on and Easy Login	39
RGS operating modes	41
Multi-monitor configurations	41
Remote Computer monitor blanking overview	43
Video overlay surfaces	43
Image quality	43
Remote USB overview	44
USB session switching	45
Isochronous USB support	45
Install-time configuration of remote USB	45
Unique smartcard handling	47
Computers supporting remote USB	50
Supported USB devices	51
Remote audio	51
Remote audio on Windows	51
Remote audio on Linux	54
Support of sound recording devices on Microsoft Windows	55
Computers and operating systems which support RGS audio	56
Remote Clipboard overview	57
Interoperability of RGS and Microsoft Remote Desktop Connection	60
Remote Computer power saving states	61
Supported keyboard locales	61
RGS security features	62
Installing RGS	64
Installing RGS on Windows	64
Installing the Receiver on Windows	64
Manual installation of the Receiver on Windows	64
Automatic installation of the RGS Receiver on Windows	66
Usage	67
Command line options	67
Receiver installation log file	68
Uninstalling the RGS Receiver on Windows	69
Installing the Sender on Windows	69
Prerequisites for Sender installation on Windows Vista and Windows 7	69
Manual installation of the Sender on Windows	70
Starting and stopping the Sender on Windows	72
Sender command line options on Windows	73
The Sender GUI on Windows	75
Setting the Windows Sender process priority	75
Setting the Sender process priority using HP PA	76
Installing and enabling Single Sign-on	76
Enabling Single Sign-on during installation	76
Using the rgadmin tool to enable Single Sign-on	77
Manually enabling Single Sign-on (Windows XP Professional only)	79
Setting the local security policy (Windows XP Professional only)	80
Disabling Single Sign-on	80
Using the rgadmin tool to disable Single Sign-on	80
Manually disabling Single Sign-on (Windows XP Professional only)	81
Installing and Enabling Easy Login	82
Enabling Easy Login during installation	82
Using the rgadmin tool to enable Easy Login	82
Manually enabling Easy Login (Windows XP Professional only)	84
Chaining custom GINA modules for Easy Login (Windows XP Professional only)	85
Install time specification of the custom GINA module	85
Using the rgadmin tool to specify a custom GINA module	85
Manually enabling hprgina.dll to load a custom GINA module	85
Setting the Local Security Policy (Windows XP Professional)	86
Disabling Easy Login	86
Using the rgadmin tool to disable Easy Login	86
Manually disabling Easy Login (Windows XP Professional only)	87
Automatic installation of the RGS Sender on Windows	88
Usage	88
Command line options	88
Sender installation log file on Windows	90
Uninstalling the RGS Sender on Windows	90
Using the RGS Diagnostics Tool on Windows	91
Using the rgadmin tool	91
rgadmin tool on Windows XP Professional	92
rgadmin tool on Windows Vista and Windows 7	93
Installing RGS on Linux	94
Installing the Receiver on Linux	94
Uninstalling the Receiver on Linux	95
Linux Receiver Audio Requirements	95
Installing the Sender on Linux	95
Linux Sender Audio	98
Starting the Sender on Linux	98
Uninstalling the Sender on Linux	99
Pre-connection checklist	100
Local Computer (Receiver) checklist	100
Remote Computer (Sender) checklist	101
Network Interface binding on the Sender	102
Manual Network Interface reconfiguration	103
Network Interface reconfiguration using the Sender network interface binding properties	106
Using RGS through a firewall	107
Using RGS	109
Using RGS in Normal Mode	109
Receiver Control Panel	112
Setup Mode	112
Remote Display Window Toolbar	114
Remote Computer monitor blanking operation	115
Linux connection considerations	117
Full-screen crosshair cursors	117
Gamma correction on the Receiver	117
Black or blank connection session with the Linux Sender	117
RGS login methods	118
Standard Login	118
Easy Login	119
Single Sign-on	120
Changing your password	120
Collaborating	121
Creating a collaboration session	121
Collaboration notification dialog	123
Effect of low bandwidth and/or high latency networks on collaboration	125
Advanced capabilities	126
General options	127
General tab	127
General tab Experience section	128
Auto Launch	130
Game Mode	130
Remote audio operation	131
Configuring audio on the Microsoft Windows XP Professional Sender	131
Calibrating audio on the Microsoft Windows XP Professional Sender	135
Configuring audio on Microsoft Windows Vista and Windows 7 Sender	138
Configuring audio on Linux	138
Disabling audio on the Sender	139
Using audio	140
Potential audio issues	141
Remote USB operation	142
Attaching a local USB device to a Remote Computer	144
USB session switching	145
Local/Remote USB Device Management	146
Supported remote USB devices	147
Remote USB Access Control List	147
Determining USB device information	149
Determining USB device information for Windows	149
Determining USB device information for Linux	150
Verifying the USB data	150
Troubleshooting remote USB	151
Computers supporting remote USB	151
Supported USB devices	151
Check USB cable connections	151
Reset the USB device	151
Enable Remote USB	152
HP Remote Virtual USB Driver	153
USB device drivers and program support	154
Adjusting Network timeout settings	155
Network timeouts	156
Receiver network timeouts	156
Sender network timeout	159
Network timeout issues	159
Dialog timeouts	161
Hotkeys	163
Changing the Setup Mode hotkey sequence	165
Remote Clipboard operation	165
Remote Clipboard data transfers	166
Remote Clipboard filtering	169
Using the RGS log to detect clipboard problems	171
Receiver and Sender logging	173
Receiver logging	173
Sender logging	174
Statistics	176
Using Directory Mode	177
Directory file format	177
Starting the Receiver in Directory Mode	178
RGS properties	181
Property syntax	181
Setting property values in a configuration file	181
Setting properties on the command line	182
Authenticator properties	182
RGS Receiver properties	183
Receiver property hierarchy	183
Restoring Receiver properties default values	183
Properties set using the Receiver Control Panel	183
Receiver command line properties	183
rgreceiverconfig file properties	183
Archive file properties	184
Receiver default properties	184
Receiver property groups	184
Receiver general properties	188
Receiver experience properties	195
Receiver browser properties	195
Receiver audio properties	196
Receiver microphone property	196
Receiver USB properties	196
Receiver network properties	197
Receiver hotkey properties	198
Receiver Remote Clipboard properties	199
Receiver logging properties	200
Receiver image codec properties	201
Auto Launch session properties	202
Window placement and size properties	202
RGS Sender properties	204
Sender property groups	204
Sender general properties	205
Microphone property group	208
Sender network timeout properties	208
Sender USB access control list properties	208
Network Interface binding properties	209
Sender clipboard property	210
Sender event logging on Windows	211
The HPRemote log	211
Usages of the HPRemote log	214
Additional information on event logging	215
Remote Application Termination	216
RGS connection and user status	216
HPRemote log format	216
Agent design issues	221
Desktop session logout	221
Selective environment shutdown	221
Wrapping applications of interest	222
Administrator alerts	222
Anticipating user disconnects and reconnects	222
General agent design guidelines	222
Sample Agent	224
Additional features for Windows systems	229
RGS Sender Service Recovery Settings	229
Microsoft Remote Desktop Recovery	230
Optimizing RGS performance	231
Performance tuning for all platforms	231
Performance tuning for Windows	231
Troubleshooting graphics performance	232
Graphics adapter frame buffer read performance	232
Configuring your network for optimal performance	233
Troubleshooting RGS	235
Potential RGS issues and troubleshooting suggestions	235
RGS error messages	236
Receiver error messages	236
USB devices supported by RGS	239
Linux remote audio device support	246

Match case Limit results 1 per page

Agent design issues

Designing an agent to provide Remote Application Termination requires consideration of a number of

issues in order to minimize data loss and determine when a last-resort shutdown of a disconnected

desktop session is required. Listed below are several topics 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.

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 specified

time limit for reconnection has expired). This action would drop all connections to the remote

session.

●

Benefit

—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 specific applications of interest. It

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

applications requiring oversight and control.

●

Benefit

—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 specific 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 specific applications. May also require a

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

shutdown process.

Agent design issues

205