Upgrade horizon 7

[fborges555]

hi gurus

as you can tell by my previous post, I am still new to this, I have never upgrade horizon but this will be my first, has anyone here have like a step by step process that I can follow ,so I don't screw up and it goes smoothly.

Thanks a bunch

[a_p_]

Upgrading is actually a pretty straight forward task.

However, it depends on your environment, i.e. it's important to ensure that it meets the requirements for the new version.

• Which vCenter Server, and ESXi versions/builds do you use?
• Which Horizon Version/build do you currently use?
• To which version do you want to upgrade?
• How does the Horizon environment look like in regards of Horizon Server workloads (composer, connection servers, security servers, ...)?

André

[sjesse]

This page should be your friend for every upgrade. Check your current versions  and then check what you intent to upgrade

VMware Product Interoperability Matrices

[BenFB]

This is our process.

Prerequisites

1. Verify the upgrade path is supported.
   1. https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#upgrade&solution=23
2. Verify compatibility of the VMware Components
   Update sequence for vSphere 6.0 and its compatible VMware products (2109760)
   Update sequence for vSphere 6.5 and its compatible VMware products (2147289)
   Update sequence for vSphere 6.7 and its compatible VMware products (53710)
   
   1. UAG
      https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&23=&326=
   2. vCenter Server
      https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&23=&2=
   3. ESXi
      https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&23=&1=
   4. VMware Tools
      https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&23=&139=
3. Verify compatibility with Zero/Thin Clients.
   1. VMware Compatibility Guide - Horizon (Thin Clients) Search
4. Verify that there are no pending restart on the Connection Servers/Composer Server. Restart the Connection Servers/Composer Server at least once prior to starting the upgrade.
5. Verify AD LDS replication is healthy.
   1. From each connection server run the following command
      C:\Windows\System32\repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int
      Forcing replication between ADAM databases (1021805)
      View Connection Server fails to replicate (2014488)
      Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381...
6. Submit change control for the upgrade.
7. Download the installers and copy them to the server.

Upgrade process

1. Verify all of the prerequisites
2. Verify there are no scheduled or pending tasks.
   1. Use PowerCLI on the connection server to check for tasks.
      If any exists make sure they will not run during the upgrade.
      If there are no scheduled tasks you will see "Get-DesktopVM : No output object matching the ComposerTask parameter".
      Get-DesktopVM -ComposerTask attachUdd,detachUdd,mkChkPoint,rebalance,refresh,replaceUdd,resync | select Name,pool_id,composerTask
3. Disable provisioning
   1. Wait for all pending tasks to be completed in vCenter (Disk space reclamation, refresh, etc...).
4. Backup the ADAM/Composer database and snapshot the servers (Performing an end-to-end backup and restore for VMware View Manager (1008046)).
   1. Shutdown the Connection Servers
   2. Shutdown the Composer server
   3. Take a snapshot of the servers.
   4. Take a backup of the SQL database
   5. Power on the Composer server. Wait for the server to boot to the login screen before proceeding to the next step.
   6. Power on the Connection Servers one at a time. Wait for the server to boot to the login screen before powering on the next server.
5. Log back in to Horizon Admin, take a manual backup of the Connection Servers.
6. Verify AD LDS replication is healthy.
   1. From each connection server run the following command
      C:\Windows\System32\repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int
      Forcing replication between ADAM databases (1021805)
      View Connection Server fails to replicate (2014488)
      Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381...
7. Upgrade the Composer Server
   1. Login to the Composer Server
   2. Run the installer
   3. Enter the password for the database connection.
   4. Select "Use an existing SSL certificate"
      1. You can check the existing certificate that is being used by the composer server here.
         https://composerserverip:18443/
   5. Once the installation completes successfully, restart the server.
8. Remove one of the Connection Servers from the load balancer pool.
   1. Login to the server
   2. Run the installer
   3. Once the installation completes successfully, restart the server.
   4. Point a client to the Connection Server, verify you can login successfully.
   5. Add the Connection Servers that were just upgraded back to the load balancer pool.
   6. Remove the next Connection Server from the load balancer pool.
   7. Repeat the above steps on any additional connection servers.
9. Verify AD LDS replication is healthy.
   1. From each connection server run the following command
      C:\Windows\System32\repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int
      Forcing replication between ADAM databases (1021805)
      View Connection Server fails to replicate (2014488)
      Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381...
10. Wait minimum of 24-48 hours. Purge snapshots of Connection Server and Composer VMs.
11. Upgrade VMware Tools & Horizon Agent on parent VMs.
12. Recompose pools to the new image.

[fborges555]

Thanks AP

1) I have vcenter appliance 6.5 / VMware ESXi, 6.5.0, 7967591

2) I have Horizon 7.0.1 build-3988955

3) I would like 7.5 or later

4) I have composer,connection server , security server.

I think I have almost all together except for the steps and the security server process.

Thanks again for jumping in.

[fborges555]

BenFB

I am a little lost as what to do with security server that I have paired with connection broker , do you have steps for this one that I can follow

Thanks a bunch all for the help

[BenFB]

I don't use Security Servers so I can't comment on that. I'd advise completing this upgrade and then migrating from Security Servers to Unified Access Gateways (UAG). They will eventually replace the Security Server entirely and offer additional flexibility (They eliminate the 1:1 pairing with connection servers and allow for complete load balancing).

[a_p_]

I haven't used security servers for a while now, but they should basically be handled like connection servers.

Regarding UAG: Please note that as of UAG v3.4, VMware unlocks some features - which were available in previous versions - depending on the Horizon license/license. If you are for exapmle using Horizon Standard, and use tokens for logon, you will need to upgrade to Horizon Advanced in order to have this feature with UAG.

André

[drtvmware]

Have same kind of scenario, we are using Citrix XenApp 7.15 LTSR on Citrix HyperVisor.

In process of moving hypervisor and published to Horizon.

We are only publishing apps and licensed for Horizon App Standard.

Already setup Cluster running 6.7 of 2 Host for now.

Can we use same cluster for Horizon with same vCenter Server 6.7?

It means setup Connection server?

RDSH pool vm's for publishing apps

Do we need Composer ? What other servers needs to setup

[BenFB]

You only need Composer if you are doing linked clones.