Manage hardware terminals

Prerequisites

• The hardware terminal version is V7.5 or later.

  Important

  If the hardware terminal version is earlier than V7.5, the terminal can adhere only to the default system policy after onboarding. It cannot adhere to any custom policies that you create.

• You can create custom terminal groups and bind custom terminal policies to them to manage terminal behavior and experience. The system provides a default root group and policy. If you want to use custom groups and policies, you must create them first. For more information, see Manage terminal groups and policies.

Procedure

You can onboard hardware terminals in one of the following ways.

After a terminal is successfully onboarded, the logon screen automatically displays the organization ID, so users no longer need to enter it. End users cannot change the organization ID.

Common operations

After you onboard a hardware terminal, you can perform the following operations:

• Search for hardware terminals by the following criteria. Fuzzy search is supported.

  • Terminal SN

  • Terminal alias

  • IP address

  • Last logged-on user

• Set a terminal alias by using one of the following methods:

  • In the Terminal Alias column for the target terminal, click the icon and enter a custom name.

  • In the terminal list, click the SN of the target terminal. On the hardware terminal details page, edit the terminal alias.

• Shut down a hardware terminal.

  • Single operation: In the Actions column for the target terminal, click Shut Down. You can also choose to shut down the cloud desktop.

  • Batch operation: Select multiple target terminals and click Shut Down at the bottom of the list.

• Restart a hardware terminal.

  • Single operation: In the Actions column for the target terminal, click Restart. You can also choose to restart the cloud desktop.

  • Batch operation: Select multiple target terminals and click Restart at the bottom of the list.

• Enable remote diagnosis.

  The terminal must be connected to the network to use this feature.

• Force a remote upgrade.

  You can perform a remote upgrade on a hardware terminal. This feature is available only for hardware terminals that run V7.0.5 or later. When you configure a remote upgrade, you can select a restart method, such as requiring a manual restart or forcing an immediate restart after the download.

  Note

  The restart action applies only to the terminal and does not restart the cloud desktop.

  The restart immediately after download option is a forced action that end users cannot refuse. Use this option with caution.

• Export terminal information.

  Select the target terminals and click Export at the bottom of the list. The exported spreadsheet file contains detailed information about the selected hardware terminals.

Prerequisites

To restrict a hardware terminal to specific end users, you must first enable trusted device authentication. For more information about how to enable trusted device authentication, see Trusted device authentication.

Procedure

1. Log on to the EDS enterprise console.

2. In the left-side navigation pane, choose Clients > Hardware Terminals.

3. On the Hardware Terminals page, find the target terminal, click the ⋮ icon in the Actions column, and then select restricted logon users.

   Note

   The restricted logon users feature and the password-free logon feature are mutually exclusive. If password-free logon is configured for a hardware terminal, you cannot add restricted logon users.

4. On the View/restrict logon users panel, click the Convenience Account tab or the AD Domain Account tab based on the account type of your end users.

5. From the Addable Users list, select a user and click Add User.

   Note

   If you select AD domain account, you must first select an AD domain from the drop-down list.

   • To add more users, select other users from the Addable Users list and click Add User.

   • To remove a user, select the user from the restricted logon users list and click Remove User.

Related operations

If you want to allow end users to log on only to the hardware terminals that you specify, you must enable trusted device authentication and add restricted logon terminals for the users. For more information, see Add a restricted logon terminal for a convenience account and Add a restricted logon terminal for an AD user.

Prerequisites

• Make sure that you have created at least one level-1 group under the root group and have onboarded at least one supported hardware terminal in the level-1 group. Otherwise, you cannot publish the customization task.

• Make sure that the onboarded hardware terminal is connected to the network after it receives the customization task. Otherwise, the customization will not take effect.

Limitations

This feature applies only to WUYING Cube, WUYING Ark, and WUYING Ark Pro terminals that run version V7.7 or later. WUYING Ark Pro does not support custom system startup logos.

Invalidation mechanism

• The interface customization task is deleted or overwritten.

• The hardware terminal is moved to another terminal group that does not have an interface customization task.

• The hardware terminal is removed from management. Note: An onboarded terminal that is restored to factory settings still applies the customization after it connects to the network.

Procedure

1. Log on to the EDS enterprise console.

2. In the left-side navigation pane, choose Clients > Hardware Terminals.

3. In the upper-right corner of the Hardware Terminals page, click Interface Customization.

4. On the Interface Customization page, click Create Customization Task.

5. On the Interface customization tab of the Create Customization Task panel, configure the following items.

   Customization item	Description	Requirements
   Basic information
   Customization task name	Enter a name for the interface customization task.	The name can be up to 30 characters in length.
   Logo customization
   System startup logo	On the Interface customization tab, click the icon next to a Logo customization item to preview a diagram showing the logo and confirm whether you want to customize it. The options include: WUYING Logo Custom Logo: Click Upload Image, select an image that meets the requirements, and click Open. Note If the preview image is not clear, right-click the image in the diagram and click Open Image In New Tab.	A custom logo must meet the following requirements: Format: BMP Dimensions: 372 × 80 px Size: ≤ 5 MB Note Only WUYING Cube and WUYING Ark can apply this configuration. WUYING Ark Pro does not support custom system startup logos.
   Top-left logo		A custom logo must meet the following requirements: Format: PNG Dimensions: width ≤ 200 px, height ≤ 38 px Size: ≤ 5 MB
   Bottom-left menu logo		A custom logo must meet the following requirements: Format: PNG Dimensions: 128 × 128 px or 258 × 258 px Size: ≤ 5 MB
   Wallpaper customization
   Lock screen wallpaper	On the Interface customization tab, click the icon next to a Wallpaper customization item to preview a diagram of the wallpaper and confirm whether you want to customize it. The options include: WUYING default wallpaper Custom wallpaper: Click Upload Image, select an image that meets the requirements, and click Open.	A custom wallpaper must meet the following requirements: Format: JPG Dimensions: 1920 × 1080 px Size: ≤5 MB
   Pre-logon wallpaper
   Post-logon wallpaper

6. On the Interface customization tab, click Preview. After you confirm the preview, click Close and then click Next.

7. On the Preview and select phased release scope tab of the Create Customization Task panel, select a scope for the phased release. Select the target level-1 group and click Phased release.

   Note

   Only level-1 groups can be selected for a phased release. The root group, level-2 groups, and empty groups are not supported.

8. Full release:

   Note

   • A customization task can be fully released only after it has been released in phases. The scope for a full release cannot be selected. By default, the root group is used as the scope.

   • After a full release is successful, previous customization tasks become invalid. Onboarded terminals are automatically updated after they connect to the network.

   1. On the Phased release tab of the Create Customization Task panel, confirm the phased release status and click Full release.

   2. In the Confirm full release of customization task dialog box, confirm the information and click OK.

Related operations

Version detection and download

The new version detection feature is enabled by default. You can let end users decide whether to download updates, or you can centrally control whether to automatically download updates and specify the schedule for automatic downloads.

1. Log on to the EDS enterprise console.

2. In the left-side navigation pane, choose Clients > Hardware Terminals.

3. In the upper-right corner of the Hardware Terminals page, click Configure Terminal Update.

4. On the Hardware Terminals tab of the Client Updates page, click Edit Upgrade Configuration.

5. In the Edit Upgrade Configuration dialog box, set the following parameters as required:

   • New Version Detection: This feature is enabled by default and cannot be disabled. Hardware terminals automatically detect new versions and perform automatic downloads, reminders, installations, and restarts based on the download and installation settings.

   • Download Settings: These settings control whether the system automatically downloads the update package and sends reminders when a new version is detected.

     • Select a method for Download Available Update Packages.

       • Customized by End User: End users can configure the upgrade package download method in Hardware > Settings.

       • Managed by Administrator: The administrator decides whether to enable automatic downloads. If enabled, the hardware terminal automatically downloads the installation package when an available upgrade is detected. This takes effect after the terminal restarts. The administrator can configure the execution schedule and time for automatic downloads.

         Note

         If you select Managed by Administrator, end users cannot modify upgrade-related configurations on the terminal. For all time-related upgrade settings, the actual execution time is based on the hardware terminal's system time. For example, if the terminal's time zone is set to Bangkok, the execution time is based on the Bangkok time zone.

     • If you enable Automatically Download Available Update Packages, you must configure the download schedule and time.

       • During the configured schedule and time, the upgrade policy initiates automatic downloads and sends reminders.

       • Outside the configured schedule and time, automatic downloads and reminders are disabled, but users can still manually download and install the package.

     • If you disable automatic downloads of available update packages, you must then decide whether to enable New Version Reminder.

       • If enabled, a pop-up window immediately reminds the end user to manually download the new version when the system detects one.

       • If disabled, the system does not send reminders. To upgrade to a new version, the end user must go to the Hardware > Settings > Upgrade page to manually check for and download the new version.

   • Installation Settings

     After the download is complete, the terminal must be restarted to complete the upgrade. To facilitate management, you can configure Auto-restart For Installation to prevent delays from users who postpone the restart.

     Note

     If enabled, the terminal automatically restarts and installs the update during the administrator-specified time window, provided that the update package has been downloaded and the terminal is powered on and connected to the network.

     Auto-restart for installation restarts only the terminal, not the cloud desktop.

     • If enabled, after the new version is downloaded, the system automatically restarts and completes the installation according to the Restart time window settings specified by the administrator. The user can decline the restart, and the installation task is postponed to the next day.

     • If disabled, the end user must manually restart the terminal to complete the installation.

6. At the bottom of the dialog box, click Confirm.

Upgrade detection methods

To ensure that terminals can use the latest features, Elastic Desktop Service Enterprise provides the Internet upgrade method and the local area network (LAN) upgrade method. You can choose the method based on your business needs.

• Internet upgrade method: The terminal can directly download new version upgrade packages from the internet. This method is suitable for scenarios with good network conditions and is the default upgrade method for hardware terminals.

• Local area network (LAN) upgrade method: The terminal automatically detects and downloads new version upgrade packages through a WUYING Gateway. This method can effectively prevent network bandwidth congestion caused by batch downloads of upgrade packages.

  • How to enable: For more information, see Configure a gateway for terminal upgrades (WUYING x Panabit).

    1. Purchase a specified model of WUYING Gateway from Alibaba Cloud Marketplace.

    2. In a level-1 group, generate a WUYING Gateway binding code and bind it to the specified WUYING Gateway. Each binding code can be used only once and becomes invalid after it is successfully used.

    3. After the binding is complete, the upgrade detection method for all terminals in this group automatically switches from Internet upgrade to LAN upgrade.