Skip to content

Version Management

Client software packages that end users need to install, and various agent software packages that need to be installed inside cloud desktops, can be manually distributed and deployed during environment setup. As software products evolve, these packages will face frequent iterations.

The Version Management function of the xSpace management backend centralizes uploading, automatic distribution, and forced update mechanisms, eliminating tedious on-site operations and enabling rapid, automated software version updates.

1. Management Responsibilities and Scope of Impact

  • Management Entity: Both cloud terminal (client) and agent versions are maintained by the system administrator.
  • Scope of Effect: The final version upgrade measures will uniformly take effect for all users and desktop resources under all tenants in the xSpace system.

2. Core Operation Logic: Why Prioritize Version Management?

The first operation after system login is usually version management, which is actually a continuation of version updates during system deployment. The main reasons are as follows:

  1. Agent Version Update: Typically, the agent version in pre-built cloud desktop images is old. Since VDI desktop images are not updated with every new release, the agent version needs to be uniformly upgraded through the management component.
  2. Thin Client Version Update: Due to production cycle limitations, the client versions of thin clients shipped from the factory are often not the latest stable versions and cannot be returned to the production line for client version updates.
  3. Provide Official Download Channels: The management component needs to provide a unified download address for PC clients and mobile apps to end users through the version management function.

3. Functional Mechanisms

  • Centralized Upload: Upload the latest software packages centrally to the management component's version file repository.
  • Automatic Distribution: Use the version file download channel to automatically push version packages to various terminals.
  • Automated Update: Ensure version consistency across the entire system environment through forced update mechanisms.