With updating of VMware Infrastructure to 5.1; I also installed the latest Standalone Converter 5.1.0. While doing P2V conversions with Windows Server 2008 R2; I faced a few problems.
With Converter 5.1 Build 1087880: Was constantly getting the error:
Unable to obtain hardware information for the selected machine.
I made sure to follow the checklist given on VMware KB 1016330 but to no avail. Hence reverted all the changes I did according to the given list.
With Converter 5.0 Build 470252 (as used that version previously with success but with vCenter 5.0): Surpassed the initial error but when pointed to my vCenter 5.1; the Converter would stop responding and get crashed.
I then finally resolved the issue by using Converter 5.0.1 Build 875114. Worked like a charm!
I still haven’t figured it out what could be the issue! But for now the Converter 5.0.1 is working great with vCetner 5.1 Update 1. But I did figured out the following steps bears no fruit;
- VSS Shadow Copy service on source machine does not need to be on.
- Third Party antivirus or backup services on source machine need not to be stopped.
- Simple file sharing on source machine need not to be disabled.
Tags: converter, datacenter, error, hardware information, standalone, Unable to obtain hardware information for the selected machine., vcenter 5.1 update 1, VMware
Ashfaq Ahmad Shinwary 
July 3, 2013 at 12:19 AM |
I have used 5.0.0 and 5.1 and both have the same error, Unable to obtain hardware information for the selected machine. Does it have anything to do with win7 and the 7GB vmdk file? I can’t seem to get this Fusion VM converted to ESXi…arrgghh.
July 3, 2013 at 1:34 AM |
Have you tried Standalone Converter version 5.0.1? That worked for me!
July 10, 2013 at 11:07 PM |
No luck with 5.0.1.
July 17, 2013 at 9:24 PM |
Try installing the agent first on your source machine; and then later manage it remotely from the Converter! See of that helps!
August 12, 2013 at 6:42 PM |
I also keep having the same problem with 5.0, 5.01 and 5.1 converting a Linux machine
August 23, 2013 at 7:25 PM |
I see; well i haven’t experienced any p2v linux environment conversions yet!
September 2, 2013 at 9:14 PM |
The way I got around this was by choosing the remote machine option & IP of 127.0.0.1.
September 6, 2013 at 12:10 PM |
I see! Will check how that works.
September 9, 2013 at 1:32 PM |
I got to this post looking for a workaround to the same problem.
What i finally did was as simple as loging off my windows session and log back in. After that the converter worked like a charm.
BTW my version is 5.1
September 10, 2013 at 5:36 PM |
A complete reinstall fixed my issue.
October 11, 2013 at 11:45 PM |
Disable EUC.
November 27, 2013 at 8:04 AM |
I think he means UAC.
Another alternative is to use local builtin administrator account as this bypasses UAC
May 28, 2014 at 12:01 AM |
Disabling UAC worked for me.
June 11, 2014 at 2:23 AM |
Thanks.. This works for me . I have uninstalled converter 5.5 and installed 5.0.1.
January 12, 2016 at 7:53 PM |
I used the same solution as Simon Payne. Use the Administrator account. Converter v.5.1.0 build 1087880 and Windows 2008 Server R2
June 20, 2020 at 12:08 AM |
Thanks a bunch for sharing this with all folks you actually know what you’re speaking approximately! Bookmarked. Kindly also visit my website =). We will have a link trade agreement among us|
May 28, 2021 at 7:49 PM |
Once more, these are just a couple of of the numerous summer time occasions in the Southern Illinois region. The goal of poker is to win the pot of chips at the middle of the desk.