View Client Build 353760 - fixes issues with 2 Windows 7 patches

If you've recently done patches and can no longer connect to the View environment you may require an updated client. See the following VMware KB article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1034262

Affecting both 32-bit and 64-bit versions of Windows 7 OS, the error causes the connection between a user's computer and a VMware-hosted virtual console to fail.

Although VMware didn't explain how patches 2482017 (security update for all versions of Internet Explorer) and 2467023 (fixes an issue with how Windows 7 and Windows Server 2008 R2 loads and unloads system binaries) interrupts the PC and virtual console connection, it provided two options for fixing the situation:

• Install a VMware View Client patch.
• Uninstall the two Microsoft patches.

VMware also recommended that if the newest Microsoft security update batch hasn't been installed, download and install the View Client patch before updating Windows 7 machines.

Chris Wolf from Gartner also has a great Blog entry related to this issue and the implications on the Bring Your Own Device (BYOD) model: http://blogs.gartner.com/chris-wolf/2011/02/10/windows-7-update-breaks-vmware-view-client-an-important-lesson-in-byod/

Confused about VDI licensing?

With so many clients looking to explore what virtual desktop has to offer, we have looked in depth at what is involved to be in compliance with Microsoft operating system and application licensing.

For VDI, Microsoft’s licensing model is VDI Standard and Premium Suites. These are great offerings and simplify the process to acquire Microsoft VDI. And in my view and for many customers, this is a cost-effective solution and I encourage IT decision makers to examine and compare Microsoft offerings with others out there in the market. The VDI Suite includes not only the basic infrastructure needs, but critical management components to ensure a successful VDI deployment. So customers can, for instance, employ System Center Virtual Machine Manager and take advantages of the many integrations among System Center family, Windows Server 2008 R2, and Windows 7. For a more comprehensive offering, the VDI Premium Suite includes additional desktop and application deployment options.

Still many may have a fundamental question, why a new licensing model is necessary for VDI? To better understand it, the following chart details a number of VDA or Virtual Desktop Access scenarios and we should also further look into how software was deployed yesterday and how software can be deployed today and beyond. 

Traditional software deployment is per device. Which assumes an OS will be associated with a particular hardware device like a PC or laptop, once installed. And as well, an application will be associated with a particular OS instance, once installed. However, with VDI, we now can deploy dynamically and roam personal desktop, applications, or both based on an IE session of an authenticated user, and not necessarily need to install and tie an instance of OS or an application to a particular physical device or a particular instance of OS, respectively. Therefore, traditional licensing model does not correctly reflect the usage of licensed software in a VDI deployment. Further, a key factor for the success of any virtualization initiatives is the management as explained. There are also licensing implications on including a VDI deployment into a software deployment and management infrastructure and can and probably will further complicate the overall licensing solution. A licensing model specifically addressing VDI deployment scenarios is essential. Both the VDI Standard Suite and the VDI Premium Suite are licensed per client device that accesses the VDI environment, and thereby allow for flexibility of server infrastructure design and growth.