System state and user data in non-persistent environments need to be designed separately. Standard image updates or session recycling should not accidentally clear work results that should be retained. For specific implementation, you need to check the current components and versions of the project.

Who this is for:Regular readers and small teams who are working on Omnissa Horizon and need to solve specific problems in the title. Data verification date: 2026-10-26.

First, identify the product line

The Omnissa product catalog lists Horizon 8, Horizon Cloud and other digital workspace components separately. Horizon Cloud's documentation discusses images, desktop pools, applications, and user assignments; therefore "installing the Horizon client" does not equate to having a cloud PC that can be logged into.

Persistent and non-persistent desktops determine preservation strategy

List rebuildable software, user settings and non-losable files, and specify the save location one by one. Use the sample to walk through logout, reconnection, and image update, and check the results in another environment. If a desktop reconnection is normal, it cannot be assumed that the data must exist after reconstruction.

Persistent desktops are typically designed around long-term retention of personal environments, while non-persistent desktops are more like a standard environment with resources allocated on a per-session basis. Both can have data saving schemes, but the saving location and dependency conditions are different. Do not directly interpret "the desktop is restored after exiting" as a service failure, nor should a successful reconnection prove that all user settings are permanently retained.

Three categories of status need to be listed first: systems and applications that can be generated repeatedly, personal data that must be retained, and temporary files that are only used in this session. Specify the storage method and responsible person for each type of status. During the test, the four actions of disconnecting, logging off, restarting, and rebuilding were performed to confirm which operations would trigger the restore; before actually executing the test that would clear the data, worthless samples should be used and backed up.

Check each requirement for your task

  1. Confirm whether the desktop is a personal persistent environment or a pooled non-persistent environment.
  2. Specify the storage locations for system, personal data and temporary files respectively.
  3. Use the sample to check the difference between disconnection and logout, and complete independent export of important data.

Migration requires an old environment that can be returned to

It’s easier to spot problems with two rounds of verification: the first to check the process with a sample, and the second to check the results with a real, approved working copy. The frozen content and the content that can still be modified in the migration window should be clear to avoid version conflicts caused by editing on both sides. After the switch is successful, keep the necessary rollback time, confirm that the data is complete, and then clean up the old resources according to the retention policy.

Where the conclusion applies and what to do next

Historical VMware Horizon data must be checked with the current Omnissa product version; Horizon 8 and Horizon Cloud cannot replace tutorial by name alone.

This article is based on public information. We have not purchased or tested the product. The scenarios describe ways to verify suitability, not customer case studies. Features and terms depend on the current official documentation for the relevant version.

Official sources and further reading

Read more:Cloud PC knowledge hub · Find an article for your question · Omnissa Horizon product line identification

Related questions to explore

Back to the brand and product knowledge directory · Browse cloud PC topics