What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?

Step 1: Upload the Image File

Upload the external image file to an OBS bucket. For details, see Uploading an Image File (Windows).

Step 2 Register the Image File as a Private Image

On the management console, select the uploaded image file and register it as a private image. For details, see Registering an External Image File as a Private Image (Windows).

Step 3: Create an ECS

1. Access the IMS console.
   1. Log in to the management console.
   2. Under Compute, click Image Management Service.

      The IMS console is displayed.

2. Click the Private Images tab.
3. Locate the row that contains the private image and click Apply for Server in the Operation column.
4. Set parameters as promoted to create an ECS. Note that:
   • You are advised to select Pay-per-use for Billing Mode because the ECS will be deleted when you are finished with it.
   • Bind an EIP to the ECS so that you can upload installation packages to the ECS or download them from the ECS.
   • You must add inbound rules for the ECS security groups to ensure that the ECS can be accessed.
   • If the image file has Cloudbase-Init installed, set a password and log in to the ECS using the password when prompted. If Cloudbase-Init is not installed, use the password or certificate contained in the image file to log in the ECS.

   For details, see Purchasing an ECS.

5. Check the ECS to see if the private image used to create the ECS has been pre-configured.
   1. Check whether the ECS can be successfully started. If it can, Guest OS drivers have been installed for the image file on the original platform or the drivers have been automatically installed for the private image on the cloud platform. If the ECS cannot start up, install Guest OS drivers for the image file on the original platform and go back to Step 1: Upload the Image File.
   2. Check whether you can log in to the ECS using your configured password or key. If you can, Cloudbase-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloudbase-Init as instructed in Installing and Configuring Cloudbase-Init.
   3. Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.
   4. Use MSTSC to log in to the ECS. If the login fails, enable remote desktop connection by referring to 3 in Step 4: Configure the ECS.

   If the ECS meets the preceding requirements, the private image has been pre-configured. Skip Step 4: Configure the ECS and Step 5: Create a Private Image from the ECS.

Step 4: Configure the ECS

Remotely log in to the ECS created in Step 3: Create an ECS to configure it.

1. Log in to the ECS.
2. Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.
3. Enable remote desktop connection for the ECS as needed. For details about how to enable this function, see Enabling Remote Desktop Connection.
4. (Optional) Configure value-added functions.
   • Install and configure Cloudbase-Init. For details, see Installing and Configuring Cloudbase-Init.
   • Enable NIC multi-queue. For details, see How Do I Enable NIC Multi-Queue for an Image?
   • Configure an IPv6 address. For details, see How Do I Configure an ECS to Use DHCPv6?

Step 5: Create a Private Image from the ECS

For details, see Creating a System Disk Image from a Windows ECS.

(Optional) Clear the Environment

After the image registration is complete, delete the image file as well as the intermediate private image and ECS to avoid generating any additional charges.

• Delete the image registered in Step 2 Register the Image File as a Private Image.
• Delete the ECS created in Step 3: Create an ECS.
• Delete the image file from the OBS bucket.