Vmware Converter.

Hi.

I just tried to use VMware converter to convert a Physical machine (Win NT) to Virtual Machine.

Following issues came up while converting the machine.

Installation Of Converter Agent:
1. While installing thru the manager it give Unknown error while installing agent.
You can also install the agent directly on the machine. In this case you will know what the messages are:
Mostly the errors will be related to folders not having permissions. This is because Agent tries to write all the files using System Account and hence in NT desire System Acc to have write priviledges on the folders.
To see which folder the installation has stopped on start the installer from the command prompt on the machine like the undergiven command:
abc.msi /l install.log
The above given command starts the installation and logs the progress into install.log simulatneously.
2. Once the installation is complete (manual/Automatic) it often happens that the manager tries to start the agent installation again and again.
this is because the agent service is not running as the machine needs to reboot once the agent has been installed. Make sure that the machine is rebooted after agent installation.

Destination Folder:
The Destination folder needs to be accessible from both destination machine, source machine and manager machine. and should have write access permissions for installation.
So best way out of the problem is to give Domain\Anonymous Full controll to it for the time the migration is going on.

While bringing up the machine as well there were some issues as given below:

The machine start but you will not be able to install vmware tools:
Reason for this is that NT doesnt has builtin drivers for IDE cdrom which is probably being used in the OS. Since the drivers not loaded no drive available to vmware to load vmware-tools iso to. A very simple solution is available for this problem. Change the drive to a SCSI drive as drivers for scsi are built in.

The Machine doesnt connects to network in a bridged enviornment:
The issue which I saw in this particular problem was that the machine was on a bridged connection and the bridging service apparently didn't start up when the virtual machine was started.
Just shutdown the virtual machine and restart vmware services for this to resolve.
If it still doesnt works remove the ethernet adapter and create a new one.