Troubleshooting
www.amulethotkey.com
| Page 41
5. Disconnect then reconnect the PCoIP session.
6.
On the host PC, manually configure the display topology
using the Display applet in the Windows Control Panel.
In future PCoIP sessions, Windows remembers the display
topology that you specified in the Control Panel and does not
try to enforce a display topology defined in the zero client
OSD.
Note:
The background and a workaround for this problem are
described in Teradici knowledge base article,
display issues after installing firmware 4.0.2?
8.2
Devices attached to the Mouse USB port are
blocked unexpectedly
This section describes how to resolve a problem with USB
devices being unexpectedly rejected by the Mouse ports on the
DXZ4 security edition zero client front panel.
8.2.1 Symptoms
The DXZ4-A and DXZ4-AM Mouse USB ports include an integral
USB hub. In normal use, the hub is transparent to end-users.
However, the hub can have unexpected consequences if your
organization uses the
USB Permissions
feature of the PCoIP
protocol (see the note below) to block unauthorized devices
(black-listing) or only allow authorized devices (white-listing).
If your organization has black-listed USB hubs (for example, to
prevent users circumventing rules on prohibited USB devices),
then any mouse, keyboard or other device plugged into the
Mouse USB port on the DXZ4-A or DXZ4-AM will be blocked. This
is because the port’s integral USB hub is itself rejected.
Likewise, if the Mouse USB ports on the DXZ4-A or DXZ4-AM
are white-listed to only allow specific HID devices (human
interface devices such as a mouse or keyboard), then any HID
device attached to the rear ports will be unexpectedly rejected.
This is because the DXZ4-A detects the hub behind the Mouse
port, recognizes the hub as a non-HID device, and blocks the
attempted connection before the actual HID device can be
detected.
Note:
The
USB Permissions
feature is available for PCoIP host
and zero client devices. It allows administrators to define lists
of authorized and unauthorized USB devices. This feature is
configured in the PCoIP Management Console or the AWI.
For more details, see the
Teradici.PCoIP.Zero.Client.and.Host.
Administrator.Guide
, available to download from the Teradici
website.
8.2.2 Workarounds
If your organization needs to black-list USB hubs or white-list HID
devices, any device connected to the DXZ4-A or DXZ4-AM Mouse
ports will be blocked. There are two possible workarounds:
•
Instruct users to connect their device to any other USB port
on the DXZ4-A or DXZ4-AM.
8.1.6
Fix 3: Disable the Use Client Topology Settings feature
on the host computer
Note:
If the user is likely to connect to their remote worksta
-
tion from different zero clients (for example, in a hot-desking
environment), the most reliable solution is to implement fix 1.
We do not recommend fix 3 if the physical monitor
arrangements are likely to differ for each zero client.
For this fix, open the PCoIP Host Software Settings dialog on the
host computer. Disable the setting that causes the PCoIP Host
Driver Function to report the zero client display topology to the
Windows operating system.
1.
On the host PC, right-click the PCoIP icon in the Windows
task bar notification area (
1
in
Open Properties
.
Figure 32:
PCoIP.icon.in.the.Windows.Task.bar
2. In the
PCoIP Host Software Settings
dialog, click
Monitors
in
the left pane.
3. In the
Monitors
screen, clear the
Use client topology
settings
check box. See
.
By disabling this setting, you prevent the PCoIP Host Driver
Function from writing the zero client display topology settings
to the operating system on the host PC when a PCoIP session
starts.
Figure 33:
Clear.the.client.topology.settings.option.
4. Click
OK
.
