This topic answers common questions about using peripherals with cloud computers.
Contents
Category | FAQ |
General | |
Keyboards and mice | |
Printers and cameras | |
USB flash drives and UKeys | |
Phones and tablets |
General
Supported USB peripherals
Cloud computers provide USB redirection, allowing you to connect various devices such as printers, USB flash drives, graphics tablets, and cameras. For more information, see Configure peripheral access.
If a peripheral device does not work with your cloud computer, contact your administrator to check if USB redirection is enabled in the cloud computer's policy.
Missing Devices option in toolbar
The Devices option may disappear from the top menu bar if you connect to a cloud computer that runs Linux Ubuntu without using the Adaptive Streaming Protocol (ASP) and then manually upgrade the OS.
Normally, whether the Devices option appears in the toolbar depends on the USB redirection policy set by your administrator. If USB redirection is enabled, the option appears. If it is disabled, the option does not appear. If your administrator has enabled USB redirection in the console but the Devices option is still missing from the toolbar, you must contact your administrator. The administrator can take the following actions:
For cloud computers with a Linux Ubuntu 18.04 image, the administrator can change the image in the console to upgrade the OS. You do not need to upgrade the OS manually from within the desktop.
If you need a cloud computer with a Linux Ubuntu 20.04 image, the administrator can select a desktop template that includes the Linux Ubuntu 20.04 image when creating a new cloud computer.
Keyboards and mice
Keyboard not working correctly
If your keyboard produces incorrect characters or behaves unexpectedly in the cloud computer, such as displaying 1.00, 0.90, 0.80... when you press the A key, or 1.00, 0.60... when you press the S key, the cause may be sticky keys. You can try the following solutions:
Press the
Ctrlkey to restore the session. If the session is not restored, disconnect from the cloud computer and reconnect.Change the image. For more information, see Change the image of a cloud computer or a cloud computer pool.
Mouse pointer behaves abnormally in a game or 3D software
Enable cursor confinement to lock the mouse pointer within the cloud computer desktop.
Connect to the cloud computer.
Click the floating ball and select Settings.
Go to Preferences > Control.
Turn on the Confine Cursor switch.
Once enabled, the mouse pointer stays within the cloud computer desktop and cannot move to other areas (such as the floating ball or outside the window).
Cursor confinement resets to disabled after you disconnect and reconnect. Re-enable it each session.
(Optional) To temporarily release the cursor, press Esc twice, or use
Ctrl+Alt+2(orCtrl+Option+2on macOS). To set a custom shortcut, configure it in the Release Cursor Shortcut section.
The steps above are based on Windows client version 7.11. The UI may differ in other versions.
Printers and cameras
Printer connection failure with error 0x0000011b
A Windows cloud computer is connected to a printer via USB and shares the printer on a local area network. Other cloud computers then access the cloud computer that is sharing the printer by using its IP address. When you try to connect to the printer, a dialog box appears, indicating that Windows cannot connect to the printer and displaying the error message 0x0000011b. In this case, you can add a new registry entry on both the cloud computer that is sharing the printer and the cloud computer that needs to use the shared printer.
In the cloud computer, press
Win+Rto open the Run window, enterregedit, and click OK to open the Registry Editor.In the Registry Editor window, open the directory
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print, and then press the Enter key.In the panel on the right, right-click a blank area and select New > DWORD (32-bit) Value.
Name the registry entry created in the previous step
RpcAuthnLevelPrivacyEnabledand set its value to0.
No printer driver for Windows Server
Printer manufacturers typically provide drivers for Windows 7/10/11 operating systems. Some may also provide drivers for Windows Server 2016/2019. If a driver for Windows Server 2016/2019 is not available from the manufacturer, you can use the following solution.
Solution
Obtain the Windows 10 driver from the printer manufacturer's official website.
Install the driver on your cloud computer.
If the driver installs and functions correctly, it is compatible with Windows Server 2016/2019, and you can use the printer normally.
If the installation fails, you must manually install the driver by specifying the file path.
Extract the downloaded Windows 10 driver files on the cloud computer.
In the device's properties panel, click the Advanced tab, and then click New Driver next to the driver information.
In the new panel, click Have Disk, browse to the directory where you extracted the driver files, and follow the on-screen instructions to complete the process.
NoteIf the extracted package contains multiple drivers and you are unsure which one to select, check the driver name on an on-premises device where the printer is already installed and working correctly. Then, select the corresponding driver for installation.
USB camera not recognized
Symptom
My cloud computer does not recognize the USB camera connected to my on-premises device.
Causes
This issue can occur for several reasons:
The USB redirection policy is not enabled for the cloud computer.
You have not connected the USB camera in the peripheral settings.
The USB camera has a poor connection, or the USB cable is damaged.
Solution
Try the following steps to resolve the issue:
Ensure that your administrator has enabled the USB redirection policy for your cloud computer. For more information, see Peripheral-related policies.
On the cloud computer desktop, open the DesktopAssistant and select Peripherals. In the Peripherals panel, find the USB camera and click Connect.
Unplug and replug the USB camera, or try a different USB cable.
USB flash drives and UKeys
Using UKey devices
Common USB UKey devices are available in three types: HID, MASSSTORAGE, and composite (HID and MASSSTORAGE). The procedures and notes for using UKey devices in a cloud computer vary by type.
HID UKey devices
HID-type UKey devices use USB redirection by default in a cloud computer, so you can connect them by using the default settings.
For some UKey devices, the cloud computer may fail to retrieve the device name. Such devices might be blacklisted by default. As a result, the device does not appear in the peripheral management list of the cloud computer. In this case, you must add the device to the whitelist.
NoteThe following steps use the Windows client V6.0 as an example. The UI may vary depending on your client version.
On the card view page of the Windows client, click the
icon and select Settings.In the Preferences panel, select Peripheral Management.
Under Local Peripherals, find the device, and in the USB redirection whitelist/blacklist column, select Whitelist.
Unplug and replug the UKey device, or reconnect to the cloud computer.
MASSSTORAGE and composite HID and MASSSTORAGE UKey devices
For MASSSTORAGE and composite UKey devices, it is difficult to distinguish them from other storage devices by their appearance. By default, these devices use device redirection, similar to other storage devices. However, UKey devices do not function correctly with device redirection. To resolve this, follow these steps:
In the cloud computer, open the DesktopAssistant and click Peripherals.
In the Peripherals dialog box, click Advanced Peripheral Settings.
In the Advanced Peripheral Settings dialog box, click Unknown Device.
Find the corresponding UKey device and select USB Redirection.
Unplug and replug the UKey device.
UKey not in peripherals list
Symptom
USB redirection is enabled in the console, but after you insert a UKey device, it does not appear in the peripherals list of the cloud computer.
Cause
The cloud computer may be unable to retrieve the names of certain UKey devices. These devices might be blacklisted by default. Blacklisted devices do not appear in the peripherals list.
Solution
On the card view page of the client, click the
icon and select Settings.In the Preferences panel, select Peripheral Management.
In the peripheral management settings, find the device and add it to the whitelist.
Unplug and replug the device, or reconnect to the cloud computer.
UKey listed but unusable
If USB redirection is enabled in the console and an inserted UKey device appears in the peripherals list as available but does not work in the cloud computer, you can try the following solutions:
Change the UKey device's redirection mode to USB redirection.
In the cloud computer, open the DesktopAssistant and click Peripherals.
In the Peripherals dialog box, click Advanced Peripheral Settings.
In the Advanced Peripheral Settings dialog box, click Unknown Device.
Find the corresponding UKey device and select USB Redirection.
Unplug and replug the UKey device.
Install the required driver.
For many UKey devices to function correctly after being connected via USB redirection, you must install a corresponding driver on the cloud computer. If the UKey device appears in the peripherals list but is unusable, you must install its corresponding driver.
Cannot transfer files to USB flash drive
After you connect to a cloud computer and insert a USB flash drive into your on-premises device, the cloud computer recognizes the drive, but you cannot modify files on it or transfer files to or from it. In this case, you need to contact your administrator to modify the cloud computer's policy and set Local Disk Mapping to Read/Write.
Procedure:
On the Policy Management page, find the policy associated with the cloud computer and click Modify Policy in the Actions column.
In the Modify Policy panel, select the Basic Policy tab.
Find Local Disk Mapping and select Read/Write.
Reconnect to the cloud computer.
Phones and tablets
Connecting to phones or tablets
Currently, only Windows cloud computers that use the Adaptive Streaming Protocol (ASP) can connect to and use some models of Android phones and tablets via USB redirection. However, connection stability is not guaranteed, so use this feature with caution. Other models of Android phones and tablets may not work correctly in the cloud computer, even if they are connected via USB redirection and their status is Available. The following Android phone and tablet models are known to be supported:
Xiaomi 6 series
Xiaomi 10 series
Meizu
Huawei nova 6
To ensure that an Android phone or tablet can be recognized and used correctly on a cloud computer, the following conditions must be met:
Android Debug Bridge (ADB) environment variables are configured on both the cloud computer and the on-premises device you use to connect to the cloud computer.
The cloud computer can recognize these Android devices.
Verifying ADB environment variables
Open the Command Prompt app (CMD) on your on-premises device and cloud computer, and run the command adb in the window.
If an ADB version number is returned, the ADB environment variables are configured.
If the command is not recognized, the ADB environment variables are not configured.
If the ADB environment variables are not configured, follow these steps on both the on-premises device and the cloud computer to add them.
In the Start Menu, search for
environment variablesand click Edit the system environment variables in the search results.Add the
ANDROID_HOMEvariable.In the System Properties dialog box, click the Advanced tab, and then click Environment Variables.
In the Environment Variables dialog box, click New under the System variables section.
In the New System Variable dialog box, enter the variable name and value, and then click OK.
The variable name is
ANDROID_HOME, and the variable value is the path to the directory that contains adb.exe, for example,D:\platform-tools.
Modify the
Pathvariable.In the System variables area of the Environment Variables dialog box, find and select the variable named
Path, and click Edit.In the Edit Environment Variable dialog box, click New, enter
%ANDROID_HOME%in the blank row, and then click OK.
Verifying Android device recognition
After you connect an Android device to your on-premises device, open the Command Prompt application (CMD) on the cloud computer and run the adb devices command in the window.
If the returned message only displays
List of device attachedand is followed by nothing, it means that the cloud computer cannot recognize the connected Android device.If the response message displays
List of device attachedand is followed by a serial number, it indicates that the cloud computer can recognize the connected Android device.
ADB device not recognized by cloud computer
Symptom
Your on-premises device recognizes an ADB device, but the cloud computer does not.
Cause
This occurs if the ADB environment variables are not configured on the cloud computer.
Solution
Follow these steps on the cloud computer to add the ADB environment variables.
In the Start Menu, search for the keyword
environment variables, and click Edit the system environment variables in the search results.Add the
ANDROID_HOMEvariable.In the System Properties dialog box, click the Advanced tab, and then click Environment Variables.
In the Environment Variables dialog box, click New under the System variables section.
In the New System Variable dialog box, enter the variable name and value, and then click OK.
The variable name is
ANDROID_HOME, and the variable value is the path to the directory that contains adb.exe, for example,D:\platform-tools.
Modify the
Pathvariable.In the System variables area of the Environment Variables dialog box, find and select the variable named
Path, and click Edit.In the Edit environment variable dialog box, click New, enter
%ANDROID_HOME%in the blank row, and then click OK.
(Optional) Verify that the environment variables are configured correctly. Open Command Prompt (CMD) and run the
adbcommand. If the ADB version number is returned, the environment variables are configured successfully.
Abnormal external mouse behavior on iPad
Symptoms
Pointer style: The mouse pointer in the cloud computer overlaps with the native iPadOS pointer, which appears as a semi-transparent gray circle.
Excel operation issues:
You cannot select multiple columns with the mouse.
After selecting a single column, you cannot select a cell in that column with a single left-click. You must double-click to select it.
Cause
This occurs because the Perform Touch Gestures feature is enabled on the iPad. As a result, the native iPadOS pointer cannot be hidden within the cloud computer, causing the two pointers to overlap. When this feature is enabled, mouse operations are mapped to touch actions. This causes operational issues in Excel and other applications.
Solution
Follow these steps to turn off Perform Touch Gestures.
On your iPad, open the Settings app.
Go to Accessibility > Touch > AssistiveTouch, and then turn off Perform Touch Gestures.