Because vCenter Server and View Composer are often installed on the same virtual or physical machine, some preparation tasks apply to both.

Preparing for Upgrades That Include vSphere

If you are upgrading vCenter Server in addition to upgrading to the latest version of Horizon 7, you must consult the VMware vSphere Upgrade Guide and perform the following tasks in the following order:

  1. Verify that the virtual or physical machine meets the system requirements for the version of vCenter Server that you want to upgrade to.
  2. Verify that the virtual or physical machine on which the current View Composer is installed meets the security requirements for the new version.

    See Upgrade Requirements for View Composer.

  3. If vCenter Server is installed in a virtual machine, take a snapshot of the virtual machine.

    For instructions on taking snapshots, see the vSphere Client™ online help.

  4. If the computer name is longer than 15 characters, shorten the name to 15 or fewer characters.
  5. Back up the vCenter Server database and the View Composer database.

    For instructions on performing a database backup, see the documentation from your database vendor.

  6. Verify that the database server is compatible with the version of vCenter Server you plan to use.

    For example, if the database server is Oracle 9i, you must upgrade.

  7. Verify that the database is compatible with the new version of View Composer.

    View Composer supports a subset of the database servers that vCenter Server supports. If you are already using vCenter Server with a database server that is not supported by View Composer, continue to use that database server for vCenter Server and install a separate database server to use for View Composer and Horizon 7 database events.

  8. Make a copy of the folder that contains TLS certificates.

    This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.

  9. Document the IP address and system name of the machine on which vCenter Server is installed.
  10. For all linked-clone and instant-clone desktop pools, use Horizon Administrator to disable provisioning of new virtual machines.

    For linked-clones, because View Composer might be upgraded during a different maintenance window than its desktop pools, provisioning must be postponed until both components are upgraded.

  11. If any linked-clone desktop or instant-clone desktop pools are set to refresh the OS disk on logoff, use Horizon Administrator to edit the Desktop/Pools settings for that pool and set Delete or refresh machine on logoff to Never.

    For linked-clones, this setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop on which Horizon Agent has not yet been upgraded.

  12. If any linked-clone or instant-clone desktop pools are scheduled to do a refresh, recompose, or image push operation, use Horizon Administrator to cancel these tasks.

Preparing for Upgrades of View Composer Only

If you are upgrading only View Composer and are not upgrading vCenter Server, you must perform the following tasks:

  1. Verify that the virtual or physical machine on which the current View Composer is installed meets the security requirements for the new version.

    See Upgrade Requirements for View Composer.

  2. If View Composer is installed in a virtual machine, take a snapshot of the virtual machine.

    For instructions on taking snapshots, see the vSphere Client online help.

  3. Back up the View Composer database.

    For instructions on performing a database backup, see the documentation from your database vendor.

  4. Verify that the database is compatible with the new version of View Composer.

    View Composer supports a subset of the database servers that vCenter Server supports. If you are already using vCenter Server with a database server that is not supported by View Composer, continue to use that database server for vCenter Server and install a separate database server to use for View Composer and Horizon 7 database events.

  5. Document the IP address and system name of the machine on which vCenter Server is installed.
  6. For all linked-clone desktop pools, use Horizon Administrator to disable provisioning of new virtual machines.

    Because View Composer might be upgraded during a different maintenance window than its desktop pools, provisioning must be postponed until both components are upgraded.

  7. If any desktop pools are set to refresh the OS disk on logoff, use Horizon Administrator to edit the Desktop/Pools settings for that pool and set Delete or refresh machine on logoff to Never.

    This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop on which View Agent has not yet been upgraded.

  8. If any desktop pools are scheduled to do a refresh or recompose operation, use Horizon Administrator to cancel these tasks.