I think I did not get your answer at 100%. The document to follow implies upgrading all the components you have for that solution in their respecitve order. You could have just a Connection Server and some desktops or you could have Workspace ONE Access, UAT, etc.
Give us more insight of your current platform.
I am planning on doing a similar upgrade this week (7.10 -> 7.13) and would be interested in hearing about potential issues with the upgrade from others.
I have 3 Connection Servers, 2 behind a load balancer and 1 standalone, DEM 9.9 and App Volumes 2.18. I plan on doing DEM and AV at a later date.
Some of takeaways I have so far;
Horizon 7 -7.13 Upgrade Guide -> https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-upgrades/GUID-E3607442-8936-49A8-97B4-722D0...
I am told that going to 7.13 from 7.10 doesn't work without problems so I am told to go from my 7.4 to 7.10. Where can I download the 7.10 software? I cannot seem to find a link for this.
You can download from the Download page.
We are on version 7.12 right now and the HTML5 interface is quite slow at times especially in a desktop pool when the Machines list with View Composer info is active. Just entering search details bogs the page down (where other tabs in my browser are just fine).
I did the upgrade 2 days back from Horizon 7.12 > 7.13.
Take snapshot of your existing Connection Server
its straight forward process, go to the settings > server > Connection server and disable the one which you are going to upgrade.
Complete the process one by one each and enable the one upgraded, along with that it will upgrade the HTML access also.
After upgrade and if you login to Horizon console don't panic it will take some time to sync your Pools and names.
We just upgraded from 7.10.2 to 7.13.1 on Tuesday evening. We had to upgrade Composer server, Connection server and Security server in a very particular order, and it also required a PowerCLI script, since we're not on UAG yet. (Thank you, Chris Halstead, for the workaround -- I'll post a link below.) Our vSphere & ESXi & vmware Tools were already compatible so we didn't have to make any changes there (6.7). Our Horizon 8 clients work with 7.13.1. Choke points for us were: (1) certificate on Composer server and (2) recomposing about 80 pools at once (which we scripted with PowerCLI) and (3) a mistake I made with the parent image (chose local datastore on ESXi host for OS instead of shared datastore). Next morning we had a few "problem vm's" to delete and vmware support was very helpful. Please be careful and be prepared.