Skip to content

Terminal Usage

Regardless of whether the xSpace client software is installed on a PC, laptop, or thin client, the interface appearance after launch remains consistent, and the processes for first-time login and daily use are largely the same.

1. Core Operation Process

From a timeline perspective, terminal usage mainly involves the following four key stages:

  1. Access Settings: Configure the cloud platform address. Configure the management component address (IP or domain name) to be connected to the client to establish communication foundation.

  2. Login Authentication: Identity verification. Use password, SMS, or other login methods to log in to xSpace through identity verification.

  3. Desktop Management: Enter the desktop card list. View cloud desktop resources under your personal account, and perform desktop power management (power on, power off, restart) or connection settings here.

  4. Connect and Disconnect: Use the desktop. Click the connect button on the desktop card to connect to the cloud desktop for work; disconnect after use.


2. Network Requirements (Important)

To ensure the normal operation and connection stability of cloud desktops, terminals must maintain real-time network connectivity throughout their usage cycle and meet the following communication requirements:

  • Access Management Component: The terminal must be able to normally access the management component's API interface (i.e., the cloud platform address configured in access settings).
  • Connect to Agent: The terminal needs to be able to directly access the cloud desktop's agent, or be able to connect to the cloud desktop's agent via an access gateway.
  • Continuity Requirements: The terminal must remain connected to the network. Network interruptions during either the login phase or the desktop operation phase will lead to abnormal desktop connections or automatic disconnections.

Tip: While the mobile client installed on mobile phones or tablets may have slight differences in appearance, the actual operation logic remains consistent with the usage steps described above.