Link to home
Start Free TrialLog in
Avatar of Borland dBase III Plus
Borland dBase III PlusFlag for Hong Kong

asked on

Convert Hyper-V to VMware

Hi All,


I am using VMware 6.0 server, I convert Hyper-V VM to VMware through vCenter Converter. The Guest OS is Windows Server 2016. The vm converted to VMWare server successfully. When I started the vm, I cannot use mouse in VM and I cannot access the shared folders of VM from a Windows 10 client. I have disabled the firewall in vm.


I checked the vm property in ESXi server, system has installed VMware tools. Can anyone help?


Best Regards,

ScanDisk

Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

does the virtual machine have a network interface and an IP Address ?
Avatar of Borland dBase III Plus

ASKER

Hi Andrew,

After I converted to VMware, the static IP setting lose in guest OS. I need to set back the static IP (IP : 172.16.10.100) in guest OS. I can ping the vm's IP, but I cannot access \\172.16.10.100 in Windows 10 client computer.

Best Regards,
ScanDisk
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Andrew,

Sorry for late reply. Thanks for your information.

Yes, I also found the other articles that after convert the Hyper-V to VMware, the IP address of VM will be removed. I also found that I cannot install VMware Tools to this VM in ESXi server console. I need to connect ESXi Server console through VMware Workstation and then I can install VMware Tool into the VM.

After installation of the VMware Tools, I can use mouse in ESXi server console to control VM and the client computer can access the shared folder of this VM. The issue has been fixed. Thanks.

Best Regards,
ScanDisk