H3C Workspace Cloud Desktop
Shared Desktop Pool Configuration Examples

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W101-20230915

 

Contents

About configuring shared desktop pool 1

Prerequisites· 1

Restrictions and guidelines· 1

Example: Configuring a shared desktop pool 2

Network requirements· 2

Analysis· 2

Procedures· 3

Synchronizing the Space Console with the domain controller 3

Uploading a system image· 4

Creating a desktop image· 4

Creating a shared desktop pool 32

Deploying desktops· 35

Authorizing a user 38

Verifying the configuration· 39

Related documentation· 43

 

About configuring shared desktop pool

Based on the Windows server system, the shared desktop pool supports multi-user login, and a desktop can be created and used concurrently by multiple users. When users only need a desktop for simple operations or basic applications, there is no need to allocate independent desktops for each user. Instead, the desktop can be shared to maximize utilization of server resources.

The following information describes how to share a desktop among multiple users through the shared desktop pool and domain users on the Space Console of H3C Workspace.

Prerequisites

·     Complete the building of the H3C Workspace Cloud Desktop environment, including installing the H3C Space Console and completing its initial deployment, and making the endpoint with the self-developed SpaceOS system connected to the network. For more information, see H3C Workspace Desktop Management Software Installation and Deployment Guide.

·     After initialization configuration is completed, the license server is installed on the virtual machine (VM) of the Space Console or on another physical server, and the configuration is completed on the License page of the Space Console. For details, see "License management" in the H3C Workspace Cloud Desktop Space Console User Manual.

·     For E1009 and later versions, you also need to upload the client installation package of the corresponding endpoint to the Upgrade Services page on Space console, and upload the optimization tool zip package H3C_Workspace-version-OptTools.zip to the Image Tool page on Space Console.

Restrictions and guidelines

·     The shared desktop supports local disk mapping and clipboard peripherals, which are enabled by default without policy control.

·     The operating system for a shared desktop must be Windows Server 2008, 2012 R2, 2016 (recommended), or 2019 (recommended).

·     To use a webcam through USB redirection on a shared desktop, use a Windows endpoint, and make sure the shared desktop runs Windows Server 2016 or 2019.

·     A shared desktop can be accessed through the Workspace APP client or Web client. When you connect to a shared desktop from the Web client, select the application connection mode. For the detailed procedure, see H3C Workspace Cloud Desktop Client User Manual (Office Scenario).

·     The configuration was created and verified in a lab environment, and all the servers and software were started with the factory default configuration. If the device has been configured, ensure that the existing configuration does not conflict with the configuration in the following example.

Example: Configuring a shared desktop pool

Network requirements

The R&D Department of a company restricts access to external websites, but sometimes the R&D personnel need to use the desktop to obtain work-related resources from some external websites. If everyone is allocated a desktop, it will cause a great waste of server resources. This problem can be effectively solved by the shared desktop pool, that is, by creating a desktop that can be used concurrently by multiple users. Network requirements are as follows:

·     Multiple users access the same desktop system, and users' personal data is stored in different user files and isolated from each other.

·     The shared desktop is bound to the user account. Employees can log in to the desktop using their own accounts and passwords.

Analysis

In this configuration example, the shared desktop pool is configured:

·     The shared desktop pool is applicable to endpoints using operating systems (OS) including Windows, SpaceOS, Android, iOS, MacOS, UOS, NeoKylin, and KylinOS.

·     A desktop in the shared desktop pool can be authorized for multiple users to use at the same time, and multiple desktops can also be authorized for a single user.

·     Different users log in to the desktop with their own accounts and passwords. Drive C of each user is the same. Users can only access their own user files on C:\Users, and the data disks of users are the same and shared. After the desktop is restarted, the system will not be restored, the corresponding user account will not be deleted, and the user data and settings will also be preserved.

The specific configuration is as follows:

1.     Enable the Space Console to synchronize the employees' account information on the domain controller.

2.     Based on the application scenario and frequently-used software, create the corresponding desktop image, and use this desktop image to create a shared desktop pool. The shared desktop pool only supports domain users.

3.     Deploy a desktop through the created shared desktop pool and authorize users to use the desktop.

4.     Perform user login authentication.

Figure 1 Network diagram

 

Procedures

Version E1013P11 is used as an example to describe the typical configuration method of the shared desktop pool. For other versions, configure the shared desktop pool based on an actual situation.

Synchronizing the Space Console with the domain controller

 

NOTE: It is assumed that you has set up the domain controller and created the accounts for employees.

 

On the Space Console, synchronize the configuration information on the domain controller. Select System > Advanced Settings > Server Configuration > OU Sync from the left navigation pane. On the OU Sync page, select the authentication server and sub-base DN, and click Sync Now in the Actions column to start synchronizing the specified configuration information.

Figure 2 OU Sync

 

Uploading a system image

On the H3C Space Console, upload the ISO system image of the Windows Server series to build an image source VM. In this example, Windows Server 2012 R2 is used. If a qualified system image already exists in the system, skip this step.

 

IMPORTANT: ·     If the upload path of the system image is the local directory of a host, only this host can use the system image. ·     If the upload path of the system image is a shared storage path, all hosts can use the system image.

 

Figure 3 Uploading a system image

 

Creating a desktop image

Desktop images are VM templates. To create a desktop image, you need to create an image source VM and clone or convert it to a desktop image.

·     Create an image source VM: Create an image source VM based on the uploaded system image.

·     Build an image source VM: Install the operating system (OS), CAStools, VdiAgent, and other software and optimize the image source VM.

Creating an image source VM

On the H3C Space Console, create an image source VM "share" for department A.

1.     Select Images > Desktop Images from the left navigation pane, select the Image Source VMs tab to display the image source VM list.

2.     Click Create. On the Create Image Source VM page, select Create Image Source VM for the creation type, and then click Next. Three creation types are available, including Create Image Source VM, Deploy VMs from OVF, and Create VHD-Based VM. In this example, the first type is selected.

Figure 4 Selecting a creation type

 

3.     On the Basic Info page, enter the image name, and set Image Type to VDI and System Image to the system image uploaded in "Uploading a system image."

Figure 5 Configuring the basic information of the new source image VM

 

4.     On the Configure VM page, select the Basic Settings tab, and configure the storage path, flavors, and network. Select the Advanced Settings tab, and configure parameters, such as the CPU working mode and file name. After completing the configuration, click Next. The image source VM is created.

Figure 6 Settings of the image source VM

 

Table 1 Parameters for creating an image source VM

Parameter	Description
Image Type	For the shared desktop, only the VDI type is supported.
Host	Host where the image source VM is located.
System Image	Select the system image of Windows Server 2012 R2 that is previously uploaded on the Data Center > System Images page.
Type	Specify a disk type, including New File, Create RBD, Existing File and Block Device. When there is an active RBD storage pool on the host, Create RBD is selected by default. Otherwise, New File is selected. ·     New File: A file here is a disk file built on the file system. For the VM, a file is a disk based on a virtual disk file. The disk attachment method of such a file is more convenient for management. If you select New File, an empty storage file is created as the disk of the VM. ·     Create RBD: If you select this option, an RBD is created as the disk of the VM in the RBD storage pool. ·     Existing File: If you select this option, you need to select an existing storage file that is not used by other VMs as the disk of the VM. For example, you can select a volume from the local file directory, shared file system, or network file system (NFS) storage pool as the disk of the VM. ·     Block: A block device is also called a raw device that does not have a file system, for example, a storage LUN on an IP SAN or FC SAN. Block devices are typically used in a virtualization environment that requires high performance, for example, databases and high-performance I/O compute. If you select this option, you need to select an existing storage volume that is not used by other VMs as the disk for the VM. For example, you can select a volume from the RBD, iSCSI, FC, or LVM logic storage pool as the disk of the VM.
Path	It is the storage path for the image source VM file. When deploying a desktop image, you need to re-select a storage path for the desktop image. Directories /vms/images and /vms/isos are for local files. As a best practice, choose other locations to prevent the lack of local directory space.
Flavors	Desktop image settings that are configured on the System > Flavors page, such as the CPU, memory, and system disk size. As a best practice, select Medium Performance for a shared desktop pool.
Operating Mode	The CPU operating mode includes Compatible, Host Matching, and Passthrough. The Compatible mode is selected by default. ·     Compatible: Virtualizes physical CPUs of different models into vCPUs of the same model. This mode feature high migration compatibility. ·     Passthrough: Directly passes physical CPUs to VMs. This mode features low migration compatibility but provides better performance for VM operating systems than the Compatible mode and Host Matching mode. VMs using the passthrough CPU operating mode can be migrated only between hosts with the same CPU model. ARM hosts support only the passthrough mode. ·     Host Matching: Virtualizes physical CPUs of different models into vCPUs of different models. This mode features low migration compatibility but provides better performance for VM operating systems than the Compatible mode.
Physical host	With this feature enabled, the application software considers a VM as a physical host. This parameter is available only when the CPU operating mode is Host Matching.
Attach Hardware	·     You can attach hardware devices to the image source VM as needed, for example, NIC, disk, CD-ROM, floppy disk, GPU device, and watchdog. ·     To attach a disk for the VM, you need to initialize the added disk as the data disk after installing the OS.

 

Building an image source VM

1.     Select Images > Desktop Images from the left navigation pane, select the Image Source VMs tab to display the image source VM list. Click Console in the Actions column to start building an image source VM, for example, "share".

Figure 7 Clicking Console to start building an image source VM

 

2.     Install the operating system for the image source VM according to the wizard, as shown below.

Figure 8 Selecting a language and other preferences

 

Figure 9 Start installing the operating system

 

NOTE: Select the operating system to be installed. As a best practice, select Windows server 2012 R2 Standard (server with a GUI).

 

Figure 10 Selecting the operating system to be installed

 

Figure 11 Accepting the installation license agreements

 

Figure 12 Selecting the installation type Custom install Windows only (advanced)

 

Figure 13 Clicking Load Driver (L)

 

Figure 14 Selecting the driver to be installed based on the operating system

 

IMPORTANT: ·     For the 32-bit Windows operating system, select the driver under A:\x86\. ·     For the 64-bit Windows operating system, select the driver under A:\amd64\. ·     You must load the drivers and make sure all compatible drivers are selected in the driver dialog box. Otherwise the VM may fail to run normally due to absence of drivers.

 

Figure 15 Selecting all compatible drivers

 

NOTE: When installing the operating system, partition the disks if there are multiple disks.

 

Figure 16 Selecting the partition for installing the operating system

 

Figure 17 Waiting until installation is completed

 

Figure 18 Configuring the Admin password

 

Figure 19 Image source VM after the operating system is installed

 

3.     Install the sound card device for the VM. Select Data Center > Virtualization from the left navigation pane, select the Image Source VMs tab to display the image source VM list. Click Edit. Click Attach Hardware in the upper right corner, set Hardware Type to Sound Card and Type to ac97, and click OK.

Figure 20 Modifying a VM

 

Figure 21 Adding a sound card device

 

4.     Upload the required office software to the image source VM by means of sharing or through the FTP server, and install the office software.

5.     Install CAStools and VdiAgent: CAStools and VdiAgentt are integrated in the agent_tools tool. VdiAgent is installed first, during which the CAStools installer is started automatically. After installation of CAStools is completed, the VdiAgent installation process continues.

a.     On the image source VM console, select Install Template Tool > Attach Optical Drive, and open CD Drive (D:) agenttools.

Figure 22 Attaching an optical drive

 

Figure 23 Opening CD Drive (D:) agenttools

 

b.     Open the windows folder, and run agent_tools_setup. In the VdiAgent Setup dialog box, click Next.

Figure 24 Installing agent_tools

 

Figure 25 VdiAgent Setup dialog box

 

c.     In the Environment Setting dialog box, enter the IP address or domain name (a FQDN) of the management node host for Space Console, use the default port setting, and click Next.

Figure 26 Environment Setting dialog box

 

d.     Select the target folder for installing VdiAgent, and click Install to start the installation.

Figure 27 Selecting the target folder

 

e.     In the VdiAgent installation process, the CAStools installer is automatically started. In the dialog box displayed during CAStools installation, click OK to continue with the installation. After installation is completed, click Close.

Figure 28 Restart dialog box displayed during CAStools installation

 

Figure 29 Completing CAStools installation

 

f.     After the CAStools installer is closed, the system continues with VdiAgent installation. After VdiAgent installation is completed, click Finish.

Figure 30 Installing VDIAgent

 

Figure 31 VDIAgent installation completed

 

IMPORTANT: The image source VM requires the deployment of RDS to allow users to access shared desktops via remote connections. Users will be unable to connect to shared desktops once the RDS service expires. The RDS service will be installed automatically during the installation of VdiAgent for the image source VMs with Windows Server series OS installed. After the installation is completed, restart the image source VM for the RDS service to take effect.

 

g.     Restart the image Source VM.

6.     Configure and optimize the system service: Use the optimization tool to optimize system configuration and improve system operation efficiency.

a.     Select Install Template Tool > Mount OptTools.

Figure 32 Mounting OptTools

 

b.     Switch to the CD-ROM drive and run H3COptTools.

Figure 33 Running H3COptTools

 

c.     Select Cloud Desktop Template Optimization, and click OK.

Figure 34 Selecting Cloud Desktop Template Optimization

 

d.     On the homepage of H3C Optimization Tool, click Check to check the operating system.

Figure 35 Checking the operating system

 

e.     After the check is completed, items that fail the check are marked red. Select optimization options and then click Optimize to optimize the items that failed the check.

 

IMPORTANT: Make sure that AC97 driver uninstalled is selected.

 

Figure 36 Failed items in the optimization check

 

Table 2 Optimization items

Optimization Item	Introduction
Install AC97	(Required) Installation of the VM sound card.
Optimize system acceleration	VM user experience optimization. As a best practice, select this item.
Optimize display experience	VM user experience optimization. As a best practice, select this item.
Customize the user profile	(Required) Used for template deployment.
Configure vGPU license server	VM user experience optimization. Select this item if the vGPU is installed.
Optimize system fluency	VM user experience optimization. As a best practice, select this item.
Video playback	VM user experience optimization. As a best practice, select this item.
Perform sysprep optimization after system startup	VM user experience optimization. As a best practice, select this item.
Install the Renesas USB driver	(Required) Install the USB driver.

 

a.     Click Install to install the AC97 sound card.

g.     Select a disk to save the custom user profile, and click OK.

Figure 37 Selecting a disk to save the custom user profile

 

h.     Select the cloud disk installation location, and click Install. After the cloud disk installation is completed, click Finish.

Figure 38 Selecting the cloud disk installation location

 

Figure 39 Cloud disk installation completed

 

i.     After optimization, click OK to restart the image source VM.

Figure 40 Restarting the VM after optimization is completed

 

7.     Configure the DNS: Set the DNS of the image source VM to the IP address of Microsoft Active Directory (AD) domain controller. The purpose is to allow domain users to automatically join a domain.

a.     Select Control Panel > Network and Internet > Network and Sharing Center > Local Area Connection Properties > Internet Protocol Version 4 (TCP/IPv4), and set the DNS address of the image source VM to the IP address of the Microsoft AD domain controller

Figure 41 Configuring the DNS

 

NOTE: If you have enabled the domain tree configuration for the domain controller, configure the IP address of the alternate DNS server as the domain tree address. For details about how to enable the domain tree configuration, see "Configure authentication servers" in the H3C Workspace Cloud Desktop Space Console User Manual.

 

8.     Modify the startup type of Windows Audio service: To ensure that the desktop supports software that needs to play audio, you need to change the startup type of Windows Audio service to Automatic in this step.

a.     On the Server Manager page, select Tools > Services.

Figure 42 Server Manager page

 

b.     In the Services dialog box, double-click Windows Audio. The Windows Audio Properties (Local Computer) dialog box opens.

Figure 43 Double-clicking Windows Audio

 

c.     Click Start to start the Windows Audio service, change its startup type to Automatic, click Apply, and click OK.

Figure 44 Modifying the startup type of Windows Audio service

 

d.     Restart the VM.

9.     Install patches: If the operating system of the image source VM is Microsoft Windows Server 2008 R2, install two patches NDP452-KB2901907-x86-x64-AllOS-ENU.exe and Win7AndW2K8R2-KB3191566-x64.msu sequentially. To obtain the patch package, contact the technical support engineers.

Checking before publishing a desktop image

1.     Check whether the Windows Audio service is running: Check the lower right corner of the screen. If the Windows Audio service is not running, start the service according to "Modify the startup type of Windows Audio service."

Figure 45 Checking the running status of the Windows Audio service

 

Figure 46 Windows Audio service in running state

 

2.     Check whether the domain name of the domain controller can be pinged: Click  on the toolbar to open the Windows PowerShell window as Admin, and ping the IP address or domain name of the authentication server.

Figure 47 Pinging the IP address of the authentication server

 

3.     Check whether the remote desktop is enabled: Select Control Panel > System and Security > System, and click Remote settings. On the System Properties dialog box displayed, select the Remote tab, and check whether "Allow Remote Assistance connections to this computer" is selected. If not, select this option, click Apply, and then click OK.

Figure 48 Accessing the Remote settings page

 

Figure 49 Confirming that "Allow remote connections to this computer" is selected

 

Publishing a desktop image

You can publish the built image source VM as a desktop image by means of cloning or converting. Later, use this desktop image to create a desktop pool or deploy a desktop. Taking cloning an image source VM to a desktop image as an example

1.     On the image source VM list page, click Clone.

Figure 50 Cloning as desktop image

 

2.     Configure the desktop image name, select the image storage, and enable Create Snapshot After Cloning according to the actual needs, and click OK.

Figure 51 Configuring parameters in the Clone as Desktop Image dialog box

 

Creating a shared desktop pool

On the H3C Space Console, create a shared desktop pool named DeptA. The number of desktops is equal to the number of R&D personnel in the department (20 people).

1.     On the Desktop Pools page, click Create or Create Desktop Pool. The Create Desktop Pool page opens.

Figure 52 Creating a desktop pool

 

2.     Configure the basic information of the desktop pool, and click Next: Login Info. In this example, set Name to DeptA, Desktop Type to VDI, Desktop Pool Type to Shared, and Max Desktops to 20, and Desktop Prefix to DeptA.

Figure 53 Basic information of the desktop pool

 

Table 3 Creating a desktop pool - Parameters for basic information

Parameter	Description
Desktop Pool Type	Type: Select VDI.
Deployment Location	Select the location for desktop deployment, including Cluster or Host. If you select this option, the system automatically deploys desktops across hosts in a cluster for optimal resource usage.
Desktop Pool Type	Options include Static, Dynamic, Manual, Share, and Application Server. In this example, select Share. ·     Static: To assign each user a dedicated desktop, select this option. A static desktop is persistent. All data and settings of its user will persist through a reboot. ·     Dynamic: They are dynamically assigned to users in the preauthorization list you configured for the pool. When the system receives a request from a preauthorized user, the system randomly selects a desktop from the dynamic desktop pool for that user. First come, first served. When the user logs out and restarts the VM, the VM will be restored to its initial state. Dynamic desktop pools are applicable to scenarios such as public training and teaching, and reading rooms. ·     Manual: It is a type of dynamic desktop pool without the protection mode. After the user logs out, the desktop pool is not restored to its initial state. You can restore the desktop pool function and restore the VM to the state at a specified time by setting the restore point. ·     Shared: They save data of multiple users, and their desktop data disks are shared among multiple users. ·     Application Server: To batch deploy application server VMs used for providing virtual applications, select this option. To authorize users to use virtual applications, select Application > Application Center > Virtual Application > Application Group. For details, see the H3C Workspace Cloud Desktop Virtual Application Configuration Guide (for Office Scenario).
Max Desktops	Set the maximum number of desktops in the desktop pool. In this example, the department has 20 employees.
Desktop Prefix	Specify the prefix in the names of the desktops automatically deployed from the desktop image template. The deployed desktops will be named in prefix-random_number format.

 

3.     Configure the login information, and click Next: Configuration. The user type is Domain Users by default.

Figure 54 Login information of the desktop pool

 

4.     Add the configuration information of the desktop pool, where Initialization Type must be set to Fast. Then, click Next: Confirm Configuration. In this example, select the desktop image share_A created for DeptA, and configure other parameters based on the actual conditions.

Figure 55 Configuration information of the desktop pool

 

Table 4 Creating a desktop pool - Parameters for configuration information

Parameter	Description
Desktop Image	It is used to bulk deploy VMs of the same configuration in the desktop pool. In this example, select the created desktop image share_A.
System Disk Storage	Location of the system disk storage volume of the VM. If cluster-based deployment is selected, make sure the cluster has shared storage accessible to all its hosts.
Initialization Type	The shared desktop pool only supports the fast initialization mode.
Fast Deployment	Select Deploy Now, and click Finish. The Batch Deploy page opens. If you click Finish without selecting Deploy Now, the system returns to the Desktop Pools page.

 

5.     After the desktop pool is created, you can view the desktop pool information of DeptA in the desktop pool list.

Figure 56 Desktop pool created successfully

 

Deploying desktops

You can use the created shared desktop pool for batch deployment of desktops. In this example, the number of desktops deployed is 20 (number of department employees).

 

NOTE: When the desktop image associated with the desktop pool is deployed in fast mode for the first time, you can deploy only one desktop. In this case, you need to check that the desktop is available and then deploy the remaining desktops.

 

1.     From the navigation pane, select Desktop Pools. Select a desktop pool, and then click Batch Deploy. After configuring relevant information according to the wizard, click Finish.

Figure 57 Desktop image page

 

Figure 58 Page displayed upon the first batch deployment

 

Table 5 Parameters for batch deployment

Parameter	Description
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. You can deploy only one VM upon the first fast deployment.
Configure	Select the number of CPUs and memory size of the VM. Options include or low, medium, or high performance. As a best practice, select the flavor consistent with settings of the image template.
OU	If the desktop pool is for domain users, specify the organization unit (OU) on the domain controller so as to join desktops to a domain conveniently.
Boot After Deploy	Initialize the desktops immediately after they are deployed.
4K Resolution	To enable 4K display on the desktops, enable this feature.
Bind NUMA Node	When performing cross-host operations (such as migration, cloning, restore, and import) on the desktop after binding, ensure that the Non Uniform Memory Access (NUMA) architectures of the source and destination hosts are consistent, otherwise the desktop operations may fail. CAUTION: When the number of bound physical CPUs exceeds the total number of host CPUs, NUMA nodes bound to the desktop will not take effect.

 

Figure 59 Configuring the network

 

NOTE: As a best practice, configure a static IP address segment for the desktop pool. If the static address segment is not configured, you need to manually configure the static IP address and DNS for each desktop before joining desktops to the domain. Static IP assignment aims to plan the IP address range according to user needs and ensure that the shared desktop can join the domain successfully. In this case, you must configure the DNS address as the IP address of the domain controller.

 

Figure 60 Configuring a static IP address segment

 

2.     The first desktop deployment is completed.

Figure 61 Desktop deployment completed

 

Authorizing a user

To authorize the desktops in the desktop pool of DeptA to the employees in DeptA, select Preauthorize tab above the desktop list, click Select User to select the user to be authorized, and complete the authorization.

 

NOTE: You must create and configure users in advance.

 

Figure 62 Authorizing a user

 

Figure 63 Selecting a user

 

Figure 64 Authorized successfully

 

Verifying the configuration

You can log in to the shared desktop through the Workspace app or Web client. The Web client is used as an example to verify the authorization result.

1.     The employee Zhang San enters "Management platform address: 8083/WorkspaceWebApp/#/login" in the browser to visit the H3C Workspace Web client, and enters his account and password to log in to the Web client.

Figure 65 Logging in to the Workspace Web client (Zhang San)

 

2.     After login, Zhang San can access the desktop list and view the authorized shared desktop DeptA-001.

Figure 66 Desktop list

 

3.     After connecting to the shared desktop, Zhang San can create a file on the desktop. When he opens the C:\user\zhangsan\desktop folder, he can see the new file.

Figure 67 User's personal files

 

4.     The employee Li Si enters "Management platform address: 8083/WorkspaceWebApp/#/login" in the browser to visit the H3C Workspace Web client, and enters his account and password to log in to the Web client.

Figure 68 Logging in to the Workspace Web client (Li Si)

 

Figure 69 Desktop list

 

5.     After connecting to the shared desktop, Li Si opens the C:\user\zhangsan\desktop folder. In this folder, Li Si can see the personal data folders of both users Li Si and Zhang San, but is not authorized to access the folder of Zhang San.

Figure 70 Personal data folders of different users

 

Figure 71 No permission to access folders of other users

 

Related documentation

Document	Obtaining method
H3C Workspace Cloud Desktop Space Console User Manual	https://www.h3c.com/en/Support/Resource_Center/EN/Cloud_Computing/Catalog/H3C_Workspace/H3C_Workspace/
H3C Workspace Desktop Management Software Installation and Deployment Guide
H3C Workspace Cloud Desktop Client User Manual (Office Scenario)