Tag Archive for vmware

vSphere 5 Standard vSwitch Multi NIC vMotion Setup

vSphere 5 offers the new feature of Multi NIC vMotion allowing you to push vMotion traffic simultaneously down more than a single NIC. In previous releases of vSphere, only a single NIC would ever be used even if multiple NICs were part of a network teaming policy.

To configure Multi NIC vMotion, simply follow the below steps:

Step 1. Under the Configuration tab of a host, click Networking then select Add Networking. Select the option VMKernel and click next, select the network adapters you want to use for vMotion and click next.

Step 2. When presented with the below screen, enter a network label for this first VMKernel port, for example “vMotion-1″ and check the box “use this port group for vMotion” and click next.

Step 3. On the next screen enter the IP address and subnet mask for this first VMKernal port and click next, then click finish. This will now create the vSwitch with the first port group and assign the two chosen virtual adapters to the switch.

Step 4. When the vSwitch has finished building, click the Properties button for the switch and you will be presented with the below screen. Click the Add button and go through creating a second VMKernel port for vMotion as you did in the previous steps.

Step 5. Once you have created your second VMKernel port, go back to the vSwitch properties windows, select the first vMotion VMKernel port and click edit.

Step 6. Click the NIC Teaming tab, then under Failover Order, check the box “Override switch failover order”. The NIC teaming options will now become available as shown below.

Step 7. In the NIC teaming policy editor, ensure only one NIC is moved under Active Adapters and any others placed under Standby Adapters. Once completed, click OK and the changes will apply. This will force this VMKernel port to only use a singular NIC in the networking team.

Step 8. Follow steps 5 to 7 for the second VMKernel port and remember to invert the NIC teaming policy from what you set for the first VMKernel port. For example, if vMotion-1 has vmnic1 as active and vmnic2 as standby, vMotion-2 should have vmnic2 as active and vmnic1 as standby.

The configuration of Multi NIC vMotion is now complete and you should experience much fast vMotion operations. To confirm your setup is working correctly, examine the performance statistics for the virtual adapters you chose during the setup, and issue a vMotion operation. You should see simultaneous active across all NICs.

VMware View 5.1 Storage Accelerator

With the release of VMware View 5.1 a number of new features have been introduced, particularly around storage performance. For me, the key feature is the View Storage Accelerator, or you may hear it referred to as Host Caching.

Without going into intricate detail, the storage accelerator basically creates an additional file within the datastores for the replica disk and all linked clone OS disk. This file is know as a digest file and is used as a caching mechanism. The way this digest file increases performance is by minimising the amount of read requests back to the replica disk. This is done by caching commonly read blocks from the replica disk into the OS disk digest file which can be read directly acting as a cache. This can help minimise boot and log on storms within your View environment.

Enabling the Storage Accelerator is relatively simple and can be achieved by following the below steps.

Step 1. Log in to you VMware View administrator console, under View Configuration click servers. Locate your vCenter server and click Edit.

Step 2. Click on the Host Caching tab then check the Enable host caching for view check box. This will enable the caching capability and allow you to specify the size of the cache for all, or individual hosts. The minimum cache size is 100MB with a maximum of 2GB. Click OK to apply the change.

Step 3. Locate a linked clone pool you want to enable the storage accelerator on and Edit the settings. Click on the far right tab named Advanced Storage and check the Use host caching check box. Click OK to apply the settings.

The storage accelerator features is now enabled for this linked clone pool, and will require a recompose to generate the necessary digest files. Hopefully you will now see a performance increase on read intensive operations.

Thanks for reading.

VMware View Enable Display Settings

When connected to a VMware View session you may have noticed that you do not have access to change any display settings. This can be a problem for users that have a large monitors  as View auto sets the desktop resolution for best clarity. In my experience, I have had users complain about how small icons and text are shown within their View session which at the time I didn’t have a solution for.

Thankfully, VMware have bundled a group of ADM templates containing many options for tweaking View components such as the View agent and PCOIP parameters.  You can fine these ADM templates on any one of your connection servers in the following location.

C:\Program Files\VMware\VMware View\Server\extras\GroupPolicyFiles

Once you have created a new GPO and loaded these ADM templates into your group policy manager, navigate to the following policy.

Computer Configuration > Administrative Templates > Classic Administrative Templates > VMware View Agent Configuration > Agent Configuration > Toggle Display Settings Control

To enable the use of the Windows display settings, you need to disable the Toggle Display Settings Control.

Equally you can add the below registry key to a logon script to achieve the same result.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] “NoDispCPL”=-

Thanks for reading.

VMware View Scheduled Recompose

In this post we’ll go over writing a View PowerCLI script to schedule a recompose of a desktop pool.

If your like most VMware View administrators you’ll probably use linked clones, and know that now and again these clones will need recomposing to keep up to date with operating system patches or updates for embedded applications. If your organisation is like mine and operates on a 24 hours basis, getting downtime to perform a recompose can end up being headache and is usually scheduled for a unsavory hour.

Unfortunately scheduled tasks was not part of the View v5 release which i imagine left many people in my situation slightly disappointed. To get around this need for functionality, i turned to the View PowerCLI extensions and wrote a script to perform my desired tasks.

Below you will fine my script, along with one of my working examples that allows you to specify a linked clone pool to be recomposed from a specific virtual machine and snapshot at a defined time and date.

 

Script: Get-Pool -pool_id your-pool-id | Get-DesktopVM | Send-LinkedCloneRecompose -schedule ‘yyyy-MM-dd-23 hh:mm’ -parentVMPath “your-parent-vm-path” -parentSnapshotPath “your-snapshot-path

 

Example: Get-Pool -pool_id LC-EXT-H2F | Get-DesktopVM | Send-LinkedCloneRecompose -schedule ’2012-01-23 11:42′ -parentVMPath “/Hangar 1/vm/VMware View/Linked Clones/viewpocmlc” -parentSnapshotPath “/Base Windows 7 Image/Base Windows 7 Tweaked/Windows 7 with Basic Apps”

 

Below is an example desktop pool’s options which details the paths for -parentVMPath shown under Parent VM, and -parentSnapshotPath shown under Image.

Thanks for reading and be sure checkout how to schedule the refresh of a desktop pool Here

VMware View Scheduled Refresh

In this post I will detail how to make use of the VMware View PowerCLI extensions. One feature I has hoping to see in the release of VMware View 5 was the ability to schedule tasks such as refreshing desktops or recomposing entire pools. Unfortunately this feature wasn’t added to View so i seeked my own solution. With View PowerCLI you can perform most if not all main functionality and better still, schedule when you went these commands to run. In this post the relevant commands for scheduling the refresh of a pool at a defined time are outlined.

Script: Get-Pool -pool_id your-pool-id | Get-DesktopVM | Send-LinkedCloneRefresh -schedule ‘yyyy-MM-dd hh:mm’

Example: Get-Pool -pool_id LC-EXT-H2F | Get-DesktopVM | Send-LinkedCloneRefresh -schedule ’2012-01-23 09:12′

Installing VMware Tools in Linux Command Line (CLI)

This post details how to install VMware tools through a Linux command line by auto mounting the tools ISO through the vSphere client.

Step 1. Click right on your Linux virtual machine, highlight guest and click ‘Install/Upgrade VMware Tools’.

 

 

Step 2. Run through the below commands to extract and run the installation.

 

mount /dev/cdrom /mnt/

tar -C /tmp -zxvf /mnt/VMwareTools-5.5.3-34685.tar.gz      //Press tab for file name

umount /mnt

cd /tmp/vmware-tools-distrib

./vmware-install.pl

 

Step 3. Press enter to all the default options.

Once rebooted, VMware tools will be installed.

PowerCLI What Do I Need?

VMware PowerCLI can be a very powerful tool in managing your vSphere environment. To get started there are two installs you will need to download and execute on to either a server or workstation that has visibility of your vSphere environment. Once installed you’ll be able to experiment with scripting commands and scheduling tasks. Remember to look out for a later post on using PowerCLI scripts with VMware Site Recovery Manager.

 

Microsoft Powershell 2.0

 Direct | Mirror

 VMware PowerCLI 5.0

Direct | Mirror

 

Run 32 Bit Apps on 64 Bit Platforms

With application virtualisation legacy applications can be made available on newer operating system platforms, in particular 64 bit architectures. VMware ThinApp is designed to allow 32 bit application run on 64 bit operating system natively out of the box, however with some applications this doesn’t always work as expected.

Within the ThinApp packager there is an option you can enable that allows the emulation of a 32 bit platform for your virtualised application allowing its use on a 64 bit operating system. The following steps detail how to enable this feature.

Step 1. Before building your application, edit your package.ini file by uncommenting the wow64=0 entry as shown below.

Step 2. Save your package.ini file and built your application.

Set ThinApp Application Name

In this post I will be showing you a simple way to define the name of you ThinApp application as sometimes it doesn’t always show up as expected.

Step 1. Before building your application, edit your package.ini file with the following entry under the header of your chosen entry point.

StatusBarDisplayName=App name

Step 2. Save your package.ini file and built your application, the application launch name should appear something like this.

VMware ThinApp with .NET Framework

With a lot of Microsoft applications .NET Framework is commonly required during installation. When trying to ThinApp these applications .NET Framework can be required as part of the virtualised app. This post will detail a step you may fine yourself needing to take if you experience .NET related problems with your ThinApp applications.

Basically, when you install .NET Framework not all components are executed and compiled during the time of installation. Some of these components can remain uncompiled until the application calls for them. If this is the case with an application you are trying to virtualise you may run in to issues launching the ThinApped application.

To get around this, during the installation period (After prescan, Before postscan) run the following command in a command prompt window.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

This will compile any remaining components within your .NET installation ready to be captured as part of your new ThinApp.

If all components have been compiled, the below message should be returned.