I assume you have this start-conditions:
Lets say that the data is on drive h:\ and is a single partition.
I am planning on putting it on a separate external drive that is unused.
I've actually already created a virtual machine called broken server.
Lets say it's i:\broken server. What's the command to convert it? I am running Worstation 12 on Windows 7
Edit settings of "broken server"
Add hardware > select "harddisk" > select SCSI > click NEXT > select "Use a physical disk"
Now you should see a screen popup which allows you to select a PhysicalDrive by its drivenumber.
Make sure you select the external drive with the harddisk of the server.
When you sure you got the right number click NEXT.
Call the vmdk in next screen "import.vmdk" and safe it.
Now you should have a very small new vmdk named "import.vmdk" in the directory of "broken server"
Next you can use the vmware-vdiskmanager command to convert this small import.vmdk (which is just a pointer to the external disk at this time )
into a regular vmdk that no longer needs the external disk.
D:\Program Files (x86)\VMware\VMware Workstation/vmware-vdisksmanager.exe -r import.vmdk -t 0 "brokenserver.vmdk"
Let me know when you have done this ...
next task is to reconfigure the driver of your new VM ...
Is this a sector by sector copy? If so I don't have enough room on the hard drive.
I have it running now importing it directly onto the new server. The hard drive is 360gb but only about 20 are used. Is it going to take up the full size of the drive?
Sorry - last few days were very busy.
Do you have done the patching too ?
When I try to boot the VM it crashes. I'm not sure what you mean by patches.
1 person found this helpful
When I try to boot the VM it crashes
What exactly is the issue you have? An inaccessibly boot device, crash within the OS, ...?
It's not unusual that a converted machine cannot boot right away, because the virtual "hardware" is different from the physical hardware that's been used before.
What usually needs to be done is to inject the proper HDD controller driver, and disable/uninstall hardware related drivers, and tools.
In case the VM cannot boot, you can use VMware's Converter and run a "Configure Machine" job on the VM, which should fix the boot issue. Then - depending on the issues you have - you may need to do some cleanup with installed hardware related drivers, and tools, which may involve booting the guest OS in Safe Mode.
As mentioned in my previous post, you may use VMware Converter with the Configure Machine option, which is supposed to injected the controller driver.
Once the VM starts, disable/delete hardware related drivers, services, and tools manually.
I have the server running now. Thanks.