Purchasing a Desktop Pool

The billing mode is related to the payment method, billing cycle, and resource status changes of your desktop. Select a billing mode based on your service requirements.

A region is the location of the physical data center of a desktop. Different regions indicate different physical distances between the physical data center and users, as well as different network latency. To reduce latency and improve access speed, select the region closest to your workloads.

• Desktops in different regions cannot communicate with each other over the intranet and need to be managed by region. Create your desktops in the same region.
• Once a desktop is purchased, its region cannot be changed. Exercise caution when selecting a region.

A project corresponds to a region. Projects group and isolate compute, storage, and networking resources across physical regions. Users can be granted permissions in a default project to access all resources in the region associated with the project. For more refined access control, create subprojects under a project and purchase resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.

The desktop name can contain 1 to 64 characters. Only uppercase letters, lowercase letters, digits, and hyphens (-) are allowed.

A desktop pool is a collection of desktops with the same specifications and image. It allows administrators to centrally manage and maintain a group of desktops in a project. Desktop pools are classified into dynamic pools and static pools.

• A dynamic pool is an M:N-type desktop group in which the binding between a VM and a user is not fixed. Each time a user logs in to the desktop pool through a client, Workspace automatically assigns an available VM to that user.
• A static pool is a 1:1-type desktop group. Initially, the binding between VMs in the pool and VM users is not fixed. After a user logs in to a VM in the pool for the first time, that VM becomes permanently bound to the user. From that point on, the user will always be assigned the same VM when accessing the desktop pool, and that VM will no longer be assigned to any other users.

An AZ is a physical region where resources use independent power supplies and networks. AZs are physically isolated but connected through an intranet. If an AZ becomes faulty, other AZs in the same region will not be affected.

Select the required CPU architecture as needed. For example, select Kunpeng for UOS desktops and x86 for Windows desktops.

1. Select Encryption to go to the encryption page.
2. Select the Select existing key option.
   1. Select the required key from the Key Name drop-down list.
   2. Click OK.
3. Select the Enter key ID option.
   1. Enter a key ID in the text box.

      You can view the key ID in the key list.

   2. Click OK.

A KMS key can be custom, default, or shared.

• Shared keys: You can use DEW to create grants that allow other accounts to share your keys. For details, see Creating a Grant for a Custom Key.
• Custom keys: You can select an existing key or create a key. For details about how to create a custom key, see Creating a Custom Key.
• Key sharing via resources: You can use Resource Access Manager (RAM) to share your keys with other accounts via resource sharing. For details, see Sharing Your Resources.
  

  • When you use KMS to encrypt disks, the system automatically grants the key to the Workspace service account for creating and using encrypted disks for Workspace.
  • You are advised not to remove the related authorization (grant_to_workspace_xxx). Otherwise, the desktop functions encrypted by the key will be affected. For example, if the authorization is removed, the desktop cannot be started properly.

A Virtual Private Cloud (VPC) is an isolated, configurable, and manageable virtual network environment for cloud desktops. You can customize VPCs, subnets, and security groups. Desktops in different VPCs cannot communicate with each other by default.

• Check whether the security group in use includes the inbound and outbound rules required by desktop access. If not, desktop access and use will be affected.

  For details, see How Do I Configure Security Group Rules When Using a Custom Security Group?

• The 172 network segment is reserved for running internal services. Therefore, do not select a VPC network starting with 172. Otherwise, desktops cannot be purchased.
• If you want to use the shared VPC and subnet from another account, accept the resource sharing invitation first. For details, see Responding to a Resource Sharing Invitation.

  For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide.

If the scaling policy is disabled, the number of desktops in the desktop pool is fixed to the initial purchase quantity.

• Table 5 describes the scaling policy of the desktop pool.

  Table 5 Scaling policy

  Pool Type	Method	Scale-Out Policy	Scale-In Policy	Auto Fault Isolation	Binding Retention Duration upon Disconnection
  Dynamic pool	Dynamic scaling	Minimum Desktops: Minimum number of desktops reserved in a desktop pool. If the total number of desktops exceeds this value and idle desktops outnumber reserved idle desktops, the excess idle desktops will be automatically deleted. If the total number of desktops falls below this value, desktops will be automatically created to reach this value. Reserved Idle Desktops: To improve user access efficiency, some idle desktops (those not assigned to users) can be reserved in a desktop pool. If the number of idle desktops in the current desktop pool does not reach the maximum number of auto-created desktops, desktops will be automatically created to reach the value of reserved idle desktops. Maximum Auto-Created Desktops: Set this limit to prevent excessive, unnecessary costs from continuous auto-creation in a desktop pool. NOTE: Desktops that are automatically created are on-demand desktops. You can set the minimum number of desktops only when they are billed on a pay-per-use basis.	Unassigned Desktop Retention Duration: For the yearly/monthly billing: Excess auto-created desktops that are not assigned to users in a desktop pool can be retained for a configured duration before being automatically deleted. Manually created yearly/monthly desktops will not be deleted automatically. The number of excess unassigned auto-created desktops is calculated by subtracting the reserved idle desktops from the total unassigned desktops in the pool, considering only those that were automatically created. The value ranges from 0 to 43,200 minutes. For the pay-per-use billing: Excess unassigned desktops in a desktop pool can be retained for a configured duration before being automatically deleted. The number of excess unassigned desktops represents the smaller of two values: the total number of desktops minus the number of minimally required desktops in the pool, and the number of unassigned desktops minus the number of reserved idle desktops. The value ranges from 0 to 43,200 minutes.	Automatically Isolate Unreachable Desktops: When you enable this function, the system will automatically isolate unassigned desktops that are faulty or cannot be connected. Max Isolated Desktops: specifies the maximum number of isolated desktops. The value ranges from 1 to 1,000. NOTE: Isolated desktops will not be assigned to any users. Desktops provisioned through auto scale-out are not included in idle-desktop or maximum-desktop calculations. Isolated desktops that are eligible for the scale-in policy will be deleted first. Isolated yearly/monthly desktops must be manually unsubscribed if needed. Normal desktops will be automatically removed from isolation.	After a client user disconnects from a desktop, the desktop can be retained for a period of time. After the retention period expires, the desktop is automatically unbound from the user and reset. The value ranges from 10 to 43,200 minutes. NOTE: After the retention duration expires, the desktops will be unbound and reset. Save the desktop data in a timely manner to prevent data loss.
  	Creation upon access	Maximum Auto-Created Desktops: Set this limit to prevent excessive, unnecessary costs from continuous auto-creation in a desktop pool.
  Static pool	Dynamic scaling	Reserved Idle Desktops: To improve user access efficiency, some idle desktops (those not assigned to users) can be reserved in a desktop pool. If the number of idle desktops in the current desktop pool does not reach the maximum number of auto-created desktops, desktops will be automatically created to reach the value of reserved idle desktops. Maximum Auto-Created Desktops: Set this limit to prevent excessive, unnecessary costs from continuous auto-creation in a desktop pool. NOTE: Desktops that are automatically created are on-demand desktops.	Not supported	Not supported	Not supported
  	Creation upon access	Maximum Auto-Created Desktops: Set this limit to prevent excessive, unnecessary costs from continuous auto-creation in a desktop pool.

• Configure the retention duration upon pool desktop disconnection.
  • Disconnection and unbinding: After a client user disconnects from a desktop, the desktop can be retained for a period of time. After the retention period expires, the desktop is automatically unbound from the user and reset.
  • The retention duration upon disconnection ranges from 10 to 43,200 minutes.
    

    • The desktop is reset after it is automatically unbound. Save any required data in advance to prevent data loss.
    • This function is supported only when Pool Type is set to Dynamic Pool.

If an existing AD domain is used, you need to create users on the AD server before assigning desktops.

When creating users, you can set a user or batch import users. For details, see Table 7.

• Windows desktop permissions:
  • Administrator group: Users in this group have system administrator permissions, that is, full permissions on a computer. They can perform all management tasks, including managing all users, on the computer.
  • Common user group: Users in this group have basic operation permissions on a computer, for example, running applications. They are not allowed to modify the OS settings or data of other users, or shut down a server computer.

• Windows desktop permissions:
  • Administrator group: Users in this group have system administrator permissions, that is, full permissions on a computer. They can perform all management tasks, including managing all users, on the computer.
  • Common user group: Users in this group have basic operation permissions on a computer, for example, running applications. They are not allowed to modify the OS settings or data of other users, or shut down a server computer.

• UOS desktop permissions:
  • Administrator group: Users in this group can run the sudo and su commands to switch to the root user as well as change the root user password.
  • Common user group: Users in this group have basic operation permissions on a computer, for example, running applications. A user in this group cannot modify the OS settings or data of other users.