TechTalk: Drive down virtual desktop SAN storage costs with XenDesktop Personal vDisk

1. March 15, 2012 Lead Systems Engineer Andy Prior TechTalk: Drive down virtual desktop SAN storage costs with XenDesktop Personal vDisk

2. Introduction Personal vDisk (PVD) Overview Application Support Install and Config Troubleshooting and Support Agenda

3. Introduction

4. Persistent personalization of user profile and applications Including user installed and entitlement based apps Compatible with PCCLM and application virtualization solutions Such as SCCM, App-V and XenApp 100% persistence with VDI pooled storage/management Near zero management overhead What Is Citrix Personal vDisk? PvD is a new Machine Catalogue type & PvD sits between Assigned Desktops and Static Pooled Desktops, PvD allows the de-coupling of user settings and applications from the base O/S image, greatly simplifying O/S image management. PPCLM � PC Configuration and Life Cycle Management.PvD is a new Machine Catalogue type & PvD sits between Assigned Desktops and Static Pooled Desktops, PvD allows the de-coupling of user settings and applications from the base O/S image, greatly simplifying O/S image management. PPCLM � PC Configuration and Life Cycle Management.

5. 5 VDI Desktop Models � Pooled Desktops Try to use pooled/shared, but advanced workers struggle with lack of customizationTry to use pooled/shared, but advanced workers struggle with lack of customization

6. 6 VDI Desktop Models � Assigned Desktops Address the advanced user with dedicated, but now management and costs become challengingAddress the advanced user with dedicated, but now management and costs become challenging

7. 7 VDI Desktop Models � Pooled with Personal vDisk Provides the management efficiency of pooled/shared/random with the personalization breadth of dedicatedProvides the management efficiency of pooled/shared/random with the personalization breadth of dedicated

8. Personal vDisk Overview

9. Delivering and Managing the PvD Desktop

10. May be attached to any storage targets defined in the hypervisor Thin provisioning is supported for those hypervisors that support it Can be located on same as VM, or different (IOPS split among locations) Default size and location selected in Desktop Studio catalog creation (or PVS XenDesktop setup wizard, if PVS in use) PvD disks can be resized PvD Disks Characteristics

11. PVD Storage Architecture The PvD Catalogue type �sits� between Assigned desktops and pooled desktops, compared to assigned desktops PvD is more efficient on storage and flexible in that there are support tools to re-set a users PvD. The PvD Catalogue type �sits� between Assigned desktops and pooled desktops, compared to assigned desktops PvD is more efficient on storage and flexible in that there are support tools to re-set a users PvD.

12. 12 Business Value

13. PVD Application Support

14. PVD has been designed so that applications installed while PVD is running should �just work� Nonetheless, there are some noteworthy exceptions and recommendations/best practices � Application Support

15. 15 PVD Kernel Mode Drivers load in Windows �phase 1� (very early boot) This means applications that install phase 0 (very very early boot) won�t work Certain AVs, hardware drivers, etc � but these probably shouldn�t be installed in PVD anyway Note that these applications will work fine if installed into the base VM! Platform software should be installed in the base VM as a best practice Windows service packs and updates, etc � Applications common to many users should be installed in the base VM Office, browsers, Adobe Reader/Flash, etc � Application Support PVD KND�s load in Windows �Phase 1� Windows has three boot �phase�s�, PVD loads in Phase 1 anything which loads prior to this will not function as the PVD KMD will not be able to re-direct any reads or writes to the PVD. PvD works by intercepting IO requests (file and registry keys/values) and re-directing those requests based on a set of rules, this set of rules is called the resource catalogue. PVD KND�s load in Windows �Phase 1� Windows has three boot �phase�s�, PVD loads in Phase 1 anything which loads prior to this will not function as the PVD KMD will not be able to re-direct any reads or writes to the PVD. PvD works by intercepting IO requests (file and registry keys/values) and re-directing those requests based on a set of rules, this set of rules is called the resource catalogue.

16. 16 Managing Layers � When needed � Citrix PvD �sits� in the �desktop cake� above the common base image but is part of the user environment, the PvD will not only encompass user data and settings but also allow the de-coupling of user and corporate installed applications from the common base. Citrix PvD �sits� in the �desktop cake� above the common base image but is part of the user environment, the PvD will not only encompass user data and settings but also allow the de-coupling of user and corporate installed applications from the common base.

17. 17 PvD plays nicely with profile management solutions PVD can be used as a simple profile management solution itself For simple environments with single �desktops� PVD + Citrix Profile Manager (UPM) makes a powerful combination, enabling roaming profiles and persistent personalization! Citrix Profile Management When to use both? Based on how the apps and desktops are leveraged � if the user is always accessing a single desktop, a single layer works no matter how many devices they leverage to access that desktop. BUT if the user tends to use multiple resources (aka running apps from XA, multiple virtual desktops etc) then they will want their profile data to roam (aka Outlook signatures, Office settings, IE settings, My Docs, Favs etc). Using UPM and Folder Redirection (optional) enables this.When to use both? Based on how the apps and desktops are leveraged � if the user is always accessing a single desktop, a single layer works no matter how many devices they leverage to access that desktop. BUT if the user tends to use multiple resources (aka running apps from XA, multiple virtual desktops etc) then they will want their profile data to roam (aka Outlook signatures, Office settings, IE settings, My Docs, Favs etc). Using UPM and Folder Redirection (optional) enables this.

18. Install and Configuration

19. 19 New option in meta-installer (VDA) to �enable� PvD Installs no matter which option � just not �on� Install VDA is installed as normal into the base VM image, with the new installer you get an option to enable PvD or not, all the relevant files are installed anyway, if you need to enable PvD at a later stage you can.VDA is installed as normal into the base VM image, with the new installer you get an option to enable PvD or not, all the relevant files are installed anyway, if you need to enable PvD at a later stage you can.

20. 20 Run the inventory � New step when updating the base image Launches via Start Menu Shutdown reminder CtxPvd.exe -s inventory Inventory Once the VDA is installed and the base image is ready, run the inventory, this creates a template VM (along with the resource catalogue), this template is used to create all other PvD�s for new machines. Each time the base image needs to be changed the inventory will need to be run, this will update the template VM and allow any changes to be propagated to the other VM�s. This is expensive in terms of IO though, each VM will need to re-align the PvD�s.Once the VDA is installed and the base image is ready, run the inventory, this creates a template VM (along with the resource catalogue), this template is used to create all other PvD�s for new machines. Each time the base image needs to be changed the inventory will need to be run, this will update the template VM and allow any changes to be propagated to the other VM�s. This is expensive in terms of IO though, each VM will need to re-align the PvD�s.

21. 21 Creating Machines New catalogue types available in Desktop Studio.New catalogue types available in Desktop Studio.

22. 22 Creating a Catalog During a new catalogue setup you are asked for the size of the PvD and the drive letter to assign to it.During a new catalogue setup you are asked for the size of the PvD and the drive letter to assign to it.

23. 23 Host Setup Extra Storage Location Option available to place Personal vDisks When configuring a new host connection in desktop studio you can select where the PvD disks will be located, this can be on the same storage as other virtual machines or held on a separate storage location.When configuring a new host connection in desktop studio you can select where the PvD disks will be located, this can be on the same storage as other virtual machines or held on a separate storage location.

24. 24 The P: Drive � Once installed and running the user has three drives, C:\ P:\ & V:\ C:\ Here the user sees a merged view of the base image�s C: drive and the hidden V: drives applications and settings P:\ Persistent PvD drive The VHD created using the template is mounted as P: and in that VHD has another VHD on it and that is mounted as V: and is hidden and captures the apps installed/machine state. �Unfortunately this VHD on the volume is called UserData.vhd ... but it is really the machine state and not u"user data" UserData.vhd, contains only applications. Perhaps a name change would be useful. The Thick_provision file is a sparse file that has no space allocated but is EOF'ed/VDL'ed to indicate it consumes the required space available. Calculated by split in space for total user space between profile and apps minus the amount currently used by UserData.vhdOnce installed and running the user has three drives, C:\ P:\ & V:\ C:\ Here the user sees a merged view of the base image�s C: drive and the hidden V: drives applications and settings P:\ Persistent PvD drive The VHD created using the template is mounted as P: and in that VHD has another VHD on it and that is mounted as V: and is hidden and captures the apps installed/machine state. �Unfortunately this VHD on the volume is called UserData.vhd ... but it is really the machine state and not u"user data" UserData.vhd, contains only applications. Perhaps a name change would be useful. The Thick_provision file is a sparse file that has no space allocated but is EOF'ed/VDL'ed to indicate it consumes the required space available. Calculated by split in space for total user space between profile and apps minus the amount currently used by UserData.vhd

25. Let See it! � � P: Drive � data held here is retained through reboots of the VM and a PvD Reset, the users Windows Profiles are also held here so again, these settings are retained over VM restarts and PvD resets. This is the drive created when you provision the desktops from MCS or PVS Wizards. � C: Drive - (a mix of the base O/S Image and the hidden V: drive or UserData.vhd file held on the P: drive but not C:\Users which is re-directed to the P: drive) data here is retained during VM reboots (after all that�s what the PvD is for) but during a PvD reset from Desktop Director all data in the hidden V: drive or UserData.vhd is removed. � Demo Script: This is after explaining the whole C-P-V drive concept. Show the install of the new VDA � Options are to install or not, not installing will install all the required files but will not activate them, this allows you to enable PvD at a later stage if required. Once installed show the taking of inventory taking a snapshot ready for MCS � inventory needs to be taken every time the base image is changed, in MCS this is a manual task, in PVS this can be done with versioning or automated with the automatic update features of PVS 6.x Logon to a ready made MCS Machine. � Fill up the C:\Apps folder with about 1Gb of data, then look in Desktop Director to show the Personal vDisk Apps % has changed, I then show the P:\UserData.vhd and see that the size has changed. Install Firefox and Adobe Reader, again see the disk space change. Make changes to the currently logged on user, change the wallpaper, add Desktop Gadgets etc (something visual) Create a folder in the P:\ drive called �Keep Me� Show Desktop Director and the new changes to the Machine Details pane. Reset the PvD from Desktop Director Once the VM has restarted log back on as the same user and see that the user level changes are still present, and the folder �Keep Me� is still there, but the UserData.vhd file is now back to its original size and that Firefox, Adobe reader and any data copied to the C:\ (hidden V: or UserData.vhd) has now gone. � � P: Drive � data held here is retained through reboots of the VM and a PvD Reset, the users Windows Profiles are also held here so again, these settings are retained over VM restarts and PvD resets. This is the drive created when you provision the desktops from MCS or PVS Wizards. � C: Drive - (a mix of the base O/S Image and the hidden V: drive or UserData.vhd file held on the P: drive but not C:\Users which is re-directed to the P: drive) data here is retained during VM reboots (after all that�s what the PvD is for) but during a PvD reset from Desktop Director all data in the hidden V: drive or UserData.vhd is removed. � Demo Script: This is after explaining the whole C-P-V drive concept. Show the install of the new VDA � Options are to install or not, not installing will install all the required files but will not activate them, this allows you to enable PvD at a later stage if required. Once installed show the taking of inventory taking a snapshot ready for MCS � inventory needs to be taken every time the base image is changed, in MCS this is a manual task, in PVS this can be done with versioning or automated with the automatic update features of PVS 6.x Logon to a ready made MCS Machine. � Fill up the C:\Apps folder with about 1Gb of data, then look in Desktop Director to show the Personal vDisk Apps % has changed, I then show the P:\UserData.vhd and see that the size has changed. Install Firefox and Adobe Reader, again see the disk space change. Make changes to the currently logged on user, change the wallpaper, add Desktop Gadgets etc (something visual) Create a folder in the P:\ drive called �Keep Me� Show Desktop Director and the new changes to the Machine Details pane. Reset the PvD from Desktop Director Once the VM has restarted log back on as the same user and see that the user level changes are still present, and the folder �Keep Me� is still there, but the UserData.vhd file is now back to its original size and that Firefox, Adobe reader and any data copied to the C:\ (hidden V: or UserData.vhd) has now gone.

26. Troubleshooting and Support

27. PVD maintains logs in the base of the volume attached to the VM (alongside the VHD containing the PVD user-installed applications) These logs contain a wealth of information that should be captured and provided to support/engineering if customers experience problems Most frequently seen PVD support cases � Failure of PVD to start virtualization (PVD can�t locate volume/VHD, etc �) Customers trying to install unsupported apps (phase 0 apps, etc �) Customers trying to move PVDs between VMs Troubleshooting and Support

28. 28 PVDs can, in theory, be moved between VMs Requires administrator to use the hypervisor console and physically move the PVD volume Useful in cases where the user�s VM is entirely lost In general, this is not recommended If absolutely required, ensure the VM image is the same or substantially similar, and try to keep the same hostname Since PVDs are essentially just volumes in a storage tier, they can be backed up and restored like any other storage volume Customers should be doing this already! Troubleshooting and Support (cont�d)

29. 29 Desktop Director has helpdesk-facing PVD metrics and support % of application area in use / total size % of user profile area in use / total size PVD reset PVD reset allows the helpdesk to reset the application area while leaving the user�s data intact Ala �revert to factory default� Useful to reset PVDs that become wedged due to users installing broken applications Troubleshooting and Support (cont�d)

30. 30 When reporting PVD issues (PVD won�t boot, app doesn�t work, etc), collect � the PVD logs from the root of the PVD disk � OS version and type, bitness � list of applications installed in the base image (appwiz.cpl) � list of applications installed in the PVD, if applicable � which hypervisor, version (XenServer, Hyper-V, etc) � provisioning technology (MCS, PVS) and version PVD Support/Engineering will need this information to troubleshoot Diagnostic Information to Collect

31. Look in IVMSupervisor.log � This log contains early boot messages and may help isolate the problem Boot the VM from the hypervisorconsole and login Is the PVD present? Is the PVD formatted? Does the PVD have �proper� content (eg, \users folder and UserData.vhd file) Is the PVD full? Troubleshooting PVDs That Don�t Start