Please provide your feedback in this short Flings' survey.
fling logo of Horizon Reach

Horizon Reach

version — February 22, 2021

Contributors 1

View All

Comments 186

  • profile picture of Chris Koch
  • profile picture of Andrew Morgan
  • profile picture of Agalliasis
  • profile picture of Andrew Morgan
  • profile picture of Agalliasis
  • profile picture of Andrew Morgan
  • profile picture of Andrew Morgan
  • profile picture of Talent
View All


Warning: Horizon Versions 7.10 through 7.12 have a known issue which can cause Horizon Reach to trigger a low memory issue on the Horizon Connection Server.

For Horizon 7.10, ensure to deploy Horizon 7.10.2. For 7.11 and 7.12, please refer to the following document here.

Warning: Please do not deploy multiple instances of Horizon Reach which connect to the same Cloud Pod Architectures. Horizon Reach's discovery is intensive and should only be run from a single instance. Running multiple instances can and will add load to your connection servers.

Horizon Reach is a web based, monitoring and alerting fling for VMware Horizon On Prem deployments. Horizon Reach is designed to tackle the disconnect in Enterprise environments wherein each Pod in a Cloud Pod Architecture is its own technology domain and fault domain, or a customer is running multiple, disconnected pods, outside of a Cloud Pod Architecture, but would still like to treat them all as one unit of compute.

Often when troubleshooting these fault domains, it can feel like a game of “Whack a mole” jumping from Pod to Pod trying to find a pertinent session, alarm or event to the problem your user is describing.

Reach tackles this issue by performing health checking and gathering pertinent errors from each separate environment and displaying them all in a single place, creating an easy location for administrators to monitor the environment, along with providing a detailed first step in the troubleshooting process.




vCenter Hosts

Unified Access Gateway

Pool View

Sessions View


In order to successfully and easily deploy Horizon reach, you will need:

Supported servers

  • Windows Server 2016
  • Windows Server 2019
  • Windows 10 1809 (x64) Note: don’t use this for large scale

VMware Horizon (all license editions)

  • VMware Horizon 7.5.1 (bare minimum)
  • VMware Horizon 7.6 (better)
  • VMware Horizon 7.10 (best)


With the release of 1.1, a new installer is available instead of the old zip file and PowerShell script installation process. If you wish to upgrade from a previous version, please follow the below steps:

Upgrading from pre 1.1.2x:

  • Stop the existing Reach service
  • Run the “Remove-reachservice.ps1” PowerShell script from the current directory
  • Backup the directory (zip it).
  • run the new installer.
  • stop the new service.
  • copy serviceconfiguration.json and local.db from the old installation folder to the new.
  • Start the new service.
  • Logon and make sure it’s all working.
  • If all ok, delete the old location.


  • Uninstall the latest version
  • Run “Install-reachservice.ps1” from the old installation directory



  • Added support for Horizon 8.1
  • Bugfixes

Version 1.1.x is a massive update, below is a list of some of the major changes:

Unified Access Gateways can now be monitored by Horizon Reach directly including support functions:

  • Download configuration
  • Download logs

User Sessions are now visible in the following views:

  • Pools
  • Farms
  • Unified Access Gateways
  • Global Entitlements
  • Global Application Entitlements

The Alarms system has now been completely reworked to allow notifications for Alarms via the following Methods:

  • SMTP
  • Slack
  • Third Party Integration (PowerShell script)

vCenter Updates:

  • Hosts are now visible, and performance of the hosts is tracked.
  • Datastores are now visible and free space is now tracked.
  • Clusters are now visible and added to specific views such as pools, farms, etc. ·

Miscellaneous Updates:

  • LDAP Integration vastly improved and now supports Cyrillic characters.
  • Improved Dashboard.
  • vGPU profiles are now listed on pool views.
  • Many bugfixes
  • PowerShell scripts are now available to leverage API integration. Github 

Similar Flings

No similar flings found. Check these out instead...
May 21, 2021
fling logo of App Volumes Packaging Utility

App Volumes Packaging Utility

version 1.3

This App Volumes Packaging Utility helps to package applications. With this fling, packagers can add the necessary metadata to MSIX app attach VHDs so they can be used alongside existing AV format packages.

Aug 25, 2014
fling logo of Latency Sensitivity Troubleshooting Tool

Latency Sensitivity Troubleshooting Tool

version 1.0

The Latency Sensitivity Troubleshooting Tool provides scripts and examples to troubleshoot configuration and performance problems with the Latency Sensitivity feature in VMware vSphere 5.5.

Mar 16, 2015
fling logo of Horizon View Persona Management Share Validation Tool

Horizon View Persona Management Share Validation Tool

version 1.0

The Horizon View Persona Management Share Validation Tool is a command-line utility that analyzes user profiles and CIFS shares used by Persona Management to ensure minimum security requirements are met. Persona depends on two CIFS shares to function: the central profile store and the redirected folder share.

May 07, 2018
fling logo of Cellular Module User Space USB Driver on ESXi

Cellular Module User Space USB Driver on ESXi

version 1.0

This Fling provides this driver to enable deployment on ESXi on their IoT devices.

May 17, 2022
fling logo of VMware OS Optimization Tool

VMware OS Optimization Tool

The VMware OS Optimization Tool helps optimize Windows desktops for use with VMware Horizon View.

Jun 26, 2019
fling logo of IOBlazer


version 1.01

IOBlazer is a multi-platform storage stack micro-benchmark. IOBlazer runs on Linux, Windows and OSX and it is capable of generating a highly customizable workload.

View More