4
Identifying the optimal deployment architecture depends on an organization's
requirements, and this decision in turn influences an organization's choice of EUC
control plane. Following are the different types of control planes and deployment
options for EUC brokers. The control plane, as the name suggests, handles the
provisioning, power, and brokering and is the primary interface for administrators.
It usually functions as an API interface as well.
EUC control planes typically broker a user connection to an application or desktop.
For applications, they broker through application presentation (typically RDSH
based), and for desktops, they can use either hosted shared desktops (HSD) or a
virtual desktop infrastructure (VDI) session.
Following are the three primary alternatives, along with some example use cases.
Traditional On-Prem Broker
With this EUC broker option, organizations typically buy licenses on a per-user basis
and install in their datacenter. While several vendors and products fall into this category,
Citrix Virtual Apps and Desktops (CVAD) and VMware Horizon are by far the most
widely used.
When building an on-prem EUC deployment, the responsibility for the architecture
and deployment falls to the organization or to outsourcing, including determining
all the components of the broker software to be deployed, such as controller servers,
database servers, licensing servers, edge security servers or devices, and any other
required supporting services. As part of deploying these items, you also determine
what high availability (HA) options are available for each service and select one that
makes sense for your design requirements.
EUC Deployment
Architectures
