Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
VMDK TO VHD - PROBLEM WITH LEGACY APP

Answered VMDK TO VHD - PROBLEM WITH LEGACY APP

  • Montag, 28. Januar 2013 13:51
     
     
    Anmelden
    0
    Hello.
    I'm Brazilian and i have a application that run in Vmware and this application run in Windows 2000 and has a Legacy Application.

    I need convert de VMDK to VHD, but when i make Sysprep in the Virtual Machine in VMWARE and i convert the Virtual Machine to VHD and turn on in virtual pc, the virtual machine crashes. 

    What i make  ?

    Thanks

    Atenciosamente Julio Araujo

     

Alle Antworten

  • Montag, 28. Januar 2013 14:34
     
     Beantwortet
    Anmelden
    0

    What are you using to convert the VMDK to VHD?  Often it requires that the VMtools be removed from the VMDK before starting the process.

    Not all applications will work with sysprep.  Many applications must be installed after an image is built from a sysprep image.  Are you sure your application is capable of being sysprepped?

    Any possibility that you can rebuild the virtual machine from scratch on the Hyper-V destination?  This ensures that you have a clean install.  This and other forums have lots of posts of both success and failure of converting from VMDX to VHD.  It's just a constant possibility that your particular VMDK has something in it that the designers of the conversion utility did not test for.

    .:|:.:|:. tim

     
  • Montag, 28. Januar 2013 14:46
     
     Beantwortet
    Anmelden
    1

    Hi Tim.

    Don't have any possibility to rebuild the virtual machine because is the app legacy and we don't have a documentation of the legacy application.

    I used starwind 2v2 to convert vmdk to vhd and i remove the VMtools and VMclient.

    HELP-ME kk

    Atenciosamente Julio Araujo

     
  • Montag, 28. Januar 2013 18:16
    Moderator
     
     
    Anmelden
    0

    If you are using virtualPC you will have a HAL problem.  If you are using Hyper-V the problem will be a lot easier to deal with.

    The absolute biggest thing you have to deal with is changing the boot device from SCSI to IDE in the 2000 Server - not an easy task but possible.  And a simple disk format conversion does not handle stuff like this.

    If you still have the original VM (and I sincerely hope you do) - use the same 2000 Server methodology that is highly documented for moving the installation to new hardware.  Boot the VM on ESX, Use Server Backup and perform a backup, Install a new server in a target VM, apply the Backup, fix any remaining issues.

    (search around a bit, you will find the process I outlined documented in great detail).

    This is how we did it before the OS was smart enough to deal with any hardware changes.

    Beyond that, the OS is so old (and the application so critical), pay for a good conversion tool.

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.