Purchasing Pay-per-Use Desktop Pools

Scenarios

Administrators can select the pay-per-use billing mode and packages to purchase desktop pools.

Purchase Page

1. Logging In to the Workspace Console
2. On the Desktops page, choose Desktop Pools and click Purchase Desktop Pool.

   The page for buying desktop pools is displayed.

   

   When you purchase a desktop pool for the first time, the system prompts you to perform authorization.

   • IMS permissions

     Workspace supports image creation. Therefore, the permission to access IMS is required.

   • Administrator permissions for related cloud services

     Workspace supports scheduled disk recomposing and auto scaling. Therefore, the tenant administrator permissions are required.

   • VPC service permissions

     Workspace allows created networks to run on VPCs. Therefore, the permission to access the VPC service is required.

   After the permission granting is approved, an agency named workspace_admin_trust will be created on IAM. To ensure normal service usage, do not delete or modify the workspace_admin_trust agency when performing scheduled tasks or using the desktop pool. For details, see System Entrustment Description.

Basic Configurations

1. Configure desktop information, as described in Table 1.

   Table 1 Basic Configurations

   Parameter	Description	Example Value
   Billing Mode	Select Pay-per-use.	Pay-per-use
   Region	Desktops in different regions cannot communicate with each other over the intranet, and desktops need to be managed by region. You are advised to create desktops in the same region. NOTE: A region is the location of the physical data center of Workspace. 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.	-
   Project	Select a project as required. NOTE: If no target project is available, click and choose Create Project. The page for creating a project is displayed. Create a project by referring to Creating a Project.	-
   Pool Name	User-defined desktop pool name.	-
   Pool Type	Select Dynamic pool or Static pool. For details about the concepts, see "Related Concepts" in Product Introduction.	-
   AZ	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. NOTE: To achieve better disaster recovery, you are advised to create desktops in different AZs.	General Random
   CPU Architecture	Select x86.	x86
   Package Type	Select specifications as required.	Ultimate Ultimate | 2 vCPUs | 4 GB

2. Configure an image.
   • Image Type: Select an image type as required.
     

     • A public image is a widely used standard image provided by Workspace. It contains an OS and pre-installed public applications and is visible to all users. Public images are very stable and their OS and any included software have been officially authorized for use. If a public image does not contain the application environments or software you need, you can use a public image to create an application environment and then deploy required software. Currently, Windows public images are marketplace images.
     • A private image is created based on an existing cloud desktop or external image file and is visible only to the user who created it. It contains an OS, preinstalled public applications, and the user's personal applications. Using a private image to create a desktop saves more time.
     • The pay-per-use desktop supports public images running Windows, private images converted from desktops generated using Windows images, and private images converted from ECSs created using Windows image files. To use a private image to purchase a desktop, see Converting a Desktop to an Image and Creating a Windows Desktop Private Image.
   • OS: Select a Windows OS type in the supported OS list.

3. Configure disks as required, as shown in Figure 1.
   Figure 1 Configuring disks
   
   

   • For details about the disk type performance, see Elastic Volume Service Product Introduction.
     • High I/O disks use serial attached SCSI (SAS) drives to store data.
     • Ultra-high I/O disks use solid state disk (SSD) drives to store data.
     • General purpose SSD disks use SSD drives to store data.
   • After the desktop is created, you will be billed for the disk until the desktop is deleted.
   • The disk size must be an integer multiple of 10.
   • A maximum of 10 data disks can be configured.

4. Click Next: Configure advanced settings.

   The page for configuring advanced settings is displayed.

Advanced Settings

1. Configure the network, as shown in Figure 2.
   Figure 2 Configuring the network
   

   Click and select a VPC and a subnet.

2. Configure the automatic creation mode of desktop pool autoscaling.
   • Created upon access: When a user accesses the system and no idle desktop is available, the system automatically creates a desktop.

     A maximum of x desktops can be automatically created: The maximum number of desktops that can be automatically created during pool desktop purchase and access is determined by the remaining quota of the user. Set this parameter as required.

   • Pre-create: When the number of idle desktops is lower than the threshold, a specified number of desktops are automatically created.
     • If the number of idle desktops is less than x, the value is the number of idle desktops in the desktop pool.
     • x indicates the number of desktops to be pre-created.
     • A maximum of x desktops can be pre-created.

       For example, if the number of idle desktops is less than 5 and 10 desktops need to be pre-created. A maximum of 10 desktops can be pre-created.

       When the number of idle desktops is less than 5, the system pre-creates 10 desktops. When the number of idle desktops is less than 5 again, the system detects that the number of pre-created desktops reaches the threshold and no more desktops can be created.

   

   Desktops that are automatically created are on-demand desktops.

3. Configure pool desktop unbinding upon 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 4,320 minutes.
     

     The desktop is reset after it is automatically unbound. Save the desktop data in a timely manner to avoid data loss.

4. (Optional) Click Advanced and configure a tag, as shown in Table 2.
   

   • You are advised to use predefined tags from TMS to add the same tag to different cloud resources.
   • A maximum of 10 tags can be added.

   Table 2 Tag naming rules

   Parameter	Rule
   Tag key	The value can contain up to 36 characters. A tag key can contain letters, digits, spaces, and special characters (_.:=+-@), but cannot start or end with a space or start with _sys_.
   Tag value	The value can contain up to 43 characters. A tag value can contain letters, digits, spaces, and special characters (_.:=+-@).

5. Click Next:Assign desktops.

   The page for assigning desktops is displayed.

Assigning Desktops

1. Select the user authorization mode and configure the user to whom a desktop will be assigned.
   

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

   Select a user authorization mode as required, as shown in Table 3.

   Table 3 User Authorization Mode

   User Authorization Mode	Parameter	Operation
   Select User	You can search for activated users using filters.	You can search for a user based on the user type and username.
   Create user > User Activation > Manual Input	User information: Username is used for user authentication during desktop login. Rules for naming a username: The name can contain 1 to 20 characters. A name containing only digits is allowed. The name can contain uppercase letters, lowercase letters, digits, periods (.), hyphens (-), and underscores (_), and must start with a lowercase letter or uppercase letter. The value cannot be empty. Email is used to receive desktop provisioning emails and related notifications. Rules for verifying an email address: Enter a valid email address through system verification. The value can contain a maximum of 55 characters. The value cannot be empty. The mobile number is used to receive desktop provisioning emails and related notifications. Rules for verifying a mobile number: [+][Country/Region code][Mobile number] For a mobile number in the Chinese mainland, you can omit [+][Country/Region code] and directly enter the mobile number. The mobile number can contain spaces, slashes (/), and hyphens (-).	Configure the user information, description, and account expiration settings as prompted. Click Add User. NOTE: Enter the email address or mobile number, or both. Permission groups can be configured in batches. Configure the number of desktops as prompted.
   Create user > Manager Activation > Manual Input	Username is used for user authentication during desktop login. Rules for naming a username: The name can contain 1 to 20 characters. A name containing only digits is allowed. The name can contain uppercase letters, lowercase letters, digits, periods (.), hyphens (-), and underscores (_), and must start with a lowercase letter or uppercase letter. The value cannot be empty. The initial password is authenticated when a user logs in to the desktop. Keep the initial password secure. The password contains 8 to 32 characters. The password must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?) The password cannot be the username or the reverse username. NOTE: If your tenant connects to an AD domain, Manager Activation is unavailable by default.
   Create user > Manager Activation > Batch Import	Upload the users recorded in the table and create them in batches.	Click Download Template on the right of Import user information to download the user list template. Enter the serial number, username, email address, mobile number, expiration time, and description in the table as required. Click Upload to upload the user list that has been filled in as required. Confirm the creation. NOTE: The size of the file to be uploaded cannot exceed 1 MB. A maximum of 200 records can be uploaded at a time. Only .xlsx and .xls files are supported.
   Create user > User Activation > Batch Import	Upload the users recorded in the table and create them in batches.

2. The desktop is being assigned to users.
   • Permission groups are used to distinguish users' permissions on computers.
     • 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. A user in this group cannot modify the OS settings or data of other users, or shut down a server computer.
     • UOS desktop permissions:

3. Select a user group authorization mode and configure a user group to which pool desktops are assigned, as shown in Table 4.

   Table 4 User Group Authorization Mode

   User Group Authorization Mode	Parameter	Operation
   Select User Group	Users can be grouped to simplify user management.	You can find the corresponding user group based on the entered user group name and click OK to add the selected user group name to the list of user groups to which pool desktops are assigned.
   Create User Group	Create a user group to manage pool desktop users. The value can contain letters, digits, periods (.), hyphens (-), and underscores (_). The value cannot be empty. The value can contain a maximum of 64 characters. There are two user group types: Common user group: the user group management system provided by Workspace, which provides batch user management capabilities and is applicable when interconnection with AD user groups is not required. AD user group: user group for interconnecting with the enterprise AD, which is applicable when user permissions are managed using the enterprise AD user group.	1. Enter the user group name. 2. Select a user group type as required. 3. Confirm the creation.

4. Assign a desktop pool to a user group.
   • Permission groups are used to distinguish users' permissions on computers.
     • 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. A user in this group cannot modify the OS settings or data of other users, or shut down a server computer.
     • UOS desktop permissions:

5. Click Next: Confirm the settings.

   The confirmation page is displayed.

Confirming the Settings

1. Select Enterprise Project as needed.
   

   You can use an enterprise project to centrally manage your cloud resources and members by project.

2. After verifying that the information is correct, click Buy Now. After the task is submitted, click Back to Desktop Pool List to check whether the desktop has been created.

   If the creation fails, check the failure cause. For details, see Viewing the Desktop Pool That Fails to Be Created.

   

   The login details for the newly purchased desktop pool will be emailed to the end user. The end user can refer to the email to activate the account, download the client, and configure and use the desktop. Administrators can choose Desktops > Desktop Pools to view the purchased desktop pool.

Follow-up Operations

• The login details for the newly created desktop will be emailed to the end user. The end user can activate the account, download the client, and configure and use the desktop as instructed. Administrators can restrict desktop network interaction as required. For details, see Configuring Workspace to Access the Public Network and Configuring Workspace to Access the Intranet.
• If a Windows AD domain has been connected and an OU has been created on the Windows AD server, create the OU on the console by referring to OU Management.