After you create a VDI desktop pool, you can deploy desktops in the desktop pool and authorize users and endpoints to use the desktops deployed in the pool. You can access the VDI desktop pool details page by using one of the following methods:
From the left navigation pane, select Desktops. Click the name of a desktop pool in the desktop pool list. This method is used in the following deployment procedure.
From the left navigation pane, select Desktops > Desktop pool group name > Desktop pool name in the desktop pool tree.
From the left navigation pane, select Desktops > Desktop pool group name. Click the name of a desktop pool in the desktop pool list.
Perform this task to deploy desktops depending on the business requirements.
| When bulk deploying desktops running UOS or Kylin operating systems, enable Boot After Deploy, and assign these desktops to users 2 minutes after the deployment is completed. If you fail to do so, login failure occurs when the users perform SSO login. |
From the left navigation pane, select Desktops.
Click the name of the target VDI desktop pool in the desktop pool list.
Click Bulk Deploy.
Configure basic deployment settings, and then click Next.
Configure the network settings, and then click Next.
Verify that the deployment configuration is correct, and then click Finish.
Import File: Deploy multiple desktops in bulk according to the import template. After you download the import template, enter the names of the desktops to be deployed in the desktop name column. The number of desktops to be deployed is the number of desktop names in the import template.
Preview Import Desktop Name: The desktop name in the imported file is both the alias and computer name of the desktop, and the number of desktop names is the number of desktops to be deployed. Do not import a desktop whose name is the same as an existing desktop computer name, as this operation might cause the existing desktop to leave its domain.
VMs to Deploy: Specify the number of VMs to be deployed as desktops. This setting cannot exceed the maximum number of desktops allowed in the desktop pool. As a best practice, deploy only up to three desktops if the pool uses full initialization for desktops. If you deploy desktops by using the import template, you cannot specify this parameter.
Start Desktop ID: Start serial number for desktop names and computer names. Assume the desktop pool name is aa, the desktop prefix is bb, and the start desktop ID is 1. Then, for the first desktop deployed, the desktop name is aa-001 and the computer name is bb001. For the 345th desktop deployed, the desktop name is aa-345 and the computer name is bb345.
Configure: Select a resource flavor for the desktops depending on the required performance. Each flavor represents a set of CPU, memory, and system disk resources for each desktop. You can select the predefined flavor for high, medium, or low performance, or self-define the resources to be provisioned for each desktop.
OU: If the desktop pool is for domain users, specify the DN of the OU for the desktops. When you specify this option, use the ou=value,dc=value,dc=value format. For example, to specify the test OU in the example.com domain, enter the ou=test,dc=example,dc=com string.
Fast Deployment: To accelerate desktop deployment and conserve storage when you deploy desktops based on the base image file, enable this feature. Fast deployment is supported only by static desktop pools, shared desktop pools, and application server pools.
Boot After Deploy: Initialize the desktops immediately after they are deployed.
Protection Mode: To disable user data persistence and store user data as temporary data, enable protection mode. Any changes a user made to a desktop in protection mode are lost when the desktop is restarted from Space Console or shut down from the client.
4K Resolution: To enable 4K display on the desktops, enable this feature. The video memory size of the desktops will be set to 64 MB. If 4K resolution is disabled, the video memory size of the desktops is the same as that of the desktop image.
Bind NUMA Node: To boost desktop CPU performance, enable this feature for the deployed DVI desktops to be automatically bound to the NUMA nodes of the host.
Activation Key: Activation key for the desktop operating system. You must specify the activation key if the desktop image of the desktop pool is Windows XP and the initialization type of the desktop pool is full initialization.
Resource Pool: To deploy GPUs for the desktops, select a GPU resource pool. A GPU resource pool can provide GPU or vGPU resources. To deploy a GPU resource pool, you must also configure a service template, select a driver type, enable or disable the exclusive mode, and set the resource count. ARM hosts do not support GPU.
Service Template: A service template defines the priority of VMs that use the service template to use physical resources and the total ratio of resources that all VMs using the service template can use. You must specify a service template for each VM. To assign a high priority to a VM in using GPU resources, select a service template with a high priority for the VM. UIS Manager allocates GPU resources according to the following rules:
Allocates GPU resources in the VM boot sequence if VMs use service templates with the same priority.
Allocates GPU resources in priority order if idle GPUs are fewer than the VMs to boot.
Reclaims GPU resources from some low-priority VMs and assigns the GPU resources to high-priority VMs when the following conditions are met:
Idle GPUs are fewer than the high-priority VMs to boot.
The VMs that use the same low-priority service template occupy more resources than the resource ratio specified in the service template.
Driver Type: Select a driver type. The current version supports only VFIO.
Exclusive Mode: Select whether the VM can exclusively use the specified GPU/vGPU resources. If you select Yes, the GPU/vGPU resources cannot be used by any other VMs. This feature is available only when the host has available GPU/vGPU resources that have been added to the selected GPU resource pool. To migrate a VM when this feature is enabled, make sure sufficient GPU/vGPU resources are available on the target host and the VM is powered off.
Resource Count: Set the maximum number of GPU/vGPU resources that can be used by the VM. The value depends on the resource pool type and state of the exclusive mode feature:
If you select a vGPU resource pool, only 1 is available.
If you select a GPU resource pool and exclusive mode is disabled, the value is the maximum number of GPUs on a single host in the resource pool. For example, if the resource pool has three hosts, and the hosts have three, two, and two GPUs, respectively, the value is 3.
If you select a GPU resource pool and exclusive mode is enabled, the value is the number of available GPUs on the host attached to the VM.
VNC Console Password: Set the password used to access the VNC console of the VMs to deploy. If you do not set this parameter, access to the VNC console of the VMs does not require a password.
Network: Select the vSwitch and port/port profile for the desktops, and configure their IPv4 and IPv6 network settings and vFirewall settings. IPv6 network parameters are available only if IPv6 address management is enabled for VMs in the system setup.
IP Assignment Mode:
On an IPv4 network, select DHCP for dynamic IP assignment or select static allocation. If you select DHCP, make sure the network has DHCP servers. If you select static allocation, you must manually specify network parameters for the desktops, including an IPv4 address range. The IPv4 address ranges assigned to desktop pools cannot overlap.
On an IPv6 network, select DHCP for dynamic IP assignment or select static allocation for manual assignment. Alternatively, you can select to not set IPv6 address assignment for now. If you select DHCP, make sure the network has DHCPv6 servers for IPv6 address assignment. If you select static allocation, you must manually specify network parameters for the desktops, including an IPv6 address range. The IPv6 address ranges assigned to desktop pools cannot overlap.
vFirewalls: Select a vFirewall for the VMs. With a vFirewall, the inbound and outbound data traffic of the VMs will be filtered based on rules of the vFirewall.
If static IPv4 or IPv6 assignment is used, you can view the IP address ranges that have been assigned to desktops. This list displays only IP assignment records. It is not refreshed when VMs are deleted.
To automatically assign idle desktops to users when they log in to their VDI clients, add their usernames, endpoints, or OUs to the preauthorization list.
If a VDI desktop pool is for endpoint users, authorization is performed on a per-endpoint basis. Users can access the desktops in the VDI desktop pool from preauthorized endpoints, without providing user account information.
If a static or dynamic VDI desktop pool is for local users or domain users, you can select whether to limit the authorization time during user preauthorization. With an authorization expiration date configured, the system will automatically delete the authorization upon authorization expiration.
|
|
From the left navigation pane, select Desktops.
Click the name of the target VDI desktop pool in the desktop pool list, and then click Preauthorize.
Manage users, user groups, and OUs in the preauthorization list:
To add users or endpoints to the preauthorization list:
Click Select Users or Select Endpoints. Select one or multiple users or endpoints, and then click OK.
In a static or dynamic VDI desktop pool, you can select whether to limit the authorization time during user preauthorization. If you select this option, click OK, specify an authorization expiration date, and then click OK again.
To add user groups to the preauthorization list:
Click Select User Groups or Select Endpoint Groups. Select one or multiple user groups or endpoint groups, and then click OK.
To add OUs for domain users to the preauthorization list:
Click Select OU. Select one or multiple OUs, and then click OK.
To remove preauthorized objects from the preauthorization list:
Select one or multiple preauthorized objects, and then click Delete Authorizations. In the dialog box that opens, click OK. The users or endpoints will be unable to access any cloud desktops in the desktop pool.
To recover authorizations:
Click Recover Authorizations. Select deleted preauthorized objects, and then click OK.
This task assigns specific desktops in a static desktop pool to the desired users and endpoints. If a static desktop pool is for local users or domain users, you can select whether to limit the authorization time during user preauthorization. With the authorization expiration settings configured, the system will automatically perform the specified action upon authorization expiration.
|
|
Perform this task to manually authorize a user or endpoint to use a desktop.
From the left navigation pane, select Desktops.
Click the name of the target VDI desktop pool in the desktop pool list.
Click the Desktops tab, and then perform the following tasks:
To authorize a user or endpoint to user a desktop:
In the Authorized User Login Name or Authorized Endpoint column for a desktop, click the Search to Add icon. In the dialog box that opens, select a user or endpoint, and then click OK.
If the desktop pool is a static desktop pool for local users or domain users, you can select whether to limit the authorization time during user preauthorization. If you select this option, click OK, specify an authorization expiration date and an action to take upon authorization expiration, and then click OK again.
To delete user authorizations:
To delete a single user authorization, in the Authorized User Login Name column for a desktop, click the icon for a user. In the dialog box that opens, click OK.
To delete user authorizations in bulk, select one or multiple desktops, click More on top of the desktop list, and then select Delete Authorizations. In the dialog box that opens, click OK.
To recover user authorizations for a desktop:
Click More in the Actions column for a desktop, and then select Recover Authorizations. Select deleted authorization objects, and then click OK.