VMware Horizon™ DaaS® Platform for Service Providers provides the only virtual desktop platform built for delivering desktops and applications as a cloud service.

Multi-Tenancy

Multi-tenancy is a must for cloud delivery. With our Horizon DaaS Platform, a service provider provisions a secure environment for tenant entitlements. The tenant gets:

  • Dedicated VLAN
  • Dedicated Filer
  • Dedicated compute (depending on the type of Windows desktop delivered)
  • Dedicated access portal
  • Dedicated access gateway

Single Management: Multi-Desktop Models

Our platform provides a single platform for provisioning and managing multiple workspaces, including:

  • Full VDI desktops (Windows 7, 8, XP or Linux)
  • Shared session desktops (RDS)
  • Windows Server desktops
  • Individual applications

Tiered Role Separation

The Horizon DaaS Platform supports full role separation across the service provider, IT, and end user. Desktop management can be done by the end company or by a managed service provider.

Multi-Data Center Management

In addition to scaling within a data center, our technology enables geographic scalability across data centers. This is important for servicing customers with geographically dispersed users and for maintaining business continuity. If one data center goes down, employees can access desktops via the other data center, with no interruption to their work.

DaaS Platform Software Components

There are four major components to the Horizon DaaS Platform: Resource Manager, which is used by Service Providers to manage the infrastructure; Access Manager and Desktop Manager, which are used by tenants to manage user connections and virtual desktops respectively; and the Service Grid Backbone, the essential ingredient for ensuring conflict-free connections and security between the Service Provider and tenant components.

Resource Manager

Service Providers manage infrastructure capacity and tenant entitlement from the Resource Manager. The Resource Manager lets you define the desktop options that tenants can purchase, such as Windows 7, Windows Server Workstation, Windows XP or Linux; how much memory and CPUs a particular virtual desktop has; and whether it is persistent or dynamic (and whether the customer will be allowed to choose the option they prefer). Capacity is managed, including the ratio of virtual to physical machines, and the amount of memory overallocation is determined within the Resource Manager.

  • Choose whether to share a host or dedicate compute to the virtual desktop. This unique feature is what makes it possible for to offer Windows 7 virtual desktops while remaining in compliance with Microsoft. Only DaaS Platform supports both models: sharing hosts for Linux desktops or dedicating a host for a cloud-hosted Windows 7 desktop offering.
  • Calculate how much resource, such as storage and compute, is required to meet the tenant’s needs. You’ll see whether you have enough compute assigned to the tenant and enough overall capacity in the service grid to meet tenant needs.
  • Provision the tenant: register the tenant, provide a unique password, upload a custom look and feel, and assign a unique VLAN. Our platform then auto-configures an Access Manager and Desktop Manager specific to the particular tenant.

Access Manager

This front-end to the customer enables the tenant to manage the connection broker for mapping users to desktops and provides portal access by which the customer’s users connect to their desktops.

Desktop Manager

Each customer uses its own Desktop Manager to provision pools of desktops and to continuously monitor and manage the desktop session state.

Service Grid Backbone

The Service Grid Backbone lies between the Service Provider (i.e., Resource Manager) and tenant (i.e., Desktop Manager and Access Manager) layers. This technology, which is unique to the Horizon DaaS Platform and critical for service provider success, has the Resource manager living in both the service provider network and the Service Grid Backbone. Likewise, the Access and Desktop Managers live in both the tenant network and the Service Grid Backbone. Packets can’t cross the network, but the address space used by the Service Provider and the tenant can be identical without any issues. We built this as a non-routable network so that both the service provider and the tenant can run the same subnet IP ranges without conflict.

The Service Grid Backbone also contributes to the DaaS Platform’s comprehensive security. Service providers and tenants cannot bridge into each other’s networks but they can still communicate with each other because the tenant appliances (Access Manager / Desktop Manager) and the service provider appliance (Resource Manager) are dual-homed on the non-routable network.