Today VMware released a new client for the iPad and Android devices. Version 1.2 is optimized for VMware View 5, has support for iOS 5 including AirPlay and contains presentation mode for use with external displays and AirPlay.
VMware View Client for Android makes it easy to access your Windows virtual desktop from your Android with the best possible user experience on the Local Area Network or across a Wide Area Network.
It requires at least VMware View 4.6 and only has PCoIP only connectivity for excellent interactive performance.
The VMware View client for Android can be found on the Android Market.
The VMware View client for the iPad can be found in the iTunes Store.
It’s a release party at VMware today. After VMware Workstation 8 and Fusion 4, VMware now released VMware View 5.
VMware View 5 will deliver better PCoIP performance, more supported client devices and integrated persona management.
The biggest differences are the media services, integrated persona management, several PCoIP enhancements and extended client support.
View Media Services for 3D Graphics
This enables basic 3D applications in View desktops without like Aero, Office 2010 or those requiring OpenGL or DirectX without the need for specialized graphics cards or client devices.
View Media Services for Integrated Unified Communications
Which enables and integrated VOIP and View desktop experience for the end-user with an architecture to provide optimized performance for both the desktop and unified communication.
A few minutes ago, VMware released the VMware View client for the iPad.
As of today the VMware View client for the iPad is available from the Apple AppStore for free.
The iPad View client fully supports PCoIP and contains a few unique new gestures. For a decent session using PCoIP you will need a WiFi connection because the bandwidth requirements are similar to those of a common thin- or FAT client.
The iPad View client is compatible with the new iPad 2 but does not support the use of the integrated cameras at the moment.
You can watch a demo of the VMware View client for the iPad below.
After installing the patches described in Microsoft Knowledge Base articles 2482017 or 2467023 Windows 7 clients are unable to connect from the View Client to the View Connection Server.
According to a VMware Knowledge Base article there is a conflict with two security bulletins issued for Windows 7, causing disruptions for VMware’s View Client and creating connection failures for users attempting to access the View Client Server.
Last week I visited a new project at which the client wants to virtualize their desktops.
During the kickoff the client mentioned that they use a variety of applications, clients and operating systems and want to deliver all these desktop flavors to their users.
Nothing new so far.
But this variety of clients and operating systems also includes Apples, MacBook (Pro)’s, etc using Mac OS X. Running a View client on a Macbook Pro with Mac OS X is no problem but provisioning Mac OS X as a virtual desktop is a whole different story.
One of my coworkers pointed me to a video from this years Tech-Ed Europe about VDI protocols. Bernhard Tritsch did an interesting comparison between the different remote protocols used in today’s VDI solutions. In a 60 minute session Bernhard explains the differences between location (host vs client), type (hardware vs software) rendering and compression types (lossless vs lossy).
Although the results aren’t that good for PCoIP (software version) it still is a very interesting video.
Last week we had a meeting with a McAfee Sales Engineer and he told us something I have been waiting for for a long time.
McAfee now has a product especially for virtualized environments, McAfee MOVE (Management for Optimized Virtual Environments). After Trend Micro, McAfee is now the second anti-virus company, that I know of, which has a product especially for virtual environments.
McAfee’s Management for Optimized Virtual Environments (MOVE) platform is combines speed ad security by significantly reducing the overhead of protecting individual machines in a VMware or Citrix virtual environment. Support for Microsoft Hyper-V is not available yet.
McAfee MOVE does this by offloading all anti-virus tasks to an appliance/server which needs to be installed on each ESX host or XenServer in a cluster. The only McAfee components which needs to be installed on the virtual server or desktop is the McAfee MOVE client and the ePO agent.
With the release of VMware View 4.5 comes the challenge to upgrade your existing installation to this new version.
The upgrade is not that difficult but because I promised you all a ‘How to upgrade to VMware View 4.5‘ I will provide this service anyway.
Before you start first a few pointers:
1. make a back-up of the VMware View systems that you’re going to upgrade;
2. If some of your end users are using the Client with Offline Desktop, ask them to check in their View desktops;
3. when you have multiple connection servers and you are upgrading from 4.0 to 4.5, you need to disable the VMware View Connection Server service on all Connection servers. (Thanks Sven)
4. If you are using vSphere, you must have vSphere 4.0 Update 2 or vSphere 4.1. If you are using VMware Infrastructure, you must have VMware Infrastructure 3.5 Update 5 and VirtualCenter Server 2.5 Update 6.
Last Thursday we attended the VMware vSphere 4.1, vCenter 4.1 and View 4.5 launch event at Amerongen (NL).
We already brought you all news regarding vSphere and vCenter 4.1 and View 4.5 but we heard some interesting thing we would like to share with you.
VMware View 4.5
With VMware View 4.5 VMware has changed the names for some product related features. Let us welcome Local mode, persistent disk, dedicated and floating pools.
I’ve attended the View 4.5 beta program and I can honestly say that View 4.5 is a huge improvement. In the past, we had to deploy XenDesktop for VDI deployments with specific customer demands but with the release of View 4.5 these scenarios have decreased significantly.
General availability for VMware View 4.5 is set for early September.
Here are some of the improvements/features in View 4.5:
We’ ve been doing quite a few VMware View POC’s and the question that colleagues keep asking me is:
‘How do I optimize my Windows guest OS for use with VMware View?’.
First of all, I primarily use x86 versions of Windows XP and 7. The disk usage is much less, I seldom need more than 4 GB of RAM and application compatibility is still an issue on x64 systems.
After installation of the guest operating system in the template virtual machine I do the following to optimize the operating system for use with VMware View.
There was an issue discovered earlier today that prevents View Composer from working with vSphere 4.1.
Because of that VMware View Composer 2.0.x is not supported in a vSphere vCenter Server 4.1 managed environment as vSphere vCenter Server 4.1 requires a 64 bit operating system and VMware View Composer does not support 64 bit operating systems.
VMware View 4.0.x customers who use View Composer should not upgrade to vSphere vCenter Server 4.1 at this time. The upcoming VMware View 4.5 will be supported on VMware vSphere 4.1.
VMware has given out a VMware Alert for customers who are using VMware View in combination with PCoIP and ESX 4.0 to NOT update with ESX Update 2 yet.
After upgrading ESX 4.0 hosts with Update 2 VMware View clients are unable to connect to the virtual desktops. VMware is currently investigating a workaround for customers that have installed ESX 4.0 Update 2 and are affected see for more information and update the following KB Article: KB Link
This Knowledge Base article will be updated as new information becomes available. If you have been affected by this, please read the KB.
Symptoms are:
Connections to virtual desktops using PCoIP fail
You are no longer able to connect to virtual desktops using PCoIP
You have recently updated VMware Tools
For example, you have installed ESX 4.0 Update 2, which updates VMware Tools, and you are no longer able to connect to virtual desktops using PCoIP.
It is always nice to see how Citrix fan-boys reacts on publications about VMware View. Especially when it comes to an comparison or XenApp for View trade in. It is often said that Citrix listens to their customers but they are seldom heard! People need simple solutions in a complex IT world. Why pay for a very high end piece of engineering like a Ferrari if I can get the job done with a Volkswagen! OK, it is nice to have a car that nobody else has and can do 320 km/h but in times were budgets are under pressure, I have a hard time defending expensive, complex and high-end solutions.
The fact that VDI is putting a significant load on the storage is true, but that counts for every VDI solutions including XenDesktop, so no differences there. Also the new upcoming version of View includes a basic profile management solution “Persona Management”. Which makes the use of linked clones a very workable solution.
When you compare installing View and XenDesktop you will see the following diagram.
When it comes down to management consoles the two solutions also look very different.
As a reaction on the Citrix program to trade in your VMware View licenses for XenDesktop, VMware comes with a program to trade in your XenApp licenses for VMware View.
The trade in program is quite simple: For the price of 3 years XenApp SA (€ 182,-) you will get View Premier and 3 years SnS.
VMware’s offer differs from the one from Citrix in a few way’s.
Yesterday VMware has released the new version of their application virtualization product, ThinApp 4.5
ThinApp 4.5 includes the following new features to improve usability, performance, and updates:
Support for Windows Server 2008 R2, 32-bit Windows 7, and 64-bit Windows 7 operating systems.
ThinApp version updates to incorporate the latest features or support enhancements without rebuilding packages. The relink.exe utility updates existing packages.
Compression of MSI packages that uses the MSICompressionType parameter to improve the ThinApp SDK performance.
Reduced memory consumption and page file usage to improve startup performance. The OptimizeFor parameter works with the CompressionType parameter to customize memory performance and startup time.
Anonymous collection of statistics to expand the support for applications. You can use the Setup Capture wizard or the QualityReportingEnabled parameter to help VMware build support for applications and help you migrate more native applications to a virtual environment.
Loading of DLL files as virtual DLL files without using API functions. The ForcedVirtualLoadPaths parameter loads external system DLL files that depend on DLL files inside the package.
Product interface updates to improve usability and link to video and documentation information. German and Japanese versions of the ThinApp User’s Guide are available.
Support for vCenter 2.5 Update 6 and ESX 3.5 Update 5;
Enhancements to the PCoIP Display Protocol.
PCoIP now supports the following features:
Virtual Printing, which allows end users to use local or network printers from a View desktop without requiring that additional print drivers be installed in the View desktop.
Single sign-on support for third party providers such as Sentillion and Imprivata.
View Client supports international keyboards when using PCoIP.
November 4th we published an article on Virtual Infrastructure best practices and the response was overwhelming. During the last month we received a lot of questions regarding best practices on VDI/VMware View. When I then read a comment from VMware’s evangelist, Richard Garsthagen, that the attention on blogs for VMware View was minimal I thought well let’s extend our View articles/knowledge base.
So, VMware View best practices. First of all check the article on Virtual Infrastructure best practices to create a good understanding for the underlying virtual infrastructure challenges.
So hereby my list of best practices which I gather from VMware KB articles, instructor led VMware View design training and the VMware community:
CPU sizing;
Memory sizing;
Storage sizing;
Network sizing.
If you have additions or new insights please reply.