After listening to Mike Laverick Chinwag podcast http://www.rtfm-ed.co.uk/2010/05/03/chinwag-with-mike-mike-laverick-episode-13/ it inspired me to give it a go.
So there I was reading an e-mail from our Service Delivery Manager asking if anyone had any idea’s for making a ‘Working from home’ project more of a viable option. With my VMware hat on I immediately thought that VMware View could be a good choice for both working from home and also getting the best out of ageing desktop hardware.
At the moment we already have an environment of 8 ESX host managed by vSphere and it seemed a good idea to leverage what we already have and test View on this kit. Fortunately I also had a dev server with plenty of local disk storage available. I steamed ahead and build a test vm and then installed View. Within less than an hour I had a View server all setup and ready to go. After creating a fresh desktop vm guest with our standard Windows XP build and then adding the VMware tools and View client I was ready for action!
A colleague of mine has spent about 9 months building a new corporate desktop image with all the application required installed. This has been a very lengthy project with many many builds and a lot of testing but he has finally produced this ‘gold’ image. Now exhausted he has been asked to do the same but with Windows Server 2003 as a Citrix presentation server. (oh no! Not another nine months and users already used to the new system and demanding that they can be able to use the same new image remotely). Well…. after this story I thought that we already have a perfect desktop image to use and with a little bit of help from VMware View we can utilise this image now saving many man hours.
Yes… It’s defiantly worth a go of the 60 day trial. It’s a simple and easy to use system (so far!) And after the evaluation my even fit your business needs! I’ll keep you posted on how I get on!
First of all connect to your vSphere server:
Get-vm Guestname | Get-View | % $_.config.cpuFeatureMask}
Here’s how to get it working!
1. Obtain a copy of %SystemRoot%Microsoft.NETFrameworkv2.0.50727System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%VMwareInfrastructureVirtual Infrastructure ClientLauncherLib+).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element as shown below. Save the file.
<?xml version=”1.0″ encoding=”utf-8″?>
3. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%VMwareInfrastructureVirtual Infrastructure ClientLauncherLib
“%ProgramFiles%VMwareInfrastructureVirtual Infrastructure ClientLauncherVpxClient.exe”
4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
All credit to http://communities.vmware.com/thread/211440
First use VMKFSTOOLS to expand the VMDK file. Putty onto the ESX box and type
1. vmkfstool – X 10g servername.vmdk
This will expand the file to 10gig. note. the X has to be uppercase and the vmdk should not be the one that ends with ‘-flat’.
Mount something like BartPE to the virtual machine and boot from it. Once loaded open and command prompt and type the following:
3. list volume (note the number of the volume you want to expand)
4. select volume x (x = the volume number)