1. © 2010 VMware Inc. All rights reserved EUC2846 - View Enterprise Architecture Design and Implementation Best Practices John Dodge, Sr. Manager, Global Technology Solutions, Global EUC CoE, VMware, Inc. Confidential 1

2. Design decision entanglement OS CPU Apps Memory Storage AppsMemory Storage ? CPU OS ! Highly entangled decisions must come first

3. View Design Methodology Use case definition Persona, desktop, & pool Pod and block VMware Infrastructure Storage design User access device

4. An alternative way to think about use cases 4 Jobs Constraints Outcomes

5. Use case definition 5 Use Cases Use Case 1 Workload Category Connectivity Category Apps OS Devices Use Case 2 Workload Category Connectivity Category Apps OS Devices Customer Requirements

6. Persona, desktop, and pool design 6 Persona, desktop & pool Persona None (no persistence) Native OS Virtual Desktop OS Virtual hw Local apps Use cases and volume Pool types Floating Dedicated Local mode Non-LC Applications Virtual Traditional SaaS Display Protocol Bandwidth and latency Features

7. Use Case attributes 7 AttributeDefinition Workload CategoryStandard worker Connectivity classificationLAN Location(s)London Time of use7am-7pm GMT, Mon-Fri Core applicationsAdobe Acrobat Reader Adobe Flash player Microsoft Office 2010 Microsoft IE6 User access device(s)Thin client, iPad Use of video/multimediaNo PrintersFollow me printing Monitors and connection1xVGA DevicesUSB: Neatworks scanner Authentication (e.g., Smartcard, SSO)Standard Windows Logon PersonaApplication and user profile persistence

8. Workload categories 8 AttributeDefinition Task worker userLimited privileges in OS Cannot install applications or device drivers Session will run few applications in total and a limited number of applications concurrently User is not guaranteed session persistence except with redirected user persona Standard worker userMay have limited or granted full access privileges within the OS May be able to install applications and devices May or may not be guaranteed session and profile persistence Power userFull privileges to the local operating system Expected to install applications and devices Expects session and profile persistence May expect shared profile in multiple sessions simultaneously

9. Connectivity classification 9 AttributeDefinition Low bandwidthUser access via display protocol over moderate to low bandwidth connection with moderate to high latency (e.g., WAN, Internet). Local modeWorkload runs locally, whether connected to the LAN, connected to the corporate network via a WAN, or disconnected from the network LANUser access over a high-speed (1GBE or higher), low latency (5ms>) network with low overall utilization

10. Pod and block design 10 Pod and Block Pod(s) User/datacenter topography Security boundaries BCDR requirements Networking P1 Block 1 Pool types Administration Provisioning frequency Pool design P x Block y Pool types Administration Provisioning frequency

11. 11 Confidential

12. vSphere Infrastructure design 12 vSphere Infrastructure Mgmt blockBlock 1 vCenter ESX/ESXi Networking VMs + images Pod and block design P x Block y vCenter ESX/ESXi Networking VMs + images Connection Servers Security Srvs Infrastructure Access Infrastructure Load balancing Firewalls and VPN Bandwidth

13. Storage design 13 Confidential Storage Mgmt blockVMs datastores OS Disposable disks Workload IOPS Max footprint vSphere Infrastructure Repositories Home directories Persistent disks Profile stores Transfer server Templates Application Server workloads DR

14. User access device design 14 User access device ClientsClient mgmt Patches or updates Software distribution Asset management Preexisting equipment OS Licensing OS Monitors Devices Software Network

15. Design Objectives 15 Confidential

16. Design Objectives Functional Non- functional Constraints

17. Non-functional Specifications Non-Functional Specifications (Service Qualities) Manageability Security Availability Recoverability Performance Love 17

18. Related design considerations 18 Confidential

19. Constraints 19 Quality Knowledge Standards Budget

20. Design Checklist John Dodge design checklist * Simplicity * User involvement * Balance business and technical (best practices) * Design rationales * Clarity over ambiguity * Reusable * Simplicity 20 Follow this checklist to create lasting designs

21. Logical and Technical Specs Pursue simplicity—keep similar aspects of the design together Group logical design elements with other logical elements Combine technical specifications with other technical (or detailed) specifications Avoid repeating details whenever possible Label a logical component once and consistently Describe the technical specifications once and completely 21 Avoid repeating configuration items or specifications Make high level logical designs easy to find and understand Keep technical specs separate for interested parties

22. 22 Implementation Best Practices 22

23. Key best practices and lessons learned OS optimization Antivirus resource demands Storage design PCoIP integration Business case Avoiding the meandering path to failure

24. Avoiding the path to failure Assessment PoC Pilot Production design Production deployment