© 2007 Pride Technologies and Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

Remote PCs: the what, why and when

Definitions• Server Based Computing (SBC)−AKA Terminal Server Environment

• Citrix XenApp (formerly Presentation Server or MetaFrame)• Microsoft Terminal Server

• Virtual Desktop Infrastructure (VDI)−Virtual Machines running a desktop OS

• VMware View• Citrix XenDesktop• Microsoft Hyper-V

• Consolidated Client Infrastructure−Bladed PCs that reside in the Data Center

• HP CCI• Blade-based Professional Workstations

The need for Remote PCsHeterogeneity High Management Costs Admin Inefficiencies

> 70% of TCO ($6,800* / user/ year))

-IDC

*Gartner

Low Resource Utilization

The desktop is the least utilized resource on the network!

Too tactically focused

-IDC

Security Threats

Data Theft Virus / Malware

Phishing Hacking

Need for preventive/ proactive measures

Remote PC BenefitsClose to IT Operations− Desktops are centralized in the Data Center

− For VDI: Can reduce the amount of images to manage− Management tools access the “desktops” over local networks for

patching/maintenance

Increases flexibility− Enables pooling and sharing of desktop infrastructure− Improves disaster recovery plans− Roaming profiles allow users to access from any device− Can pair technologies such as VDI and SBC in a single solution

Security− Remote users only ‘view’ data − For VDI: All data resides on RAID storage behind the firewall

Building Blocks•Compute Nodes

•Servers•PC or Workstation Blades

•Storage•iSCSI•DAS•SAS SAN•FC SAN

•Software•VDI Software•Connection Brokers

•Management•HP ICE

•Access Devices•Thin Clients/”Zero” Client•Reuse desktops/laptops

•Services

Distributed vs. Remote PCsWhat is the difference?

Distributed PC• Single user per Desktop

PC

Remote PC

HP CCISingle user per Blade PC

HP VDIMultiple users accessing

virtual PC’s per server

Terminal Server/CitrixMultiple users accessing

applications per server

Current Paradigm Performance

StandardMost Flexible

Security and Data BackupLower Total Costs

Remote Access and Disaster RecoveryImproved Environmentals

Personal Computer

Windows OS

Applications

Thin Client

RDP/RGS

HP Session Allocation Mgr

PC Blade

Windows OS

Applications

Thin Clients

RDP/ICA

Citrix or Terminal Services

Server

Application

Windows OS

Thin Client

RDPConnection Broker

Server

Hypervisor

Win OS

Apps

Virtual Machine

Win OS

Apps

Virtual Machine

“Static” or “Dynamic” ImplementationTwo Basic Implementation’s Static1:1 Every user assigned a VM connects by it’s IP Address or NameDynamicConnection broker connects user to a VM in a pool and returns VM to pool when the user disconnects

“Dynamic” Model“Static” Model

Connection Broker

Proliant/BladesRunning Windows VMsOr CCI HW

Step 1: Access Device for Client Virtualization

- Access device can be a thin client, a notebook or a desktop PC

- Thin Client benefits

- Eliminates end-user “break-fix”

- Highly secure

- Minimal management/updates (small image)

- Reuse desktop/laptop

- Users gets Windows XP or Vista

-Standard PC applications work

-Must still manage large images

-Zero Client

-No image at device

-Only need to update a VM

- User inputs standard credentials (Name, Password, Smartcard, etc)

- Broker determines correct resource for user (Blade PC, Virtual PC, etc)

- Examples include: HP Session Allocation Manager, VMware View Manager, Pano Manager

Step 2: Broker / Allocation Server

Step 3: Resource Assigned

- User is connected via remote protocol (RGS, RDP, ICA, Console Direct) to their “virtualized” client PC

- Remote protocol transmits only keystrokes, mouse clicks and screenshots

- No corporate / end user data is transmitted to the access device

Option #1: VDI

- Virtual Windows Vista or XP loaded onto server

- Multiple users per server (~8-10 per CPU core)

Step 3: Computing Resource

Step 3: Resource Assigned Option #2: Blade PC or Workstation

- Windows Vista or XP loaded onto local hard drive

- User data folder-redirected to other storage

- Dedicated performance to user while logged in

Step 3: Computing Resource

- User is connected via remote protocol (RGS, RDP, ICA) to their “virtualized” client PC

- Remote protocol transmits only keystrokes, mouse clicks and screenshots

- No corporate / end user data is transmitted to the access device

Protocol OverviewMicrosoft Remote Desktop Protocol (RDP)

Pano Console Direct

Citrix Independent Computing Architecture (ICA)

HP Remote Graphics Software (RGS)

− Superior graphics and USB performance− Optimized video with synchronized audio− VMware support only (requires Pano Zero Client device)

− Standard Windows Remote Viewing Protocol − Good performance, supports audio output− Supported by VMware

− Highly secure, encrypted traffic− Bi-directional audio support− High performance over WAN

− Superior graphics performance− Per-node Licensing required from Hewlett-Packard− Supported by VMware

PC over IP (PCoIP)− To be incorporated into VMware− High Performance; more forgiving for high latency

VDI Benefits – Economies of scaleVM management− One base image can be used for many different VMs

• driver management is greatly simplified because all VMs use the same virtual hw

− Templates can be created for rapid deployment of new VMs

Utilize existing virtual infrastructure− Virtualized server and desktop spaces can leverage the same

hardware, architecture, and infrastructure.− Automatic load-balancing and high availability including instant VM

migration from host-to-host features.

Desktop infrastructure− Underutilized desktop assets− 5w vs 20w vs 120w (Zero Client vs Thin Client vs PC)

Sample Virtual Desktop Infrastructure on HP BladeSystem c-Class

• Pair a BL490c with an SB40• Each SB40 offers 1.5TB of

RAID 5 storage• Virtualization Layer on Blade

Hard Drives or with an Integrated Hypervisor

• Solution Sample for VDI:− 8 BL490c’s and 8 SB40’s− 4GB RAM per core− 8 NICs per Host− 80 VMs per blade− 640 users per 10U

• Solution will be 30% to 35% less costly than using DL380’s with MSA50’s

• Solution will use ~30% less watts than equivalent DL380’s & MSA50’s

• Less cables & networking costs• Equivalent response times to DL380

based solution.

VMware: up to 20 XP users/coreCitrix Xen: No CPU limits

Identifying VDI Candidates

No Guessing Allowed

−Objective tests are critical−However: work with the user: User Acceptance is

KEY! Make them feel that their opinions are important

• Many companies are offering incentives to employees• Allowing them to select their own client device• Providing dual-monitors• Other creative examples

The Basic Methodology for VDI

Categorize users and applications, identify use cases, measure usage, determine environment limitations and needs

Assess

DesignIdentify target users and use cases, select technologies, model architecture and capacity needs

Deploy

Manage

Virtualize applications, virtualize target desktops, migrate user settings and documents, deploy to desktops and terminals

Monitor and adjust resource allocations, provide software upgrades and patches, support end users

Gather Key Usage MetricsDissolvable agent measures usage:

• Per user, per app

• Time in use

• CPU

• Memory

• Disk

• Network

• Latency

• Graphics intensity

• Login duration

• App load times

Determine VDI Fitness RatingSee how well specificmachines, users and applications fit in VDI:

• Analyze by group

• Workload statistics

• System CPU

• User CPU

• Memory Use

• Paging

• Disk I/O

• Network I/O

• Advanced metrics

• User logons

• App loading

• Network latency

• Graphics intensity

• Categorize workloads

• Customizable ratings

Best Fit

Worst Fit

Performance characteristics• Near linear processor

scalability• Better than expected

memory management• Storage controllers are

extremely important− More cache for direct attached

• User experience is outstanding

Time

%CP

U Ut

iliza

tion

10/1

0/200

6 6:00

10/10/2

006 3

:00

10/10/2

006 0

:00

10/9

/2006

21:00

10/9/20

06 18

:00

10/9

/2006

15:00

110

100

90

80

70

60

50

40

30

20

70 VMs80 VMs90 VMs100 VMs

Variable

Scatterplot of %CPU for 70 VMs, 80 VMs, 90 VMs, 100 VMs

Category Savings RationaleInstall/replace/ update/move (“IMAC”) 90% Thin Client (TC) at user desk; simple upgrades, rarely

breaks, little need to move

Break/fix support 90% Desk side: TCs rarely breakBlades in data center: maintenance by fast and easy “rip and replace”

Systems management 70% Radical image standardization and greatly simplified software (SW) deployment methodology

Power Consumption 70% TC has minimal power draw; bladepc uses ultra low power CPUs

Help desk 50% Radical image standardization with minimal opportunity to change SW image, minimizes Help Desk calls

Training 40% Significant reduction due to simplified and radically standardized hardware and software

How-to support 40% Significant reduction due to simplified and radically standardized hardware and software

General operations 10% Due to ease of procuring and managing the centralized assets (i.e., blades).

TOTAL 70% Total % based on %s weighted by actual dollar amounts

TCO savings by category: hard costs

Source: Meta Group, Gartner and HP Internal Analysis

21 29 September 2009

In Summary…

Reduce and Avoid Risk

• Address risks in delivering technology to users

• Minimize security and compliance risk associated with traditional distributed clients

• Data secured in the datacenter, not vulnerable at the access device

• Manage and secure desk-based corporate IP via datacenter best practices

Reduce Cost• Reduce costs by centralizing

desk-based management in the datacenter

• Manage client computing more efficiently with automated tools and best practices

• Fewer desk-side support calls

Service Levels

• Deliver improved SLAs with your population

• Reduce end-user disruptions while delivering full desktop experience

Technical Innovation

• Blade PC/Wkstn technology at stage of maturity to deploy on enterprise-wide basis

• 3rd-generation HP Blade PCs• 2nd-gen HP Blade

Workstation• True desktop experience

Questionsand Answers

http://www.hp.com/go/vdi http://www.hp.com/go/cci