Released: VMware View 4.0.1
Feb 19th
VMware View 4.0.1 is a maintenance release that adds a small number of features / enhancements:
- Localisation of the View client in a number of languages including French and German.
- Support for vCenter 2.5 Update 6 and ESX 3.5 Update 5
- PCoIP now supports Virtual Printing, a couple of Single Sign-On Providers and International keyboards.
There are a few bug fixes included also. The best thing to do is to head over to the release notes and check them out. Then it’s time to download and update
.
vSphere Client Silent Install
Feb 11th
I was asked yesterday if I knew how to do a silent installation of the vSphere client. My client wanted to roll out the vSphere client to their Operations team automatically. They had experimented with getting it working and even asked a company about producing a custom MSI for them.
The solution is a little easier than that though. The key thing is using the right file. The VMware-viclient.exe file that can be downloaded from the vCenter server or an ESX / ESXi host is a self-extracting archive and doesn’t pay any attention to the normal parameters and switches that you can try to add to get a silent installation performed.
The right file to use is from the vCenter installation media (zip file or iso). In the “vpx” folder is a VMware-viclient.exe file that is 137Mb in size (the archive file mentioned above is about 114Mb). If you place the file on the root of your C:\ drive then a silent installation (an unattended one at least) can be performed using the following command line:
start /wait C:\VMware-viclient.exe /q /s /w /L1033 /v" /qr"
If you’d like a log file created, use this instead to write a logfile to the user’s temp directory:
start /wait C:\VMware-viclient.exe /q /s /w /L1033 /v" /qr /L*v \"%TEMP%\vmvcc.log\""
PowerShell 2.0 Installation Error
Feb 11th
I was trying to install PowerShell 2.0 and kept getting an error part way through that simply told me that access was denied while installing the Windows Management Framework Core. The installation was then rolled back. I tried a few times, with local and domain administrator accounts but to no avail. The following event was logged each time in the system event log:

After some poking around I found that the local Administrators group did not not have Full Control of the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Svchost to which it was trying to write.

Just thought I’d share this in case anyone else encountered it.
VI3 Extended Support
Feb 1st
Sorry to keep going on about VI3 but I alluded to the end of General Support in a previous post and thought it might be nice just to expand on it a bit.
VMware explain their support lifecycle policies here and basically the clock started ticking for VI3 support the day that vSphere went GA. VI3 moves into extended support on 21st May 2010. That’s only 4 months away.
So what does Extended Support mean? This is VMware’s definition:
New hardware platforms are no longer supported, new guest OS updates may or may not be applied, and bug fixes are limited to critical issues. Critical bugs are deviations from specified product functionality that cause data corruption, data loss, system crash, or significant customer application down time and there is no work-around that can be implemented.

