VMware Communities: Message List - Converter Standalone

I was able to find the bundles folder.

What log do you need - they all seem to be zipped.

Please advise.

Thanks.

John

Whole log bundle?

I could not find converter-client xml file in Installer folder

We have a Client with 10+ 2003 physical Servers that we need to convert to VMs in ESXi 6.5.

I've done some searching, and found that Server 2003 is no longer supported, and that Converter 6.0 was the last to support it.

What is the best way to P2V the 2003 Servers and get them into 6.5?

Do we use Converter 6.0 to P2V to ESXi 6.0 and then migrate to 6.5? Or will Converter 6.0 work directly with ESXi 6.5?

What Hardware version should we choose?

Any other tips for P2V on 2003?

Thanks!

Hi BCTTech,

Windows 2003 is still supported in vSphere 6.5 - VMware Compatibility Guide - Guest/Host Search .

So you can install VMware vCenter Converter Standalone 6.0 on one of your machines and run the P2V to vSphere 6.5. It should work fine.

I would also recommend VM HW version 11 (vSphere 6.0) to begin with and you need VMware Tools for legacy OSs - VMware Tools 10.0.12 Release Notes .

Hope this information helps.

Find at %ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone\converter-client.xml

Good day,

I am attempting to P2V a computer that has GPT disks in a windows 10 environment. I have successfully P2V other Windows 10 machines into this esxi 5.5 environment although they may not have been GPT disks

I have checked that the EVC mode was disabled, as this appeared to be an issue with others. This is disabled in my environment and I can select Virtual Machine versions 8, 9 & 10.

Each of them return the same error, so does each host and datastore.

VMware vCenter Converter Standalone version: 6.2.0 Build-7348398

vSphere 5.5.0 Build 2417603

I would greatly appreciate any assistance to get this working properly.

Thank you

Jeff

EFI firmware is supported from hardware version 11 and above. GPT disks are no indication for EFI, they can be used with BIOS too.

If you doubt which kind of hardware you use - start msinfo32.exe and check the "BIOS mode" on summary (first) page.

HTH

I have a Windows 2012 R2 file server with about 2TB plus of data on it. My question is... can users work on the server during the virtualization process?

They can, but you will need to instruct them to save and close all open files/work on this server before the final synchronization begins and then not to attempt to work again until it's been brought up as a VM. It is no fun task to hunt and peck around a physical file server after it has been P2Vd to identify and manually move changed files.

Hello markp56038,

Welcome to Communities.

What are you using to perform this P2V?

Most modern applications used to perform this have some form of 'final sync' option that can be performed.

Though even with this, I would agree with daphnissov that save+quit is the sensible thing to do to ensure currency.

Bob

VMware vCenter Converter Standalone v6.2.0

Hello markp56038,

From what I have read, it seems most have success with NOT initially selecting 'Perform Final Sync' option but instead to run the P2V then after this has completed to use the manual synchronize option.

Documentation may give further insight:

https://www.vmware.com/pdf/convsa_61_guide.pdf (can't find 6.2 guide -_-)

Bob

Thank you very much, so until we upgrade our VMware, we won't be able to P2V UEFI computers.

I appreciate your help.

Jeff

Correction: EFI is supported from hardware version 10+ but information about availability per GOS is placed in ESX - some GOS are allowed to have EFI, other not. There should be documentation about this in ESX (download, manuals, forum, etc.).

However upgrade to newer version is good idea and I hope will help in your case.

"An error occurred during the conversion: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId=[4B-3A-31-E9-00-00-10-00-00-00-00-00] and target volume id ;4:3139.0000010000000000. Error code: 2'"

In converter-worker.xml file in section plugins/converter_agent add tag <pcopyLogVerbose>true</pcopyLogVerbose> then restart the worker service. As result you'll see all files copied and which file gives the error 2 i.e. "The system cannot find the file specified."

Most probably you'll need to perform "chkdsk /B " on the disk with problem(s).

HTH

I have encountered a same issue with customer following the below kb article resolved the issue

VMware Knowledge Base

Regards

Yuvaraj

Thank you very much for the clarification.

I believe that an upgrade is necessary for more reasons than this, but I appreciate your insight.

I will look through the ESXi documentation to see if I can find anything relevant to my situation.

Jeff

Re: VCenter Convertor for vSphere 6

Re: Need to P2V Windows 10 Surface Book Pro - Keeps attempting startup repair

Re: Need to P2V Windows 10 Surface Book Pro - Keeps attempting startup repair

Re: SSL Exception when Converter tries to connect to vCenter

How to P2V multiple 2003 Servers to 6.5

Re: How to P2V multiple 2003 Servers to 6.5

Re: SSL Exception when Converter tries to connect to vCenter

Remote P2V fails with 'The destination does not support EFI firmware.'

Re: Remote P2V fails with 'The destination does not support EFI firmware.'

can I work on server during PV?

Re: can I work on server during PV?

Re: can I work on server during PV?

Re: can I work on server during PV?

Re: can I work on server during PV?

Re: Remote P2V fails with 'The destination does not support EFI firmware.'

Re: Remote P2V fails with 'The destination does not support EFI firmware.'

I've searched everywhere for the solution, please help!

Re: I've searched everywhere for the solution, please help!

Re: I've searched everywhere for the solution, please help!

Re: Remote P2V fails with 'The destination does not support EFI firmware.'