Cloud computer management FAQ

Symptom

A cloud computer's status is stuck on Registering.

Symptom

You cannot select a language when creating a cloud computer, and the system language defaults to Chinese after creation.

Cause

EDS automatically configures the system language based on the selected region.

Solution

Right-click the Windows logo (Start menu) in the lower-left corner of the taskbar, select Run, enter powershell, and then press Enter to open the terminal. Then, run the following two commands in sequence:

 Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Name UseWUServer -Value 0Restart-Service -Name wuauserv 

If Restart-Service -Name wuauserv fails, follow these steps:

1. Run services.msc to open the Services console, locate the Windows Update service, and ensure that its status is "Running".

2. Go to the Windows Start menu > Settings > Language & region > Language. Add the English language pack and set it as the display language.

3. After you complete the settings, run the logoff command in a command window to log off the current session (save all your work and close all applications beforehand). After you log on again, the system language will be switched to English.

Problem description

An end user has local administrator permissions on a Windows cloud computer in a computer pool (formerly desktop group). However, when they try to create a folder in the root directory of the C drive, they receive a Destination Folder Access Denied message.

Cause

By default, cloud computers in a computer pool have a restriction that prevents any user from creating files and folders in the root directory of the C drive.

Solution

Follow these steps to remove the restriction.

1. Log on to the EDS enterprise console.

2. In the navigation pane on the left, choose Resource Management > Shared Cloud Computer.

3. In the top navigation bar, select a region.

4. On the Shared Cloud Computer page, use the computer pool ID (formerly desktop group ID) provided by the end user to find the target computer pool.

5. Click the computer pool ID and then click the Command Execution Details tab.

6. On the Command Execution Details tab, click Send Remote Commands.

7. In the Send Remote Commands panel, select a command type and a cloud computer.

   Note

   For Windows cloud computers, you can select PowerShell or Bat.

8. In the Command Content text box, enter the following command and click Execute to remove the restriction on the root directory of the C drive.

   cmd.exe /c "icacls C:\ /grant CDriveLimited:(AD)"

   If a message similar to the following appears in the Command Output text box, the restriction on the root directory of the C drive has been removed.

   processed file: C:\
   Successfully processed 1 file; Failed processing 0 files

9. The end user can now create files and folders on the C drive.

Verify the result

• Linux operating system

  Connect to the cloud computer and open NVIDIA X Server Settings. In the area on the left, click X Server Information. In the area on the right, check if the NVIDIA Driver Version is 470.161.03. If it is, the GRID driver is upgraded.

• Windows operating system

  Connect to the cloud computer. Right-click a blank area on the desktop and select NVIDIA Control Panel. Check the version. If the version is 474.04, the GRID driver is upgraded.

Problem

When using cloud computers, you may need to share files between computers in the same office network. To do this, you must create a Network Attached Storage (NAS) file system. However, you are unable to select the office network during the creation process.

Cause

• The NAS service is not activated in the NAS console.

• An advanced office network is not created in the destination region.

Solution

1. Log on to the NAS console and check whether the NAS service is activated. If not, follow the on-screen instructions to activate the service.

2. Log on to the EDS enterprise console.

3. In the navigation pane on the left, choose Networks & Storage > Office Network.

4. On the Office Network page, check whether an advanced office network exists. If not, create one. For more information, see Create and manage an office network for convenience accounts.

5. After you complete the preceding steps, create the NAS file system again.

Cause

• An AF_UNIX dependency file required by asp-server was deleted, which prevents the connection. For image versions 1.5.x and 1.6.x, this file is stored in the C:\windows\Temp directory and can be removed by file cleanup tools.

• In image version 1.7.x, the AF_UNIX dependency file is set to have system and hidden attributes. On some Windows systems, this causes access errors for asp-server.

Solution

This issue is fixed in image version 1.8.0. For image versions 1.5.x, 1.6.x, and 1.7.x, use the following method to resolve the issue.

Modify the server configuration file to use a local socket connection. This prevents the connection from being affected if the AF_UNIX file is deleted. Use Cloud Assistant to run the following command:

$server_path = Split-Path -Path (Get-Process -Name aspsvdi).path -Parent
$json_path = $server_path + "\asp-server.json"
$oldLine = '"conn_type": "3",'
$newLine = '"conn_type": "0",'
$content = Get-Content -Path $json_path
$newContent = $content -replace [regex]::Escape($oldLine), $newLine
$newContent | Set-Content -Path $json_path
echo $newContent
taskkill /f /im aspsvdi.exe

Cause

1. If the cloud computer is deployed in the China (Hong Kong) region or other regions outside mainland China, you cannot access it using the default web client domain wuying.aliyun.com. You can only access it through a custom domain name that an administrator has bound to the web client in the console.

2. If the cloud computer is deployed in mainland China, the web client connection is blocked due to policy restrictions, which causes the login to appear disabled.

Solution

1. If the connection to an instance in the China (Hong Kong) region or an overseas region is disabled, bind a custom domain name to the web client. Then, use the Alibaba Cloud Workspace web client to connect to the cloud computer again. For more information, see Bind a custom domain name to the web client.

2. If the connection to an instance in mainland China is disabled, modify the policy of the cloud computer. Under Logon Method Control, select Web Client.

After you bind a custom domain name to the web client, use the Alibaba Cloud Workspace web client to connect to the cloud computer again. For more information, see Bind a custom domain name to the web client.

Cause

The administrator enabled file approval, but the user's client version is earlier than 7.13.

Solution

1. In the upper-right corner of the client, check the client version in the About section. If the version is earlier than 7.13, download the new version .

2. Check the cloud computer version in the desktop details on the client to ensure that it meets the requirements.

3. Ensure that the Ubuntu cloud computer version meets the requirements.

What to do if a Windows cloud computer is stuck starting up, fails, and shows a "Stopped" status?

This issue can have several causes. Troubleshoot your cloud computer using the causes and solutions listed below.

• VPN software causes the startup failure

  Identify the cause:

  Send remote network commands, such as ipconfig /all and route print, to the cloud computer. If you find network adapters other than Red Hat VirtIO, or routes in the routing table that are not related to the Ethernet adapter, the cause is likely VPN software.

  Solution:

  Use the taskkill command to stop the VPN software process. Alternatively, send a remote command to uninstall the VPN software.

• Security software causes the startup failure

  Identify the cause:

  Send the tasklist remote command to the cloud computer to get a list of running processes. Check the list for any processes related to security software.

  Solution:

• Use the taskkill command to stop the security software process. Alternatively, send a remote command to uninstall the security software.

  If the security software has a management console, add the blocked cloud computer processes to the allowlist.

• Insufficient disk space causes the startup failure

  Identify the cause:

  Send the remote command Get-PSDrive C | Select-Object Free to the cloud computer. The output shows that the C drive (system disk) has no free space.

  Solution:

  1. Expand the system disk of the cloud computer in the Elastic Desktop Service console.

  2. Send a remote command to delete unused files from the C drive (system disk).

What to do if a Linux cloud computer is stuck starting up, fails, and shows a Stopped status?

Identify the cause: Send the following remote command to the cloud computer to detect and fix issues.

#!/bin/bash
echo "1. Check hostname"
NAME=$(cat /etc/hostname)
echo "Local hostname: $NAME"
HOSTNAME=$(curl http://100.100.100.200/latest/meta-data/hostname 2>/dev/null)
echo "EDS hostname: $HOSTNAME"
if [ "$NAME" != "$HOSTNAME" ]; then
sudo hostnamectl set-hostname $HOSTNAME
echo "Hostname changed to $HOSTNAME"
else
echo "Hostnames are the same"
fi
echo "2. Check resolv.conf"
Resolv_home=$(cat /etc/resolv.conf | grep "nameserver" | awk '{print $2}')
echo "Resolv points to: $Resolv_home"
realm=$(cat /etc/krb5.conf | grep "default_realm" | awk '{print $3}')
if [[ -z $(cat /etc/hosts | grep $realm) ]]; then
HOSTNAME=$(hostname)
CTRL_REALM=$(cat /etc/krb5.conf | grep "default_realm" | awk '{print $3}')
cat <<- EOF >/etc/hosts
127.0.0.1 $HOSTNAME.$CTRL_REALM $HOSTNAME localhost
$(ifconfig eth0 | grep inet | grep -v inet6 | awk '{print $2}') $HOSTNAME $HOSTNAME
AME
EOF
fi
echo "3. Check DNS_IP"
IP=$(cat  /run/systemd/network/10-netplan-eth0.network  |  grep  'DNS='  |   awk -F= '{print $2}' )
DNS_IP=$(curl http://100.100.100.200/latest/user-data 2>/dev/null | grep  '^DNS_IP=' | cut -d "=" -f 2 | cut -d \" -f 2  |  sed 's/,/ /g')
echo $IP
echo $DNS_IP
if [[ "$IP" != "$DNS_IP" ]]; then
        DNS_IP=$(echo $DNS_IP | tr ' ' ',')
        a=`cat /usr/sbin/edsnetworkinit.sh | grep -A 15 eth0 | grep -A 5 nameservers | grep addresses | cut -d : -f 2 | cut -d [ -f 2 | cut -d ] -f 1`
        sed -i "s/$a/$DNS_IP/g" /usr/sbin/edsnetworkinit.sh

fi
/usr/sbin/edsnetworkinit.sh
echo "4. Check domain name"
NAME=$(cat  /run/systemd/network/10-netplan-eth0.network  |  grep  'Domains='  |   awk -F= '{print $2}' )
DOMAIN_NAME=$(curl http://100.100.100.200/latest/user-data 2>/dev/null | grep  $NAME|  cut -d "=" -f 2  |  cut -d \" -f 2)
echo "Local domain name:$NAME"
echo "EDS domain name:$DOMAIN_NAME"
echo "5. Check permission issues"
for dir in /home/WUYING*
do
    if [ -d "$dir" ]; then
        echo "Found directory: $dir"
        current_owner=$(stat -c '%U' "$dir")
        expected_owner=$(basename "$dir"  | sed 's/_/\\/')
        if [ "$current_owner" != "$expected_owner" ]; then
            echo "Changing owner of $dir from $current_owner to $expected_owner"
            chown -R "$expected_owner" "$dir"
        else
            echo "Owner of $dir is already $expected_owner"
        fi
    fi
done
echo "6. Check if the smb service configuration is modified and if the domain join was successful"
smb_conf="/etc/samba/smb.conf"
krb5_conf="/etc/krb5.conf"
smb_realm=$(cat /etc/samba/smb.conf | grep "^realm" | awk '{print $3}')
krb_realm=$(cat /etc/krb5.conf | grep "default_realm" | awk '{print $3}')
# Check if the smb.conf file contains all specified configuration items
if grep -q "workgroup * = *WUYING" $smb_conf &&
   grep -q "template shell * = */bin/bash" $smb_conf &&
   grep -q "template homedir * = */home/%D_%U" $smb_conf && 
   [ "$smb_realm" = "$krb_realm" ]; then
    echo "Not modified"
else
    echo "Modified"
    # Find the domain join script file that meets the conditions
    sh=$(find /usr/local/share/aliyun-assist/work/script -type f -size +10000c)
    $sh > /dev/null 2>&1
fi
if net ads testjoin | grep -q "Join is OK"; then
    echo "Domain join successful"
else
    echo "Domain join failed"
fi
echo "7. Check for black screen issue, and if the aspserver.so file exists"
if [ -n "$(find /opt -name "libasp-server.so*" 2>/dev/null)" ]; then
    echo "libasp-server.so file exists"
else
    echo "libasp-server.so file does not exist"
fi
echo "8. Check firewall and port 5912 issues"
if [ "$(systemctl is-active firewalld)" = "active" ]; then
    echo "Firewall is active, stopping it..."
    systemctl stop firewalld
    systemctl disable firewalld
else
    echo "Firewall is stopped"
fi
if [ "$(ss -tulpn | grep ':5912')" ]; then
    echo "Port 5912 is open"
else
    echo "Port 5912 is not open, opening it..."
    firewall-cmd --zone=public --add-port=5912/tcp --permanent
    firewall-cmd --reload
    echo "Port 5912 is open"
fi

Solution:

1. Resolve the issues based on the errors reported by the detection script.

2. Restore the cloud computer from a snapshot or rebuild the system disk.

What to do if a Windows cloud computer shows the error "The trust relationship between this workstation and the primary domain failed"?

Identify the cause:

The cloud computer object may have been deleted from the domain controller, or it may have failed the security check on the domain controller.

Solution:

Create a custom image from the cloud computer, and then use this custom image to change the image of the cloud computer. Alternatively, change the image of the cloud computer back to the one that was originally used to create it.