Posted by on Oct 25 2013 in.If you have a home lab, it's likely you already discovered how handy it can be to have VMware Converter in your virtual tool bag. Want to take an ancient laptop, and wish to breath new life into for occasional use as a VM instead? Wishing you could resurrecting that slow 'spinny' drive in a much faster virtual machine?

• Cms Unable To Obtain History
• Failed Unable To Obtain The Lock On Virtual Disks

Then VMware Converter is likely a piece of Windows software that you'll want to check out. Install it somewhere on your home network, and as long as that system you install converter on can reach the physical machine on your same network, the process of converting it into an ESXi 5.5 based VM is pretty straight forward. DisclaimerEmphasis is on home test labs, not production environments. No free technical support is implied or promised, and all best-effort advice volunteered by the author or commenters are on a use-at-your-own risk basis. Properly caring for your data is your responsibility.

TinkerTry bears no responsibility for data loss. It is up to you to follow all local laws and software EULAs. Privacy PolicyPlease review the TinkerTry. CopyrightShort excerpts of up to 150 words may be used without prior authorization if the source is clearly indicated.

This means you must include both the original TinkerTry author's name, and a direct link to the source article at TinkerTry.© 2011-2019 TinkerTry.com, LLC all rights reserved. DisclosureTinkerTry.com, LLC is an independent site, has no sponsored posts, and all ads are run through 3rd party BuySellAds. All editorial content is controlled by the author, not the advertisers or affiliates. All equipment and software is purchased for long-term productive use, with any rare exceptions clearly noted.

Affiliate Link DisclosureTinkerTry.com, LLC is a participant in the, an affiliate advertising program designed to provide a means for TinkerTry to earn fees by linking to Amazon.com and affiliated sites. These revenues help show your support by helping fund the production of quality content, at no cost to you. Other shopping links featured in the articles may be from Skimlinks, Digital River/OneNetworkDirect, or Commision Junction affiliate programs, and could also result in small commissions for purchases. Many content creators will find Skimlinks a convenient way to commoditize high-value content, with little effort. If you're interested in automatic Skimlinks to help cover the cost of running your site, consider using this.

Environment:VMware vCenter Standalone Converter v6.1.1 installed in local-only mode onWindows Server 2016 with the converter installed on a physical server (ip 10.160.0.69/24)Unbuntu Desktop 12.05 Test VM in a Hyper-V Cluster (ip 10.160.0.65/24)VMware ESXi 6.0.0 (trial) on a physical server (ip 10.160.0.66/24)Same switch, default gateway (10.160.0.1), dns serversHello!I am testing a proof of concept for my company where we can capture any physical machine on our network and bring it into our Hyper-V cluster. The best way I have found to do this is with VMware ESXi and converter.

I have setup a test Ubuntu VM that to capture to ESXi. I installed openssh-server on the VM and can ssh into it from the.69 Windows Server using Putty.

When I go to convert the VM with VMware, Isetup the job and start it. It starts with 1% about 1 hr then 2% 3hrs 15min, then 3% 1hr, then 3% 1min, then failed at 3%. Here is the status the job ends with:FAILED: A general system error occurred: connect (`10.160.0.65'): Network is unreachable connect (`10.160.0.65'): Network is unreachable connect (`10.160.0.65'):Network is unreachable Network error. Host 10.160.0.65 key can't be retrieved.

(return code 2)I don't understand why this is happening. All your help is appreciated. I'll be at my desk to answer any questions or post any more needed info.Thanks in Advance! HelloThis seems to be a different issue than your first post.

When converting a live Linux machine, the destination VM boots from an ISO (it is called Converter Helper). This helper attempts to connect and authenticate to the source machine. Which means the destination VM (which is in a virtual network) needs to have access to the source and the source to allow remote SSH connections from there.I couldn't quite understand your first post. Looks like a network configuration issue.In order to log in the helper VM, you need to enable it in Converter.

Have a look here -HTH,Plamen. Just wanted to share this in case someone else is having the same issue, and going insane.VMWare Converter Standalone 6.1.1 refused to convert a SLES 12.1 machine - constant error message of 'Unable to query live source machine'.After looking into the log files and manually executing the data generation script, it appeared that the presence of grub2 was causing the issue, as the '-batch' property was no longer valid.Instead of downgrading grub, I decided to try converter 6.0.0, which seems to work without issue. Once the migration completes, I will follow up if there are any other issues. I'm trying to test out converting my Hyper-V VMs for a dev lab, and I'm running into problems with the converter tool. The environment is managed by VCenter, and when I run the converter (from the Hyper-V host), I get to the Destination Location screen, and after I select the host, the 'Virtual Machine Version' often fails to populate (spinning forever) or if it does populate, it does so after about 15 or 20 minutes.

Cms Unable To Obtain History

I chose Version 11, and managed to start the job, but now it's saying that moving a 22 Gb VM will take 3 days? The network between the hosts should be better than that.The main problem though is that all the communication with the VMWare environment is incredibly slow. Is this a common problem, and if so, are there any suggestions for getting this to run faster?

Failed Unable To Obtain The Lock On Virtual Disks

I don't really care if I need to let moves run overnight, but if it takes an hour just to create the job, something is definitely wrong. Hi,I'm quite new the proper IT game, only really having built and configured windows machines for single users before, but as the most tech-savvy person at my company I've been elected the un-official IT guy.A while back we were set up with a refurbished HP DL380-Gen6 and DL380-Gen7 when our business grew to the extent of requiring our own server and we didn't want to spend too much on actually buying a new server (not my decision), we didn't know any better at the time and they turned out to be pretty hamstrung through the use of SATA drives rather than SAS drives. Also not sure what state they were in before we bought them. A win7/xp dualboot setup will very very likely use bootmgr on a win7 partition to boot - so if you dont copy the win7 partition there will be no bootable partition on the disk.Workaround 1: copy all partitionsWorkaround 2: copy xp-partition only and then use a BartPE LiveCD for the first boot and manually inject ntdetect.com,ntldr and a boot.iniWorkaround 3: copy xp-partition and use a floppy-image for the first bootI dont think that any of the listed options will work without manually patching the xp-driver-settings.