VMware Communities > Blogs > Virtual Desktop Blog > Tags

Blog Posts

Virtual Desktop Blog

7 Posts tagged with the vdm tag
7

What will Citrix do?

Posted by wponder VMware Mar 3, 2008

I wanted to wait till the smoke cleared before sharing some thoughts regarding Microsoft opening the specifications on several of its APIs and communication protocols. Part of the released technology was the specification of RDP.

For VMware VDI, this is probably the most interesting of the released protocol specifications. The initial impact to customers may not be that obvious. However, over time, the benefits could be huge. RDP is the preferred protocol for accessing VMware VDI based desktops. Currently, this makes the most sense to leverage as there is no added cost in doing so which is typically the case with third party add on protocols.

Although getting the optimal performance in broad set of network conditions can be tricky, but it's quite adequate in the highest majority of desktop replacement use cases. RDP has always had virtual channels which allow a third party to add feature functionality to RDP. For example, with VDM 2 we developed a generic USB device redirector that allows you to connect most USB devices, not supported by RDP to a client access device and make them available for use with your VMware VDI virtual desktop.

In order for third parties to leverage virtual channels, you either needed a team of lawyers and a chunk of change or some really good engineers that could reverse engineer. For some time now there have been licensees of the RDP spec and others who reverse engineered it in effort to add value. This included people building feature add-ons as well as full RDP client implementations. Open Source efforts such as RDesktop and commercial efforts from companies such as WYSE, VMware, ThinAnywhere, Provision Networks, Sun Microsystems, Calista and others have all contributed to enhancing RDP.

Over three years ago I started researching the use of VMware virtualization as a way to better manage and deliver desktop computing and overcome traditional server based computing short falls. As we started meeting with customers and sharing the vision of VDI it was becoming clear Citrix had lost their seat at the table. Customers were concerned with the issues surrounding Citrix as a solution, such as complexity, application compatibility and loss of a personal computing experience.

VMware VDI was resonating with IT organizations and desktop management teams as an answer for more broad desktop deployments. I was a little surprised, as no one can take away Citrix's past contributions to server based computing. It's always been my opinion Citrix and Microsoft had become comfortable with their position and the direction they were leading customers and the market.

As VMware VDI emerged it was becoming clear this was what customers wanted. I had not seen such vast interest and adoption of a desktop solution in a long time. Despite Microsoft attempting to down play interest, VECD emerged. As Citrix lost ground trying to protect the Presentation Server stronghold, they finally broke down, did a 360 degree about face, and sank 500M on XenSource.

Since they have renamed their legacy products and are attempting to broaden their vision beyond just "Application Delivery". Here at VMware we are building things from the ground up with virtualization in mind, not trying to retro fit legacy solutions to fit in a virtual world. Since the emergence of VMware VDI, millions of dollars are going into the R&D of network delivered desktops and applications. The result is innovation that improves user experience, desktop management and choice for IT organizations.

What does this mean for Citrix? For years there have been the conspiracy theories that Microsoft will buy Citrix. Over the years I have seen less and less evidence or reason to believe this, but I guess it could happen. For some time now, I have said Citrix is getting squeezed from the top by VMware and squeezed from the bottom by Microsoft. The crown jewel for Citrix is ICA. Without that, there is not a lot there you can't get from other cheaper more simple alternatives.

With the acquisition of Calista by Microsoft, it's clear they intended to continue the enhancement of RDP. With the RDP spec now open, more and more engineers can come to the party and rapidly further enhance RDP improving its performance and features in a broad array of use cases. With the XenSource acquisition, Citrix has dipped a toe in the open source world. Now that Micosoft has openly published the RDP specification, will Citrix set ICA free? Do they have any other choice? What long term value does ICA have with so many big companies now able to enhance RDP and in fact, already doing so?

7 Comments Permalink
5

It seems since late 2007 and early 2008 some virtualization players are still trying to hop on the VDI bandwagon started by VMware back in 2005. Since 2007, Citrix has been feeling the squeeze from the top by Microsoft with 2008 Server and Remote App around the corner, and squeezed at the bottom by VMware and the momentum of VMware VDI. Citrix had to do an about face on the Application Delivery strategy and messaging by getting in the VDI game with the purchase of Xen Source; an attempt catch up by trying to deliver desktops.

It also appears based on the recent release of a White Paper titled Virtual Desktop Infrastructure, SWsoft would like to ride the VMware VDI tailwinds. After reading this short overview on VDI, I wanted to offer some additional things to consider for readers that come across this paper.


“There are five components that comprise the VDI solution.”


A properly designed VDI solution is going to include more than five components. At a minimum, a proper VDI solution will encompass the following:


  1. Client Access – Fat Clients, Thin Clients, Repurposed PCs and or Mobile / Remote
    users.
  2. Virtual Desktop Management Services – Connection Brokering, Session Management and desktop provisioning such as what’s provided with VDM 2
  3. Virtualization Services – Such as what’s provided by VMware Virtual Infrastructure 3 including tools such a HA, DRS and VMotion that simplify the operations of a Virtual Desktop Infrastructure.
  4. Virtual Desktop Instances – Such as Windows XP and Vista
  5. Infrastructure Services – Such as Active Directory, File and Print, Email, employee portals etc.
  6. Application Virtualization Services – The legacy tools such as Citrix and Terminal Server used for delivering applications as well as next generation Application Virtualization tools such as Softgrid, SVS and ThinStall.
  7. Management Services – Such a VirtualCenter and other existing desktop management tools for patch management and software distribution such as Altiris, and SMS.
  8. Storage Services – The storage infrastructure for storing and managing the desktop images and data being centralized.
  9. Integration Services – The services and support provided to successfuly design, implement and integrate all
    these components, such as those provided by VMware.

“The simple purpose of the connection broker is to manage the end user connection with the virtualized desktops.”

The purpose of a broker is not simple. The role of a broker is very important in enabling VDI. At a minimum, a broker's offering should include:

  • Virtual Desktop Management
  • Session Management
  • Desktop Life-Cycle Management
  • Desktop Provisioning
  • Desktop Pooling
  • User management and entitlement to virtual desktop resources
  • Providing secure encrypted connections across un-trusted networks

All these thing and many more will be provided by VMware VDM 2. Customer looking for other alternatives can also leverage solutions from our VDI Alliance
partners that closely integrate with VMware VI3.

“VDI is a new technology that gives IT departments some choice and control over how to manage their exploding desktop infrastructure.”

VDI is not new technology. VMware customers have been deploying VMware VDI based solutions since 2005. I would say most the IT organizations I meet with do a really good job managing desktop systems. Although, they are looking for a better way to deliver desktop services, gain more control over their desktop architectures and inprove deployment and management efficency. Distributed desktop architectures are difficult and costly to manage, but I do not expect any explosions.


One area glossed over in this paper were Virtual Desktop Instances. One of many key driving factors increasing the adoption in VMware VDI, is the ability to virtualize and deliver Windows XP and Vista desktops. Doing so allows IT organizations to overcome the shortcomings of typical server based computing solutions such as Citrix Presentation Server and Microsoft Terminal Services, where application conflicts and the loss of the personal computing experience often inhibit mass adoption as the desktop environment.


According to the following requirements http://kb.swsoft.com/en/1446, SWsoft does not support or deliver Windows XP or Vista desktops. Providing each user a Windows 2003 Server is a costly proposition. If the proposition is to virtualize each server instance and then use Terminal Services, most people have come to agree that is not VDI, but rather consolidating Terminal Servers which are typically underutilized. Although Terminal Servers can be of value and Remote App is showing a lot of promise in extending the value of a VDI architectue; alone they do not offer all the benefits of a true VDI solution, to organizations with complex applicaition environments.

5 Comments Permalink
2

There are several approaches or strategies in attacking your VMware VDI desktop deployment from a design standpoint. Most organizations enter their architecture
with hesitation and reserve using a very static approach. They plan to map desktop users 1:1 each desktop user will be given a dedicated virtual desktop
and some division or swag is made regarding how many desktops they can concurrently run on each VDI server.

Really there is nothing wrong with that. Probably one of the most difficult tasks in planning a desktop migration, particularly when moving from a distributed architecture to a centralized architecture; is profiling your users, understanding the desktop compute cycles they need, and centralizing that in a
fair-share scheduling model. Because of the difficulty and effort required in looking at every user across the enterprise and coming up with a methodology that makes sense then getting the design right out the gate. I am a fan of getting sets of common users onto a VDI architecture and studying their usage patterns.

Ultimately a static 1:1 approach is not going to yield the highest return on your dollar. The more dynamic you allow the architecture to become. The higher
return you will realize. Often when I meet with customers and discuss their VDI architectures I talk about the concept of oversubscription. Oversubscription is
stepping outside the bounds of asking how many desktop users per core can I get, really understanding your users usage patterns, and figuring out how
many more users can be allocated per server by oversubscribing.


In most enterprise and office environments, as you walk around you will find large populations of empty cubes and idle desktops. Business is constantly changing and in order to stay competitive companies are being forced to change the workplace. More people are teleworking, using flexible work schedules and becoming more mobile. When users are in two hour long meetings or on conference calls several times a day, typically they are not using their desktops. When three out four people are not working on an exact 9-5 schedule the number of concurrent users is reduced. All of this combined results in an opportunity to revisit going beyond static VDI architectures making them more dynamic and oversubscribing the servers. With this approach mileage may vary in different cases. For example, a contact center environment where users are heads down, might not realize the same benefits.


As VMware VDI deployments have continued to grow and mature, customers are starting to explore unlocking the full potential of VDI. They have realized the benefits of VMware virtualization technology and are looking to gain more. As customers take a more centralized view of their desktops, they are realizing how underutilized or idle they are. It’s becoming clearer, oversubscribing the servers might not be that risky and the rewards could be great. Ultimately, this leads to a new set of questions as the creative juices start to flow.

There are several tools that can be used to harness the full potential of your VDI solution and make it more dynamic. In addition, it can actually be really simple or it can be more elegant. Each approach and the pro and cons of each is beyond this blog post. However, several customers have asked me to write about this and address some of the more simple or tactical questions.

As customers look at making their VDI environments more dynamic, The most popular question I get today is " How do I logoff idle users" followed by " How do I power off or suspend their virtual desktop". Recently I have been working with the VDI team at a collage who really wanted to do this and I felt obliged to help.

The solution is simple - VMware VDM 2 has a power policy for virtual machines that allows you to suspend or power off a virtual desktop instance when not in use. When a user logs off, it automates suspending or powering off that desktop. Ultimately this frees up the resources making them available to other desktops on the ESX server. If you think of those users on a flexible schedule or in a meeting there is no reason they need to hold up resources when idle.
Logging off these idle users is as easy as implementing a simple GPO in Active Directory that tracks idle time as well as those pesky disconnected RDP sessions.

Under the Local Computer Policy\Computer Configuration\Administrative
Templates\Windows Components\Terminal Services\Sessions folder, the following settings can be made:

• Set time limit for disconnected sessions
• Set time limit for active sessions
• Set time limit for idle sessions
• Terminate session when time limits are reached

Or

Under the Local Computer Policy\User Configuration\Administrative
Templates\Windows Components\Terminal Services\Sessions folder, the following
settings can be made:

• Set time limit for disconnected sessions
• Set time limit for active sessions
• Set time limit for idle sessions
• Terminate session when time limits are reached

Note: Windows XP has a bug where the idle tracker will not work. You
need to request a hot fix from Microsoft in order to resolve it. See KB890864

The result in the combination of the VDM 2 power policy and this simple GPO is idle users are logged off at a time interval you set, and their virtual
desktop is powered off or suspended. Simple to implement with large benefits.

To protect you from oversubscribing too far, increasing the SLA of your desktop users, and making the environment more dynamic. VMware DRS and VMotion can be added. If you are more aggressive with your oversubscription using VMware DRS you can set a threshold that ensures your users are not affected. For example, if you know your virtual desktops perform best at 8 users per core, but have over subscribed to 16 user per core; expecting only 50% are concurrent at any given time. VMware DRS/VMotion will ensure the 9/10/11 user per core is run from another ESX server with available resources. This can be as simple as having a standby server or allocating the sessions across other underutilized servers in the cluster.

2 Comments Permalink
0

VDM 2 - Beta2 now available

Posted by wponder VMware Nov 30, 2007

The VDM 2 - Beta 2 is now availalbe for download! Thanks to all the customers and partners that participated in the VDM 2 - Beta 1. Becuse of your participation, were able to collect a tremendous amount of feedback an input regarding what's most important for your VDI environments. The interest and response to VDM 2 has been tremendous.

With Beta 2 there is a lot to look forward too. The UI has a ton of improvements. The new web based administrator look and feel as well as the added visual notifications should be well received.

Based on all the feedback coming in from the beta participants the pooling has been revamped. It has been simplified while still allowing an option for advanced configuration if needed.


If you were not able to participle in Beta 1 or were waiting for Beta 2 you can still participate. Click the link below and register to download Beta 2.


VDM 2 - Beta 2 registration, go to the bottom of the page

0 Comments Permalink
0

VMware Lab Days a huge success

Posted by wponder VMware Nov 27, 2007

Just before Thanksgiving we wrapped up a series of Lab Days hosted by VMware and sponsored by our partners. These were two great events with several hands on labs, all things virtual. The best part is it was all FREE! You can not beat FREE! If you did not get a chance to attend, stay tuned for more events.

The Lab team did a tremendous job with coordination and setting up, I was blown away. All I had to do was show up, talk about VDI and run the Virtual Desktop Manager 2 lab. You can not beat that at all!!!!!


Thanks to all the customers and partners who took time out of their busy schedules to attend.

IMG_0092_jpg.jpg


Set-up team in Chicago


CIMG2766_jpg.jpg


VDM 2 Lab

0 Comments Permalink
0


This week I returned from Holiday. Nine days in mostly remote areas across Idaho and no email. We have been planning to move to Idaho for
some time now. during this trip we spent some time looking at homes and getting more familiar with the Boise area.

I am still trying to dig out of the email an get back on track and just keeps piling on. While I was gone the VMTN team updated VMTN at vmware.com. With the new version there is now a blogging capability.


Last night I took on the painful task of migrating over to the new site. I did the best I could. I think I have all the entires. I know I have missed a few comments, but I did the best I could to get them all moved over. If I missed anyones comments I am sorry, it was not intentional. On that note, this will be the last post here. Eventually, I will cancel this blog.


The Virtual Desktop Blog can now be found at its new home Virtual Desktop Blog

0 Comments Permalink
0

I was so slammed at VMworld over the last week that I have not had the
time to let everyone know the Beta 1 for VDM 2.0 is now available.

VDM 2.0 is a session broker for VDI deployments offered by VMware and is a new product built from the Propero technology we acquired back in April of this year. Over the last few months the team has been hard at work so we can deliver on the design goals we set for this release of the broker. At this stage we are really focused on simplicity and saleability. One of the biggest changes for the initial release from the original Propero technolog wasporting to Windows. This release is only supported on Windows 2003.

Technically, there are a lot of things that occur when VDM 2.0 is installed, but we have simplified that process in the installation procedure. The installation is a single MSI installer. It takes about five minutes to get the initial VDM server in a group installed and ready to configure using the web based administration. In the coming weeks I will be sharing more on the architecture and available features. Anyone thats interested in
participating in the beta can find the registration page this URL - VDM 2.0 Press Release

0 Comments Permalink
Click to view wponder's profile

wponder

Member since: Apr 5, 2006

A blog about VMware Virtual Desktop Infrastructure

View wponder's profile