Architecting service provider implementations of Horizon 7 requires special attention to how each resource block is sized. As described previously, service providers can provide both shared and dedicated management blocks. Sizing for management components such as Connection Servers and Access Point appliances can be predicted based on the number of sessions (See Table 6). However, for enterprise customers, compute resource for desktops and applications, including the number of virtual desktops per host may vary per tenant.

Horizon DaaS implementations adopt pre-defined “desktop models”, giving the tenant a choice of desktop types (session-based RDSH or full desktop, with multiple compute configurations). This gives service providers the ability to offer desktops using a monthly consumption model (number of desktops / per month). Therefore, Horizon DaaS is particularly suited to tenants that don’t have the technical skills or desire to manage their own end-to-end Horizon deployment.

The enterprise desktop is often complex, containing very large numbers of applications, configurations, user customizations and application dependencies. This sizing model allows service providers to implement Horizon 7 in a highly scalable and secure fashion. No tenant will share physical desktop infrastructure with another. The physical infrastructure of management components is fully managed by the service provider. This allows tenant administration teams to focus on managing enterprise desktops and applications.