I am attempting to use MAP 8.5 to provide an assessment of an existing VMWare environment to determine which virtual machines are ready for migration to a Hyper-V platform using the Microsoft Virtual Machine Converter (MVMC) application.I have gotten MAP to assess the VMWare virtual machines by connecting it into the vSphere server and I am getting data back on all of my machines.
The thing that is puzzling is that it states that none of my machines are currently ready to migrate using MVMC and the reason listed is that “Virtual machine is not accessible through WMI.”
Now I know that my machines are accessible through WMI, and as a test I deployed a brand new virtual machine in the VMWare environment and I can connect over WMI remotely without issue.I also ran a MAP Windows Inventory against the OU that contained this new computer and the Windows scan succeeded, with a WMI status of success listed in the InventoryResults report.
So my question is, is it possible that MAP is not reporting correct data back to me regarding the ability to connect into these VMWare virtual machines over WMI?I have tried running a Windows based inventory first, which utilizes WMI in the hopes that it would initialize things properly for the VMWare scan, and have also run a Windows and VMWare scan simultaneously, and in both of those tests I got no information
about that VMWare environment at all, literally no information, so this did not seem to help.
Can you let me know if it is possible I am missing a step somewhere, or if the VMWare scan might not be pulling back accurate data?I find it weird that the VMWare scan uses the VMWare webservice to connect into the vSpher server, but I get recommendations concerning WMI, since the scan did not use WMI in the first place, so how can it know that the machine is not accessible through
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.