All Products
Search
Document Center

Elastic Desktop Service:Import an image

Last Updated:Feb 28, 2026

Elastic Desktop Service (EDS) Enterprise supports custom images for creating cloud computers. If the built-in images do not meet your requirements, create a custom image in a virtual machine (VM), upload it to Object Storage Service (OSS), and then import it through the EDS Enterprise console. This topic uses a Windows image as an example.

The import workflow consists of six steps:

  1. Create a VM in VirtualBox

  2. Install Windows on the VM

  3. Configure the system (Cloud Assistant Agent, UAC, firewall)

  4. Export the image from VirtualBox

  5. Upload the image to OSS

  6. Import the image in the EDS Enterprise console

Prerequisites

Before you begin, make sure that you have:

Install the following software on your local machine:

SoftwarePurposeDownload
VirtualBoxCreate and manage the VMVirtualBox downloads
ossbrowserUpload the image to OSSInstall ossbrowser 1.0

Prepare a Windows ISO image downloaded from the Microsoft official website. Do not use a Windows Home edition ISO.

Limits and requirements

Supported image formats

FormatSupportedNotes
RAWYes--
VHDYesRecommended when creating the VM in VirtualBox
QCOW2Yes--
ISONoUse to install Windows on the VM, then export in a supported format
VDINoConvert to a supported format before import. See Convert the format of an image
Important

Images cannot be compressed. Upload the image file in its original, uncompressed format.

Supported operating systems

The console supports importing both Windows and Linux images. This topic describes the process for importing a Windows image.

OS editionSupported
Windows ProYes
Windows EnterpriseYes
Windows HomeNo

The following Windows versions are not supported:

  • Windows XP

  • Windows 7

  • Windows 8

  • Windows 8.1

Boot mode

Only Basic Input/Output System (BIOS) boot mode is supported. Unified Extensible Firmware Interface (UEFI) boot mode is not supported.

System disk requirements

  • The system disk must have only the boot partition (drive C). Delete all other partitions, including the recovery partition, before export.

  • Valid system disk size: 5 to 500 GiB. The value must be greater than the size of the image file.

  • Recommended disk capacity in VirtualBox: 40 GB. Resize the disk later in the EDS Enterprise console if needed.

Image name constraints

The image name must be 2 to 128 characters and can contain letters, digits, colons (:), periods (.), underscores (_), and hyphens (-). It must start with a letter and cannot start with http:// or https://.

Security notice

Alibaba Cloud does not guarantee the security of custom images. Make sure that imported images are safe and free of malware before use.

Procedure

Step 1: Create a VM

This example uses VirtualBox 7.0.4. Steps may vary depending on the version.

  1. Launch VirtualBox.

  2. In the upper-right corner, click New.

  3. Click Name and Operating System, enter a name for the VM, and then select an operating system and version.

  4. Click Hardware and specify the memory size and number of vCPUs.

    Important

    - The memory size and number of vCPUs are irrelevant to the specifications of the cloud computer created from this image. - Do not select Enable EFI. EDS Enterprise does not support EFI boot mode.

  5. Click Hard Disk, select the file location, and then configure the disk capacity and disk type.

    - Set the disk capacity to 40 GB. Resize the disk later in the EDS Enterprise console if needed. - Only RAW, VHD, and QCOW2 images can be imported. Select VHD for the Hard Disk File Type and Variant parameter to avoid format conversion later.
  6. Confirm the VM details and click Finish.

Step 2: Install Windows on the VM

Important

Do not install the operating system in UEFI mode. Use BIOS mode.

  1. Launch VirtualBox.

  2. Select the VM and click Start.

  3. Install Windows and complete the setup wizard.

  4. Delete the recovery partition. To delete the recovery partition:

    1. Open DiskPart by entering diskpart in the search box or by running the diskpart command in Windows PowerShell.

    2. Run list disk to view available disks.

    3. Run select disk <disk number> to select the target disk. For example: select disk 0.

    4. Run list volume to view the disk partitions.

      • If a recovery partition is listed: If deletion fails, use a disk tool to format the disk and then delete the partition.

        1. Run select volume <partition number> to select it. For example: select volume 1.

        2. Run delete part override to delete the partition.

      • If no recovery partition is listed, skip this step.

    Warning

    The system disk must have only the boot partition (drive C). If additional partitions exist, the cloud computer created from this image cannot start, and the disk cannot be resized.

Step 3: Configure the system

  1. Install Cloud Assistant Agent Download and install the Cloud Assistant Agent.

    Important

    - After installation, start the agent. Verify that the AliyunService process is in the Running state in Task Manager. - If Aliyun Assist Service fails to start, restart the VM and check the service status again. - For certain Windows versions, Aliyun Assist Service may not start automatically. In this case, save the shortcut of Aliyun Assist Service to the Windows startup folder: - Cloud Assistant path: C:\ProgramData\aliyun\assist\<version>\aliyun_assist_service.exe - Windows startup folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

  2. Disable User Account Control (UAC) Open Windows PowerShell and run:

       reg.exe add HKLM\Software\MicroSoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f
  3. Disable the Windows firewall Run the following command:

       netsh advfirewall set allprofiles state off

Step 4: Export the image

Locate the image file in the Folder path that was specified when the VM was created.

If the VM was moved to a different path after creation, use the actual current path.

Step 5: Upload the image to OSS

Get the OSS bucket address

  1. Log on to the Elastic Desktop Service Enterprise console.

  2. In the left-side navigation pane, choose Images Center > Images.

  3. On the Images page, click Create Image.

  4. In the Create Image panel, click the Import Image tab.

  5. In the OSS Bucket Address section, click Obtain to get the bucket address, and then click Copy.

Upload the image using ossbrowser

  1. Open ossbrowser and log on with the following settings:

    Important

    The AccessKey pair must belong to the same Alibaba Cloud account or Resource Access Management (RAM) user that is used to log on to the EDS Enterprise console. - Alibaba Cloud account login: Use the AccessKey pair of the Alibaba Cloud account. - RAM user login: Use the AccessKey pair of the RAM user.

    FieldValue
    EndpointDefault (Public Cloud)
    AccessKeyIdAccessKey ID of the Alibaba Cloud account or RAM user used to log on to the EDS Enterprise console
    AccessKeySecretCorresponding AccessKey secret
    Preset OSS PathThe OSS bucket address obtained from the EDS Enterprise console
    RegionThe region of the OSS bucket
  2. Upload the image file to the bucket.

    Important

    Only RAW, VHD, and QCOW2 formats are accepted. Images cannot be compressed. If the image is in a different format, convert it first. For more information, see Convert the format of an image.

  3. After the upload completes, find the image in ossbrowser and click Address in the Actions column to copy the OSS object address.

Step 6: Import the image

  1. Log on to the Elastic Desktop Service Enterprise console.

  2. In the left-side navigation pane, choose Images Center > Images.

  3. In the upper-left corner of the top navigation bar, select a region.

  4. On the Images page, click Create Image.

  5. In the Create Image panel, click the Import Image tab.

  6. Configure the following parameters:

    ParameterDescription
    Image NameA name for the image. The name must be 2 to 128 characters and can contain letters, digits, colons (:), periods (.), underscores (_), and hyphens (-). It must start with a letter and cannot start with http:// or https://.
    RegionThe region of the OSS bucket to which the image was uploaded.
    OSS Object AddressThe OSS object address obtained in the previous step.
    OSThe operating system of the image. Select windows or linux.
    System Disk SizeThe size of the system disk. Must be greater than the image size. Valid values: 5 to 500 GiB.
    GPU DriverSelect Yes to use this image for GPU-accelerated cloud computers of the Enterprise Graphics type.
    Protocol TypeThe protocol type of the image. Use the default value.
    License TypeBring Your Own License (BYOL): Use your own license.
    DescriptionA description of the image.
  7. Click OK.

After the import completes, the image appears on the Custom Image tab of the Images page.

Next steps

After importing an image, create a cloud computer template that uses the image, and then create cloud computers from the template.

FAQ

"AccessDenied: the bucket you access does not belong to you" error in ossbrowser

This error occurs when the AccessKey pair used to log on to ossbrowser does not match the account used to log on to the EDS Enterprise console.

To fix this, use the AccessKey pair from the same account:

  • If logged on to the EDS Enterprise console with an Alibaba Cloud account, use the AccessKey pair of that Alibaba Cloud account.

  • If logged on as a RAM user, use the AccessKey pair of that RAM user.

Using the AccessKey pair of an Alibaba Cloud account is a high-risk operation. Use a RAM user with the AliyunECDFullAccess policy instead. For more information, see Attach EDS Enterprise system policies to a RAM user.

Why is the system disk only 40 GiB after I set it to 100 GiB during import?

The recovery partition was not deleted before the image was exported. The system disk must have only the boot partition (drive C). If other partitions exist, the disk cannot be resized.

Do not use a disk partitioning tool to manually allocate disk space in the cloud computer. Doing so makes the cloud computer completely unavailable.