[tweetmeme]
This tutorial will provide you with the necessary steps to install and setup vSphere Management Assistant – vMA
The VMware vSphere Management Assistant, vMA, can be downloaded from VMware by click here and selecting your release version on the right hand side. In this tutorial I will be using version 4.1.0
Installation and Setup of vMA
1. Once you have downloaded the vMA OVF file from VMware via the link above, launch your vCenter Console and click on the file menu – Deploy OVF Template.

2. Browse to where you have saved your vMA OVF file and click Next.

3. A summary is displayed of the vMA appliance. Click Next.

4. Click Accept to Accept the End User License Agreement and then click Next.

5. Pick a Folder that you wish to store the virtual appliance in and click Next.

6. Select the host or cluster that you wish to run the vMA appliance on. Click Next.

7. Select the Resource Pool or vApp that you wish to deploy the vMA appliance into. Click Next.

8. Select the Datastore that you wish to install vMA into and click Next.

9. Select Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed or Thin Provision. My options are greyed out here as my datastore is an NFS volume that is thin provisioned on Netapp Storage SAN. Click Next.

10. A summary of your settings are displayed. Click Finish.

11. Deployment of vMA is successful. Click Close.

12. Power up the vMA appliance and open a console window. Enter in your IP Address, Subnet Mask, Gateway Address, Primary and Secondary DNS IP Addresses and Hostname.

13. A summary of your settings are displayed, type yes and press enter.

14. The root user account is disabled by default, so you must use the user vi-admin. Type in a new password for vi-admin.

15. Your vSphere Management Assistant vMA virtual appliance is now ready for use.

16. You can now open up putty or your ssh client and successfully connect through to your vMA appliance.

Disclaimer:
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.
Be the first to comment