Via a Perl Script, a very helpful post can be found here:
http://www.linuxdynasty.org/how-to-check-the-status-of-vmware-tools-per-virtual-machine-the-easy-way.html
If you’d rather use PowerShell, check out this helpful blog post which also references a follow-up VMware community post:
http://philthevirtualizer.com/2010/06/22/powercli-get-vmware-tools-versions/
http://communities.vmware.com/message/1722648
Potential issue if you are using VMware Changed Block Tracking and NFS storage.
http://danbrinkmann.wordpress.com/2011/04/21/vmware-change-block-tracking-cbt-and-nfs-uh-oh/
Here is a very useful KB article on migrating an existing vCenter Server database to 4.1 using the Data Migration Tool:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021635
Also, here’s a great blog post on VMware’s blog showing how to upgrade vCenter 4.0 32 bit to vCenter 4.1 64 bit by using the VMware Data Migration Tool.
http://blogs.vmware.com/kbtv/2010/07/how-to-upgrade-to-vmware-vcenter-server-41-using-the-data-migration-tool.html
Copied below for reference.
Our first video covering vSphere 4.1 is now live. The video compliments KB article 1022137 vSphere 4.1 upgrade pre-installation requirements and considerations. and describes the process for using our Data Migration tool to upgrade VMware vCenter Server 4.1
VMware vCenter 4.1 is part of the VMware vSphere 4.1 product suite and the Data Migration tool allows you to migrate your vCenter Server 4.0 configuration, since VMware has now entirely gone to a 64-bit platform. 64-bit brings significant performance benefits, but it also introduces some challenges that need to be considered before upgrading.
Sit back, grab that cup of java and take in a little KBTV.
The Data Migration tool is provided with your vCenter Server 4.1 installation media.
Just spend my first few hours on the Motorola Xoom that we have acquired for our Desktop Virtualization showroom!
http://danbrinkmann.wordpress.com/2011/04/11/my-first-few-hours-with-the-motorola-xoom/
The list of hardware and software continues to climb. Any vendors want to get on the list?
Soon to be added… Fusion-io card…wurd!
Thank you to those who came to our Lewan Tech Review, I hope you found it informative and hopefully I didn’t talk to fast…tough after needing lots of coffee to wake up in the AM! Please vote for our next Tech Review and be sure to signup for the AppSense training we are doing on April 13th and May 4th!
Here is the presentation from today…click the link below:
Lewan Tech Review April 7, 2011
Ray over at Yellow-Bricks.com has posted about how to get an OVF virtual machine (usually VMware Appliances) converted so you can open them in VMware Fusion on the Mac. Here’s his link:
Copied here for reference:
I needed to run an appliance inside VMware Fusion on my Mac, the appliance was in OVF format. VMware Fusion currently does not support this format and requires you to convert the image with a tool called ovftool which can be downloaded at the following location:http://communities.vmware.com/community/vmtn/vsphere/automationtools/ovf
Conversion is as simple as:
./ovftool "source.ovf" "target"
Optionally you could use parameters that are described in full detail when running ovftool –help. What remains is importing the created .vmx into Fusion, that’s it.
Chethan Kumar has recently updated the Performance Troubleshooting for vSphere 4.1 guide. This is a great asset I use regularly for any client or partner that asks about vSphere performance – especially those working with Tier 1 applications. It is very educational and addresses the most common scenarios clients experience.
Abstract:
“The hugely popular Performance Troubleshooting for VMware vSphere 4 guide is now updated for vSphere 4.1 . This document provides step-by-step approach for troubleshooting most common performance problems in vSphere-based virtual environments. The steps discussed in the document use performance data and charts readily available in the vSphere Client and esxtop to aid the troubleshooting flows. Each performance troubleshooting flow has two parts:
1. How to identify the problem using specific performance counters.
2. Possible causes of the problem and solutions to solve it.”
It is located here: http://communities.vmware.com/docs/DOC-14905
NPIV or N-Port Virtualization is a method of utilizing a single Fibre Channel port to serve multiple physical or virtual servers. NPIV allows a single SAN device to service multiple WWNs without additional switching infrastructure. NPIV is the technique used by blade system hardware to reduce the complexity of SAN connected blades. NPIV allows SAN connectivity without requiring Fibre Channel switches to be installed within the blade chassis. VMware also uses NPIV within the Raw Device Mapping (RDM) infrastructure.
Due to a statement in VMware documentation, confusion has arisen over support of Microsoft Cluster Server (MSCS) in a VMware environment where NPIV is utilized. In short NPIV is supported with VMware and MSCS where a hardware device such as HP Virtual Connect or Cisco UCS provides the NPIV functionality but not where VMware is providing the NPIV (checking the box in the guest config of a VM for NPIV).
Our demo area at Lewan is almost complete. We have capabilities to demo quite a lot!
VMware View
Citrix XenApp
Citrix XenDesktop
Citrix XenClient
AppSense
HP thin clients
Wyse thin client
Pc’s
iPad
MacBook Pro
If you want to see the next big thing in technology come find me.