:You can use the Windows public image to create non-I /O optimized instance and cannot identify the network interface controller

Problem description

With the new version of the Windows common image to create non-I /O-optimized instance, after the system has started up alone cannot identify the individual network interface controller drive, resulting in the network is disconnected, it is not possible to separate the code that remote connections

Cause

The new version of the image is installed by default for KVM drivers, Xen virtualization Xen driving pack support, but the new version image by default are not integrated, led to the creation of the network interface controller alone cannot identify the individual that uses the get-netadapter command won't be able to see network interface controller drive.

Solution

Alibaba Cloud reminds you that:

• Before you perform operations that may cause risks, such as modifying instance configurations or data, we recommend that you check the disaster recovery and fault tolerance capabilities of the instances to ensure data security.
• You can modify the configurations and data of instances including but not limited to Elastic Compute Service (ECS) and Relational Database Service (RDS) instances. Before the modification, we recommend that you create snapshots or enable RDS log backup.
• If you have authorized or submitted sensitive information such as the logon account and password in the Alibaba Cloud Management Console, we recommend that you modify such information in a timely manner.

We recommend that you replace the image with a public image that supports Xen drivers. Currently, you can only replace the following public images with Windows Server Images. You can only call the ReplaceSystemDisk operation to create public images. For more information, see replace public images.

Application scope

• Elastic Compute Service