This topic provides answers to some frequently asked questions (FAQ) about managing cloud computers in Elastic Desktop Service (EDS) as administrators.
Table of contents
Category | FAQ |
Creation and deployment | |
Users and assignment | |
Query and management | |
Storage and networking | |
Application and peripheral | |
Extension and others |
Creation and deployment
What do I do if cloud computers fail to be created?
Problem description
A cloud computer fails to be created in the EDC console.
Cause
If a large number of users attempt to create cloud computers in the EDC console at the same time, a queuing mechanism is triggered. If the cloud computer is not created within 1 hour, an error message indicating that the creation fails is displayed in the EDC console.
Solution
Release the failed cloud computer and try again. If you do not release the failed cloud computer within seven days, EDC automatically reclaims the cloud computer. You are not charged for the failed cloud computer.
What do I do if a cloud computer remains in the Registering state?
Problem description
A cloud computer remains in the Registering state.
Solution
Stop the cloud computer and create another one. For more information, see Create cloud computers.
Stop the cloud computer and use a snapshot to restore the cloud computer. For more information, see Use snapshots (public preview).
Can I migrate a cloud computer from the China (Hangzhou) region to the China (Beijing) region?
No, you cannot migrate a cloud computer from the China (Hangzhou) region to the China (Beijing) region. You cannot migrate cloud computers across regions.
How do I quickly copy a cloud computer?
To quickly copy a cloud computer, perform the following steps:
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Cloud Computers page, find the cloud computer that you want to copy, click the ⋮ icon in the Actions column, and then click Create Image to create an image of the cloud computer. For more information, see Create an image.
After you create the image, create a cloud computer template based on the image. For more information, see Custom cloud computer templates.
After you create the cloud computer template, use the template to create a cloud computer. In this case, the new cloud computer is the same as the source cloud computer. For more information about specific operations, see Create cloud computers.
Users and assignment
Why is the user list empty when I create a cloud computer?
If no user is displayed when you create a cloud computer, you have not created any user. You can create users based on the user account type. For more information, see Create a convenience user or Create and manage enterprise AD accounts.
Can I assign a cloud computer to multiple end users?
Yes, you can assign a cloud computer to multiple end users. However, only one end user can connect to the cloud computer at a time. For more information, see Assign cloud computers to users.
What do I do if no cloud computer is displayed on the EDC client of an end user?
If no cloud computer is displayed when an end user logs on to an EDC client, perform the following steps to check whether you have assigned a cloud computer to the end user:
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
Select Username from the search drop-down list, enter the username of the end user, and then press the Enter key.
If a cloud computer is assigned to the end user but no cloud computer is displayed, check whether the ID of the office network (formerly known as workspace) or organization in which the cloud computer resides is correct when the end user logs on to an EDC client.
If no cloud computer is assigned to the end user, assign one. For more information, see Assign cloud computers to users.
What do I do if an end user cannot create folders or files in the root directory of the C drive on a cloud computer?
Problem description
An end user that is granted the local administrator permissions wants to create a folder in the root directory of the C drive on a Windows cloud computer in a shared cloud computer pool (formerly known as desktop group). However, an error message indicating that the access to the folder is rejected appears.
Cause
By default, the system prohibits end users to create files or folders in the root directory of the C drive on cloud computers in a shared cloud computer pool.
Solution
Perform the following steps to remove the restriction:
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Cloud Computer Pools page, find the cloud computer pool (formerly known as desktop group) based on the pool ID provided by the end user.
Click the pool ID. On the page that appears, click the Command Execution Details tab.
On the Command Execution Details tab, click Send Remote Commands.
In the Send Remote Commands dialog box, configure the Command Type and Select Cloud Computer parameters.
NoteFor Windows cloud computers, you can set the Command Type parameter to PowerShell or Bat.
Enter the following command in the Command Content editor and click Execute to remove the access restriction on the root directory of the C drive on the cloud computer.
cmd.exe /c "icacls C:\ /grant CDriveLimited:(AD)"Check whether the end user can create files or folders in the root directory of the C drive.
Query and management
How do I restart a cloud computer by running a remote command?
When an end user connects to a Windows cloud computer, the end user may encounter exceptions such as keyboard failures. The following error codes and error messages may appear: 22, 5100, 5102, 5202, ConnectTicket.Timeout, and UnavailableDesktop.ConnectionBroken. To handle these issues, you must run a remote command to restart EDC.
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Cloud Computers page, find the cloud computer that is in the Running state, click the ⋮ icon in the Actions column, and then click Send Remote Commands.
On the Send Remote Commands page, set the Command Type parameter to PowerShell.
In the Command Content editor, enter the following command to restart EDC and click Execute.
taskkill /im spmonitor.exe -f | taskkill /im aspsvdi.exe -f | taskkill /im edsagent.exe -fWait for the command execution to complete. If the following output is returned, EDC is restarted.
Success: Terminated process "aspsvdi.exe" with PID 4164.
In this example, a Windows cloud computer is used. The actual business scenario shall prevail. For more information about remote commands, see Send remote commands.
How do I upgrade the GRID driver of an Enterprise Graphics cloud computer?
Usage notes
Before you upgrade the GRID driver of an Enterprise Graphics cloud computer, make sure that the available space of the system disk on the cloud computer is at least 4 GiB.
You must create a snapshot of the system disk for the cloud computer before you upgrade the GRID driver. If the upgrade fails, you can use the snapshot to restore the data on the system disk. For more information, see Use snapshots (public preview).
Procedure
Windows cloud computers for administrators
To upgrade the GRID driver of a Windows cloud computer, you need to only update the image of the cloud computer to V1.8.0 or later. Perform the following steps to update the image of a cloud computer:
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose . On the Images page, click the Image Updates tab.
In the upper-left corner of the top navigation bar, select a region.
On the Image Updates page, find the image version that is used by the cloud computer and click Query Involved Cloud Computer and Update Progress in the Actions column.
In the Query Involved Cloud Computer and Update Progress panel, perform one of the following operations based on your business requirements:
Single cloud computer: Find the cloud computer whose image you want to update and click Update in the Actions column. You can update the image now or schedule an update.
Multiple cloud computers: Select multiple cloud computers whose images you want to update, click Immediate/Schedule Update in the lower part of the panel, and then proceed as prompted.
For more information, see Update an image.
Windows cloud computer for end users
To upgrade the GRID driver of a Windows cloud computer, you need to only update the image of the cloud computer to V1.8.0 or later. Perform the following steps to update the image of a cloud computer:
Make sure that you have saved files on the cloud computer before you update it.
An update takes 10 to 15 minutes to complete, during which the cloud computer is unavailable.
Find the cloud computer that you want to update and click Update on its card.
In the dialog box that appears, click Update Now.
You can also specify the time to schedule the update.
In the message that appears, click Confirm Update.
In the Updated dialog box that appears, click Got it.
If you cannot connect to the cloud computer or want to roll back the cloud computer after the update, perform the following operations: click Manage on the card, choose , click the snapshot of the system disk or data disk that is created at a point in time to which you want to restore the cloud computer, and then click Confirm Restore. You can also contact your enterprise IT administrator for help.
If you fail to update the cloud computer, retry or contact your enterprise IT administrator.
Linux cloud computers for administrators
To upgrade the GRID driver of a Linux cloud computer, you need to only send a remote command.
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Cloud Computers page, find the cloud computer whose image you want to update and restart the cloud computer.
Use one of the following methods to open the Send Remote Commands dialog box.
Click the ID of the cloud computer. On the page that appears, click the Command Execution Details tab. Then, click Send Remote Commands.
Click the ⋮ icon in the Actions column and then click Send Remote Commands.
In the Command Content editor, run the following command to upgrade the GRID driver:
ImportantBefore you run the command, make sure that the cloud computer is disconnected.
Approximately 2 minutes are required to run the command.
if acs-plugin-manager --list --local | grep grid_driver_install > /dev/null 2>&1 then acs-plugin-manager --remove --plugin grid_driver_install fi acs-plugin-manager --exec --plugin grid_driver_installIf Succeeded is returned in the output or appears on the Command Execution Details tab, the command is run.
Restart the cloud computer.
Results
Linux
Connect to the cloud computer, open NVIDIA X Server Setting, click X Server Information in the left-side section, and then find the NVIDIA Driver Version parameter. If the version is
470.161.03, the GRID driver is upgraded.Windows
Connect to the cloud computer, right-click a blank area on the desktop, and then select NVIDIA Control Panel to view the GPU driver version. If the version is
474.04, the GRID driver is upgraded.
If the upgrade fails, submit a ticket to contact technical support.
Storage and networking
What do I do if the capacity of a disk remains unchanged after I resize the disk?
If the free capacity of a disk is insufficient, you can resize the disk based on your business requirements. If the disk capacity remains unchanged after the resizing, you must increase the capacity of disk partitions. For more information, see Scale up the partition of a data disk.
Why am I unable to select an office network when I create a File Storage NAS file system?
Problem description
By default, you cannot share files across cloud computers in an office network in EDC. If you want to share files across cloud computers, you must create a NAS file system. However, you cannot select an office network when you create the file system.
Cause
NAS is not activated.
An advanced office network is not created in the destination region.
Solution
Log on to the NAS console and check whether NAS is activated. If NAS is not activated, activate NAS as prompted.
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
On the Office Network page, check whether an advanced office network is created. If no advanced office network is created, create one. For more information, see Create and manage a convenience office network.
After you perform the preceding steps, create a NAS file system again. For more information, see Mount a NAS file system on a Windows cloud computer.
What do I do If the "The charge type of network package in office site is not allowed to delete" error message appears when I delete an office network?
Problem description
If you no longer use an office network, you can delete it after you release its cloud computers. However, the The charge type of network package in office site is not allowed to delete error message appears when you delete it.
Cause
The office network is associated with a subscription premium bandwidth plan.
Solution
Perform the following steps to resolve the issue:
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Premium Bandwidth Plan page, find the premium bandwidth plan and click Disassociate Office Network in the Actions column.
In the Confirm Office Network Disassociation message, click Confirm.
If the plan changes to the Not Associated state, the plan is disassociated from the office network.
Delete the office network again. For more information, see Create and manage a convenience office network.
Application and peripheral
What do I do if an end user is prompted to enter the administrator password when the end user installs applications on a cloud computer?
When an end user attempts to install applications on a cloud computer, a dialog box indicating that the end user must enter the username and password of the local administrator appears. This issue occurs because the account that is used by the end user does not have the local administrator permissions. In this case, you must grant the permissions. You can grant the permissions on one of the pages in the console:
Manage User page
Log on to the EDS Enterprise console.
In the left-side navigation pane, choose .
On the User tab of the Users & Organizations page, find the username of the account and choose one of the following methods to grant the required permissions:
Click the
icon in the Local Administrator column that corresponds to the end user. In the Configure Local Administrator dialog box, select Yes for the Local Administrator parameter and click Confirm. Select the check box of the username in the first column, choose , select Yes in the dialog box that appears, and then click Confirm.
Restart the cloud computer.
Cloud Computers page
In the left-side navigation pane, choose .
In the upper-left corner of the top navigation bar, select a region.
On the Cloud Computers page, find the cloud computer that you want to manage, click the ⋮ icon in the Actions column, and then click Send Remote Commands.
Run the following command based on the operating system of the cloud computer.
Windows cloud computer
Set the Command Type parameter to PowerShell and run the following command:
net localgroup administrators "Username" /addLinux cloud computer
Set the Command Type parameter to Shell and run the following command:
#!/bin/bash echo "ecd\\\Username ALL=(ALL) NOPASSWD:ALL #SET_BY_EDS" >> /etc/sudoersNoteReplace
Usernamewith the username used by the end user.After the end user logs on to the cloud computer, open Command Prompt. The end user can launch Run Command window by pressing the
Windows+Rshortcut keys and runningcmd. Then, the end user needs to run thewhoamicommand. The returned string is the value ofUsername.If the end user is still prompted to enter the administrator password on the Linux cloud computer after running the preceding command, the end user can perform the following steps: run the
sudo sucommand to switch to the root user, runpassword rootto modify the password, and then install applications.
Restart the cloud computer.
How do I configure automatic installation for a self-managed application?
If a self-managed application supports silent installation, the application can be automatically installed.
To configure automatic installation, click the Auto Installation in the Actions column and proceed as prompted. For more information, see Assign and install an application.
If an application does not support silent installation, you can submit a ticket to contact technical support.
What do I do if a USB device that is connected to an on-premises terminal cannot be used on a cloud computer?
You can perform the following steps to resolve the issue:
If an end user uses a Windows cloud computer, drivers cannot be installed in the temp directory. If drivers are installed in the directory, the drivers are automatically removed the next time the end user starts the cloud computer. As a result, USB devices become unavailable.
Check whether USB redirection is enabled. For more information, see Peripheral control.
If the end user wants to use the USB printer or webcam that is connected to the on-premises device on the cloud computer, check whether printer redirection and webcam redirection are enabled. For more information, see Create a basic policy.
If the end user uses UKey devices, check whether the required drivers are installed.
Contact the end user to perform the following steps to check whether the USB device blacklist and whitelist are configured on the cloud computer:
Procedure: In the upper-right corner of the card display page of cloud computers on the EDC client, click the
icon, choose , and then configure the blacklist and whitelist based on your business requirements.
Extension and others
How do I handle API call errors on cloud computers?
If an API call error occurs, you can view the error details on the OpenAPI problem diagnosis page based on the returned request ID.
API request links involve request construction, call request transmission, and request processing of customers. If errors occur during API calling, we recommend that you provide exception handling logic based on your business requirements.