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

Creating a Standby Server Group

Scenarios

You can create a standby server group within the active server group to enable service failover during emergencies or when active-group resources become insufficient.

Prerequisites

You have created an active server group by referring to Creating a Server Group.

Procedure

  1. Log in to the Workspace Application Streaming console as an administrator.
  2. In the navigation pane, choose Server Groups. The Server Groups page is displayed.
  3. Click the name of the active server group you created. The basic information page of the active server group is displayed.
  4. Click Creating a Standby Server Group in the upper right corner. The Create Standby Server Group page is displayed.
  5. Configure the parameters based on Table 1.

    Table 1 Standby server group parameters

    Parameter

    Description

    Example Value

    Server Group Name

    Enter a custom server group name.

    Naming rules:

    • The name can contain 1 to 64 characters.
    • Only letters, digits, hyphens (-), and underscores (_) are allowed.

    Server_Gp-Win2016

    Description

    Enter the description as required.

    -

    Region

    Select a region where the application is to be deployed.

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

    Same as that for the active server group

    Project

    Select the project where the application is to be deployed.

    Same as that for the active server group

    Session Mode
    • Single-session
    • Multi-session
      NOTE:
      • If no AD is connected, only the single-session mode is supported.
      • In AD scenarios, both the single-session and multi-session modes are supported.

    Same as that for the active server group

    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 through an intranet. If an AZ becomes faulty, other AZs in the same region will not be affected.

    Random

    OS

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

    Same as that for the active server group

    CPU Architecture

    Currently, only x86 is supported.

    Same as that for the active server group

    Package Type

    Select the office type and specifications based on the application type.

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

    General office

    -

    Image

    Select the image type and version to be used by the server.

    • A KooGallery image is a standard OS image provided by Workspace Application Streaming. It contains an OS and preinstalled applications. KooGallery images are visible to all users. They 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. You can customize pre-installed applications. A private image is visible only to its creator. Select the images generated in Image Creation.

    Private

    -

    Disk Type

    Select a disk type you need.

    -

    System Disk

    Select a disk type and set the disk size.

    For details about disk types and performance, see Disk Types and Performance.
    • 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 a multiple of 10.

    High I/O disk

    1020GB

    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 subnets.

    A VPC provides an isolated, configurable, and manageable virtual network environment for Workspace Application Streaming. Using a VPC makes it easier to manage and configure the internal network. Your cloud applications will be created in the selected VPC subnet so you can easily access 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:

    -

    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 connected.

    -

    Protocol Component

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

    NOTE:

    When this option is selected, any outdated component in your image will be upgraded during provisioning. This upgrade may increase the overall provisioning time.

    Selected

    Status
    • : The cloud service will not schedule available servers to access sessions.
    • : The cloud service will schedule available servers to access sessions.

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

      If the scaling policy switch is enabled, configure a scaling 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/(Max sessions per instance × Number of available instances)

        Number of available instances: the number of servers that are in the Ready status but not under maintenance

        Maximum number of sessions = Default number of sessions in the selected package + Number of additionally purchased sessions

      • You can create 1 to 10 sessions at a time. The system supports a maximum of 1 to 100 sessions in total.
      • Scale-In Policy: Elastic resources without session connections can be retained for a maximum of 5 to 120 minutes.

  6. Configure the purchase quantity and duration.

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

  7. Click Next: Confirm Configuration.

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

  8. Confirm the configuration and click Buy Now.

    • If 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. Then you can view the purchased server group and its servers on the Server Groups page.

Parent topic: Managing Server Groups