HP t420 Administrator Guide 8 - Page 41

VMware Horizon View webcam redirection, Changing the VMware Horizon View protocol

Page 41 highlights

NOTE: After you supply the correct PIN, the user's credentials will be used to log in to the VMware Horizon View Manager server. Please see the VMware Horizon View documentation for details on configuring the server to support smart card login. As long as the server is configured to allow smart card login, the user's credentials will pass through and they will be logged in to the desktop without having to enter their PIN again. NOTE: To log in to the VMware Horizon View Manager administrator server with a smart card, the local smart card driver must be installed on the thin client. See RDP smart card redirection on page 23 for more information on smart card driver installation. Once logged in to the remote host, the smart card will be passed to the remote host using a virtual channel, not USBR. This virtual channel redirection makes sure that the smart card can be used for tasks such as email signing, screen locking, and so on, but might cause the smart card to not show as a smart card device in the Windows Device Manager. NOTE: The remote host must have the proper smart card drivers installed. VMware Horizon View webcam redirection The VMware Horizon View client supports high-level webcam redirection only through RTAV using x86 units connected to a back-end server running VMware Horizon View 5.2 Feature Pack 2 or higher. Other connection methods do not support high-level webcam redirection and can redirect webcams only using USBR. Based on internal testing and validation, HP has found that the performance of a webcam connected through basic USBR performs poorly. HP does not recommend the use of this configuration and suggests that customers who require this function test using x86 units with RTAV technology to ensure satisfactory levels of performance. With USBR, the webcam might perform poorly or not at all. See RDP USB redirection on page 21 for more information. Changing the VMware Horizon View protocol VMware Horizon View Client can use either the PCoIP, RDP, or BLAST protocol. To change the protocol: 1. In VMware Horizon View Client, select a pool that supports one of the supported protocols. 2. Under the Connection menu, select Settings. 3. Change the protocol by using the drop-down box next to Connect Via. NOTE: Use VMware Horizon View Manager to set which protocol should be used for each desktop pool. TIP: HP recommends using the PCoIP protocol to enhance the desktop experience. However, the RDP protocol provides more options for customization and might work better on slower connections. VMware Horizon View HTTPS and certificate management requirements VMware Horizon View Client 1.5 and VMware Horizon View Server 5.0 and later require HTTPS. By default, the VMware Horizon View client warns about untrusted server certificates, such as self-signed (like the VMware Horizon View Manager default certificate) or expired certificates. If a certificate is signed by a Certificate Authority (CA) and the CA is untrusted, the connection will return an error and the user will not be allowed to connect. HP recommends that a signed certificate verified by a standard trusted root CA be used on the VMware Horizon View Manager server. This makes sure that users will be able to connect to the server without being prompted or required to do any configuration. If using an internal CA, the VMware Horizon View client connection returns an error until you complete one of the following tasks: ● Use Certificate Manager to import the certificate from a file or URL. ● Use a remote profile update to import a certificate. VMware Horizon View 29

  • 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:
After you supply the correct PIN, the user’s credentials will be used to log in to the VMware Horizon
View Manager server. Please see the VMware Horizon View documentation for details on
configuring
the
server to support smart card login. As long as the server is
configured
to allow smart card login, the user’s
credentials will pass through and they will be logged in to the desktop without having to enter their PIN again.
NOTE:
To log in to the VMware Horizon View Manager administrator server with a smart card, the local
smart card driver must be installed on the thin client. See
RDP smart card redirection
on page
23
for more
information on smart card driver installation. Once logged in to the remote host, the smart card will be passed
to the remote host using a virtual channel, not USBR. This virtual channel redirection makes sure that the
smart card can be used for tasks such as email signing, screen locking, and so on, but might cause the smart
card to not show as a smart card device in the Windows Device Manager.
NOTE:
The remote host must have the proper smart card drivers installed.
VMware Horizon View webcam redirection
The VMware Horizon View client supports high-level webcam redirection only through RTAV using x86 units
connected to a back-end server running VMware Horizon View 5.2 Feature Pack 2 or higher. Other connection
methods do not support high-level webcam redirection and can redirect webcams only using USBR. Based on
internal testing and validation, HP has found that the performance of a webcam connected through basic
USBR performs poorly. HP does not recommend the use of this
configuration
and suggests that customers
who require this function test using x86 units with RTAV technology to ensure satisfactory levels of
performance. With USBR, the webcam might perform poorly or not at all. See
RDP USB redirection
on page
21
for more information.
Changing the VMware Horizon View protocol
VMware Horizon View Client can use either the PCoIP, RDP, or BLAST protocol.
To change the protocol:
1.
In VMware Horizon View Client, select a pool that supports one of the supported protocols.
2.
Under the
Connection
menu, select
Settings
.
3.
Change the protocol by using the drop-down box next to
Connect Via
.
NOTE:
Use VMware Horizon View Manager to set which protocol should be used for each desktop pool.
TIP:
HP recommends using the PCoIP protocol to enhance the desktop experience. However, the RDP
protocol provides more options for customization and might work better on slower connections.
VMware Horizon View HTTPS and
certificate
management requirements
VMware Horizon View Client 1.5 and VMware Horizon View Server 5.0 and later require HTTPS. By default, the
VMware Horizon View client warns about untrusted server
certificates,
such as self-signed (like the VMware
Horizon View Manager default
certificate)
or expired
certificates.
If a
certificate
is signed by a
Certificate
Authority (CA) and the CA is untrusted, the connection will return an error and the user will not be allowed to
connect.
HP recommends that a signed
certificate
verified
by a standard trusted root CA be used on the VMware
Horizon View Manager server. This makes sure that users will be able to connect to the server without being
prompted or required to do any
configuration.
If using an internal CA, the VMware Horizon View client
connection returns an error until you complete one of the following tasks:
Use
Certificate
Manager to import the
certificate
from a
file
or URL.
Use a remote
profile
update to import a
certificate.
VMware Horizon View
29