Sign Up for the Quarterly Newsletter

Horizon Reach

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.


Video Overview



Click to enlarge


Click to enlarge


Click to enlarge


Click to enlarge


Horizon Reach was tested with a limited number of customers during its inception and private BETA phase, here are a few items of feedback:


“Within the first 30 seconds of deployment, I had visibility into problems I didn’t even know existed until this fling detected them”Chris, Telecommunications


"This new offering brings all the Horizon View data in one spot. It helps provide reports that take numerous steps to get out of View Admin.”Steve, VDI Engineer


“This tool provides visibility into things that were not possible in the Horizon Admin UI, and the only way get them was to use the Horizon API and Powershell. This tool brings useful information around the Users, Desktop Pools, Farms, Useful Reporting and setting up alarms into all one console. I highly recommend putting this fling into the Horizon environment ASAP and Kudos to Andrew for his time and effort on the tool.” - Aresh, Sr Architect


“Tonight, during an outage, Horizon Reach saved myself HOURS of troubleshooting. Horizon Reach was aware of the issue before I was and told me exactly where the problem was, without having to sign into each console of my 20 pods.”Jeff, Telecommunications

“Instantly one of the best and most useful flings out there! Easy to install, provides tons of great insights in a simple, intuitive, and snappy interface!“ - Chris, Technical Architect

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)

Read Horizon Reach Instructions.pdf

Version 1.0.1 brings vCenter performance data along with a myriad of bugfixes!

New Features

  • Gauges, gauges everywhere.
  • Search field! for those huge customers who hate to dig.
  • vCenter performance statistics will now be captured for Pods running version 7.8 or better.
  • vCenter RAM, CPU, sesions and Datastore Usage have all been added to the historical data views.
  • Datastore usage is now calculated only for datastores used by pools or farms.
    New layouts for Pools, Farms, Pods, Vcenters etc..
  • RDSH Servers load is now correctly measured and a new view is available.
    Page headers look much better.
  • vCenters now have the pod name listed.
    Added support for nested groups and some additional LDAP logging on startup.
  • Added the ability to modify a connection rather than just add and delete.
    Side nav will now collapse if screen space is low.
  • Don't use internet explorer, friends don't let friends do that, I've added a warning too.
  • Further logging enabled for LDAP integration including a self test on service start.
  • LDAP now supports nested groups.
  • Events view has been deprecated due to a thread exhaustion issue on the server side.

Bug Fixes

  • Farm usage is now accurate, wow that was broken!
  • Many cast errors were found and dealt with.
  • Problem machines now correctly display the vCenter.
  • Fixed a health score bug in the page header.
    Fixed a problem machines bug in pools and farms.
  • Fixed a bug in pod numbers calculation.
  • Improved the speed of database enumeration of sites and pods.
  • Fixed a bug in global application entitlements where the lack of shortcuts would cause the UI to freak out.
  • Fixed a bug in Datastore usage where it was reporting the wrong value.
  • Fixed a bug where Reach sessions may not be logged off correctly during polling.
  • Fixed a bug where applications were being requested for each farm multiple times.
  • Fixed a bug where pod health would be called twice for no reason.