【VDI】Remote Application Deployment Guide_V5.9.1_R2_EN
Introduction
The Remote App Servers module is designed to manage servers (running Windows Server) on which remote apps are published. This function module applies only to x86 and C86 HCI clusters.
Configuration
Agent Management
Install and Uninstall Agent
Function
This function applies to scenarios where the agent needs to be installed on VM templates for remote app servers, and to scenarios where the agent needs to be uninstalled or re-installed for troubleshooting.
Prerequisites
- The VM is running Windows Server 2008 R2 (64-bit), Windows Server 2012 (64-bit), Windows Server 2016 (64-bit), or Windows Server 2019 (64-bit).
- HCI vmTools has been installed on the VM.
- The remote session host function has been enabled for the remote app server.
Procedure
- To install the agent, perform the following steps:
a) Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, click More and select Download Agent to download the agent installer to your local PC.
b) Import the agent installer SFRemoteAppServerInstall.exe into the Windows Server VM and execute it. Check the Remote application server checkbox, enter the management IP address of the VDC cluster in the VDC Address, and complete the installation as prompted. The VM will restart after the installation is complete.
- To uninstall the agent, perform the following steps:
a) Go to the agent installation directory C:\Program Files (x86)\Sangfor\SSL\RemoteAppServer on the VM, and run the uninstaller uninst.exe as an administrator.
Update Agent
Function
After a VDC upgrade, you must update the agent on remote app servers in bulk via the VDC console to ensure the proper functioning of the new features.
Prerequisites
The remote app servers have been managed on VDC. For details about managing a remote app server on VDC, see Chapter 2.2.1 Remote App Server Creation.
Precautions
Updating the agent will cause the remote app servers to restart, during which app services will be interrupted. Update the agent during non-service hours.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, select the remote app servers, and click More > Update Agent. In the Update Agent dialog box, click OK.
Remote App Server Management
Remote App Server Creation
Function
This function is designed to consolidate app servers created in bulk on HCI or existing physical machines running Windows Server into a resource pool on VDC for remote app resource publishing.
Precautions
Customers can either deploy a DHCP server on the network to assign IP addresses to remote app servers, or manually configure the IP addresses. DHCP-based assignment is recommended because it is the only way to assign IP addresses to remote app servers in nonpersistent mode.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, click New.
- On the Add Server page, manage the remote app servers in Batch or by Individual. The following table describes the applicable scenarios of the two management modes.
| Management Mode | Description |
|---|---|
| Batch | This mode applies only to remote app servers deployed in bulk on HCI. In this mode, you can import remote app servers deployed from the same template on HCI into a server collection in bulk for unified management on VDC. |
| Individual | This mode applies to remote app servers of all types. In this mode, you can add the IP addresses of the remote app servers one by one for separate management of the servers. |
- Batch
In this mode, you must configure the basic attributes of the server collection. Select a remote app server template, and select remote app servers deployed from the template based on the service requirements. For details about managing remote app servers, see Chapter 2.5 Remote App Server Resource Management.
The following table describes the parameters of the batch mode.
| Category | Parameter | Description |
|---|---|---|
| Basics | Server Collection Name | Set a name for the server collection. |
| Basics | Server Collection Description | Enter a description for the server collection as required, such as its purpose and type, for quick identification and management. |
| Basics | Group | Set a group for the server collection for easy management. The default value is Default Group, and you can change it as required. |
| Advanced | Template | Select the template from which the target remote app servers are deployed. This parameter setting will determine the options for Import Servers. |
| Advanced | Import Servers | Select remote app servers to be imported to the server collection. To select remote app servers deployed from the template selected in Template, click the List icon. |
| Advanced | Max Concurrent Sessions Per Server | Set the maximum number of concurrent remote app sessions for each server in the server collection. The default value is 0, indicating an unlimited number. If apps on each remote app server have a concurrent licensing limit, set this parameter to keep the number of users accessing the apps on a remote app server within the limit. |
- Individual
In this mode, you must set the basic attributes of each remote app server and specify the access IP address and port number based on the service requirements.
The following table describes the parameters of the individual mode.
| Category | Parameter | Description |
|---|---|---|
| Basics | Server Name | Set a name for the server. |
| Basics | Description | Enter a description for the server as required, such as its purpose and type, for quick identification and management. |
| Basics | Group | Set a group for the server for easy management. The default value is Default Group, and you can change it as required. |
| Basics | Servers | Determine whether to enable the server to provide services for aDesk VDI users. It is Enabled by default. |
| Advanced | Server IP | Specify the IP address of the remote app server. |
| Advanced | Server Port | Set the agent’s service port number on the remote app server. The default value is 7170. You can modify the service port in the agent settings window on the remote app server. |
| Advanced | Max Concurrent Sessions | Set the maximum number of concurrent remote app sessions for the server. The default value is 0, indicating an unlimited number. If apps on the remote app server have a concurrent licensing limit, set this parameter to keep the number of users accessing the apps within the limit. |
Increase of Remote App Servers in a Server Collection
Function
As the number of users increases due to service growth, you can add more remote app servers to an existing server collection to support more concurrent users.
Prerequisites
New remote app servers have been deployed on HCI from the template used by a server collection. For details, see Chapter 2.5.2 Deploy More Remote App Servers from a Remove App Server Resource.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, select the target server collection and click Edit.
- On the Edit Server page, click the List icon next to Import Servers. On the Import Servers page, select the remote app servers newly deployed from the template specified by Template and click OK.
Domain Configuration
Function
For an AD domain environment, you can distribute domain configurations to remote app servers deployed from a template on HCI in bulk to automatically add them to a domain for simplified O&M.
Prerequisites
- Remote app servers have been imported in bulk.
- Remote app servers can resolve the address of the domain controller and communicate with it.
- The VM template from which the app servers are deployed has been added to the domain if the remote app servers are in nonpersistent mode.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, select the target server collection and click Edit.
- On the Edit Server page, go to the Domain Configuration tab, and select Join server to AD domain. Enter the LDAP Server IP Address, LDAP Server Domain Name, Admin CN, and Admin Password, and click Test Connectivity; or select a domain server that has been integrated with VDC to have the relevant information automatically filled.
The following table describes the parameter on the Domain Configuration tab.
| Parameter | Description |
|---|---|
| Protocol | Set a protocol for integrating an AD domain with VDC. The default value is LDAP. For security purposes, select LDAPS if the customer has enabled LDAPS for their domain controller. |
| LDAP Server IP Address | Required. Specify the IP address of the domain controller for VDC to detect domain controller connectivity and obtain OU information. If the customer has multiple domain controllers, select one of them. If VDC has been integrated with an LDAP server under Authentication, you can select the LDAP server from the drop-down list to have the LDAP Server Domain Name, Admin CN, and Admin Password automatically synchronized. |
| LDAP Server Domain Name | Required. Specify the name of a domain that remote app servers will join. |
| Admin CN | Required. Specify the username that the domain user uses to add remote app servers to the domain. It is recommended to use the domain admin account. If you want to grant the least privilege to the domain user for security purposes, ensure that the user has permission to read the OU structure and create computer objects within the OU to which virtual desktops belong. |
| Admin Password | Required. Enter the domain user’s password to add remote app servers to the domain. |
| AD Domain OU | Specify an AD domain OU to which the remote app servers in the server collection will be added to ensure easy management and correct domain policy application. The default value is computer OU; you can change it as required. |
Power Schedules
Function
You can set power schedules to start up, shut down, or restart remote app servers deployed on HCI from a template and managed on VDC in bulk.
Prerequisites
Power schedules are only applicable to remote app servers imported in batch mode.
Precautions
- Startup/shutdown schedules and restart schedules cannot be configured at the same time.
- Restart schedules apply only to running remote app servers, meaning the powered-off remote app servers will not be restarted.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, select the target server collection and click Edit.
- On the Edit Server page, click the Power Schedules tab, select Restart schedules, Startup Schedule, or Shutdown Schedule as required, and set the scheduled time.
- Restart schedules
Select Restart schedules, click Add New Plan, and specify the restart time in the New Restart Time dialog box.
- Startup Schedule
Select Startup Schedule, click Add New Plan, and specify the startup time in the New Startup Time dialog box.
- Shutdown Schedule
Select Shutdown Schedule, click Add New Plan, and specify the shutdown time in the New Shutdown Time dialog box.
Remote App Server Policy
Function
You can configure policies for VDC to perform session control for remote apps, including session, load balancing, and overload protection policies.
Precautions
Remote app server policies apply to all remote app servers by default.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, click More and select Remote App Server Policy.
- In the Remote App Server Policy dialog box, set policies based on service requirements.
The following table describes the parameters in the Remote App Server Policy dialog box.
| Parameter | Description |
|---|---|
| Enable session persistence on remote app server | This option is enabled by default, with a default session persistence duration of 15 minutes. It prevents the loss of a user’s operation status data by avoiding automatic remote app session termination in case of client disconnections due to network errors. If this option is selected, a remote app session will still be maintained for the specified duration in the event of unexpected client disconnections. The session will be terminated if the client is not reconnected within that duration. The minimum session persistence duration is 5 minutes. If this option is unselected, a remote app session will be terminated immediately upon an unexpected client disconnection to release the resource. |
| Allow session multiplexing | This option is enabled by default. This defines session scheduling rules for scenarios where multiple apps are allowed on one remote app server. If this option is selected, a user is assigned one session for accessing different apps on the same server to reduce resource overhead. If this option is unselected, a user is assigned an independent session for accessing each app. This option applies only to iOS, Android, and thin clients. Session multiplexing will be forcibly enabled on Windows clients. |
| Overload Protection | This function protects against server overload based on CPU, memory, and system disk utilization. When a server’s resource load exceeds the predefined threshold, new sessions to the server will be scheduled to other idle servers. This prevents the overloaded server from affecting the experience of existing users. |
Program Whitelist
Function
You can manage and control remote apps’ behavior of calling other programs, which avoids potential security risks by preventing users from calling unauthorized programs through a published app.
Precautions
The program whitelist only controls whether a published app can call specified programs. However, the call result depends on the user’s permissions. For example, suppose the published Chrome browser must call Microsoft Word to open an online document, but the user is prohibited from using Microsoft Word based on the software policy in the security group policies distributed by the domain controller. In that case, the user cannot open the online document through the published Chrome browser even if you have added Microsoft Word to the program whitelist.
Procedure
- Log in to the VDC console and go to Assets > Remote App Servers. On the Remote App Servers page, click More and select Program Whitelist.
- In the Program Whitelist dialog box, configure the processing policy based on the service requirements.
The following table describes the parameters in the Program Whitelist dialog box.
| Account Type | Description |
|---|---|
| Allow any third-party programs | This option is selected by default. It enables published apps to call any programs the user can run. |
| Allow specified third-party programs | If this option is selected, published apps can only call the programs listed in the whitelist. Access to any other programs will be denied. |
Remote App Server Resource Management
- When using Windows Server VMs as remote app servers, VDC supports adding remote app servers in bulk on HCI under the Resources module for publishing remote app resources or session-based desktop resources.
- This function module applies only to x86 and C86 HCI clusters.
Add a Remote App Server Resource
Function
If remote app servers with new apps are required due to business needs, you can create the corresponding VM templates first and then deploy remote app servers in bulk from the templates on VDC for subsequent operations.
Prerequisites
- VDC has been integrated with HCI.
- Corresponding Windows Server VM templates have been deployed and imported into VDC.
- The VM templates must be powered off and not in use.
Procedure
- Log in to the VDC console and go to Services > Resources. On the Resources page, click New and select Virtual Desktop.
- Complete the settings in the Basics section as required, where you must select Remote App for Work Mode.
The following table describes the parameters in the Basics section.
| Parameter | Description | Remarks |
|---|---|---|
| Name | Specify the name of a resource. | Required |
| Description | Describe the resource’s usage and type for easy identification and management. | Optional |
| Group | Specify the resource group to which the resource belongs, facilitating categorization and management. | Required. It is set to Default_Group by default. |
| Area | Specify the administrative area to which this resource belongs. Select Default area if management by level and area is not required. Otherwise, specify the corresponding area. This way, this resource can be managed by administrators in the corresponding area and accessed by users in the corresponding area. | Required. Default value: Default area. |
| Status | Specify whether this resource provides services for external systems. If it is set to Disabled, this resource is not displayed in the resource list of authorized users (that is, this resource is inaccessible to users). | It is Enabled by default. |
| Work Mode | Specify the type of VMs to be created based on the resource. If it is set to Desktop, a desktop VM template can be used to deploy desktop resources. If it is set to Remote App, a Windows Server VM template can be used to deploy remote app servers, which can then be managed under Assets > Remote App Servers. | Default value: Desktop. To create remote app servers based on this resource, you must set this parameter to Remote App. |
| Icon | Specify the icon displayed for the resource in the resource list on VDC. |
You can select a default icon or upload an image. |
- On the Virtual Machine tab, complete the settings in the Basics and Private Disk sections as required.
The following table describes the parameters on the Virtual Machine tab.
| Parameter | Description | Remarks |
|---|---|---|
| VM Name | Specify the prefix for VM names. A deployed VM will be named after its creation sequence number, prefixed with this value. Adding a hyphen (-) after the value is recommended, such as WS16-OA-. | – |
| VM Template | Specify the remote app server template for the resource. The remote app servers of the resource will be deployed based on this template, and their system disks will remain consistent with those of the template. | To deploy remote app servers based on the VM template, ensure that the template is shut down. |
| Desktop Type | Specify the mode of deployed remote app servers, either persistent or nonpersistent. Persistent: When selecting this mode, the remote app servers will be deployed in persistent mode. The system disks will not be restored after servers restart, and the data of logged-in users will be retained. Nonpersistent: When selecting this mode, the remote app servers will be deployed in nonpersistent mode, and the system disks will be restored to the template state after the server’s restart. |
Select a mode as required. |
| VM Type | Specify the mode of deployed remote app servers, either Linked Clone or Full Clone. Linked Clone: Remote app servers share a system disk image with the template and can be created quickly. Full Clone: Each virtual desktop uses a separate system disk, which can ensure the service independence of each desktop. However, the creation is slow. This mode is applicable only to virtual desktops in persistent mode. |
Persistent remote app servers support the linked clone and full clone modes, while nonpersistent servers support only the linked clone mode. |
| Encryption Settings | Specify whether to encrypt remote app servers. If this feature is enabled, all disks of the remote app servers deployed from this resource will be encrypted, and any operation that may cause user data leakage is prohibited, including cloning, exporting, or mounting private disks to other VMs. This feature prevents data leakage within the remote app servers, meeting the requirements for high data security. | You are not recommended to encrypt remote app servers. |
| Enable huge-page memory | Specify the memory allocation mode for remote app servers on HCI clusters. Allocating contiguous and complete memory improves VM performance and user experience. This feature is enabled by default. | If this feature is enabled, memory reclaiming will be disabled. |
| Enable L3 cache | Specify whether to enable L3 cache for remote app servers on HCI clusters. Enabling this feature reduces scheduling performance costs caused by IPIs and improves user experience. This feature is enabled by default. | – |
| CPU Cores | Specify the number of vCPU cores allocated to the remote app servers deployed from this resource. You can adjust the number of vCPU cores as required. | – |
| Mem Usage | Specify the memory size allocated to the VMs deployed from this resource. You can adjust the memory size as required. | – |
| Private Disk | Specify whether to allocate a separate disk from the system disk to the remote app server. The data stored in this private disk is not affected by template updates or a shift to the nonpersistent mode. | – |
- In the Add New Virtual Machine section, click New. On the Add New Virtual Machine page, select an HCI cluster to deploy the remote app servers from this resource and click Next.
Note:
Only one HCI cluster can be selected each time. If the remote app servers need to be deployed from this resource in multiple HCI clusters, you need to repeat the add operation multiple times.
- On the Basics tab, complete the settings as required and click Next.
The following table describes the parameters on the Basics tab.
| Parameter | Description | Remarks |
|---|---|---|
| Count | Specify the number of remote app servers to be added to the target HCI cluster. | – |
| App Versions | Specify the template version used for creating remote app servers. The latest version is selected by default if the template has multiple versions. You can change it as required. | – |
- On the Configuration tab, complete the settings as required and click Submit.
The following table describes the parameters on the Configuration tab.
| Parameter | Description | Remarks |
|---|---|---|
| Run Location | Specify the run location for the remote app servers. By default, it is set to Cluster, enabling a remote app server to run on the node with the lowest load in the HCI cluster. You can change the run location to a specific HCI node as required. | – |
| Group | Specify the VM group to which the remote app servers deployed from this resource belong in the HCI cluster. You can select a group as required for easy management. | – |
| Datastore | Specify the datastore to which the remote app servers deployed from this resource belong in the HCI cluster. | – |
| Storage Policy | Specify the storage policy for the remote app servers deployed from this resource. This parameter is available only if the Datastore is set to a virtual datastore. It ensures that the remote app servers are created based on the corresponding virtual storage policies on HCI to meet the requirements for multi-replica redundancy and performance. |
In addition to the default two-replica and three-replica policies on HCI, you can create custom storage policies under Storage > Virtual Storage on HCI. For details, see the Sangfor HCI User Manual. |
| Edge | Specify the NIC bridge location of the remote app servers deployed from this resource. You can select virtual switches created on HCI as required. |
You can select only the distributed switches and edges on HCI. |
| Snapshot Policy | If the data of the remote app server resource is important, administrators can select a snapshot policy predefined on HCI. According to the policy, HCI will regularly take snapshots and back up the remote app servers. To create an HCI snapshot policy, log in to the HCI console and go to Reliability > Snapshots > Snapshot Policies. For details, see the Sangfor HCI User Manual. | Storage-based snapshots and disk snapshots cannot coexist. To utilize storage-based snapshot policies, it is required to delete the disk snapshots on VMs. |
- Click Save to complete the configuration for remote app server resources.
Deploy More Remote App Servers from a Remote App Server Resource
Function
This feature is designed to deploy more remote app servers from an existing remote app server resource, thereby meeting growing user demands.
Prerequisites
- VDC has been integrated with HCI.
- A remote app server resource has been created on VDC.
- The VM templates associated with the remote app servers must be powered off and not in use.
Precautions
After adding the remote app server resources, the new remote app servers must be added to the corresponding server groups (Assets > Remote App Servers) so that they can provide remote app services externally. For details, see Chapter 2.2.2 Increase of Remote App Servers in a Server Collection.
Procedure
- Log in to the VDC console and go to Services > Resources. On the Resources page, click Edit corresponding to the virtual desktop resource.
- On the Virtual Machine tab, add remote app servers as required in the Add New Virtual Machine section.
- Deploy new remote app servers in an existing HCI cluster.
To deploy new remote app servers in an existing HCI cluster, click Add corresponding to the target cluster, set the quantity in the Add VM dialog box, and click OK.
- Deploy remote app servers in a new HCI cluster.
To deploy remote app servers in a new HCI cluster, click New and perform Steps 4 to 6 in Chapter 2.5.1 Add a Remote App Server Resource.
- Click Save, and VDC will start to deploy the remote app servers.
Create a Remote App Resource
Function
Remote apps on Windows Server can be utilized to meet the needs of users who require specific apps rather than a complete desktop environment, helping to reduce costs. This feature suits hot-desking scenarios where the service software supports multi-user instances and is compatible with Windows Server systems.
Prerequisites
- x86 HCI clusters have been deployed.
- VDC has managed remote app servers and has not been occupied by session-based desktop resources when Windows Server is used to publish remote apps.
- The apps to be published have been deployed on the corresponding app servers.
- Only apps that support multiple instances and are not installed in the user directory can be published as remote apps.
Precautions
Before utilizing app resources, they need to be associated with the corresponding users through role association. Therefore, you must associate the app resources with roles first and then associate the roles with users.
Procedure
- Log in to the VDC console, go to Services > Resources, click New > Remote App to enter the New Remote App Resource page.
- Complete the settings in the Basics section as required.
The following table describes the parameters in the Basics section.
| Parameter | Description | Remarks |
|---|---|---|
| Name | Name the remote app resource. The name will be displayed in the resource list after users log in to VDI. | Required |
| Description | Describe the usage and type of the remote app resource for easy identification and management. | Optional |
| Group | Specify the resource group to which the remote app resource belongs, facilitating categorization and management. | Required. It is set to Default_Group by default. |
| Area | Specify the administrative area to which this resource belongs. Select Default area if management by level and area is not required. Otherwise, specify the corresponding area so that this resource can be managed by administrators in the corresponding area and accessed by users in the corresponding area. | Required. Default value: Default area. |
| Status | Specify whether this resource provides services for external systems. If it is set to Disabled, this resource is not displayed in the resource list of authorized users (that is, this resource is inaccessible to users). | It is Enabled by default. |
- Complete the settings in the Server and App section. The configuration methods are as follows:
a) Click the List icon in Server to enter the Server page. Select the Windows Server collection, the Windows Server app server individually managed by VDC, or the desktop app server resource created by VDC, where the apps to be published are located, and click OK to save the configuration.
b) In Program Path, choose Select from list or Input manually as required. The difference between the two methods is as follows.
| Option | Description |
|---|---|
| Select from list | When this method is selected, VDC will obtain the program list from the Windows Server Start menu and automatically identify their startup paths for you to select from. However, if the app programs are not added to the Windows Server Start menu, VDC cannot identify them, and you can only select Input manually. |
| Input manually | When this method is selected, you are required to manually enter the app program paths on the Windows Server system. The value must indicate the exact location of the EXE files. For example, the program path of WeChat is C:\Program Files (x86)\Tencent\WeChat\WeChat.exe*. |
Their configuration methods are as follows:
- Select from list: Choose Select from list, click the List icon in App Programs to enter the App Programs dialog box, and select the app programs to be published.
- Input manually: Select Input manually and enter the EXE file installation paths of the apps that need to be published. Click Obtain Icon in Path, and VDC will automatically obtain the icons of the corresponding EXE files from the app servers.
c) If the icons obtained by VDC from the app servers in the previous step are incorrect, or if administrators want to change the icons, click Select Again and select default icons or upload new ones in the Icons dialog box.
d) If the published apps require special startup parameters to implement specific features, you can enter the parameters in Startup Parameters. For example, to set Google Chrome as the default browser upon startup, enter www.google.com in this field.
e) If the published apps include upload or download features that involve interaction with data stored locally on the app servers, you can configure the parameters in Working Directory to specify a default calling path that is different from the apps’ installation paths for the software to use these features.
- Complete the settings in the Advanced section as required, and click Save to complete the configuration for creating remote app resources.
The following table describes the parameters in the Advanced section.
| Parameter | Description |
|---|---|
| Window Launch Mode | Control the window launch modes of the published apps when opened on clients. By default, the Maximize Window mode is in use. Default: A program is opened based on the default settings of window launch mode. Maximize Window: A program is opened in a maximized window. |
| App Instance Limit | This item specifies how VDC handles repeated clicks on an app icon on the resource page, which consists of two modes: None and Single Instance Only. By default, the None mode is in use. None: When a running app is clicked, the app’s default settings determine whether a new or existing app window will be opened. Single Instance Only: Clicking a running app will open the existing app window rather than a new one. |
| Auto Create Desktop Shortcut | Specify whether a desktop shortcut for an app will be automatically created after a user logs in to VDI to enable quick access to the app. This feature only applies to China-made OSes with the remote app credential persistence feature enabled, such as Kylin V10 and UOS V20, and Windows virtual desktops with nested remote app resources enabled within the virtual desktop feature. |