Subscribe RSS Feed | Follow on Twitter

Archive for the ‘Pooling’ tag

View Pool Manager

without comments

Thanks to Eric Sloof for linking to the new free Fling available at the VMware Labs website. The tool called View Pool Manager is a development from Andre Leibovici who’s well known for his blog The tools allows you to manage a few tasks around the VMware View Pool management. The View Pool Manager can help you to save time, maybe a few hours a week. Try it!


Image Source:




Written by Christoph Harding

March 26th, 2013 at 1:00 pm

VMware View Pool Manager

without comments

Great news on Andre has published a new article on his blog talking about a new tool which can manage VMware View pools. This is just a sneak peek. His aim is to release the tools as a Fling, but this must be approved first be the VMware Fling committee.

This tool allow administrators to bind an Active Directory connection and specify:

* How many users there should exist per group (based on VMware View pool size) 
* Floating or Persistent deployment 
* Source Security Groups (all users to be distributed to pools) 
* Destination Security Groups (All groups the users may be assigned to)

Technicalities: Floating deployment does not take in consideration if user has a persistent desktop. Persistent deployment ensures users are kept within the same security group and desktop pool they have previously been assigned to.


Image source:


Written by Christoph Harding

January 29th, 2013 at 12:17 am

Posted in VMware View

Tagged with , , ,

Using VMware Mirage with VMware View floating pools

with 2 comments

Today I’d like to share an interesting read with you which was written by my colleague Andreas Wilke, who’s a Technical Account Manager at VMware. Please note that the configuration mentioned in the article is currently not officially supported by VMware.

One major benefit of desktop virtualization is the central image management for all desktop clients that can be deployed in many different pools as a View master image for floating or dedicated pools. Inside a floating pool deployment our current recommendation is to use a ThinApp repository for your applications which are streamed over a low latency connection from a network share to the View clients. With that solution you will avoid installing applications to the master image and can use the same master image inside many pools with different set of applications in each pool.

The challenge in that scenario begins with the installation of applications inside the master image itself for applications that can’t be used with ThinApp or are hard to be packaged with it. Usually you don’t want to have the local installed applications inside each pool for each user or it can’t be installed with other applications due to incompatibility reasons.

When you start to install applications inside different master images of your View environment you will start to lose control of the central image management. You will need to install patches inside each master image individually. Inside a growing View environment it will be hard to manage all the additional master images. You have to start using a central image and application management tool for your master images (ex. SCCM).

With VMware Mirage there is one simple way to get back the control of all your master images inside your View environment. The only thing you have to do is to install the Mirage Client inside your master images and add them as CVD (Centralized Virtual Desktop) to an existing or new Mirage environment. Inside your Mirage environment you can create a new Base Image that will be used as a Reference CVD for all your master images. This can easily be done inside the Mirage management console. With this solution you can easily update only one reference machine with patches/installed applications and synchronize the changes to your View master images. The updated View master images can be used to recompose your existing floating pools.

There are two things you need to consider when you want to use this:

  1. You have to disable the Mirage Client deamon each time before you create a new snapshot of the master image so it will not run inside the deployed floating pools.
  2. If you are not using VMware View Persona Management our recommendation is to disable the Microsoft Software Shadow Copy Provider. This service is necessary for Wanova Mirage, so please active it if you update your master image and disable it before you deploy or recompose the new floating pools

That’s it. A easy integration of VMware Mirage with VMware View and floating pools. If you are already using an application management system for your application you can use it as well to manage your installed applications inside your View Master images and reference machine in combination with VMware Mirage.

A picture tells more than 1000 words…. So here you can see the combination of all products:


What do you think about this configuration? Please feel free to leave your comment.

Would you like to hear more about this solution?

Written by Christoph Harding

September 11th, 2012 at 9:18 am

Assign a user to a persistent desktop before first use

without comments

Usually the persistent desktop design offers a chance to assign a virtual desktop to a user on first connect/use. The administrator entitles the user or a user group which inherits the users account to a persistent desktop pool but the virtual desktop assignment would be done on first use. However sometimes it may require a pre assignment which can be done the following way.

Read the rest of this entry »

Written by Christoph Harding

December 22nd, 2009 at 12:13 pm

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.