HP t420 Administrator Guide 8 - Page 33

RDP multimedia redirection, RDP device redirection, RDP mass storage redirection

Page 33 highlights

NOTE: For more information about RDP multi-monitor sessions, see the HP ThinPro white paper True MultiMonitor Mode for RDP (available in English only). RDP multimedia redirection 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. TIP: For simplified management, HP recommends that MMR be enabled or disabled on the remote host. RDP device redirection Device redirection makes sure that when a user plugs a device into the thin client, the device is automatically detected and accessible in the remote session. RDP supports redirection of many different types of devices. RDP USB redirection USB redirection works by transmitting low-level USB protocol calls over the network to the remote host. Any USB device plugged into the local host appears within the remote host as a native USB device, as if it were plugged in locally. Standard Windows drivers support the device in the remote session, and all device types are supported without requiring additional drivers on the thin client. Not all devices default to USB redirection. For example, USB keyboards, mice, and other input devices usually are not set to be redirected, as the remote session expects input to come from the thin client. Some devices such as mass storage, printers, and audio devices might use additional options for redirection. Note the following additional information about USB redirection with RDP: ● The server must support USB redirection for it to be available to the thin client. General-purpose USB redirection is supported with RDVH servers with RemoteFX, Windows 8, Windows 10, Windows Server 2012, and Windows Server 2016. ● The protocol in USB Manager in Control Panel must be set to RDP. ● For RDP connections, the controls in USB Manager determine if a USB device is redirected. The settings for the individual connection determine how a USB device is redirected. RDP mass storage redirection By default, the RDP session redirects all mass storage devices to the remote host using high-level drive redirection. When a device such as a USB flash drive, USB DVD-ROM drive, or USB external HDD is plugged into the thin client, the thin client detects and mounts the drive on the local file system. RDP then detects a mounted drive and redirects it to the remote host. Within the remote host, it will appear as a new disk drive in Windows Explorer, with the name on ; for example, Bill_USB on HP04ab598100ff. There are three restrictions to this type of redirection. ● The device will not appear in the taskbar on the remote host with an icon to eject the device. Because of this, make sure to give the device a sufficient amount of time to sync data after a copy before removing the device to be sure that the device does not corrupt. Typically, less than one second is required after RDP 21

  • 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
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184

NOTE:
For more information about RDP multi-monitor sessions, see the HP ThinPro white paper
True Multi-
Monitor Mode for RDP
(available in English only).
RDP multimedia redirection
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.
TIP:
For
simplified
management, HP recommends that MMR be enabled or disabled on the remote host.
RDP device redirection
Device redirection makes sure that when a user plugs a device into the thin client, the device is automatically
detected and accessible in the remote session. RDP supports redirection of many
different
types of devices.
RDP USB redirection
USB redirection works by transmitting low-level USB protocol calls over the network to the remote host. Any
USB device plugged into the local host appears within the remote host as a native USB device, as if it were
plugged in locally. Standard Windows drivers support the device in the remote session, and all device types
are supported without requiring additional drivers on the thin client.
Not all devices default to USB redirection. For example, USB keyboards, mice, and other input devices usually
are not set to be redirected, as the remote session expects input to come from the thin client. Some devices
such as mass storage, printers, and audio devices might use additional options for redirection.
Note the following additional information about USB redirection with RDP:
The server must support USB redirection for it to be available to the thin client. General-purpose USB
redirection is supported with RDVH servers with RemoteFX, Windows 8, Windows 10, Windows Server
2012, and Windows Server 2016.
The protocol in USB Manager in Control Panel must be set to RDP.
For RDP connections, the controls in USB Manager determine if a USB device is redirected. The settings
for the individual connection determine how a USB device is redirected.
RDP mass storage redirection
By default, the RDP session redirects all mass storage devices to the remote host using high-level drive
redirection. When a device such as a USB
flash
drive, USB DVD-ROM drive, or USB external HDD is plugged into
the thin client, the thin client detects and mounts the drive on the local
file
system. RDP then detects a
mounted drive and redirects it to the remote host. Within the remote host, it will appear as a new disk drive in
Windows Explorer, with the name
<device label> on <client hostname>
; for example,
Bill_USB on HP04ab598100ff
.
There are three restrictions to this type of redirection.
The device will not appear in the taskbar on the remote host with an icon to eject the device. Because of
this, make sure to give the device a
sufficient
amount of time to sync data after a copy before removing
the device to be sure that the device does not corrupt. Typically, less than one second is required after
RDP
21