VDI & Thin Client — Complete Study Guide

Virtual Desktop Infrastructure VDI + Thin Client

Complete Study Guide — Mind Map · Architecture Diagrams · 18-Mark Exam Q&A

Complete Mind Map

VDI Overview — Key Concepts

🎯 Desktop Infrastructure Challenges (from slides)

Distributed Workforce

Mobile & remote workers
Outsourcing & offshoring
Contract workers

Limited Control of PCs

Patch compliance
Security gaps
Regulatory compliance

⚖️

Focus on PC Hardware

Many makes & models
Refresh cycles cost

Management Complexity

Deployment issues
Support overhead
Security management

💰 Operating Cost: Move / Add / Change = $1,000 per incident

🖥 What is VDI?

Hosts desktop OS in a VM in the datacenter
Users access via thin clients / any device
Breaks the link between OS and physical hardware
Centralises data, apps, and profiles

✅ VDI Benefits

Hardware independence (OS Virtualisation)
Centralised management & patching
Enhanced security — data stays in datacenter
Data isolation via file shares & profiles
Any-VM access: user always gets their data

📡 Opportunities Enabling VDI

Network capacity growing exponentially (graph in slides)
62% primary broadband access (2004 data)
DSL, cable, fiber, wireless proliferation
Sufficient bandwidth for desktop streaming

🗂 File Shares & User Profiles

VDI proximity to datacenter enables data isolation
Users can log into any VM and get same data + profile
More apps installed → less stable (conflict issue)
Solution: install only OS in VM; stream apps on demand

VDI Protocols

🔌 VNC Architecture (from slide — framebuffer model)

Applications

↕

Window System

↕

Display Driver

── RFB Protocol ──

Framebuffer (VNC)

⟶

vncserver (Remote)

Exports screen
Imports keyboard/mouse

↕ Network ↕

vncviewer (Local)

Imports screen view
Exports keyboard/mouse

Cross-platform Support

🖥 UNIX↔🪟 Windows

🖥 UNIX↔🍎 Mac

🪟 Win↔🍎 Mac

🏛 Remote Desktop Services (RDS) Architecture — Windows Server 2008 R2

💻

RD Client

End-user device (thin/fat)

🌐

RD Web Access

Browser-based connection portal

🔥

RD Gateway

SSL proxy from outside firewall

🔀

RD Connection
Broker

🖥

RD Session Host (RDSH)

Shared session-based desktops & RemoteApp

📦

RD Virtualization Host (RDVH)

Personal & Pooled VMs via Hyper-V

🗂

Active Directory + Licensing

Auth, policy, licence management

TS → RDS rename: Terminal Server → RD Session Host | TS Gateway → RD Gateway

NEW in R2: RD Virtual Host | RemoteApp & Desktop Connections

⚡ PCoIP (PC-over-IP) — Host vs Client Rendering

❌ Client Rendering (Problem)

Separates components by network → command/response traffic crosses network → latency degrades application performance. Each pixel must be requested.

✅ Host Rendering (PCoIP Solution)

Renders everything on server → broadcasts only encrypted pixels, not raw data → client just decodes pixels → works even on high-latency WANs.

Multi-codec

Intelligent per-region encoding
Video: lossy codec
Text: lossless codec
Pixel-perfect results

Dynamic Adaptation

Auto-adjusts on congested networks
Uses UDP for low overhead
Configurable bandwidth limits
Max quality when clear

Security Advantage

Only pixels transmitted, not data
No data ever leaves datacenter
No client-side exposure risk

Protocol Comparison Table

Feature Area	Feature	Standard PC	PCoIP	RDP
Applications
	App Dependent	Yes	Yes	No
	Resolution Support	Any	Any	Restricted
Graphics & Media
	Graphics & Media Rich Content	Full	Full	Poor
	GPU Loading	N/A	None	Varies
	Screen Update Rate	60 Hz	60 Hz	Poor
Bandwidth Adaptation
	BW Saving Lossy Encoder	N/A	Yes	No
	BW Adaptive Encoder	N/A	Yes	No
Device Support
	USB Protocol	USB 2.0	USB 1.1	USB 2.0
	Audio Support	HD 5.1	HD 5.1	Stereo
Security
	Device Authorization	No	Full	Limited
	O/S Exposure	Yes	No	Yes

🟢 Green = Fully supported / Highest performance 🟡 Yellow = Partial / Limited 🔴 Red = Not usable / Not supported

VDI Suggestions & Best Practices

1️⃣ Don't Make Big VMs

Installing all apps in VMs makes them unstable
More apps = more conflicts = less stable
Avoid "bloated" VM images

2️⃣ Create Smallest VM Possible

Install ONLY the OS from a single template
Keep VM clean and minimal
Easy to clone, patch, and replace

3️⃣ Deliver Apps On Demand

Stream applications from file server
Deliver only what user needs / has permission for
App-V / application virtualisation

4️⃣ Single App Repository

Create a centralised software repository (V1, V2…)
Update once, all VMs get the new version
Version-controlled and auditable

5️⃣ No Distribution Needed

Eliminates software push/distribution
Update repository → all users immediately get V2
No per-machine installation required

6️⃣ Use File Shares for User Data

Separate user data from VMs
Roaming profiles + folder redirection
Data isolation and secure backup

📝 Possible Exam Questions & Model Answers (18 Marks Total)

Question formats: 9+9 marks (2 questions) or 6+6+6 marks (3 questions). Click each question to reveal the model answer.

DESCRIPTIVE Q1. Explain the concept of Virtual Desktop Infrastructure (VDI). What are the key challenges in traditional desktop infrastructure that VDI aims to solve? Discuss with examples.

Format: 9-mark descriptive | Covers: VDI overview + challenges diagram

🎯 Core Answer (1-2 lines): VDI hosts desktop operating systems as virtual machines in a centralised data center; users access them remotely, breaking the dependency on physical hardware and enabling centralised management, security, and cost control.

Full Answer:

Definition: VDI = Desktop OS (e.g., Windows XP/Vista) runs as a VM inside a data center server. Users connect via thin clients, laptops, or browsers using protocols like RDP or PCoIP.
Key Principle: Desktop OS Virtualisation breaks the link between the Operating System and any specific hardware — enabling hardware independence.
Challenge 1 — Management: In traditional setups, each of the ~224 million US PCs (2004 data) must be individually patched, secured, and updated. VDI centralises this — patch once, apply everywhere.
Challenge 2 — Cost: Every "move, add, or change" to a desktop costs $1,000 per incident. VDI reduces these by managing all desktops from one datacenter.
Challenge 3 — Security: Distributed PCs are vulnerable to theft, patch non-compliance, and data breaches. VDI keeps all data in the datacenter — nothing sensitive leaves.
Challenge 4 — Distributed Workforce: Mobile workers, contractors, outsourced staff need access anywhere. VDI allows any device to securely connect to the corporate environment.
Challenge 5 — PC Hardware Diversity: Many different makes/models with varying refresh cycles. VDI abstracts away hardware — one golden OS image works on any hardware.

📊 Refer to Diagram: "Desktop Infrastructure Challenges" slide — Shows 5 arrows pointing to a balance scale center: Distributed Workforce, Limited Control of PCs, Management Complexity, Focus on PC Hardware, Reducing Cost (CAPEX/OPEX).

DESCRIPTIVE Q2. Describe the components and working of Remote Desktop Services (RDS). How does the RD Connection Broker coordinate between different RDS roles? Include a labelled architecture diagram.

Format: 9-mark descriptive + diagram | Covers: RDS roles table + architecture diagram from slide

🎯 Core Answer: RDS (Windows Server 2008 R2) is Microsoft's VDI framework where the RD Connection Broker acts as a central traffic manager routing clients to either session-based desktops (RDSH) or virtual machine desktops (RDVH), all accessible via web, gateway, or direct RDP.

RDS Components (from slides):

RD Client: The end-user device — connects via RDP to the broker.
RD Web Access: Provides browser-based portal to list published desktops/apps from Connection Broker.
RD Gateway: SSL proxy — allows external clients (outside the firewall) to connect without VPN.
RD Connection Broker (Central): Routes users to the correct resource — session host or virtual machine. Creates unified admin experience.
RD Session Host (RDSH): Hosts shared session-based desktops and RemoteApp applications for multiple users simultaneously.
RD Virtualization Host (RDVH): Runs Hyper-V — hosts personal virtual desktops (dedicated) and pooled virtual desktops (shared pool).
App-V for RDS: App-V Management Server streams virtualised applications to the RD Session Host, which then serves them to clients.
Active Directory + Licensing Server: Provides authentication, group policy, and licence management.

How Broker Works: Client → asks Broker → Broker checks AD for user assignment → routes to RDSH (for shared session) or RDVH (for personal/pooled VM) → Connection established.

📊 Draw/Refer to: "Remote Desktop Architecture Overview" slide — Shows RD Client → RD Web Access / RD Gateway → RD Connection Broker (center) → RD Session Host / RD Virtualization Host / Active Directory / Licensing Server.
Also refer to: "Remote Desktop Session Host (RDSH)" diagram — Client → Broker → Server Farm (RemoteApp) or Server Farm (Session-based desktops).

SCENARIO Q3. A company has 500 employees, some working from home and some from office. Their current PCs have mixed hardware. The IT manager wants to reduce desktop support costs. Recommend a VDI solution and justify your choice of protocol (RDP, VNC, or PCoIP).

Format: 6-mark scenario | Covers: Protocol comparison + VDI benefits

🎯 Core Answer: Recommend a VDI implementation using Microsoft RDS with PCoIP for high-quality remote experience — this eliminates hardware dependency, centralises management, reduces $1,000/incident costs, and securely supports both office and remote workers.

Recommended Solution:

Setup: Deploy Windows Server 2008 R2 RDS with RDSH for general workers and RDVH for power users needing dedicated VMs.
Protocol Choice — PCoIP: Best for mixed office/home environments because:
- ✅ Full graphics support (60 Hz, HD 5.1 audio) — unlike RDP which is "Poor" for media-rich content
- ✅ Dynamically adapts to home broadband (congested networks) via adaptive encoder
- ✅ Only transmits encrypted pixels — no data exposure even on public internet
- ✅ Hardware independence — old/mixed PCs become thin client terminals
Why not RDP alone: RDP resolution is "Restricted," GPU support "Varies," and audio is only Stereo — unsuitable for creative or multimedia staff.
Why not VNC alone: VNC is free but lacks enterprise security (no device authorisation) and bandwidth adaptation — not production-grade for 500 users.
Cost Justification: Centralised patching eliminates $1,000/incident MAC charges. Single OS template replaces 500 diverse PC images.

📊 Refer to: "Comparison" table slide (PCoIP vs RDP vs Standard PC) — Green/Yellow/Red feature matrix shows PCoIP superiority for media-rich, remote work scenarios.

DIAGRAM Q4. With the help of a neat diagram, explain how VNC (Virtual Network Computing) works. Describe the roles of vncserver and vncviewer, and explain the RFB protocol layer between them.

Format: 6-mark with diagram | Covers: VNC protocol + framebuffer architecture slide

🎯 Core Answer: VNC is a remote control system that exports a computer's "desktop" (framebuffer) over a network; vncserver runs on the remote machine and sends screen updates, while vncviewer on the local machine displays them and sends back keyboard/mouse input — using the RFB (Remote FrameBuffer) protocol.

vncserver (Remote side):

Provides the "remote" half of the remote control system
Exports the view of the remote desktop screen environment
Imports keyboard and mouse inputs from local machine
Communicates changes via the RFB protocol (framebuffer pixel updates)

vncviewer (Local side):

Provides the "local" half of the remote control system
Imports the view of the remote desktop screen (renders it locally)
Exports keyboard and mouse inputs to the remote machine

Framebuffer Architecture (from slide — RealVNC diagram):

Stack: Applications → Window System → Display Driver → [RFB cut line] → Framebuffer
VNC intercepts at the framebuffer level — OS-agnostic
Works across UNIX ↔ Windows ↔ Mac because it operates at pixel level

3 Common Configurations:

1. Local PC/Mac accessing remote UNIX
2. Local UNIX accessing remote PC/Mac
3. Local UNIX accessing remote UNIX

📊 Draw/Refer to: "Real VNC" framebuffer diagram from slides
Draw: [Applications] ↕ [Window System] ↕ [Display Driver] ── RFB Protocol line ── [Framebuffer]
Then show: Remote machine (vncserver) ⟷ Network ⟷ Local machine (vncviewer)

DESCRIPTIVE Q5. Explain the PCoIP (PC-over-IP) protocol. Describe its three main features: host rendering, multi-codec display processing, and dynamic network adaptation. Why is PCoIP considered superior to RDP for VDI?

Format: 6-mark descriptive | Covers: PCoIP slides — host rendering + multi-codec + dynamic adaptation

🎯 Core Answer: PCoIP (by Teradici) is a zero-client VDI protocol that renders all graphics on the host server and transmits only encrypted pixels to the client — enabling rich, secure desktop delivery even over high-latency WANs, unlike RDP which relies on client-side rendering commands.

Feature 1 — Host Rendering:

All graphics processing done at the server (TERA Host chip)
Only encrypted pixels are broadcast across the network — not raw application data
Client (TERA Portal) only decodes pixels to display the image
Result: No OS/data exposure, works on any hardware (no dependencies or incompatibilities)
Enables rich experience even on high-latency WAN connections

Feature 2 — Multi-codec Display Processing:

Different regions of screen encoded with optimal codec (e.g., video = lossy JPEG-like, text = lossless)
Intelligent image analysis per screen region
Result: Efficient bandwidth use + pixel-perfect image quality

Feature 3 — Dynamic Network Adaptation:

Automatically lowers image quality when network is congested
Maximises quality when network is clear
Uses UDP protocol to reduce bandwidth overhead
Configurable minimum bandwidth threshold

PCoIP vs RDP Superiority:

Full HD media support (RDP = "Poor") | 60 Hz refresh (RDP = "Poor")
Full device authorisation (RDP = Limited) | No O/S exposure (RDP exposes O/S)
Bandwidth adaptive encoder (RDP = No)

📊 Refer to: "Host Rendering" slide diagram — Server-side rendering with TERA Host, pixel broadcast across network, TERA Portal decodes pixels.
Also: "Multi-codec protocol" slide — Multiple codec streams merging into a single optimised display with different regions colour-coded by codec type.
Also: "Dynamic network adaptation" slide — Graph showing bandwidth thresholds and quality slider (Perception-Free scale).

SCENARIO Q6. An organisation currently installs all required applications on every virtual machine, causing instability and high management overhead. A VDI consultant recommends restructuring the environment. Describe the VDI best practices that should be applied, explaining how applications and data should be managed in a well-designed VDI environment.

Format: 9-mark scenario | Covers: VDI suggestions section (slides 23–28)

🎯 Core Answer: The solution is to create the smallest possible VM (OS only), keep user data on file servers via roaming profiles, and deliver applications on-demand from a centralised software repository — eliminating bloated VMs, improving stability, and removing the need for software distribution.

Problem with Current Approach (from slides):

Installing all applications into large VMs → instability increases with each additional app
"The more applications you install, the less stable things tend to get"
Every VM must be individually updated → high maintenance overhead

Best Practice 1 — Create Smallest VM Possible:

Install ONLY the OS from a single template — nothing else
All VMs are identical, clean, stable clones
Easy to replace a corrupted VM by re-cloning the template

Best Practice 2 — Separate User Data (File Shares + Profiles):

User data stored on dedicated file server, not inside the VM
Roaming profiles + folder redirection from Active Directory
User can log into ANY VM and always get their personal data and profile
VM is now stateless — can be recycled/replaced without data loss

Best Practice 3 — Deliver Apps On Demand:

Use application virtualisation (e.g., App-V) to stream apps from a file server
Deliver only what the specific user needs or has permission to use
Apps are not permanently installed in the VM — they run in an isolated bubble

Best Practice 4 — Single Centralised Software Repository:

Create one software repository (Version 1, then V2, V3...)
To upgrade all users: update the repository once → all users automatically get the new version
No software distribution process needed — eliminates SCCM-style push deployments
Versioned and auditable — rollback is simple (point back to V1)

Summary Diagram Flow:

File Server 1 → provides User Data (roaming profiles)
File Server 2 (Repository V2) → streams application packages on demand
Multiple small OS-only VMs ← pull apps and data only when needed

📊 Refer to slides: "Don't Make Big VMs" → "Create the Smallest VM" → "Deliver Apps on Demand" → "A Single Location for Applications" → "No Distribution Needed"
Draw: [Small OS VM] + [App Stream ←File Server 2 (V2 Repo)] + [Data ← File Server 1]
The architecture shows 2–3 identical OS-only VMs, one data file server, one app repository server.

DIAGRAM Q7 (Bonus). Compare and contrast Personal Virtual Desktops and Pooled Virtual Desktops in the context of RD Virtualization Host (RDVH). In what scenarios would you recommend each? Use a diagram.

Format: 6-mark diagram+comparison | Covers: RDVH slide with Personal vs Pooled VDs

🎯 Core Answer: Personal Virtual Desktops are permanently assigned to one user (persistent, customisable), while Pooled Virtual Desktops are drawn from a shared pool assigned temporarily at login — Personal for power users, Pooled for task workers to maximise server utilisation.

Personal Virtual Desktops:

Each user mapped to one specific VM — assigned 1-to-1 in Active Directory
User can customise, install software, save local files
VM persists between sessions (state saved)
Higher resource requirement (each user needs a dedicated VM running)
Use case: Power users, developers, creative staff who need customisation

Pooled Virtual Desktops:

User connects → Connection Broker assigns any available VM from the pool
No persistent state — VM resets to clean template after logout
Fewer VMs needed than users (not all log in simultaneously)
All VMs are identical — easy to maintain (patch the template, pool updates automatically)
User data preserved via roaming profiles / file shares (not in the VM)
Use case: Call centre agents, kiosk users, hot-desking environments

Broker's Role: RD Connection Broker queries Active Directory — if user has Personal VD assignment, directs to that VM. If Pooled, picks least-loaded available VM from pool.

📊 Refer to: "Remote Desktop Virtualization Host (RDVH)" slide
Shows: RD Client → (?) → RD Connection Broker → Active Directory
→ "Personal Virtual Desktops" cluster (top) OR "Pooled Virtual Desktops" cluster (bottom)
Draw both clusters with arrows from broker; label Personal (1 user : 1 VM) vs Pooled (N users : M VMs, M < N).

Quick Revision — Key Facts to Remember

$1,000 per MAC incident (traditional)

224M PCs in US alone (2004)

VNC = freely available, cross-platform

RFB = Remote FrameBuffer (VNC protocol)

PCoIP = host rendering, encrypted pixels only

RDS = Windows Server 2008 R2 VDI framework

RDSH = shared session desktops + RemoteApp

RDVH = personal/pooled VMs via Hyper-V

Broker = routes client to correct resource

RD Gateway = SSL proxy, no VPN needed

App-V = streams apps without installing them

VM tip = OS only in VM, apps streamed on demand

PCoIP uses UDP for lower bandwidth

VNC developed by AT&T Laboratories