HP Xw9400 Remote Graphics Software 4.2.0 User Guide - Page 121

Remote Graphics and Microsoft Remote Desktop, Interaction

Get HP Xw9400 - Workstation - 16 GB RAM PDF manuals and user guides View all HP Xw9400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 121 highlights

Using Remote Graphics Software Remote Graphics and Microsoft Remote Desktop Interaction Prior to release 4.0, RGS Sender for Windows could not coexist on systems enabled for Windows Remote Desktop connections. At release 4.0, connections made with either HP Remote Graphics or Windows Remote Desktop will work. Simultaneous desktop sharing, however, is not possible. A RGS connection to a sender already occupied with a Remote Desktop connection only works if the user credentials match for both connections. This implies that the same user wants access to transition from Remote Desktop to a RGS connection. If allowed, the current Remote Desktop connection disconnects and the RGS Receiver takes control of the current Windows desktop session. The current user does not log off and work continues with the new connection. The reverse works as well. A user who connects to his or her RGS session with a Remote Desktop connection displaces the first connection. In this case, the Remote Desktop connection causes the RGS Sender to disconnect all of its receivers (including all RGS collaborators). The Windows desktop session remains active during the switch. If a user disconnects from a system using the Windows Remote Desktop disconnect button, the session remains logged in and all applications continue to run. The session, however, locks its screen. Remote Graphics connections only work if the credentials match the currently logged-in user. If a user logs out of their session while using Remote Desktop, the RGS Sender returns the system to its initial logged out state. Any authorized user can connect and log into this system using Remote Graphics. A Remote Desktop connection made to a sender already occupied with a RGS connection by a non-matching user prompts the new user to logout the current RGS user. Only administrators can logout other users. Non-administrators are refused with a warning message about permissions. If Remote Desktop logs out the current RGS user, then the sender disconnects all of its receivers (including all RGS collaborators). Note: Under reverse circumstances for the above, RGS connections will not logout an existing Remote Desktop user regardless of authority. RGS will report an authorization failure message concerning a different user owning the desktop. 113

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
Using Remote Graphics Software
113
Remote Graphics and Microsoft Remote Desktop
Interaction
Prior to release 4.0, RGS Sender for Windows could not coexist on systems enabled
for Windows Remote Desktop connections. At release 4.0, connections made with
either HP Remote Graphics or Windows Remote Desktop will work. Simultaneous
desktop sharing, however, is not possible.
A RGS connection to a sender already occupied with a Remote Desktop connection
only works if the user credentials match for both connections. This implies that the
same user wants access to transition from Remote Desktop to a RGS connection. If
allowed, the current Remote Desktop connection disconnects and the RGS Receiver
takes control of the current Windows desktop session. The current user does not log
off and work continues with the new connection. The reverse works as well. A user
who connects to his or her RGS session with a Remote Desktop connection displaces
the first connection. In this case, the Remote Desktop connection causes the RGS
Sender to disconnect all of its receivers (including all RGS collaborators). The
Windows desktop session remains active during the switch.
If a user disconnects from a system using the Windows Remote Desktop disconnect
button, the session remains logged in and all applications continue to run. The
session, however, locks its screen. Remote Graphics connections only work if the
credentials match the currently logged-in user.
If a user logs out of their session while using Remote Desktop, the RGS Sender
returns the system to its initial logged out state. Any authorized user can connect
and log into this system using Remote Graphics.
A Remote Desktop connection made to a sender already occupied with a RGS
connection by a non-matching user prompts the new user to logout the current RGS
user. Only administrators can logout other users. Non-administrators are refused
with a warning message about permissions. If Remote Desktop logs out the current
RGS user, then the sender disconnects all of its receivers (including all RGS
collaborators). Note: Under reverse circumstances for the above, RGS connections
will not logout an existing Remote Desktop user regardless of authority. RGS will
report an
authorization
failure message concerning a different user owning the
desktop.