Virtual Desktop Blog

VMware VDI - VDM 2.1 Reviewer's Guide now available

wponder — Fri, 06 Jun 2008 03:33:00 GMT

I am pleased to announce the availability of the VMware VDM 2.1 Reviewer's Guide. I had the honor of working with Doug Brown, founder of DABCC, well known expert and long time contributor to the Server Based Computing, Application Delivery and Virtualization communities. Many of you might be familiar with Doug Brown's Methodology in Box (MIAB) deployment and install guides. Doug's MIAB takes a step-by-step approach to deploying and installing server based computing and virtualization products.

By taking a simple step-by-step real world approach MIAB can ensure audiences from all levels of technical aptitude and background are ensured a successful deployment.

Partnering with Doug for the creation of the VMware VDM 2.1 Reviewer's Guide just made sense. Who better to help create this guide. The VMware VDM 2.1 Reviewers Guide is a subset of a typical DABCC (MIAB), with the goal to provide a step-by-step guide for people interested in evaluating VMware VDI for their VMware based VDI deployments. By using the the VMware VDM 2.1 Reviewer's Guide new comer to VMware VDI and VDM 2.0 can quickly and easily get a full VMware VDI environment up and running for evaluation.

At a later date Doug will follow-up this work with a more extensive MIAB available from DABCC.

For more information about DABCC please visit - www.dabcc.com

The VMware VDM 2.1 Reviewer's Guide can be found here - VMware VDM 2.1 Reviewer's Guide

VMware Project North Star ( Thinstall )

wponder — Fri, 07 Mar 2008 20:51:00 GMT

I am pleased to share with everyone the first public Beta release of VMware Project North Star ( Thinstall ) is now available for download.

VMware Project North Star (Thinstall) will be the first branded version of Thinstall application virtualization technology.

This beta is the first step towards launch of a fully supported and widely available release of the technology as a VMware product. We are excited to enable VMware customers - both existing and new - to experience the benefits of application virtualization firsthand from within the VMware community.

Intrested in How to get the software? Go to http://www.vmware.com/go/thinstall

Beta Participant Support

There is no active support available for this Beta release of VMware Thinstall . However, VMware welcomes and appreciates your feedback. You can file any product suggestions directly onto the VMware community forum. If you run into problems installing or using the product, we suggest using the following excellent resources:

VMware community forum:

http://communities.vmware.com/community/beta/northstar

Product documentation:

http://www.vmware.com/products/beta/northstar/project_north_star_beta_manual.pdf

Sales Inquiries

Thinstall 3.3 is available for purchase today. All customers who order Thinstall 3.3 today are eligible for an automatic upgrade to the VMware Project North Star (Thinstall) product when it is generally available (GA). Please contact sales@thinstall.com, your VMware Sales team or VMware Partner for any sales inquiries on Thinstall 3.3.

Please stay tuned to www.vmware.com/go/thinstall There will be another beta shortly and it aims to include some very exciting features!

VMware - vmSight webcast

wponder — Wed, 20 Feb 2008 20:21:00 GMT

vmSight the leader in virtual network intelligence will be hosting a webcast detailing how VMware VDI and vmSight can be used to gain stronger and sustainable HIPPA and PCI compliance. The webcast will be hosted Feburary 26th and there is still time to register.

Executives, IT auditors and systems administrators responsible for validating security and compliance in virtual environments or others who are considering the move to a virtual environment and want to understand how they can benefit while addressing regulatory compliance concerns should consider taking the time to listen in.

For more information and registration please visit the following URL

Achieve Stronger and Sustainable HIPAA and PCI Compliance with Virtual Desktops

VMware VDI - Virtual Desktop Manager 2 Released

wponder — Tue, 05 Feb 2008 02:44:00 GMT

Last week at VMware we reached a major milestone in moving the next generation of desktop computing forward with the release of VDM 2. First I would like to thank the 1000’s of beta participants who took the time and downloaded, tested and provided enormous amounts of feedback. It’s all the tremendous feedback that will help us continue to deliver innovative features that help you execute and deliver your next desktop architecture.

Second I would like to thank the engineering teams that invested countless hours and sleepless nights to deliver a high quality product building a solid foundation that will shape the future of virtual desktop management. In 2005 VMware started executing on the VMware VDI vision. Since some of the biggest names in server based computing have completely changed their business models, rebranded their products, adjusted their message and spent 100’s of millions of dollars in effort to adopt the vision of VMware VDI.

VDM 2 was not a rebranding exercise of slapping a VMware VDM 2 logo on some legacy product. It was a completely new product built from the Propero technology acquired in 2007 with the vision of virtual desktop management in mind. Rather than taking the high road and fastest time to market a conscious decision was made to build a solid foundation from which the future of virtual desktop management could safely rest.

Some of the enterprise class features offered in VDM 2 included:

Support for multiple VirtualCenter instances
Support for existing individual virtual machines
Support for provisioning virtual desktops using persistent and non-persistent pools
Support for XP and Vista virtual desktops
Support for XPe, XP, Vista, 2000 Pro, Linux and integrated thin client devices
Advanced power control policies for automating suspending, powering off, powering on, destroying and resuming virtual desktops
Support for live migration of running desktops using VMware VMotion
Support for granular resource allocation using VMware DRS
Support for higher availability of virtual desktops using VMware HA

These are just a few features available in this release of VDM 2. In addition we have added a new community forum for VDM 2 that can be found here

~~c-2553~~

We also have started to release several deployment guides and tech notes to help with your virtual desktop deployments. If there are other topics you would like to hear about please feel free to send me your requests.

Using the Wyse V10L and S10 Thin Clients with VDM
Introduction to Virtual Desktop Manager

Windows XP Deployment Guide

VMware VDM 2 Load Balancing Guide

http://www.vmware.com/pdf/vdm20_intro.pdf

Thanks again to all the VMware VDI customers for your support.

Sorry guys, the bandwagon is full....

wponder — Fri, 11 Jan 2008 21:40:00 GMT

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:

Client Access – Fat Clients, Thin Clients, Repurposed PCs and or Mobile / Remote
users.
Virtual Desktop Management Services – Connection Brokering, Session Management and desktop provisioning such as what’s provided with VDM 2
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.
Virtual Desktop Instances – Such as Windows XP and Vista
Infrastructure Services – Such as Active Directory, File and Print, Email, employee portals etc.
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.
Management Services – Such a VirtualCenter and other existing desktop management tools for patch management and software distribution such as Altiris, and SMS.
Storage Services – The storage infrastructure for storing and managing the desktop images and data being centralized.
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.

Virtual Desktop Blog is on the move

wponder — Wed, 03 Oct 2007 17:20:00 GMT

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

VMware VDI - VDM 2.0 Beta now live

wponder — Sat, 15 Sep 2007 14:50:00 GMT

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

VMware VDI - VMworld session you don't want to miss

wponder — Sat, 08 Sep 2007 15:37:00 GMT

Not a lot to share lately. I have been traveling for the last three weeks and will be traveling through the early part of Oct. Last week I
was in London, the VMware VDI team all got together for some great meetings and sessions. I have also been heads down working on a few new
papers and getting ready for VMworld. Just after VMworld I am finally taking some time off for some much needed Fly Fishing! If anyone out
ever wants to go let me know. It needs to be in the Rockies, Canada, New Zealand or South America though, because I like to go WAY out.

Sorry I digressed, can you tell I am ready to go! VMworld is a few short days away and I will do my best to post some
pictures and updates from there. Anyone attending swing by the VMware booth, say hi and share your experiences on how you VMware VDI efforts
are going! There is one session you will not want to miss.

Mark Benson, a VDI Solution Architect with the VDI development team will present the following session on Tuesday 9/11

DV18. Tuesday 9/11 5pm – 6pm.

“VDI with VMware’s Next Generation Connection Broker - Architecture, Security and Deployment Scenarios”

“As many people are realizing the potential of hosting desktop operating systems on VMware ESX Server in the data center, aspects of
access security, scalability and high availability become increasingly important. This session discusses the architecture of VMware’s next
generation connection broker from a design perspective, paying special attention to the security features and deployment scenarios supported.
We’ll also provide insight into how the product was developed to simplify the operational management needs of VDI in large production
environments.”

Just after the session will also be a “meet the developers” session for 90 mins immediately following the session. This will be a great opportunity to meet the team.

See you there!

VMware - ACE 2 - Pocket ACE Guide - Now Avialable

wponder — Tue, 21 Aug 2007 04:42:00 GMT

Early this summer I wrote a guide covering Pocket ACE that has finally made its way through the system. Pocket ACE is a new feature included in the release of ACE 2 Enterprise Edition. Pocket ACE allows an ACE Administrator to deploy a Virtual Machine to a portable storage device. A user can take that portable
device and run their virtual machine by attaching the device to any supported x86 based system.

I wanted to take the time to acknowledge a few people that were instrumental in helping along the way. Matt Ginzton, Gilad Ben Zeev, Chris Leroy and Ed Albanese. Matt is a Sr. Staff Engineer at VMware and always helps me with all things ACE and Pocket ACE related. Gilad is a Sr. MTS Engineer at
VMware and played an important role in helping me better understand our instance customization. Ed Albanese is a Product Manager at VMware. Ed plays an important role by directing and reviewing content and ensuring the highest quality. Chris Leroy is a Sr. MTS Engineer at VMware and helped in the areas of disk i/o
performance, sync performance and overall review contributions. This guide is intended for IT Architects and technical influencer's looking to better understand
Pocket ACE. I hope you find it useful. The guide can be found here, VMware Pocket ACE Guide.

VDI - Cardinal Healthcare - Webinar

wponder — Thu, 26 Jul 2007 15:30:00 GMT

Last week I had the privilege of doing a joint webinar with one of our first VDI customers, Cardinal Health. I was joined by Justin Hooper, Director of Windows Systems at Cardinal Health. Cardinal Health is the largest worldwide provider of health care solutions, with over 40,000 employees. They are global in nature and are recognized by Fortune Magazine as one of America’s Most Admired Companies.

Cardinal Health was an early adopter of VDI and selected VDI from VMware to support and deliver the desktop infrastructure of two mission critical call centers. At the time, there still was not a lot of information available regarding the architectural choices and deployment practices of VDI based solutions. Justin and his team did a tremendous job of being innovative in order to design a solution that meets the business requirements of Cardinal Health. One of the most innovative things I
feel they accomplished was in how they executed their client side strategy. After evaluating different alternatives from PC’s to thin clients.

They decided to go with low-end PC’s. Because VDI was new at the time, Justin’s team had to create their own custom image. The image is PXE booted from the network by each of the client end points. In essence this enabled them to create their own low cost unmanaged client end point. When a device is powered on it downloads its image from the network. Once the boot process is complete, the user is given a chooser created by Justin’s team for selecting the environment they need. Once the user has made their selection, a connection is established to their hosted virtual desktop.

Simple, clean and affective. This client side approach is also an effective way for organizations to move to a Virtual Desktop Infrastructure today, while still leveraging the existing investment in desktop hardware they might have. In addition, it provides a clean and effective migration path to adopting alternative client devices such as thin clients, once the PC investment has depreciated. In this webinar Justin shares with us the architectural details and lessons learned from their
deployment. The webinar can be found at the following location, Select recorded webinars and its listed on page 2:

Cardinal Health’s Call Center PC Virtualization with VMware Virtual Desktop Infrastructure VDI

VDI + RemoteApp = Match made in heaven

wponder — Mon, 23 Jul 2007 17:40:00 GMT

The Terminal Server team has been really busy over at Microsoft and the fruits of their labor can really be seen in the latest release of Longhorn Beta 3. Potential and existing VDI customers are always telling me they really want a simple, clean, low cost and easy to manage way of delivering, existing and candidate applications compatible with Terminal Services to their desktops.

One of the features I have been waiting to see from 2008 server and the Terminal Services team is RemoteApp. RemoteApp is a new feature that introduces usability concepts that have been around for a while, but have really started to take off even more, as the desktop environment continues to change.

So what is the concept? A RemoteApp application accessed from a Terminal Server displays as if it was another application loaded on the user’s local desktop. This concept is nothing new really. On the Terminal Services front there have always been seamless windows from Citrix. Sun’s SGD product had the concept of the integrated client that took the seamless windows concept a step further by integrating the applications into the start menu and desktop.

On the virtualization front, its similar to the Unity feature of the VMware Fusion product for MAC. In order to leverage RemoteApp with VDI desktops, XP desktops will need the RDP 6.0 client installed. Vista desktops will have this by default. Getting started is simple. Any application loaded on the Terminal Server can be selected as one available, as a RemoteApp using the TS RemoteApp Manager. Once you have selected the applications that will be available, you have the option
of creating an .rdp file or .msi package. These contain the connection and configuration information of the application and can be distributed to VDI desktops using file shares or software distribution methods.

As a quick test, I loaded Dreamweaver 8, created an .msi package and published it via Software Distribution using Active Directory. Once installed, an application icon shows up in the Start Menu under Programs/Remote Programs. An icon can also be created on the users desktop if desired.

When a RemoteApp is started, a splash screen will appear indicating that an application is being started. This really is the only indication to the end user that the application is remote. An important note is if more than one RemoteApp is run simultaneously they share the same Terminal Server session.

Once the application is running you can see, not only does it run as a seamless window, but it also carries the theming from 2008.

RemoteApp should be exciting to VDI administrators because of how cleanly it’s implemented. When available, it should prove to provide a simple and clean way of
providing centrally hosted applications to VDI desktop users.

Adding users to the local Remote Desktop Users group

wponder — Tue, 03 Jul 2007 15:24:00 GMT

Currently, I am working on a best practices guide for building VDI hosted XP desktops. It’s been an interesting exercise. Most the content is stuff I have collected over the years and has been repeated a million times across the Net. In a lot of ways it really is no different than building a solid standardized image for enterprise based PC's. The hardest part has been putting as much useful information in it without letting it creep and it end up being to long.

Last night I was doing some testing, when I should have been spending time with my dogs, for a section that is hands down the most commonly asked question I get. How do I add users to the Remote Desktop Users Group? This is one of the most common VDI stumbling blocks. There are a couple of approaches. Probably more than I am listing below even.

1. You could create a startup script that populates the local Remote Desktop Users group with users or groups. The script can be managed through GPO by adding it to the Computer Configuration\Windows Settings\Scripts\Startup Policy.

When using this approach, I prefer to create a group called VDI users in AD, and populate it with users that will use VDI virtual machines. This group is then added to the local Remote Desktop Group at start-up.

A sample code snip-it is below.

option Explicit

Dim objGroup

Dim strComputer
strComputer = "."

On Error Resume Next

Set objGroup = GetObject("WinNT://" & strComputer & "/Remote Desktop Users,group")

objGroup.add("WinNT://DOMAINNAME/VDI Users,group")

Set objGroup = Nothing

2. Another approach is using a Restricted Group. Under Computer Configuration\Windows Settings\Security Settings\Restricted Groups add
a group.

In this case I use the built-in Remote Desktop Users, once created add the appropriate users from this Restricted Group GPO Each has its pros and cons but this should give you a starting point.

VMware Fusion enables another Switcher

wponder — Wed, 20 Jun 2007 23:23:00 GMT

Fu - sion – noun the act or process of fusing; the state of being fused. A long time ago, early in my career I never would have imagined I would need or want to use anything beside Windows. I started out as a Windows Server and Network admin. I really had no aspirations or interest in learning other operating systems. Over time, that changed as our business was looking for alternative and innovative ways to do things.

Ever since, I have helped customers find alternative ways to do things and focused on interoperability, primarily in the desktop space. Before joining VMware, I worked for a company that ran zero Microsoft products, no Windows Operating Systems and no Windows or Windows based applications. The also were thin. They had over 38,000 thin clients deployed globally. Talk about Green. They were Green before Green was in.

I was there for six years and was exposed to every alternative imaginable. They had quite a few Macbook pro’s running around. I myself did not have one, but was always enamored by their design. I never really thought it was practical for me to use one.

I live in a VM, I have VDI in my office and work from a virtual XP desktop day to day. I use offline files and folder redirection for syncing between my VMware assigned laptop and my VDI desktop. When I came to VMware, I got the standard IT assigned laptop that was about good enough to run Word and Outlook. Trying to run all the VM’s I needed for testing and generating content, plus doing my day to day work when traveling just sucked. I could not stand it any more. I really needed something with a a little more RAM and more importantly something faster than a 4200 RPM drive. Between the pain of the IT assigned laptop, falling prey to the continued assault of MAC commercials and the day to day glow of the Fusion team. I started looking into getting a Macbook pro, as I knew Fusion would be the ticket too bring it all together. I waited and waited till the Santa Rosa systems shipped. Then a few weeks back, I officially broke down and got a Macbook Pro. I would not quite say I was a switcher yet. I really was only looking for a well designed machine that had enough power to do what I needed when traveling, doing demos, testing etc.

The plan was to run XP by moving my assigned laptop image over, piece of cake by the way using converter, built inside ACE 2. Then, I figured I would load Vista since I had not seen Aero and needed to do some VDI testing. I had been doing VDI testing and playing with the desktop environment. I like it, I think its sweet. I like the sidebar etc.Before I loaded Vista, I played with OS X a little and got familiar with Expose, the dashboard etc. I have never used a Mac and was getting my bearings. Finally, I loaded Vista in a boot camp partition. Well, Aero 3D flip was a disappointment, too me its just a 3D alt-tab. OS X expose, and the dashboard are much more appealing.

At the end of the day, I needed XP and Vista and OS X was growing on me. In steps Fusion after all, I had been dying to play with our unity feature. I am just
blown away, thus far it exceeds my expectations and really is exactly what I was hoping for, seamlessly integrates the desktop experience with Unity. It’s simple to switch between Unity or a full screen Windows desktop. I can create snapshots of my laptop image. I run can run my boot camp partitions as VM’s. USB device support. If you are considering switching but still need to hang on Fusion is the ticket. It is the ultimate interoperability tool.

Fusion

FusionXP desktop running as a single window

Fusion

FusioniSight camera is connect to the VM!

Fusion

Fusion Unity View of my XP desktop. Each application is independent . See Outlook in the dock!
Fusion

FusionExpose of with Unity!

Fusion

FusionExpose with Unity!

Fusion

Fusion Expose with Unity!

NEC VPCC based VDI

wponder — Wed, 06 Jun 2007 23:59:00 GMT

Last week I was in Japan meeting with the local VMware teams, customers and partners. One of the highlights of my trip was getting the chance to catch up with a great VDI partner NEC. NEC was one of the early partners who joined the VDI Alliance, and was one of the first too launch an end to end VDI solution leveraging VMware's VI3. At VMworld last year, NEC announced their VPCCsolution which was one of the first end to end VDI solutions that offered everything from client to storage. In addition, it was the first solution offering a solution that addresses Multimedia performance issues often found with SBC and thin client solutions.

Their efforts included working with other leading technology providers in the industry and resulted in the first thin client device and software that enables multimedia formats to be decoded on the client side rather than the server side. Because their thin client device, the US100 is a thin-os device. There is little too no management required when compared to other devices that run an embedded OS. Therefore, you end up with the best of both worlds in a client device that requires no management, but can also deliver a PC like multimedia experience. Another feature of the VPCC solution is the tight integration with their IP Telephony products.

The VPCC solution is packaged to fully support the NEC VoIP offerings as well. Not only is this bundling unique but the multimedia integration with the US100 is as well. All the the voice traffic is decoded on the US100 device further reducing any server side decode required. The VPCC solution also comes with its own connection broker that is integrated with the NEC Sigma System Center server management software. One of the features I like most is the ability to do patch management of virtual desktop OS for simplifying patch management. If you are looking for a fully integrated end to end VDI solution you should check out the NEC VPCC offering. If you have never been to Japan, you will find that everyone is very polite. I also find it very service oriented . The food, as expected was also great. Lost of Sashimi!

Here is a nice view of Tokyo from the current VMware office.

VPCC

Here is another nice view of Tokyo

Dinner - Good Sashimi!

http://bp2.blogger.com/_mwnQG3BGo10/RmSG9CtQeaI/AAAAAAAAAA8/UIANP6mYJhw/s1600-h/P1030417.JPG

Stabilizing iSCSI based Virtual Desktops

wponder — Wed, 23 May 2007 15:45:00 GMT

Starting with ESX 3.0.1 iSCSI support was introduced. This opens up the opportunity to leveraging lower cost storage options when hosting virtual desktop instances. The topic of, what disk to store desktop images on, is one that gets tossed around like a hot potato. For some customers it seems like a non-issue. Their cost per gig is the same regardless if its enterprise fibre channel storage or low end storage. Some are not interested in introducing a second architecture into their data center as is the case when considering iSCSI.

For others, cost is an issue, and the possibility of leveraging iSCSI is very important to them. In my lab, I currently have an older NAS array
with around ½ terabyte of usable storage.

Several months back I decided it was time to start running some virtual desktops on it and see what performance is like.
I quickly realized, there was a little bug where ESX would not see iSCSI LUNs on my NAS appliance. So, for some time I ran an unsupported patch. Because it was unsupported, I left things as is and did not really watch the performance. This past week I was building some Solaris Express VMs for another test, when all hell broke
loose. Somehow, during the eternal boot of the Solaris VM my ESX system hosed. Because I was having such an issue, I decide it was time to do
some basic patch management. In all fairness, I was way behind on all my ESX patches. I had actually moved more VMs to iSCSI than I had
realized. All of which where very important.

The moral of the story is now, an official iSCSI patch is available for ESX 3.0.1. Patch number ESX-6657345 solves previous issues with iSCSI. After loading the patch on my systems I still was having an issue though. My ESX hosts could not log into the iSCSI target. What was really odd, is my NAS box did not see
the login attempts. It logs denied connection attempts and it saw nothing. The messages log on my ESX hosts were logging connection
refused. I tried removing and adding the iSCSI adapter through the VIC which also did not work. Finally, I got everything working and very
stable using the following steps.

Download patch ESX-6657345 and install it using esxupdate

From the VIC under configuration, storage adapters disable any iSCSI adapters
From the ESX console run esxcfg-swiscsi –d
From the ESX console run esxcfg-swiscsi –k
From the ESX console delete any iSCSI targets listed in /var/lib/iscsi/bindings
From the ESX console run esxcfg-swiscsi –e
From the ESX console run esxcfg-swiscsi –s
From the VIC under configuration, storage adapters enable any iSCSI adapters
From the VIC under configuration storage adapters rescan for the targets

After completing this, I was back in business and it has been much more stable. Soon I hope to share how some virtual desktops are working via
iSCSI, stay tuned.