Help Center/ Workspace/ User Guide (Application Streaming)/ Administrator Operation Guide/ Server Group/ Managing Server Groups/ Creating a Server Group
Updated on 2024-03-15 GMT+08:00
View PDF

Creating a Server Group

Scenarios

Before publishing an application, the administrator needs to create a server group for deployment.

Prerequisites

You have created an image by referring to Creating an Image.

Procedure

  1. Log in to the Workspace Application Streaming console as an administrator.
  2. In the navigation pane, choose Server Groups.
  3. Click App Server Group.
  4. Configure the parameters based on Table 1.

    Table 1 Server group parameters

    Parameter

    Description

    Example Value

    Server Group Name

    Custom server group name.

    Naming rules:

    • 1 to 64 characters
    • Letters, digits, hyphens (-), and underscores (_) only

    Server_Gp-Win2016

    Description

    Enter the description as required.

    -

    Region

    Region where the application is to be deployed.

    Applications in different regions cannot communicate with each other over the intranet, and applications need to be managed by region. You are advised to create applications in the same region.

    CN South-Guangzhou

    Project

    Select a project to be deployed as planned.

    cn-south-1

    Session Mode
    • Single-session
    • Multi-session
      NOTE:
      • In scenarios where the AD server is not interconnected, only the single-session mode is supported.
      • In scenarios where the AD server is interconnected, the single-session mode and multi-session mode are supported.

    -

    App Group Type
    • Application: Users can access an application without installing it.
    • Desktop: A desktop application group is a complete virtual desktop. Users access the remote desktop.

    Application

    Associated Application Group

    Determine whether to select Auto create.

    NOTE:

    After selecting Auto create , enter the application group name. The name contains 1 to 64 characters, including letters, digits, hyphens (-), and underscores (_).

    Select Auto create.

    Billing Mode

    Select Yearly/Monthly or Pay-per-use as required.

    Pay-per-use

    AZ

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

    Random

    OS

    OS type of the server to be created. Currently, only the Windows OS is supported.

    Windows

    CPU Architecture

    Currently, only x86 is supported.

    x86

    Package Type

    Select the office type and specifications based.

    • General office: general office applications
    • Graphics-optimized: efficient graphics processing applications

    General office

    -

    Image

    Select the image type and version used by the server.

    • A KooGallery image is a standard OS image provided by Workspace Application Streaming and is visible to all users. It contains an OS and preinstalled applications. KooGallery images are highly stable and authorized. Windows Server 2016/2019 Datacenter edition (English) image is supported.
    • A private image is created based on a standard OS image file. It is visible only to the user who created it. You can customize pre-installed applications. Select the images generated in Creating an Image.

    Private

    -

    Disk Type

    Select a disk type.

    -

    System Disk

    Select a disk type and set the disk size.

    For details about the performance of different disk types, see EVS Overview.
    • 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.

    The disk size ranges from 10 GB to 1,020 GB. The value must be an integer multiple of 10.

    High I/O Disk

    1020

    Network

    Select a virtual network. If applications need to be available in multiple service subnets, select multiple subnets or click Click here to manage subnets under network configuration to create a subnet.

    A VPC is an isolated, configurable, and manageable virtual network environment for cloud applications, facilitating internal network management and configuration. Your Workspace Application Streaming service will be created in the selected VPC subnet to facilitate your access to the resources and applications on the enterprise intranet.

    -

    Additional Sessions

    Additional sessions for a single server. The value varies with the server package specifications.

    NOTE:

    After a server group is created, the number of sessions cannot be changed.

    -

    Session Scheduling Policy
    • Number of Session Connections: Session connections of the server. Set this parameter based on the server package specifications.
    • CPU Usage: CPU usage of the server. The value ranges from 1 to 100.
    • Memory Usage: Memory usage of the server. The value ranges from 1 to 100.
      NOTE:

      If any metric of a server exceeds the threshold, no more sessions are accepted. The policy schedules available servers in the server group to establish sessions.

    -

    OU Name

    If an OU is created on the Windows AD server, you can select the OU to be used.

    NOTE:

    This parameter is required only when the AD is interconnected.

    -

    Protocol Component

    HDP server access component, which is installed in the APS instance and used to communicate with the Workspace Application Streaming client.

    NOTE:

    After this option is selected, if the version of the component in your image is outdated, the component will be upgraded during provisioning, which may prolong the provisioning.

    Check the box

    IP Virtualization
    • : IP virtualization is disabled.
    • : IP virtualization is enabled.
      NOTE:
      • If IP virtualization is enabled, each session is assigned a different IP address. The number of virtual IP addresses pre-assigned by the server is the same as the maximum number of sessions in the package.
      • Maximum number of sessions = Default of sessions + Additional sessions
      • This parameter can be configured only in multi-session mode.

    Scaling Policy
    • : The scaling policy is disabled.
    • : The scaling policy is enabled.

      If the scaling policy is enabled, configure the policy.

      • Scale-out policy: When the session usage exceeds x%, pay-per-use elastic resources are automatically created.
        NOTE:

        Session usage = Sum of instance sessions in use/(Maximum number of instance sessions × Available instances)

        Available Instances: number of servers in the Ready status that are not in under maintenance.

        Maximum number of sessions = Default of sessions of the selected package+ Additional sessions

      • x (range: 1–10) sessions can be created at a time. A maximum of x (range: 1–100) sessions can be created.
      • Scale-in policy: Elastic resources without session connections can be retained for a maximum of x (range: 5–120) minutes.

  5. Configure the purchase quantity and duration.

    If the billing mode is Yearly/Monthly, configure the required duration.

  6. Click Next step: Confirm Settings.

    If the billing mode is Yearly/Monthly, you can choose whether to automatically renew the subscription.

  7. Confirm the configuration and click Buy Now.

    • The billing mode is Pay-per-use. After the resource is created, you can view the purchased server group and its servers on the Server Groups page.
    • If the billing mode is Yearly/Monthly, pay for the order first and view the purchased server group and its servers on the Server Groups page.

Parent topic: Managing Server Groups