VMware Converter Standalone 5.0 U1 - cannot convert W2k3

Similar Questions

• VMware Converter Standalone 5.5 does not display a Drop Down Menu for the Type of Destination

  Hi people,

  I try to use VMware Converter Standalone 5.5 for use with VMware Player and am not able to select the Type of Destination of my choice (I like to choose "VMware workstation" or another VMware virtual machine in the drop-down menu "Select the destination type").  Please see the image below where the combo box is not there at all.  Thanks for your help.  Hai

  

  This isn't a bug, it is a limitation of the converter. It is stated in the documentation. Converter considers that any machine under tension like physics. It cannot convert powered on Linux machines to hosted (i.e. Workstation/Fusion) destinations.

  A solution would be to convert it to ESX and then convert the (from) power off the VM power to the workstation.

  HTH

  Plamen

• VMWare converter standalone fails at 1%.

  Hello

  I have a problem of conversion of some machines on the subnet to another. Since then, I work at the University, here are fairly complex network infrastructure. Whenever I need an open port, I have to record a call and to wait a few days so that it can be resolved.

  I have:

  5.1 ESXi on the subnet has

  PC which is on the subnet and is able to connect to the subnet B via port 80, 445, 9089.

  Some servers that will be migrated at the subnet B.

  Now when I try to set a task with VMware converter standalone installed on PC to clone a physical host (win 2 k 3) on subnet B, I get status failed with the error message: an error occurred during conversion: 'unknown exception '.

  I found on this forum similar problem (P2V conversion fails at 1%, 'an error occurred when converting' unknown exception' ') and double-checked my logs.

  2013-08 - 01 T 11: 11:06.719 + 02:00 [warning 02020 'Default'] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Unable to connect to server 1.2.3.4:902 (this is the IP of ESXi server)

  2013-08 - 01 T 11: 11:06.719 + 02:00 [02020 info 'Default'] [, 0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

  2013-08 - 01 T 11: 11:06.719 + 02:00 [02020 info 'Default'] [, 0] error 2338 opening disk ha-nfcssl: / / [ESXi_storage] servername/servername.vmdk @1.2.3.4:902! 52 14 82 92 62 db ec - a3 c4 4 a 72 fd f1 da b5 ac.

  the problem is unclear to me. Source machine tries to connect directly to ESXi server and storage. But for me to record a call "opening port" for each server that I want to convert is a little awkward to say and I was wondering is - it possible somehow to migration through PC in a subnet that has access to powered on the source machine and the ESXi server. And these machines would not need to directly contact the ESXi Server?

  Thanks for your replies.

  S.

  Hello

  You can convert to the format of the workstation and then convert the resulting ESX VM again. If you have a machine with enough storage in the subnet B, convert, and then physically move the machine or the storage of subnet A and convert again. So, you can bypass the firewall completely.

  HTH

  Plamen

• VMware Converter standalone OR... I'M CONFUSSED!  Help, please

  Hello

  I have the vmware converter plugin installed.  What is this for?  I can't find any documentation.  The only documentation I can find is for the stand-alone version.  Work together or what?  Then the documentation still says to install the converter on the source machine and I understand not what converter, they're talking about. I want to do a cold cloning on my SQL servers.  It's the standalone "VMware-converter - 4.0.1 - 161434.exe" and it's the VMware converter ' VMware - Converter.exe "I use the standalone version for a test of my Vista machine as a clone of good hot and has worked.  But I do not understand the cold cloning process.  Can someone point me to the documentation.

  My environment is PE2950, ESXi 4.0 embedded, vCenter Server vSphere 4.0.  I am cloning all standard W2K8 servers.  Some SQL, domain controllers and servers of rest files.  A Server Application.

  Help!

  Thank you

  GEOBrasil

  GEOBrasil,

  I understand the confusion around the different products of converter.  I hope that I can help you better understand which version is right for you.  The reason for the different versions is based on what type of conversion you want to do, which are based on physical operating systems (Source) and your virtual environment (Target) is going to be.

  Couple of warning or best practices:

  -VMware recommends NO conversion P2V from DC.  It is better to build NEW virtual machines for this.

  -Hang your applications (SQL, WEb, etc.) before making a hot-clone (plug-in or standalone Enterprise)

  First, for each platform VI3.x, VI4.x there are TWO business (plugin) version and a standalone version (Windows & Linux applications)

  -VMware comparison chart gives an overview of the differences (http://www.vmware.com/products/converter/get.html)

  Non-exhaustive summary below:

  Enterprise Edition:

  Pros: vCenter integration and automation, supports

  Cons: you have to pay for it (you already have it if not the factor in your assessment.  No 'multi-stage' conversion (i.e. 1 snapshot converter, deltas on a machine running are lost or migrated manually).  No Linux support. Can't stand VI as a platform to target.  Includes the CD "cold-clone".

  Stand-alone Edition:

  Benefits: support Linux.  Supports the VMware Desktop products (workstation, Fusion, etc.) as target platforms. "Several steps" cloning, intial snapshot conversion as deltas.  Source and target of service and the power of command for Windows.

  Cons: Billable per-incident support.  No automation, scheduling.

  Cold-conversion

  Benefits: no changes can occur on the source server.  preserves the logical partitions.  No service application comes into conflict with the local area.  No installation on the source area

  Disadvantages: Requires downtime for the source server.  Requires the driver support for all devices on a physical to be present in BootCD (WinPE) Server

  Hope this helps

• VMware Converter Standalone copy is the copy block level and sometimes at the level of files

  Hi team,

  I use VMware converter standalone for P2V and V2V migrations. I noticed that some readers are cloned by the converter by block-level copying and some readers are colned by the file-level copy. Anyone can unmask me why is it so? Block level and file level methodology is decided by the converter on what basis? is the size of the size\sector disc or disc type? Any suggestion will be highly appreciated.

  Thanks in advance

  Kind regards

  Rohit

  Screen enclosed... Post edited by: RohitGoel

  RohitGoel wrote:

  Is there a limit of resizing who decide if vmware converter will use the file level cloning. I have attacehd a screen shot... I'm resizing it had ' (from 50 GB to 80 GB) drive also for traget VM but yet Vmware converter used method block based to clone and 'E' is also a resized to target disk is converted by file based cloning. .. is there something else that decides on the level of the file or block level when it resizes?

  No limit of resizing.

  To resize the D: you extend that will always use at the block level.

  What do you do to E:?  Size reduction?

• Using vmware converter standalone

  Hola, estoy using vmware converter para comenzar a virtualizar pero Necesito saber como hago UN para the vm no cambie su number, sid, ip, licenses etc.

  Hay siempre esto o Quebec is can sejar tal cual?

  If no converter El cargo in which sysprep can pasar?

  I hope I can help.

  MUCHAS gracias.

  Buenas

  ESO suele pasar con licenses OEM. None are 'legal' porque van en theory sujetas virtualizarlas the red, grafica, memoria y placa base of Mac of the card. As puedes hacer Lo e tratarlas como nuevas, contains the activacion por telefono pero facilities.

  Por cierto, sube al ultimo ServicePack (sp3 of xp, 2 k 3 y xp64 sp2) para descartar antes este tema as tambien dio su guerra por aquel entonces.

  If esta u otra respuesta're util, por favor su marca used notificador.

  Gracias / looks

• VMware Converter standalone 4.0.1 gets 97% error: impossible to reconfigure the virtual target computer. Linux P2V conversion

  I have 97% then it goes down. I'm conversion server Ubuntu 9.10. I will attach the logs. "GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127 and message:

  /VMware - updateGrub.sh: 38: grub: not found

  GRUB runtime error

  Vmware runtime error - updateGrub.sh through chroot into/mnt/p2v-src-root

  22/10/09 discovered Ubuntu 9.10 uses Grub2 is the problem and can it work with Grub2?

  Let me know if you can help.

  OKI I did the P2V and after it failed to 97%,

  I started the virtual machine with the LiveCD mode help, connected root to/dev/sda1, installed grub2 and finally ran "upgrade-from-grub-legacy".

  After the reboot, everything works fine.

  So no need to replace your UUID and all that. That should be enough.

  Thank again for this band of working capital.

  Bragi - of Iceland

• Cannot start vmware converter

  I am at my wits end and I thought that I'll never ask publicly a question as simple as that: I installed Virtual Center 2.5 and want to run vmware converter. services are running, but how do I start the GUI?

  This should be the easiest thing in the world, but there are no shortcuts, no start, no exe files work menu entry (they are all CLI tools), and my VI client doesn't give me any options to import...

  It seems to be properly installed in C:\Program Files\VMware\Infrastructure\Converter Enterprise, services run etc. I just want to see the graphical interface, so I can import a physical machine.

  It seems that you have installed the Converter server. Have you downloaded the plugin converter to the VI Client? "If this isn't the case, please go to the Plugins menu-> manage Plugins... and download the plugin converter in the tab" available "within"plugin Manager"?

  If the converter server is installed and registered successfully with your VirtualCenter server, you should be able to see a link to download the plug-in in the tab"available" converter plugin Manager '. "

  Only after the installation of the converter plug-in, you should be able to see the VI Client options for importing a physical machine. You may have to restart the VI Client after downloading the converter VI client plug-in.

• VMWare Converter Standalone for ESXi 4.0 - thin discs?

  I wonder if there are plans for Converter support the commissioning of thin disks on ESXi 4.0?

  VMotion is not an option for me unfortunately, and am not looking forward to recreate a VM just to get a thin disk...

  In theory, I guess I might be able to create a thin disk and clone one hard drive to another, but it's not something that I've tried before and so I'm not sure of what is involved?

  Someone at - it an entry into that? I'll be workining on ESXi 4.0 installation as soon as I have time (assuming that my whitebox support)...

  Hello.

  Check out http://www.yellow-bricks.com/2009/05/21/vmware-converter-401/ or http://blog.tpv.dk/?p=3

  Good luck!

• VMware Converter refused while trying to convert the Linux server

  Hey all, I'm trying to convert a Server CentOS 6.6 Nagios in a virtual machine on a cluster of ESXi 5.5.0 and not having a chance. When I try to start the conversion I get following error message:

  [Code] Permission to perform this operation was denied [/ code]

  I use VMware vCenter Converter Standalone server Version 5.5.3 Build-2183569 and I am doing the server Linux my VMware vCenter Server, Version 5.5.0 Build 2001466. I thought I could use the wrong password but I can't able to root very well on the Linux server. Iptables is off and Selinux is disabled. I played with the free version of ESXi and now I'm under more Essentials. I Googled it and found a lot of answers, but none of them fit my situation. Here, any help would be greatly appreciated.

  Thank you

  Joe B

  If you run the client VMware Converter from a Windows OS, try running with the help of the high privilege (Run As Administrator): http://www.jonathanmedd.net/2013/12/vmware-converter-permission-to-perform-this-operation-was-denied.html

• Error VMware Converter in converting a physical server

  Hi support them.

  We Vsphere 5.5 and trying to convert a physical machine into a virtual machine with the help
  VMware Converter 5.5 standalone.

  source server is windows 2008 r2

  We receive the following error

  FAILED: An error occurred when opening a virtual disk. Check
  that the Converter server and machines running the source access access network
  to the ESX/ESXi hosts source and destination

  Please help me solve the same if it's not
  the appropriate forum to discuss this please guide transmit me on the right Forum

  You can also find the error logs

  Thank you

  Anoop

  The error is:

  2014 05-11 T 18: 17:05.288 + 04:00 [warning 03248 "Default"] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Failed to search for host for server presxi13.in.nawras.com.om address: no host is unknown 2014-05-11 T 18: 17:05.288 + 04:00 [info 03248 "Default"] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

  Your physical machine could not connect to the ESX Server, allow the COMPLETE domain name resolution in a physical machine. HTH

• VMWare converter - Windows NT

  Hello

  Not sure if this is the right place for this question, but I need to create an image of VM to a Windows NT computer.  I was hoping to use the Converter Standalone package, until I realized that it was not compatible with NT.  Then I read that an older version (3.0.2) of the converter work with NT, but was crushed to learn that he was no longer available for download.  Can anyone offer any suggestions?

  Thank you

  Glen

  glenikins wrote: I checked this and v4.0.1 does support Windows NT (SP6) but only for a machine virtual source, not to a conversion powered physical machine.  It's a physical Windows NT machine that I need to convert it to a virtual machine.  Do I have any options for this?

  Yes, there are always options.  The manifest is for VMware converter - 3.0.3 - 89816.exe is no longer available for download on VMware, however, it can be downloaded from elsewhere.  Don't say that I recommend that, however, it is an option and if you choose that route then ensure that the SHA1 checksum: 29ed0cc664df0a7caba542ad1d3e18eb3aed4e96

  Another option might be to use imaging software to create an image of the pHDD to a vHDD in a virtual machine and then see if the converter can handle the VM image to start correctly and install VMware Tools.

  Then the other option is similar to the second option that after imaging P2V start the virtual machine with the appropriate ISO Image and manually inject the necessary Mass Storage Controller and keyboard driver and settings in the Windows registry to enable the virtual machine to start and then install VMware Tools.

• Unable to get hardware information for the selected with vmware converter 5.5 computer (could not get the ability to \\.\PhysicalDrive0: error opening peripheral drive: 32 an unknown error (0 x 20) (32))

  Hello

  I'm doing a P2V with vmware converter standalone 5.5

  The source is the same machine that hosts the vmware converter 5.5

  The operating system is W2003 which acts as a domain controller

  VMware converter is launched by the administrator account.

  The error that I see on the balls of vmware - converter.worker is:

  2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
  2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive1."
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
  2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
  2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive1."
  2014 02-13 T 17: 36:41.155 + 01:00 [warning 04344 'Default'] attention: no attached disks have been detected.
  2014 02-13 T 17: 36:41.155 + 01:00 [04344 error 'Default'] [LiveWindowsComputer] could not find disks connected to the computer.
  2014 02-13 T 17: 36:41.170 + 01:00 [info 04344 "Default"] scheduled timer cancelled, succeeds StopKeepAlive
  2014 02-13 T 17: 36:41.170 + 01:00 [04344 error "Default"] unknown exception when calling VMOMI method queryComputerInfo
  2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
  2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive1".
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\ '.
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\ '.
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\ '.
  2014 02-13 T 17: 36:50.421 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:50.421 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
  2014 02-13 T 17: 36:50.452 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:50.452 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
  2014 02-13 T 17: 36:50.499 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
  2014 02-13 T 17: 36:50.499 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive1".
  2014 02-13 T 17: 36:56.155 + 01:00 [05648 WARNING 'Default'] attention: no attached disks have been detected.
  2014 02-13 T 17: 36:56.155 + 01:00 [05648 error 'Default'] [LiveWindowsComputer] could not find disks connected to the computer.
  2014 02-13 T 17: 36:56.155 + 01:00 [info 05648 "Default"] scheduled timer cancelled, succeeds StopKeepAlive

  This had already happened with another server (also W2003 DC), but the hardware was completely different; Unfortunately, I wasn't able to solve this year here.

  Any help or advice would be appreciated, thanks in advance

  Thank you for all your help

  I finally found the guilty service.

  It was pcmonitor monitor/remote control software. Once I stopped it is service vmware converter could get the capacity of the physical drives.

  It is rather curious because I made several servers P2V conversions using this software (so far the last one two weeks ago - the difference between that server and this one was that the first was not a domain controller).

  Hopefully this thread will help others in the future.

• VMWare Converter - 2gig - not preallocated pieces

  I have a strange problem that I can't find any information on, but I'm betting is a bug. I use 5.0 ESXi and VMWare Converter standalone 5. When converting to a virtual machine (for backup purposes) with a 40 g drive, choose to use the option "not previously affected. The virtual machine is saved and is about 7g. To make it possible to put it on DVD (s), I use the option of breaking into pieces of 2 G, also "not previously affected." However, when you use this option, I get about 20 2 files. Also when you use the option of 2G block, seems always pre assignment even though I specified that it should not. Has anyone experience this problem?

  Welcome to the community,

  What did you choose as a target for the conversion? ESXi does not support fragmented files of 2 GB.

  André

• VMware Converter fails on physical client - not enough space

  Hello

  I try to use VMware Converter on a physical client that runs Windows 7 and get this error message:

  Failed: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source computer has not all NTFS volumes. Error code:
  2147754783 (0x8004231F).

  When you run DISKPART - VOLUME LIST I can see that the two partitions is formatted with NTFS.

  Anyone have any idea why the process fails?

  Thanks in advance.

  -Edgar

  In addition, found this with a search... you all unallocated on your hard drives partitions?

  http://community.Spiceworks.com/topic/254411-VSS-error-when-trying-to-P2V-server-using-VMware-Converter