The vMA is a Virtual Appliance that you can download from VMware. It’s primary function is to enable command line based management of your ESX/ESXi systems.
Basically this is a pre-packaged virtual machine that includes vCLI and the vSphere SDK for Perl, which means that you don’t have to build your own management VM or install these tools locally on a management station.
vMA is in many regards seen as a replacement for the ESX Service Console which no longer is present in ESXi.
Downloading vSphere Management Assistant (vMA)
Basically there are two methods you can use when deploying vMA.
- Download the .OVF file to your local machine and upload it to your ESX/ESXi host.
This is useful if you have already downloaded the vMA appliance and plan on deploying it to several hosts/clusters. This saves you from downloading it several times, and you can even use PowerCLI to automate the deployment of vMA, but I’m not going into that scenario this time around.
- Deploy the .OVF file directly from vmware.com, via the vSphere Client, to your host.
In this post, I’ll focus on how to deploy vMA using method 2 – Direct Deployment
Direct Deployment of vMA
Start your vSphere Client and connect to your host or vCenter.
Navigate to “File“, find and select the “Deploy OVF template” option
This starts the OVF deployment wizard. In the “Deploy from a file or URL” text box, enter the following URL: http://download3.vmware.com/software/vma/vMA-220.127.116.11-268837.ovf and click on “Next“.
Note: This URL is valid at the point of writing, but might change at a later date when a new version is released by VMware.
The URL is now validated, and you are presented with the OVF Template Details window, where you can review the settings defined in the OVF file.
Click “Next” to view and accept the VMware EULA. After reading it throroughly click on “Accept” and then on “Next” again to continue
Next up is the “Name and Location” screen, where you can customize the name of your vMA instance. If you are deploying the several vMA instances to the same host/vCenter, you will need to change this to prevent naming conflicts.
After naming your vMA, click on “Next” again, and you’ll get presented with the “Disk Format” screen. Here you can select between thin provisioned or thick provisioned disks, for this installation I chose to change it to thin provisioned, but the default is thick provisioned disks.
After making your selection, we once again click on “Next” and now we’re nearly there! Review the summary screen to make sure you have selected the right options and click on “Finish” to finally start the download and deployment of your vMA.
The download starts, and a nice little progress window shows you how far along you are.
Of course, the time it takes to deploy vMA this way is highly dependant on available bandwidth and download speeds. In this particular environment the download is estimated to take approximately 39 minutes.
Tip: If you want to deploy vMA in this manner, to several hosts, you can place the downloadable vMA .OVF file on an accessible file share or http server and serve your local path or URL to your host via the vCenter Client as well. This is particularly useful in scenarios where your vCenter Client doesn’t have internet access or if you want to speed up deployment by downloading it only once, but without scripting it.
Once the vMA has finished downloading and installing, it will pop up inside your vSphere Client on the host you deployed it to.
vMA Initial Configuration
The first time you start vMA, it fires a configuration wizard to help you configure it.
The wizard guides you through the network setup and setting the vi-admin user password.
And there it is. Now you can use your favorite SSH client (Putty) to connect to the vMA, or by using the console in the vSphere Client.
For details on using vMA and vCLI see the vSphere Management Assistant (vMA) site. You can even add ESX/ESXi and vMA to your Active Directory and use that as an authentication source, but I’ll leave that for another post on another day.