So, the key value associated with Unidesk is its layering technology. The reason for this is that it enables customers to have VDI deployments and not be consumed with worry to the same degree as are most shops that have persistent VDI instances (VDI VMs assigned to one user that are always available and always for that user specifically). It allows for non-persistent VDI VMs—the Holy Grail, for lack of a better term—for all VDI deployment scenarios. One golden image, which is deployed to users on demand.
Let’s say, hypothetically, that you have twenty thousand users worldwide, but that at any given time, generally only four thousand or so are concurrently connected and working. This means that if you have a non-persistent VDI deployment, you don’t have to have resources available 24/7 for twenty thousand users with unique VDI virtual machines, just in case they want to log in and get work done at any time and from anywhere, which is basically what the new SLA (service-level agreement) users have come to expect.
So why are these layers important? Well, each user has a “personalization layer” that lists all their apps. When that user’s non-persistent VM is deployed, guess what? Applications get layered on top of the VM based on what the administrator has assigned to that user. These don’t change, no matter when or from where the user logs in. You know what else never changes? Delta UUIDs, the default printer (unless the user changes it), computer names, and other sorts of things that you usually see with physical PCs. It is also a plus that the applications available to a user are only those the user has permission for, and that this can be changed only by the administrator, because it’s in the data center, not under someone’s desk. Guess what else? Service, driver, and DCOM support exist in the Unidesk universe, because to the VDI VM, applications act as though they are actually installed in the registry and the file system.
So what happens in the case of an outage? If (and, to be clear, this is unique to each company’s own disaster recovery policies)a company’s infrastructure with a VDI non-persistent designed architecture comes back on line and goes live, and the associated Unidesk servers come back online, then the user’s desktop comes back online. It is what it is, and some things just never change. It has to be there to work, right?
Unidesk is actively talking with all the cloud providers, and these conversations continue, but Rome was not build in a day, nor was it destroyed in a day. I say this to illustrate the fact that PCs still have a place in our universe, and they will for a while. Virtualization’s heavy hitters all have internal mobility groups committed to turning mobile devices (consumption devices) into productivity devices. They come up with any and every way to connect mobile devices to monitors, keyboards, and mice in order to allow endpoint users to be productive. I find it hard to believe that VDI is on its way out, or even just starting down the slippery slope to death. With the proliferation of access devices, Microsoft client operation systems must live somewhere. The place that makes the most sense is the data center. Now, I am not a psychic, but I have been around a minute, and it takes a long time for a solution to die, especially if there is nothing better available.
I recently interviewed Unidesk’s chief solution architect, Ron Oglesby, for the Virtualization EUC Podcast Series. Take a listen to our in-depth conversation, which covers pretty much anything and everything associated with VDI. And see if you can keep up—we are both fast talkers.
Episode 7 of my Virtualization EUC Podcast Series: http://recordings.talkshoe.com/TC-129734/TS-828019.mp3.