Thank you Plamen. I have a new problem. It looks like the really large disks(2.147 TB), give the the following error in VMware converter standalone
Unable to obtain hardware information for the selected machine
Thank you Plamen. I have a new problem. It looks like the really large disks(2.147 TB), give the the following error in VMware converter standalone
Unable to obtain hardware information for the selected machine
What converter version do you use?
What does the worker log read about that?
How did you get on with this?
Hello,
I recently installed vCenter Converter Stanalone as a client-server type on a Windows 2012 machine.
This machine has been flagged for POODLE violation and I don't have any other "server" type application installed on it.
I found the following article that has instructions on how to disable SSL. However the fix on this article didn't seem to resolve the POODLE violation as the machine is still being reported for this vulnerability.
VMware KB: Disabling SSL encryption on VMware Converter Standalone 5.x
Has anyone else worked on disabling SSL on converter standalone server? Are there any other steps I need to take? I'm connecting to vCenter Server 5.1 and have installed Converter Server Standalone 5.1
Thanks,
I am using the 5.1 converter because we are on esxi 5.1
Hi
i have convert one of my physical system to virtual (Windows server 2003 Sp2) it conver successfully but now just now there is 1 problem is some times in a day that's network become DC. in this vmnic there are more than 8 VMs but just this virtual machine's network disconnect is there any tools that help me to send a report that realy what time that network has been dc simple program such as PING just can pin my vm about 24hours and send report to me when it get time out
Best regards
Babak
what do i have to do ?
It's very likely you have a problem with the DNS for one or more of your hosts. Check in C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs and look for the vmware-converter-worker-*.txt files. You'll probably find strings such as "Error: Host address lookup for server <yourhostname> failed: No such host is known" Fix these DNS issues (NB: you might have the DNS records setup correctly, but an incorrect search suffix on your converter server) and vConverter will magically start working.
Hi all,
Quick question, when performing a block level conversion, does this also perform a defrag type activity or will it convert the fragmented drive as-is?
Thanks
B
File level perform some kind of defrag, but if using file level is always recommend perform defrag before start the conversion process. Block level make copy of block by block image of drive instead of copy files.
Some references: Differences between file-level and block-level cloning - CNET
File-level cloning also has a benefit in that it can be used to defragment drives. Since file-level cloning does not monitor which blocks are used on the drive, the files it copies can be stored on any set of blocks that are available on the new drive. Therefore if a file is fragmented among several groups of blocks on one drive, when it is copied to the new one it will be written in a contiguous group of blocks, thereby defragmenting the file.
And VMware KB: Reducing disk volume size using VMware Converter fails
Hi,
Thanks for the reply, luckily i'm on top of everything regarding file level conversions, thanks for the links though.
I'm specifically looking for info on block level, I'm convinced i read and article regarding block level conversions and a link to defrag - So I am trying to find a definitive (with some evidence, articles etc) on whether defrag is or is not required for block level conversions.
Thanks!
B
Hi All,
I'm trying to convert old Win2k3 server to my vSphere environment using vCenter Converter Standalone (tried version 5.0 to 5.5) and job is failing at first percent with error:
FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754774 (0x80042316)
At source machine there are no errors in eventlog.
ps. is there still chance to download vcenter converter earlier than 4.0?
Thanks!
Hello
This is not due to converter version. It is a VSS error (VSS_E_SNAPSHOT_SET_IN_PROGRESS). Have a look at this article: VMware KB: VMware Converter fails at 1% on Windows Server 2003 with the error code 2147754774
Regards
Plamen,
thanks for quick reply, I've found that article earlier, but I've checked and I have only one VSS provider
"Microsoft Software Shadow Copy provider"
Any other suggestions? how about converter 3.x - I found that it use cold conversion that should help in case of VSS error (?)
Hi,
I had similar issue. Once restart of VSS services helped (or was it restart of the server?), in the second case it didn't help and we used the old version of converter with bootable CD. I don't know where to download it now, though.
Unfortunately the boot CD for cold cloning is not available for download anymore.
I would also suggest restarting VSS (and if that doesn't help - the whole machine). Getting the same error after restart when there are no additional providers is something that looks very improbable (just because I dare not use the word 'impossible' ).
Thanks, I'll try with bootable CD with vmware converter. Let you know next week about results!
Here it's a code snippet (in Java) witch creates the source spec for this local machine conversion and it works:
LOG.info("invoked setupSource() - prepare THIS LOCAL MACHINE as source spec");
ConverterComputerSpecLiveComputerLocation liveLoc =
new ConverterComputerSpecLiveComputerLocation();
// hostname set to empty string = This local machine source
ConnectInfo connectInfo = this.converterServerMachine.getConnectInfo();
liveLoc.setHostname("");
liveLoc.setUsername(connectInfo.getCredentials().getUsername());
liveLoc.setPassword(connectInfo.getCredentials().getPassword());
liveLoc.setOsType(ComputerSpec.getLiveLocationOsType(this.converterServerMachine));
this.sourceSpec = new ConverterComputerSpec();
this.sourceSpec.setLocation(liveLoc);
Pay attention that the hostname is an empty string (not null). Also you should provide administrative credentials, and the source OS type (which is always "windowsOs" in the case "this local machine")
Thanks!! worked for me, nothing else did. chrisweatherford
I've tried installing this on both a Win7x64 and also a Win10x64 computer with the same results. I am the Administrator of the computer. I am the only user of the computer. The file I am using is VMware-converter-en-6.0.0-2716716.exe. I've tried running it straight up and also by right-clicking and running it as an Administrator. Same results.
Any suggestions/advice would be greatly appreciated.