The document provides advice on adopting virtual workspaces based on Kyle Davies' experience. It outlines a 6 step process for a successful adoption: 1) Assess the existing environment; 2) Design the architecture and plans; 3) Build the architecture and standard operating environment; 4) Test functionality and applications; 5) Transition users in a phased approach starting with "troublesome" users; 6) Deploy to all users over time. Key recommendations include extensive testing, sizing appropriately based on actual usage rather than averages, phasing rollouts, and having support available during transitions.

1. WORKSPACE:
VirtualWorkspace Adoption
Advice
Kyle Davies – Solutions Architect
VMWORLD EU 2017 -VMTN6643E

2. WHO AM I?
• Kyle Davies
• CDW - Solutions Architect
• Twitter: @kdavies1988
• Blog: www.kyle-davies.com
• Experience: 10Years+
• Accreds: vExpert 2016-2017, Citrix CTA, FormerAtlantis
ACE, Cisco Spark Ambassador…

3. VMWARE DISCLAIMER
• This presentation may contain product features or functionality that are currently under
development
• This overview of new technology represents no commitment fromVMware to deliver these
features in any generally available product
• Features are subject to change, and must not be included in contracts, purchase orders, or
sales agreements of any kind
• Technical feasibility and market demand will affect final delivery
• Pricing and packaging for any new features/functionality/technology discussed or presented,
have not been determined
• This information is confidential

4. MY DISCLAIMER
• This is not specific to any vendor (VMware, Citrix, Microsoft etc)
• A lot of the points in this deck are valid for physical device transformations/migrations
• There are many tools on the market for assessments
• Data in this deck is example data
• Thoughts are my own, and not necessarily the thoughts of CDW

5. AREASTO BE COVERED
• Planning
• Sizing
• Application compatibility
• User testing & user on boarding
• Key takeaways

6. QUESTION
HANDS UP ….
IFYOU ARE RUNNING AVIRTUALWORKSPACE
WITHINYOUR ORGANISATION?

7. QUESTION
HANDS UP….
IFYOU ARE PLANNING AVIRTUALWORKSPACE
IMPLEMENTATION WITHINYOUR
ORGANISATION?

8. 01
ASSESS
& PLAN
05 TRANSITION
03 BUILD
04 TEST
02
DESIGN
& PLAN
06 DEPLOY
• ASSESS EXISTING USER ENVIRONMENT
• OUTLINE CORE IT AND BUSINESS
OBJECTIVES
• DESIGN OF
ARCHITECTURE
• DEFINITION OF BUILD,
TEST, SERVICE
TRANSITION AND
DEPLOYMENT PLANS
• BUILD OF
ARCHITECTURE AND
THE DEFINED
STANDARD OPERATING
ENVIRONMENT
• EXECUTION OF TEST
PLANS
• SMALL SCALE PILOT
• EXECUTION OF SERVICE
TRANSITION PLANS
• HANDOVER TO SERVICE
AND SUPPORT
• EARLY ADOPTER PHASE A
• EARLY ADOPTER PHASE B
• EXECUTION OF
DEPLOYMENT PLANS
6 STEPS FOR A SUCCESSFUL JOURNEY

9. ASSESS
• Understand why you are looking to
implement A virtual workspace
• Define clear deliverables against IT
objectives and business outcomes
• Is it for everyone or key users?
• Application media, licenses and
documentation?
• Are you replacing endpoints?
• What surrounding infrastructure do
you have?
• Are your internal teams capable of
supporting the platform?
• Do you need to prove the platform
once implemented?
• Training requirements?

10. ASSESS
• Understand existing user experience

11. ASSESS
• Understand existing impact

12. ASSESS
• Understand key user issues

13. ASSESS
• Understand existing profile & GPO impact

14. ASSESS
• Understand locally stored data

15. ASSESS
• Understand software required
107 required software packages
Now run compatibility exercises/extensive testing

16. ASSESS
• Understand average consumption BUT DON’T SIZE ONTHIS!

17. 01
ASSESS
& PLAN
05 TRANSITION
03 BUILD
04 TEST
02
DESIGN
& PLAN
06 DEPLOY
• ASSESS EXISTING USER ENVIRONMENT
• OUTLINE CORE IT AND BUSINESS
OBJECTIVES
• DESIGN OF
ARCHITECTURE
• DEFINITION OF BUILD,
TEST, SERVICE
TRANSITION AND
DEPLOYMENT PLANS
• BUILD OF
ARCHITECTURE AND
THE DEFINED
STANDARD OPERATING
ENVIRONMENT
• EXECUTION OF TEST
PLANS
• SMALL SCALE PILOT
• EXECUTION OF SERVICE
TRANSITION PLANS
• HANDOVER TO SERVICE
AND SUPPORT
• EARLY ADOPTER PHASE A
• EARLY ADOPTER PHASE B
• EXECUTION OF
DEPLOYMENT PLANS
6 STEPS FOR A SUCCESSFUL JOURNEY

18. SIZING
• Resource over subscription
• Multiple monitor usage
• Resource utilization
• Boot & login storms
• Application support
• Periphery pass through
• Storage
• Application workload impact
• Pooled vs dedicated
• Average sizing isn't good enough
• Server hosted, mobile native orVDI
Things to be mindful of:

19. 01
ASSESS
& PLAN
05 TRANSITION
03 BUILD
04 TEST
02
DESIGN
& PLAN
06 DEPLOY
• ASSESS EXISTING USER ENVIRONMENT
• OUTLINE CORE IT AND BUSINESS
OBJECTIVES
• DESIGN OF
ARCHITECTURE
• DEFINITION OF BUILD,
TEST, SERVICE
TRANSITION AND
DEPLOYMENT PLANS
• BUILD OF
ARCHITECTURE AND
THE DEFINED
STANDARD OPERATING
ENVIRONMENT
• EXECUTION OF TEST
PLANS
• SMALL SCALE PILOT
• EXECUTION OF SERVICE
TRANSITION PLANS
• HANDOVER TO SERVICE
AND SUPPORT
• EARLY ADOPTER PHASE A
• EARLY ADOPTER PHASE B
• EXECUTION OF
DEPLOYMENT PLANS
6 STEPS FOR A SUCCESSFUL JOURNEY

20. TEST
• Most overlooked area of virtual
workspace adoption
• Functionality requirements
• Periphery pass through
• Benchmarking!
• Don’t shy away from troublesome
people!
• Application launch is not good
enough!
• Test, test and test again!
Things to be mindful of:

21. 01
ASSESS
& PLAN
05 TRANSITION
03 BUILD
04 TEST
02
DESIGN
& PLAN
06 DEPLOY
• ASSESS EXISTING USER ENVIRONMENT
• OUTLINE CORE IT AND BUSINESS
OBJECTIVES
• DESIGN OF
ARCHITECTURE
• DEFINITION OF BUILD,
TEST, SERVICE
TRANSITION AND
DEPLOYMENT PLANS
• BUILD OF
ARCHITECTURE AND
THE DEFINED
STANDARD OPERATING
ENVIRONMENT
• EXECUTION OF TEST
PLANS
• SMALL SCALE PILOT
• EXECUTION OF SERVICE
TRANSITION PLANS
• HANDOVER TO SERVICE
AND SUPPORT
• EARLY ADOPTER PHASE A
• EARLY ADOPTER PHASE B
• EXECUTION OF
DEPLOYMENT PLANS
6 STEPS FOR A SUCCESSFUL JOURNEY

22. DEPLOY
• On board your troublesome users near
the beginning
• Run A phased adoption with phases of
early adopters
• Physical presence
• Instant support
• Work through your problems, don’t
hesitate to halt or slow down the
deployment
• Ensure you know of key times of the
day, week, month or year that can
seriously impact business productivity
• Don’t bring across profiles!
• Migration sign off sheets
• Communicate in advance about
changes
• Run an internal marketing campaign
• Initial month(s) allow quick change
cycles on the platform
Things to be mindful of:

23. KEYTAKEAWAYS
• Run an assessment
• Understand your user needs
• Understand why you are doing what you
are doing
• Test, test and test again
• Phase adoption
• Try to be available physically during
large migrations
• Benchmarking is key for benefits
realization
• Silly things can help
• IdentifyVIP users

24. THANKYOU
VMWORLD EU 2017 -VMTN6643E
Kyle Davies – Solutions Architect
Blog: www.kyle-davies.com
Twitter: @kdavies1988