With Windows Server 2008 R2 released to the market, VDI has come into the picture as the future of next evolution of desktop. Now you can use your Netbook or any computer with a browser to initiate your VDI session.
Here is the snapshot which i have tested on my environment:-
1. Using a browser on your computer, key in your VDI URL. For example: https://rdsacess.ms4u.info/rdweb
). Below page appeared. Quite similar as Exchange Outlook Web Access (OWA). Enter a valid username and password.
2. Once you have authenticated, you will redirect to a page where you can see a pool of virtual machine which i have assigned. There are 2 different ways desktop sessions are display out. You can have a “personal desktop” or a “virtual pool”. The personal desktop (Display as My Desktop icon) means every time you get a VDI guest session it is the exact same dedicated session just for you. The virtual pool is a series of sessions that are available that remote users “share”, so the base guest session is shared, but through a seamless use of “roaming profiles” type of configuration, the user experience is unique to that guest session so that even if they go back into the virtual pool and get a different guest session, their files, profile configuration, etc come with them and they see the same experience pooled system to pooled system.
Click on Win7 Client Pool to start activate/access to Windows 7 Client Virtual machine.
3. Remote desktop connection dialog prompt. Click Connect button.
4. A dialog box appear to request for valid authentication. Once you have key in a valid username and password, it will RDP to Windows 7 Virtual machine.
As i can see, VDI is a cool stuff and very useful for mobile worker.
Let look into planning part. For VDI deployment, you need to properly do planning especially on resources that you want to assign to each VM.
a) 32GB RAM for a server
b) 1GB per VM for Windows 7
You can easily setup 30 VM and reserved 2GB for parent partition. (Just estimation, you still need to consider about processor utilization).
Setup Virtual Desktop Pool
The following are important consideration when setup Virtual Desktop Pool:-
a) A Hyper V server
b) Virtual Machine in virtual desktop pool must be identical and has program installed.
c) Virtual desktop can only consist Windows client operating system. No server operating system.
d) A Virtual machine can only be a member of a single pool.
e) You can have multiple Virtual Machine pool
f) The name of the virtual machine (display on Hyper V) must be FQDN and must be the same as virtual machine computer name.
g) User should not save any file on a virtual machine that is in virtual desktop pool. The reason is user may not be connected to the same virtual machine next time.
Setup Personal Virtual Desktop
The following are important consideration when setup Personal Desktop:-
Similar as "Setup Virtual Desktop Pool" consideration:- (a), (c) and (f)
a) 1 VM assigned to a single user
b) Display as "My desktop" Icon.
c) You can remove the assigning VM by using Active Directory User and Computer.
d) Schema must extend to Windows Server 2008. Domain functional level must be at least Windows Server 2000 native mode.
e) A VM should not be both member of a virtual desktop pool and personal virtual desktop
To setup VDI, you need the following components:-
a) A Remote Desktop Virtualization Host (RD Virtualization Host) server
b) A Remote Desktop Connection Broker (RD Connection Broker) server
c) A Remote Desktop Session Host (RD Session Host) server in redirection mode
d) A Remote Desktop Web Access (RD Web Access) server
e) Domain controller
f) Virtual machine configured as a personal virtual desktop or Virtual Desktop Pool
Components (a) until (e) should install with Windows Server 2008 R2.
How Microsoft VDI Work?
1.A user initiates the connection to the virtual desktop pool by using RD Web Access or by using RemoteApp and Desktop Connection.
2.The request is sent to the RD Session Host server running in redirection mode.
3.The RD Session Host server running in redirection mode redirects the request to the RD Connection Broker server.
4.The RD Connection Broker server checks to see if an existing session exists for the requesting user account. If a session already exists, proceed to step 6. If the session does not exist, proceed to step 5.
5.The RD Connection Broker server sends a request to the RD Virtualization Host server to locate and start the virtual machine.
6.The RD Connection Broker server returns the virtual machine name to the RD Session Host server running in redirection mode.
7.The RD Session Host server running in redirection mode redirects the request to the client computer that initiated the connection.
8.The client computer connects to the virtual desktop pool.
Great Articles about VDI
RDS Explained - http://blogs.technet.com/yungchou/archive/2010/01/04/remote-desktop-services-rds-architecture-explained.aspx
VDI Explained - http://blogs.technet.com/yungchou/archive/2010/01/06/microsoft-virtual-desktop-infrastructure-vdi-explained.aspx
Benchmarks: vSphere 4.0 vs XenServer 5.5 vs Hyper-V R2 for Terminal Services and VDI workloads
APP-V seems as another components that work in VDI. Will look into it soon..