Managed Application Delivery

Any tool that we have used in the past can still be considered. I will just take one easy example, and that would be applications that are delivered via Group Policies (you can insert your tool name to replace Group Policies). While it is still possible to deliver applications in this fashion, we would still be tying the application to the desktop the user is working on. I like to try to transition away from this, though it is not always possible.

If I am continuing to use Group Policies, I may need to rethink the association of how these policies are tied into Active Directory. Do I still want to delver applications to computers object, or is it now more appropriate to deliver these applications to user objects? How will application installation affect the VDI images (and more importantly, how much space is consumed on the SAN)? How do I manage updates of these applications, and full upgrades as the versions inevitably increment year after year? Again, I would not throw out this type of technology, but I would not use this as the primary mechanism for delivery of applications if it can be avoided.

Virtualize Your Applications

Any tool that can wrap up an application into a single EXE file (the same way that Virtual Machines are really just VMDK and VMX files) sounds too good to be true. I’ll discuss ThinApp, and you can insert your tool of choice.

Virtualizing your application into an EXE file requires you to have an understanding of what your users need to do with an application, and then you capture that installation, and publish the EXE to the user. It might exist on a file share, and be accessed by many users at one time. It might be copied onto a USB stick, and shared with contractors or remote users. It might be copied to a laptop so a road warrior can always have those tools with him as he waits for his flight to board.

I like the idea of virtualizing the application. I want to ThinApp every application I can, so I have a strong bias here…but after you dive into how to maintain ThinApps for a wide user base, you may have the same opinion. Updating an application for end users is as simple as creating a new ThinApp package, and replacing the existing EXE file they are using…next time they start the application, the new version is running!

Summary Of Application Delivery

The ability to reconsider how you manage, deploy, update, and control the applications end users consume on your business computers is going to be a large part of your VDI Proof of Concept. Be ready to explore the combination of the varied methods available to deliver applications. I truly believe that by separating the application from the traditional dependencies that currently exist (when we install applications onto the desktop), a VDI solution can actually deliver on the promised ROI when you consider keeping applications up to date, running, and more importantly…keeping the user productive with those applications.

Selecting VDI Proof Of Concept Candidates

This is by far, one of the easiest choices for me, if I have control over the Proof of Concept testers. The IT team. These are the people who will understand any problems that they are running into, can articulate the problems as well as the resolutions, AND they would be the ones responsible for supporting users who will use a VDI solution. I can think of no reason why this should not be the first adopters of the VDI solution.

Thin Client or Repurposed Desktop PC’s?

Do you go out and buy a ton of Thin Clients, to replace the desktop PC’s? Possibly, but realistically not during the kicking of the tires or Proof of Concept. You will realistically be purchasing a few Thin Clients, perhaps even from various manufacturers, so you can find the ones that deliver the desktop experience your users require, while providing an easy and streamlined mechanism for managing the thin clients. (I would not want to replace the traditional desktop PC with a device that needs just as much management, just so I can get to the ‘cool’ new Virtual Desktop.) Repurposing PC’s? Fine for the initial testing and Proof of Concept (while testing Thin Client devices). Long term vision for me is to get rid of the desktops PCs, be it during the normal lifecycle replacement, or as I roll a VDI solution out to different groups in the organization.

This goes back to the facts that Thin Clients use less power, are easier to manage, and are just dumb devices that allow a user to access their desktop. Replacing a whole organization just for the sake of replacement is not necessarily a great idea, but it is a great end result that you can be shooting for as you roll out a VDI solution.

Selecting a Thin Client can be made easier when you work with a partner who can provide you an unbiased recommendation to help you align with your business needs (keeping the user base productive and happy). They have done this before, have some experience in the end user experience, and know your environment intimately enough to make some great suggestions.

Starting Your Proof Of Concept

So each organization’s needs will vary, but let us assume the best of situations exists for our Proof Of Concept.

Dedicate a server for the Proof Of Concept

We would want to dedicate a well configured server to running our Virtual Desktops. Be it a VMware, Citrix, or Microsoft solution, it will be in your best interest to see how well a server can run the desktops, give you some dedicated resources to running Virtual Desktops so you get an accurate view of the levels of performance you can provide for your user base, while centralizing those resources.

Dedicate some time for your IT staff to ‘play’ with the technology.

The IT staff is your most trusted resource internally for technology consumption. Give them the power to spend some time exploring the way this technology can change the way you support and deliver the desktop operating system to your users, as well as the applications they require to stay productive. As they will be the team that gets the first Virtual Desktops, ask them to use ONLY the VDI delivered desktop operating system to truly get a feel for the way this solution can work.

Define goals for the success of the Proof Of Concept

Why even do a Proof of Concept if there is no goal? You can make it as simple or complicated as you want, but I like to keep it simple. Is there any difference from running a tradition desktop PC? Does this impact the users’ productivity? What options do I have to address any issues that arise? How are we handling USB keys? Does the operating system & the applications perform as well as on a physical desktop? How invasive is a major desktop patch in the world of VDI for my organization?

Whatever you define as questions you need answered, make sure the team knows about these, has answers to them, and can provide you with a report (even if it is not a formal written report) regarding the measured criteria you set forth in your VDI Proof of Concept.

A Trusted Advisor can expedite a Proof of Concept

At the risk of including some sales sounding lingo here, I think this is an important item to include. A Partner (be it a consultant, reseller, or anyone who has experience in the solution) is an important resource to bring on board when considering a shift in the way you deliver desktops. They will bring best practices, past experiences, and can assist you in avoiding a long drawn out proof of concept. VDI itself is still relatively new, even though the use of a Virtualized Infrastructure is now an expected datacenter skill. If you are considering this as a solution for your IT organization, kick the tires a bit yourself, but when you want to design, scale, and build out a procedural change in the management of the desktop infrastructure, I find that I have been able to lead teams in the transition from tradition desktop management and empower the teams to take advantage of the benefits of having a VDI delivered desktop solution.

Good Luck, and have fun exploring VDI!

Since 1996, Mark Gabryjelski has been involved in design and integration of solutions for clients in all markets. With focus on datacenter optimization, he has worked with companies across all aspects of business. Leading the virtualization trend since 2001 nationally, with a focus in the Northeast corridor, he has been on the bleeding edge of solutions involving network, storage, server, operating system, and application virtualization. Mark is currently Senior IT Consultant at CAS Severn. Contact him here.

Pages: 1 2