This document discusses use cases and configuration for VMware Horizon Workspace. It provides an overview of Horizon Workspace and its capabilities for file collaboration, application access, and virtual desktop access. It then defines common Horizon Workspace use cases such as call centers, BYOD, and desktop outsourcing. Specific business requirements and considerations are discussed for each use case, including defining user profiles. The document concludes with a customer success story and details about deploying the Horizon Workspace virtual application.

1. Getting Started with Horizon Workspace:
Use Cases and Configuration
Stephane Asselin, VMware
Kristopher Boyd, VMware
EUC6044
#EUC6044

2. 2
VMware Horizon Is the Platform for Workforce Mobility
Transform: Simplify
desktops, diverse apps
and data into
centralized services
Deliver: Empower your
workforce with flexible
access across devices,
locations and connectivity
Broker: Manage & Secure
centrally and broker services
to your workforce by policy

3. 3
• Data Access across devices
• Collaboration & sharing
• Policy based data controls
• Flexible & secure storage
options
• 1-Click Request/Access
• Single Sign On for SaaS Apps
• Centralized access to apps
from Web Client and Mobile
• Single vApp with Flexible
Installation
• User & Group Entitlement
based on AD
• Manage Data, App and
Desktops from Single Portal
• Native View Client from Horizon
w/SSO
• Horizon Access from a View
Desktop w/SSO
• Access View Desktop from Web
Clients and iPad
New! Horizon Workspace 1.5

4. 4
File Collaboration with Colleagues, Customers and Partners
Challenge
 Users introducing consumer devices and
apps into corporate environment
 Need a secure way to collaborate on files
both internally and with customers, partners
and work-at-home employees
Solution
 Anytime, anywhere access
 Offline & online data access
 High-fidelity doc previews
 Document versioning, commenting
and auditing
v1
INTERNAL EXTERNAL
v2
v3

5. 5
Easy Access to Enterprise Applications & Services
Challenge
 Different way of getting apps from
every platform
 Multiple logins increases support costs
 Provisioning applications is costly
Solution
 Single context-based catalog
 Data, Apps, Services, Virtual Desktops
 Single Sign On
 One-click access to activate / download app

6. 6
Access to Virtual Desktops Has Never Been Easier
Challenge
 Multiple logins
 Launching another client is cumbersome
 Often not possible or ideal to install view
client on some devices
Solution
 SSO brokering user to available desktops
based on entitlement policy
 Leverage Blast protocol to access View
from any HTML5 browser

7. 7
Horizon Workspace – Administration and Management
Overview
 Manage Horizon Workspace
modules
 Provision entitlements to resources
 Policy Manager controls
 Application Catalog builder
 Reporting across assets and usage
Benefits
 Single tool to manage end user
 Holistic view of entire usage of
the environment

8. 8
Personal and Corporate Profiles on Single Handset (Android)
• Users have unrestricted access to their
personal persona (Download, make calls,
share pictures, etc.)
• The personal phone cannot be
viewed/altered by the enterprise
• Private life remains private
• Enterprise can still “refer” mobile apps
from stores
• The corporate workspace is
completely enterprise-owned
and controlled
• Ability to provision, manage
and remove corporate data on
employees’ devices
• Access to corporate
applications and infrastructure
support

9. 9
Defining Horizon Workspace Use Cases
• A use case in this context is a common set of
computing platform functional requirements for
a given set of users.
• A use case defines all common
characteristics, including hardware (physical
and virtual), software (OS and applications),
and peripheral devices, such as printers and
input devices such (smart card readers).
• The use case is important to virtualization
because it is the combination of users and
their applications that is the objective of a
Horizon workspace project.
End User
Requirements
Platform
requirements
Use
Cases
For example, the virtualization of call center
applications represents tools for end users
whose routine computing activities are so
similar as to require similar computing
performance and capabilities. This could be
referred to as the call center use case.

10. 10
Defining Horizon Use Cases
• Call Center/Outsourcing
• OS Independence
• Developer/Offshore
• Desktop Outsourcing
• ROBO
• BYOD
• Merger and Acquisition
Consolidation
Workspace
Use Cases

11. 11
Horizon Use Cases
Call Center/
Outsourcing
 Increase data security
while keeping IP in the
datacenter
 Streamline deployment of
applications
 Reduce cost of managing
applications and devices
 Improved time to provision
new desktops
OS Independence
 Reduce high costs, and
application compatibility
with OS migrations
 Extend life of existing
desktop hardware to
access virtual Windows
PC desktops
 Reduce application
conflicts and costly
application porting
Developer/Offshore
 Enable end users while
keeping IP and
applications in the
datacenter
 Accelerate provisioning
of applications
 Reduce cost of managing
end point devices

12. 12
Horizon Use Cases (cont.)
Desktop
Outsourcing
 Reduce costs and
increase control
 Strengthen security with
centralized application
control and management
 Streamline application
management and
deployment
 Deliver built-in application
business continuity
Remote Office
Branch Office
 Provide control while
keeping applications and IP
in the datacenter
 Remove the need of IT
resources at branch
 Manage remotely—
applications centralized in
corporate datacenter
 Provide always-on
availability
BYOD
 Enable application access
from variety of devices and
locations
 End-user mobility with
consistent application
experience
 Improve security and control
with company applications
and IP in the datacenter
 Reduce helpdesk and
support costs

13. 13
Horizon Use Cases – User Profiles
 With clearly defined use cases, we can build comprehensive use
profiles that include application sets and expected
performance usage
 User profiles allow for more accurate planning and designing of the
Horizon application manager solution
 With each use case, we can set up a pilot group for comprehensive
testing that includes real world simulations
 The pilot groups allow us to capture real time and historical
performance data for each use case

14. 14
Horizon Use Cases – User Profile Samples
Classification Definition Detail
Administrative
Users
Perform repetitive tasks using limited set of
applications
Uses IT to complete repetitive tasks within a production process
• Enters data at moderate speed
• Performs more complex operations
• Uses a mix of office and enterprise applications
• Includes administrative assistants, word processors, and office
coordinators
Knowledge
Users
Users that work primarily with information or
develop and use knowledge in the workplace
using an extensive set of tools and applications
Uses several applications simultaneously
• Enters data at moderate speed
• Performs more complex operations
• Uses a mix of office applications and specialized, decision-
supporting applications
• Includes analysts, consultants, and project managers
Power Users Users that work with advanced functions and
programs which are outside the reach of normal
users due to the complexity and advanced
knowledge required to perform these tasks
Uses IT to create products
• Uses highly specialized applications
• Includes engineers, graphic artists, and computer programmers
Data Entry Users Users that perform repetitive tasks using a
limited set applications
Similar to Administrative Users, but perform a
more limited set of operations
Works intensively with only one application at a time
• Enters data quickly
• Works continuously
• Includes transaction processors, customer service
representatives, and help desk representatives

15. 15
Horizon Use Cases – Business Requirements Considerations
 Usability
• Application shortcuts
• Single sign-on
• Printing
• Access to user data
• Access to shared data
• Application inventory
• User migration
• High availability/Business continuity
• Disaster recovery
 Performance
• User login time
• Application load times
• Application responsiveness
• Printing
• Performance on mobile devices

16. 16
Horizon Use Cases – Business Requirements Considerations
 Reliability
• Redundant infrastructure components
• Production application package distribution point redundancy
• Original source package files retention
• Load balancing and load distribution
 Security
• Unique security requirements for each use case
• Access requirements
• Single Sign On
• SAML integration
• Application access
• RADIUS two-factor authentication

17. 17
Customer success
 Canadian West Coast company
• Main driver: BYOD and workforce mobility
• Progression: vHAM - » Workspace
• ROBO and work from home users

18. 18
Horizon Workspace vApp
Workspace vApp
Configurator
VA
OS (SLES)
tcserver
Management VA
OS (SLES)
App
API
DBtcserver
Data VA
OS (SLES)
App
API
DB LDAPJetty
App
Connector
VA
OS (SLES)
tcserver
App
Gateway
VA
OS (SLES)
Nginx
Modules
• Central Wizard UI
• Distributes settings
across VAs
• Network, Gateway,
vCenter, SMTP
attributes
• Add / remove modules
• Manage certs, security
• User authentication (RSA SecureID)
• AD secure bind and synchronization
• Set replication schedule
• Sync View pools and ThinApp
• Enables single user-
facing domain
• Routes requests to
correct node
• Reverse proxy insulates
VAs
• Workspace Admin UI
• Application Catalog
• Manage user entitlements
• Workspace Groups
• Reporting
• Stores files
• Controls file sharing policy for
internal and external users
• Manage file preview server
• Serves end user web UI

19. 19
Questions

20. 20
Other VMware Activities Related to This Session
 HOL:
HOL-MBL-1304
Horizon Workspace - Explore and Deploy
 Group Discussions:
EUC1005-GD
Workspace with Rasmus Jensen
Panel Session:
EUC6045
EUC Field Experience with:
Kristopher Boyd
Simon Long
Justin Venezia
Stephane Asselin
Ray Dessault

21. THANK YOU

23. Getting Started with Horizon Workspace:
Use Cases and Configuration
Stephane Asselin, VMware
Kristopher Boyd, VMware
EUC6044
#EUC6044