Remote PCs provide benefits over traditional distributed desktop computing by centralizing desktops in the data center. This allows for improved security since user data resides behind the firewall. It also improves manageability since desktop images only need to be managed in one location rather than on individual PCs. Remote PC implementations can take the form of virtual desktop infrastructure (VDI) where each user is assigned a virtual machine, or blade PCs which are dedicated physical machines located in the data center. Protocols like RDP, ICA and RGS are used to transmit the desktop experience from the centralized computing resources to users' local access devices. Remote PCs can provide significant cost savings through better utilization of resources and lower management costs compared to traditional distributed desktop

1. Remote PCs: the
what, why and
when
© 2007 Pride Technologies and Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice

2. 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

3. The need for Remote PCs
Heterogeneity High Management Costs Admin Inefficiencies
> 70% of TCO ($6,800* / user/ year) Too tactically focused
) *Gartner
-IDC -IDC
Security Threats Low Resource Utilization
Need for preventive/
proactive measures
Data Theft Virus / Malware
The desktop is the least
utilized resource on the
Phishing Hacking network!

4. Remote PC Benefits
Close 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

5. 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

6. Distributed vs. Remote PCs
What is the difference?
Apps Apps
Win OS Win OS
Virtual Virtual
Applications Machine Machine Application
Windows OS Hypervisor Windows OS
PC Blade Server Server
Applications
HP Session Citrix or
Allocation Mgr Connection Broker Terminal Services
Windows OS
RDP/RGS RDP RDP/ICA
Personal Computer Thin Client Thin Client Thin Clients
Remote PC
Distributed PC
HP CCI HP VDI Terminal Server/Citrix
• Single user per Desktop
PC Multiple users accessing Multiple users accessing
Single user per Blade PC
virtual PC’s per server applications per server
Current Paradigm Security and Data Backup
Performance Lower Total Costs
Standard Remote Access and Disaster Recovery
Most Flexible Improved Environmentals

7. “Static” or “Dynamic” Implementation
Two Basic “Static” Model “Dynamic” Model
Implementation’s
Static
1:1 Every user
assigned a VM
connects by it’s IP
Address or Name Connection
Broker
Dynamic
Proliant/Blades
Connection broker
Running
connects user to a
Windows VMs
VM in a pool and
Or CCI HW
returns VM to pool
when the user
disconnects

8. 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

9. Step 2: Broker / Allocation Server
- 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

10. Step 3: Computing Resource
Step 3: Resource Assigned Option #1: VDI
- Virtual Windows Vista or XP loaded onto server
- Multiple users per server (~8-10 per CPU core)
- 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

11. 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
- 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

12. Protocol Overview
Microsoft Remote − Standard Windows Remote Viewing Protocol
Desktop Protocol
− Good performance, supports audio output
(RDP)
− Supported by VMware
Citrix Independent − Highly secure, encrypted traffic
Computing − Bi-directional audio support
Architecture (ICA)
− High performance over WAN
HP Remote − Superior graphics performance
Graphics Software − Per-node Licensing required from Hewlett-Packard
(RGS)
− Supported by VMware
− Superior graphics and USB performance
Pano Console
Direct − Optimized video with synchronized audio
− VMware support only (requires Pano Zero Client device)
− To be incorporated into VMware
PC over IP (PCoIP)
− High Performance; more forgiving for high latency

13. VDI Benefits – Economies of scale
VM 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)

14. Sample Virtual Desktop Infrastructure
on HP BladeSystem c-Class
VMware: up to 20 XP users/core
Citrix Xen: No CPU limits
• 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
• Pair a BL490c with an SB40 • Solution will be 30% to 35% less costly
• Each SB40 offers 1.5TB of than using DL380’s with MSA50’s
RAID 5 storage • Solution will use ~30% less watts than
• Virtualization Layer on Blade equivalent DL380’s & MSA50’s
Hard Drives or with an • Less cables & networking costs
Integrated Hypervisor • Equivalent response times to DL380
based solution.

15. 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

16. The Basic Methodology for VDI
Assess
Categorize users and
applications, identify use
cases, measure usage,
determine environment
limitations and needs
Monitor and adjust Identify target users
resource allocations, and use cases,
Manage provide software select technologies, Design
upgrades and patches, model architecture
support end users and capacity needs
Virtualize applications,
virtualize target desktops,
migrate user settings and
documents, deploy to
desktops and terminals
Deploy

17. Gather Key Usage Metrics
Dissolvable agent
measures usage:
• Per user, per app
• Time in use
• CPU
• Memory
• Disk
• Network
• Latency
• Graphics intensity
• Login duration
• App load times

18. Determine VDI Fitness Rating
See how well specific
machines, users and
applications fit in VDI:
• Analyze by group
• Workload statistics
• System CPU
• User CPU
• Memory Use Best Fit
• Paging
• Disk I/O
• Network I/O
• Advanced metrics Worst Fit
• User logons
• App loading
• Network latency
• Graphics intensity
• Categorize workloads
• Customizable ratings

19. Performance characteristics
• Near linear processor Scatterplot of %CPU for 70 VMs, 80 VMs, 90 VMs, 100 VMs
110
scalability 100
Variable
70 VMs
80 VMs
90 90 VMs
%CPU Utilization
100 VMs
80
• Better than expected 70
60
memory management 50
40
• Storage controllers are 30
20
extremely important 06
15
:0
0
06
18
:0
0
06
21
:0
0
00
6
0:
00
00
6
3:
00
00
6
6:
00
20 20 20 /2 /2 /2
9/ 9/ 9/ 0 10 10
− More cache for direct attached 10
/
10
/
10
/
10
/1
Time
10
/
10
/
• User experience is
outstanding

20. TCO savings by category: hard costs
Category Savings Rationale
Install/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 break
Blades 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
Source: Meta Group, Gartner and HP Internal Analysis

21. In Summary…
• Address risks in delivering • Data secured in the
technology to users datacenter, not vulnerable at
Reduce and • Minimize security and
the access device
Avoid Risk compliance risk associated • Manage and secure desk-
with traditional distributed based corporate IP via
clients datacenter best practices
• Manage client computing
more efficiently with
• Reduce costs by centralizing automated tools and best
Reduce Cost desk-based management in practices
the datacenter
• Fewer desk-side support
calls
• Reduce end-user disruptions
Service • Deliver improved SLAs with
while delivering full desktop
Levels your population
experience
• 3rd-generation HP Blade PCs
• Blade PC/Wkstn technology • 2nd-gen HP Blade
Technical Workstation
at stage of maturity to deploy
Innovation on enterprise-wide basis
21 29 September 2009
• True desktop experience

22. http://www.hp.com/go/vdi
http://www.hp.com/go/cci
Questions
and Answers