Jan 312009

Some good info in the 108 articles new or updated since Sunday.  Here’s this weeks selection:

Jan 302009

View Manager 3.0.1 includes a few improvements with the universal print driver.  More importantly, it adds the capability to pass the client machine name to the VM which has been a much requested feature.

From the release notes :

View Manager 3.0.1 includes the following enhancements:

  • Integrates the ThinPrint Virtual Channel Gateway module so that View deployments can communicate with ThinPrint server.
    Important : ThinPrint’s .print engine for VMware View must be installed on the target print server prior to installing View 3.0.1.
    Print jobs originating from virtual machines are subject to different licensing criteria on ThinPrint server. In order to provide the print server with information about the origin of a print request, View uses the TPVCGateway module as the print provider.
  • Provides the capability for the Windows View Client to pass the machine name of the client device to the guest virtual machine.
    On the guest virtual machine, ViewClient_Machine_Name environment variable is set to represent the client machine name at initial login. It is also updated when the client reconnects to the guest virtual machine. In order to assist with third-party integration, a mechanism is provided to allow scripts to be executed on login and reconnect. The details of the scripts are held in a Windows registry key that can be set manually or by using a Group Policy Object (GPO). View Manager 3.0.1 provides an update to the vdm_agent.adm template to include this definition. The registry keys are
    HKLMSoftwarePoliciesVMware, Inc.VMware VDMAgentConfigurationCommandsToRunOnConnect and  
    HKLMSoftwarePoliciesVMware, Inc.VMware VDMAgentConfigurationCommandsToRunOnReconnect

    The commands to be run are defined as name=value pairs where the value is the command that is executed.  For example, to specify multiple commands, you can enter:
    Command1 = CMD /C c:script1.vbs
    Command2 = CMD /C c:script2.vbs

    Note : Other applications might have set the CLIENTNAME variable in some circumstances. In order to avoid collisions, this variable is not modified or updated.

  • Contains bug fixes described in Resolved Issues .

You can download the updated release here .

Jan 282009

The VI toolkit 1.5 was released.  Rather than retype the benefits, I’ll use the internal announcement from the development team:

"The VI Toolkit is a great automation tool and if you manage more than about 20 VMs or deploy VMs or ESX hosts on a regular basis you should check it out, it can really save you a lot of time and effort when you’re making updates across large numbers of objects. Some popular uses include things like cloning VMs 50 or 100 times and creating virtual switches across multiple ESX servers. The most exciting new feature is the ability to execute scripts inside the VM guest, made possible by our integration with the VIX library."

You can find the full announcement here .

If your are new to the toolkit you can find some launch videos to see what it can do here .

To keep tabs on the VI Toolkit dev team you can also follow their blog , good reading for just about any VI Admin.

Of course, you can find the toolkit for download here .

Jan 262009

Whew!  I usually check the White papers for new submissions weekly but clearly I’m asleep at the wheel!  6 new ones were added.

There’s two new hi-level papers on why NetApp storage and VMware view run well together.  They bring up some good points on the advantages.  They can be found here and here .

There are some great ones on Application Virtualization.

  • The first is a performance comparison of Application Virtualization technologies which can be found here .  I don’t know if it was a sponsored study or not but the results are compelling none the less.
  • Next a great reviewer’s guide for ThinApp was posted.  This is a must have if you are going to download the ThinApp eval and try it out.  It gives you the basics of how ThinApp works and how to get started.

There’s also a new one on Best Practices running Java in a VM on ESX .  Here’s one that I definately get asked on periodically.  Very technical and good reading for those running Java in a VM.

Lastly, one question I get asked often is how many desktops a customer can stack on a ESX server.  That’s not a very easy question to answer as everyone’s workloads are different.  Here’s a great paper on some standard workloads and how they stack up and affect performance.  Definately a good read for those looking to deploy virtualized desktops.