You can upgrade the Horizon FLEX system from earlier Horizon FLEX versions.

Prerequisites

  • All Mirage servers are shut down.
  • Perform the appropriate preparation for a Mirage upgrade. See information related to upgrade preparation in the VMware Mirage Installation Guide.
  • On the Mirage Web Management server, back up the web.config file in the Rvm directory. The default location of the directory is C:\Program Files\Wanova\Rvm.

    When you upgrade the Mirage Web Management server, see Step c, the system replaces the web.config with a new version, which deletes the customized settings in the file. After the upgrade, update the web.config file by applying the customized settings in the backed-up file to the new file.

    Note:
    • Except for parameters that affect the customized features mentioned in this prerequisite, do not change the parameters in the web.config file, especially the RvmPolicyVersion parameter. The supported policy versions are 6, 7, 8, 9, 10, and 11. If you change the policy number to an unsupported version, users might lose access to Horizon FLEX virtual machines.
    • If you deploy the Horizon FLEX Admin Console and Horizon FLEX Policy Server on different ports, back up the web.config file in the RvmAdmin directory instead of in the Rvm directory. The default location of the RvmAdmin directory is C:\Program Files\Wanova\RvmAdmin.

Procedure

  1. Download the Horizon FLEX Server and Horizon FLEX Client installation files for the upgrade version.
  2. Upgrade all Horizon FLEX clients to the version that is compatible with the version to which you upgrade the Horizon FLEX Server.
    • Provide end users with the installer file for the Fusion Pro or Workstation Player upgrade version. Alternatively, you can instruct them to download the software from the VMware website.
    • Upgrade the Horizon FLEX Clients by using a mass deployment.
  3. Upgrade the Horizon FLEX Server component.
    1. To upgrade the Mirage Management Server, double-click the mirage.management.server.64x.buildnumber.msi file in the server folder.
      By default, the configuration settings you selected during the initial installation are applied. You can change the configuration settings during the upgrade process.
    2. To upgrade the Mirage server.
      • Double-click on mirage.server.64x.buildnumber.msi file. Use this option if you are a local administrator and User Account Control (UAC) is enabled.
      • Access the command prompt as an administrator and run the mirage.server.64x.buildnumber.msi file. Use this option if you are not a local administrator and UAC is enabled.
      By default, the configuration settings you selected during the initial installation are applied. You can change the configuration settings during the upgrade process.
    3. To upgrade the Mirage Web Management.
      • Double-click on the mirage.WebManagement.x64.buildnumber.msi file. Use this option if you are a local administrator and UAC is enabled.
      • Access the command prompt as an administrator and run the mirage.WebManagement.x64.buildnumber.msi file. Use this option if you are not a local administrator and UAC is enabled.
      Continue with no change.
    4. If you use Mirage to manage your Windows virtual machines, follow the instructions for upgrading from the previous Mirage version in the VMware Mirage Administrator's Guide.

What to do next

For complete Mirage upgrade instructions, see the VMware Mirage documentation at https://www.vmware.com/support/pubs/mirage_pubs.html.
Note: Do not select the Create new storage areas when upgrading the Mirage Management Server. If you select this option and enter the path to the original storage area, your entire Mirage installation is deleted. For example, the base layer, app layer, and CVD data are deleted and become irretrievable if a backup is unavailable.

See Installing the Horizon FLEX Client for End Users for information on using a mass deployment to provide the Horizon FLEX Client to end users.