EUC Group Discussion session notes (VMworld Europe 2014)

By | October 17, 2014

Horizon Technical Overview – Group Discussion

  • App Volumes standalone, not fully integrated to begin with
    • App container. Read only VMDK, using vSphere API call
    • Should plan around IOPS for application stacks
    • Writeable area for app data
    • Filter CV (stands for CloudVolumes?) agent inside virtual machines, less than 1% CPU used on guest OS, based on testing
    • Technical Enablement team working on 2k (2000) seat scaling whitepaper – To be released by end of year, in addition to Reviewers Guide
  • Linux\Android View client performance improvements being worked on for Q4
  • 1 single broker for DaaS and View Connection broker, being discussed\planned for. Broker architecture to be decided, DaaS or View?
  • Horizon Flex – Delivered via Mirage with policies, using Fusion, Workstation or Player on endpoint
  • AirWatch provides context switching and containerisation of workspace (i.e. one for personal, one for corporate apps, similar to legacy Horizon mobile)
  • Single access gateway – AirWatch, Security Server, Mirage and Workspace gateways, integrated into one access point and one admin UI. This is the goal\vision!
    • These will only merge over time, with older gateways being retired, however can’t rip and replace as this clearly isn’t practical and would impact customers heavily.
  • Automation with vRealize (vCAC) and self-provisioning to be expanded on
  • vDGA graphics and Manual Pools is recommended (cloning each VM and attaching specific GPU), as opposed to Automated\Linked Clones, as per VMware 3D whitepaper

RDSH Applications Overview – Group Discussion

  • Benefits – Deliver to user via Workspace, Horizon Client, PCoIP performance and ease of migration (only agent install required, plus added host to View).
    • Also, a XenApp migration fling is available
  • Mirage can use application layers for physical or virtual
  • As pointed out by attendee, possible requirement for more intelligent load balancing mechanism between RDS hosts based on actual workload. Current load is based on number of connections, not workload
  • XenApp applications can be published through Workspace if looking to keep XenApp, Workspace provides benefit of presenting everything from one user portal\interface
  • Multiple PCoIP sessions to one RDSH server with app publishing – Perform assessment to calculate workload, understand characteristics of application, in terms of graphic use for example (RDSH apps Deep Dive session for more depth around sizing the environment)
  • App Volumes
    • Install apps in VMDK, present to virtual desktop or RDSH
    • App Volumes manager – Map\attach to vCenter or other solution (Hyper-V) during setup
    • Writeable volume for app customisations
    • Horizon View Enterprise license (will be standalone as well).
    • Further announcement in December 14
    • Early Access program, however not currently available to Partners (doh!).

Leave a Reply