Evaluating VMware view

[hurdle]

We are in the process of looking at different desktop solutions including view.

After reading the documentation there are a couple things I am not clear on.

1. In order to use offline desktop you can't have a linked clone, but from what I understand you need to have a linked clone to update the image on the fly (recompose) So is there something built into view to update non-linked clones, or do you have to use the traditional MS methods. (aka WSUS, Group policies, ect...

2. What is the recommend way to backup the enviroment? With COW files I am assuming there is the same issue as with lab manager, where the only real solution is to backup the entire LUN? Is there a better solution out there?

3. How is MS licensing effected by linked clones? If you have one base image and 5 links off of it. Is that 6 MS licenses or 1?

Thanks in advance.

[Linjo · Accepted solution]

Hi!

I'll take a stab at your questions:

1. Correct, offline desktop needs a full clone. Linked Clones are not supported. There are no way to recompose a full clone so you need another way to update these machines.

Two causions about offline desktop, it has "experimental support", that means that its not a fully supported feature. It currently only works with ESX 3.5 / VC 2.5 U3/U4

2. What are you interested in protecting? With full clones you can use your regular ESX backup solution, with linked clones the interesting data is the user data and that should be either on the user data disk, home folder or a roaming profile. Backup that the same way as you do today.

3. I would guess that 5 licenses is needed, but I am not a licensing expert...

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[AnatolyVilchins]

I'm new to View as of 4.0, but I've been

evaluating it for the last few weeks and finally have a

production-ready system. Here's what I know:

1. To update View desktops on-the-fly (when they get shut down and
   re-privisioned by View Manager), you'll need to use linked clones
   pointing to a specific snapshot of a base image. For updating
   non-linked clones, you'll have to rely on your own tools, or manually
   clone the base image to a new VM, then update the desktop source in
   View Manager accordingly.

2. View doesn't include anything to help back up your environment.
   In my particular case, almost every virtual desktop is a disposable
   linked clone, so I really only need to worry about backing up the base
   image, which is pretty trivial. If you have data inside the virtual
   desktops that needs backing up, your best bet might be to run backup
   software inside the VM.

3. To the best of my knowledge, you'll need a volume license for
   Windows, since (in your example) 5 people may be using a clone of the
   same base image. That's 5 people using Windows, despite the origins of
   the bits, so Microsoft will want to be paid for each in-use license.
   View integrates very well with Active Directory, so you may be able to
   do some scripting magic upon joining the domain or user login.

When it comes down to it, most of what View does is automate the

cloning process and assist in basic machine setup (joining a domain,

doing a DHCP renew, etc). It is rather wild, though, to see a system

provisioning, configuring, and powering on VMs all by itself.

Lastly, setting up a View Security Server is very helpful if you're dealing with clients using the VMs over the internet through firewalls.

</div>

Starwind Software Developer

www.starwindsoftware.com