HP t510 Administrator Guide 7 - Page 53

Using multi-monitor sessions with RDP, Using multimedia redirection with RDP

Page 53 highlights

NOTE: Some Windows RDP servers will not send RemoteFX content to thin clients enabled for RDP 7.1 without a change to Group Policy. Check the setting of the following policy: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Enable RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1 In addition, Windows Server 2012 and Windows Server 2012 R2 require the following setting to be set to 32bit: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Limit maximum color depth Using multi-monitor sessions with RDP True multi-monitor support does not require special configuration. The RDP client automatically identifies which monitor is specified as the primary monitor in the local settings and places the taskbar and desktop icons on that monitor. When a window is maximized within the remote session, the window will only cover the monitor it was maximized on. Display preferences and monitor resolutions can be viewed but not modified within the remote session. To modify the session resolution, log out of the session and change the resolution on the local thin client. By default, all RDP sessions will be full-screen and cover all monitors to enhance the virtualization experience. Additional window options are available in the RDP Connection Manager. NOTE: Remote Desktop Virtualization Host (RDVH) sessions with graphics card support might only support certain resolutions and counts of monitors. The limits are specified when the RemoteFX virtual graphics device is configured for the RDVH virtual machine. Using multimedia redirection with RDP Multimedia redirection (MMR) is a technology that integrates with Windows Media Player on the remote host and streams the encoded media to the RDP client instead of playing it on the remote host and re-encoding it via RDP. This technology reduces the server load and network traffic, and greatly improves the multimedia experience, supporting 24 fps playback of 1080p videos with automatic audio syncing. MMR is enabled by default. The RDP client will negotiate with any RDP server it contacts, and if MMR is available, it will be used. MMR also uses an advanced codec detection scheme that identifies whether the thin client supports the codec being requested by the remote host before attempting to redirect it. The result is that only supported codecs will be redirected and all unsupported codecs fall back to server-side rendering. To disable MMR on the thin client for all RDP connections, set the following registry key to 0: root/ConnectionType/freerdp/general/enableMMR Because RemoteFX already delivers acceptable multimedia performance, you can disable MMR with RFX by setting the following registry key to 1: root/ConnectionType/freerdp/connections//disableMMRwithRFX TIP: For simplified management, HP recommends that MMR be enabled or disabled on the remote host. Using multi-monitor sessions with RDP 41

  • 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
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169

NOTE:
Some Windows RDP servers will not send RemoteFX content to thin clients enabled for RDP 7.1
without a change to Group Policy. Check the setting of the following policy:
Local Computer Policy > Computer
Configuration
> Administrative Templates > Windows Components >
Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Enable
RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1
In addition, Windows Server 2012 and Windows Server 2012 R2 require the following setting to be set to
32-
bit
:
Local Computer Policy > Computer
Configuration
> Administrative Templates > Windows Components >
Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Limit
maximum color depth
Using multi-monitor sessions with RDP
True multi-monitor support does not require special
configuration.
The RDP client automatically
identifies
which monitor is
specified
as the primary monitor in the local settings and places the taskbar and desktop
icons on that monitor. When a window is maximized within the remote session, the window will only cover the
monitor it was maximized on.
Display preferences and monitor resolutions can be viewed but not
modified
within the remote session. To
modify the session resolution, log out of the session and change the resolution on the local thin client.
By default, all RDP sessions will be full-screen and cover all monitors to enhance the virtualization
experience. Additional window options are available in the RDP Connection Manager.
NOTE:
Remote Desktop Virtualization Host (RDVH) sessions with graphics card support might only support
certain resolutions and counts of monitors. The limits are
specified
when the RemoteFX virtual graphics
device is
configured
for the RDVH virtual machine.
Using multimedia redirection with RDP
Multimedia redirection (MMR) is a technology that integrates with Windows Media Player on the remote host
and streams the encoded media to the RDP client instead of playing it on the remote host and re-encoding it
via RDP. This technology reduces the server load and network
traffic,
and greatly improves the multimedia
experience, supporting 24 fps playback of 1080p videos with automatic audio syncing. MMR is enabled by
default. The RDP client will negotiate with any RDP server it contacts, and if MMR is available, it will be used.
MMR also uses an advanced codec detection scheme that
identifies
whether the thin client supports the codec
being requested by the remote host before attempting to redirect it. The result is that only supported codecs
will be redirected and all unsupported codecs fall back to server-side rendering.
To disable MMR on the thin client for all RDP connections, set the following registry key to 0:
root/ConnectionType/freerdp/general/enableMMR
Because RemoteFX already delivers acceptable multimedia performance, you can disable MMR with RFX by
setting the following registry key to 1:
root/ConnectionType/freerdp/connections/<UUID>/disableMMRwithRFX
TIP:
For
simplified
management, HP recommends that MMR be enabled or disabled on the remote host.
Using multi-monitor sessions with RDP
41