Skip to main content

10 Essential VMware Management Tools

 Any VMware administrator worth his or her salt has a grab bag of useful tools and scripts to make administration easier, so much so that this list of tools usually follows them between jobs. Below is a list of what I'd consider to be 10 essential VMware management tools I personally use on a day-to-day basis as a VMware administrator.

1. RVTools

RVTools is a tiny free tool that allows an administrator to easily interrogate and report on a VMware infrastructure. It will collect just about all the information you require, displaying it in a series of useful tabs. What is exceptionally useful is that RVTools allows the export of the data in both CSV and Excel formats for manipulation of data if needed.
It is an ideal way to get a list of virtual machines in a cluster or vCenter in one easy step. It lets someone do exactly the same with hosts and pretty much every reportable item you could possibly need. It gives loads of information, perhaps too much, about a host, cluster or VM in an easily exportable list. One really useful function is that RVTools has a special tab for problem machines that will show any machines that don't meet VMware best practice or have serious issues, such as inconsistent machine names, large snapshots, zombie virtual machines and many other potential issues. [Download RVTools]

RVTools is free tool that is used to interrogate and report on a VMware Infrastructure.
(Image: Stuart Burns)
2. PowerShell

Every administrator, like it or not, is going to have to get used to Windows PowerShell. PowerShell is a key component in running anything but the smallest VMware farm. It provides a key part of VMware automation infrastructure. It allows admins to quickly create small scripts to perform frequently performed tasks all the way up to huge automation scripts to migrate entire clusters to new homes.
If you are running Windows 2008, then you will already have PowerShell installed. As proficiency increases, you can build small and useful scripts. A typical example of a PowerShell script I use frequently is to check that all datastores in the cluster are available to all the hosts. Having tens of LUNs per cluster, it saves time and reduces the margin for error. It is small time saving scripts like this that separate good admins from great admins. [Download PowerShell]
3. vCheck Daily Report

The vCheck daily report script is created by Alan Renouf and several members of the VMware community with one key goal in mind. That goal is to provide a daily health check for VMware infrastructure. It is free to download and use. It will require a small amount of customisation for specific environments, such as the email delivery settings and access settings but it is well worth it. The key takeaway from this is that it can be used to get an easy to understand report that highlights and points out issues with the infrastructure.

What is even better is that where there is a deviation from best practice it will report that. Reporting includes virtual machine faults, hardware faults, DRS, HA and many others. This script is worth its weight in gold. It is all about reporting issues and errors where as RVTools is all about reporting numbers. [Download vCheck Daily Report]
4. WinSCP

WinSCP is a useful Windows implementation of the classic SCP (Secure Copy Protocol) tool.
(Image: Stuart Burns)
WinSCP is a very useful Windows implementation of the classic SCP (Secure Copy Protocol) tool that most Linux machines have installed. It is one of those tools that is handy when an admin just needs to upload directly to a datastore, or the actual host filesystem itself. Sure, it is possible to use the upload feature built in the vSphere client, but sometimes, for example if you need to upload a fix to the actual hypervisor level storage that is not available from the client. [Download WinSCP]
5. PuTTY/DCUI Command

PuTTY, the secure shell client is a key component to any administrator's armory that gets used frequently. PuTTY can be used to troubleshoot the server without having to use ILO/DRAC and the slow and awkward interface that comes with them.

PuTTY -- and the DCUI command -- can be a valuable tool in any VMware admin's toolbox.
(Image: Stuart Burns)
It is even possible to get the full-on console experience using PuTTY when there is a need to configure some options on the console. Once logged in as root using PuTTY, use the command "dcui" to get the same text based menu as would be seen on the console. The PuTTY console also allows use of the command line tools that come with the VMware host and if needs be, manage the virtual machines directly. I frequently use it when I need to migrate virtual machines between infrastructure that is not directly connected to both source and destination and also to get around firewall issues. [Download PuTTY]
6. PowerGUI

Using the default PowerShell Integrated Environment (PSE) is not an experience to relish. I just don't use the PSE. I can, however, wholeheartedly recommend PowerGUI by Dell. Quest was the company that created PowerGUI, and Dell recently purchased Quest.
It is a fully integrated IDE that has autocompletion and plug-in modules to extend the functionality. The VMware community has additional plugins to expose VMware functionality. There is a pro version that has version control and a few other features that are overkill to most admins. [Download PowerGUI]
7. PowerCLI

PowerCLI is an essential part of scripting sauce that extends the functionality of the PowerShell environment. To use the scripting environment with VMware, you need to create a VMware account to download the tool for free. We've also published a PowerCLI getting started guide that will help get you up to speed quickly. [Download PowerCLI]
8. Virtual vCenter Mobile Access (vCMA)

Virtual vCenter Mobile Access is not really production ready, but it is a handy tool to manage the infrastructure from an iPad. It is not a tool you would use every day, it allows for rudimentary management of an environment in a pinch. [Download vCMA]
9. VMware Converter

Any seasoned administrator is going to be using the VMware converter tool frequently. As the name implies, it allows an admin to convert other physical and virtual platforms and import them into the vCenter infrastructure. Using the converter tool does more than just importing a machine into the infrastructure. The converter allows an administrator to resize the disks, alter the memory and number of CPUs prior to import. Other nice features include the ability to install VMware tools as part of the import process and also power on the imported virtual machine after it's complete. [Download VMware Converter]
10. vMA Management Assistant for Linux admins

The vMA is a godsend for Linux administrators who wish to manage the vSphere infrastructure using Linux-based tools. As every VMware admin knows, the move from ESX to ESXi left behind the RH based console that was replaced with a very small and rudimentary hypervisor shell. [Download vMA Management Assistant]

To stop all the Linux guys from deserting VMware, the clever VMware guys and girls created the vMA. The vMA is essentially a pre-packaged Linux system that allows an admin to run Linux and Perl commands against the vSphere environment. For those that don't like Powershell, Perl can be used in its place, with all the SDK elements exposed. It gives the Linux lovers a chance at automation.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664