As most of you will have heard by now, Ringcube is now part of Citrix, who integrated Ringcube’s “vDesk for VDI” into XenDesktop 5.5 as their new “personal vDisk” technology.
Personally, I haven’t heard from them before, so I was kind of curious about what this “new” technology might hold for us.
Installation is pretty easy and straightforward, not that much to do wrong actually.
I installed a new Windows 7 VM on a XenServer pool, installed all necessary updates and did some of the configurations recommended by Citrix in their Windows 7 Optimization Guide.
Inside the only 17MB large install sources for “Citrix personal vDisk” is a nice paper which guides you through the installation and configuration.
On the server side, there isn’t much to see or do, only two powershell scripts, one, which will help you create the personal vDisk, the other one to query your Desktop Groups for some statistics.
What does “personal vDisk” even mean?
Usually a desktop’s storage created by the XenDesktop MCS looks something like this:
We have the Difference Disk and the Identity Disk. That’s it! Changes to the OS are stored to the Diff-disk and usually discarded at reboot.
Now what the personal vDisk does, it creates a third disk where all the changes to the OS are stored, for example a user installs an application, a browser or even a driver, and those changes are not discarded. They are redirected by a file system filter driver, so that if an installer tries to install to the “local” system drive, it actually gets redirected to the “personal vDisk system drive”. I will show you how this looks in a second.
Installation on the client side means executing a msi, depending on your architecture you either use personalvDiskInstaller.msi or personalvDisk64Installer.msi.
There’s nothing to configure, you just click “next” five times and that’s it.
After successful installation you’ll find a new taskbar icon.
By choosing ”preferences” you open the vDisk GUI, and, again not that much to do.
By default the vDisk is going to be mounted as drive letter V:, and this drive will be visible to all users unless you hide it from them, which will reduce the helpdesk calls quite a lot. You are probably doing the same with App-V’s drive “Q:” or PVS’s write-cache drive.
You will get more information on each option by clicking the round, blue “I”.
Before shutting down the VM you have to update the “personal vDisk inventory”, otherwise you will get into problems later on.
As the next step I took a snapshot of the shut-down VM from which I am going to create my Desktop Catalog in XenDesktop Desktop Studio.
By design, for now, the only pool type supported is “pooled-static”. This is due to the fact, that the vdisk needs to be mounted really early to support adding drivers or kernel objects for example and this doesn’t work with “pooled-random”.
The overview of my created catalog looks like this:
After hitting finish the VMs get created, this might take a few minutes, depending on your environment.
As soon as the VMs are visible in your hypervisor (in my case XenServer) we can continue with the creation of the VM’s personal vDisk.
Before creating the vDisks you should think about where you want to store them and if it might be wise to use thin provisioned storage. I have XenServer 5.6 SP2 with EXT3 as file system, so I will definately use thin provisioning in my environment.
The default size of the personal vDisk is 2GB, depending on your use case this might be enough or maybe not. When using thick provisioned disks you have to have a lot of storage capacity: storage needed = (desktops * (size of vDisk))
I am going to give my vDisk 5GB of storage and because it’s thin provisioned it will, at the beginning, only use near to nothing of it.
Again, it’s only a few steps until we’re finished.
Either start the Powershell from the start menu or from the “Actions” tab in Desktop Studio. Then change to your install path of the “personal vDisk Server Tools” and execute
The script will ask you a few questions which you will have to answer in order to create the vDisks.
First you select the just created catalog: Next the storage where you want to have your vdisks put: At last the size of your vDisks: The script will now create the vDisks for all the desktops in this catalog and at the end tell you if it was successful or not.
How does this look in XenCenter?<
See how a third disk has been added to our VM and how, at the moment, it takes up 0% of its assigned 5GB on the XenServer’s storage?
Coming to an end of this article I will just give you a quick look at how this now looks in the OS. For this I created a Desktop Group and launched the desktop from Webinterface.
Looking at Windows Explorer you will now see (if you didn’t chose to hide the drives) two more drives than you would expect to.
In my case drive F: contains all the Logs and the VHD file “personal vDisk” uses to store all the changes in and drive V: is the mounted VHD file. Remember, earlier, you could have chosen to hide drives from the user, plural! This is why.
Looking at V: you will notice that this looks quite a lot like your C: drive. I told you that the file system filter driver redirects changes on C: to your personal vDisk. So whatever the user changes on his system will eventually land on V: and because of that also on my F: drive, the VHD.
I will go on and play a bit with this nice new feature of XenDesktop 5.5, it does look quite cool and I hope that some customers will come to the same conclusion.