When running Inventory Scenarios, I've found that it isn't a good idea to run multiple scenarios at the same time, at least when you first start using MAP. The reason I don’t think it’s a good idea is this, if your environment is not properly prepared it creates a lot of issues to try to troubleshoot all at once. Each MAP database is cumulative, so as new machines are discovered and new data is collected, it is appended to all of the existing data. It is also important to note that the data is static, so once collected, it will not be refreshed. If already inventoried machines are modified, the only way to capture that modification is to start a new database and inventory the environment again. Once you've become familiar with MAP and are confident that your environment is properly prepared, choosing multiple Inventory Scenarios is not a problem.

Inventory Scenarios Wizard Page

To inventory VMware hypervisors, only choose VMware on the Inventory Scenarios page of the Inventory Wizard.

At this point in the wizard, what you choose will depend on whether or not you have vCenter managing your environment.

Inventory with vCenter

MAP can discover information about your VMware hypervisors using your vCenter server. When MAP connects to vCenter, it gets the data that vCenter has on the hosts that it manages as well as the friendly names of the guest virtual machines on those hypervisor hosts.

One point of caution, if you have an environment where virtual machines might change hosts, such as manually being moved or because you use vMotion among other reasons, then it is possible that the data MAP obtains about the host/guest relationship will change when you inventory the guest machines later in a subsequent inventory. At this time, we don’t have a reliable way to uniquely identify a VMware guest virtual machine to know if it is a duplicate of one we already have information on, so we will list both in the report to allow you, the end user, to determine what are duplicates based on your knowledge of how your environment is set up.

Discovery Methods Page

If you have vCenter, you will only choose the manual entry method on the discovery page. AD DS is checked by default so make sure you uncheck that.

All Computers Credentials Page

Skip entering information on this page

Credentials Order Page

This page is not used for this and is only needed if you have multiple credentials. In those cases, the order specified here will be the order in which MAP tries to authenticate using those credentials.

Enter Computers Manually Page

Enter the vCenter server name and be sure to choose Use specific credential list. MAP uses the VMware web service, so you need to provide admin credentials that allow access to vCenter via the web service.

Connection Properties Page

Enter the ports used for VMware web service and MAP will get the host info for the environment. By default MAP puts ports 80 and 443 in the list, but some VMware installations are configured to use port 8222 for HTTP and port 8333 for HTTPS. If the SSL certificate you use is self-hosted or otherwise not able to be authenticated through a trusted CA, make sure to uncheck the Validate SSL Certificate box. If you don’t need or use HTTPS then you will want to delete those ports from the list. See the MAP TechNet Wiki article on VMware for environment preparation details.

Inventory without vCenter

If you don’t have vCenter or don’t want to use your vCenter server for any reason, you will need to provide a way for MAP to discover the host names of your hypervisors.

One point of caution, if you have an environment where virtual machines might change hosts, such as manually being moved or because you use vMotion among other reasons, then it is possible that the data MAP obtains about the host/guest relationship will change when you inventory the guest machines later in a subsequent inventory. At this time, we don’t have a reliable way to uniquely identify a VMware guest virtual machine to know if it is a duplicate of one we already have information on, so we will list both in the report to allow you, the end user, to determine what are duplicates based on your knowledge of how your environment is set up.

Discovery Methods Page

If you don’t have vCenter or don’t want to use it, then you will need to choose a method of discovery that will allow MAP to discover your VMware hypervisors. The method of discovery will depend on your environment. ONLY CHOOSE 1 DISCOVERY METHOD PER INVENTORY RUN.

  • AD DS: You can use this discovery method if you have your hypervisors listed in your Active Directory. If you happen to have them consolidated in their own OU, you can limit the discovery to just those hosts, otherwise MAP will try to inventory every host name it finds in AD.
  • IP Address: You can use this discovery method if you know the IP range that has the hypervisors you are interested in.
  • Manual Entry: If you don’t have many hypervisors that you want inventoried, you could choose this discovery method.
  • Import from a file: You can use this discovery method by creating a text file with the host names or FQDN's (1 per line) of all the hypervisors you want inventoried.

AD DS Configuration Pages

If you chose this discovery method these pages will appear. Fill in the information appropriate for your environment.

IP Address Configuration

If you chose this discovery method this page will appear. Fill in the information appropriate for your environment.

All Computers Credentials Page

MAP uses the VMware web service, so you need to provide admin credentials that allow access via the web service.

Credentials Order Page

This page is only useful if you have multiple credentials. If that is the case, the order specified here will be the order in which MAP tries to authenticate using those credentials.

Enter Computers Manually Page

If you chose this discovery method this page will appear. Enter the hypervisor host names and be sure to choose Use All Computers credential list.

Import from File Page

If you chose this discovery method this page will appear. Enter the hypervisor host names into a text file (1 per line) and be sure to choose Use All Computers credential list.

Connection Properties Page

Enter the ports used for VMware web service and MAP will get the host info for the environment. By default MAP puts ports 80 and 443 in the list, but some VMware installations are configured to use port 8222 for HTTP and port 8333 for HTTPS. If you don’t need or use HTTPS then you will want to delete those ports from the list. See the MAP TechNet Wiki article on VMware for environment preparation details.

Viewing the Results

After you have inventoried your VMware environment you can see the information collected from vCenter or the hypervisors in the VMware report which can be run from the Server Virtualization > Virtual Machine Discovery scenario detail page. If you did not use vCenter and MAP was unable to connect to a hypervisor to inventory it, then it will not appear in this report because MAP had no way of knowing what type of machine it was.

Troubleshooting

Check to see if the following services are running:

  1. VMware Inventory Service
  2. VMware vCenter Management Web Service
  3. VMware Storage Profile Driven Services

Test the connection from the MAP machine to the target by opening a browser and trying to connect to that hypervisor’s web service. To do this:

  1. Open a web browser and enter in the vCenter server name (i.e. http://myvCenterServer) and in the upper right corner click the link to “Log in to Web Access”

  2. Enter the admin credentials

  3. Make sure whatever username and password you use here is what you use in MAP. If you had to enter in a port number to get this to work, make sure to put that in the wizard instead of what is there.