Page 1 of 1
No mouse cursot after migrating.
Posted: Fri Aug 02, 2024 11:13 am
by ipod86
Hello,
I moved 2 physical PCs to an ESXi using the StarWind V2V Converter, P2V Migrator.
Some PCs can also be booted in ESXi.
However, I can't get a mouse cursor to control anything via RDP or in the remote console in the ESXI.
Re: No mouse cursot after migrating.
Posted: Fri Aug 02, 2024 11:39 am
by yaroslav (staff)
You need to install VMware tools.
Re: No mouse cursot after migrating.
Posted: Fri Aug 02, 2024 1:20 pm
by ipod86
How can I do that without a mouse?
When I start the setup via Esxi it doesn't work.
Re: No mouse cursot after migrating.
Posted: Fri Aug 02, 2024 1:34 pm
by yaroslav (staff)
Try using the keyboard.
This could be also helpful
https://www.petenetlive.com/KB/Article/0001370.
Re: No mouse cursot after migrating.
Posted: Sat Aug 03, 2024 8:27 am
by ipod86
Thanks for the answer.
I still have 2 questions.
Can I install the VMware Tools on the bare metal beforehand or will that affect further operation on the physical machine?
So far I have used the VMware vCenter Converter and have not had any problems. Does it integrate the tools when converting?
Re: No mouse cursot after migrating.
Posted: Sat Aug 03, 2024 9:05 am
by yaroslav (staff)
Greetings,
Can I install the VMware Tools on the bare metal beforehand or will that affect further operation on the physical machine?
Theoretically, yes you can install it. I believe it is more a VMware-related question. Could you please let me know the OS you use inside that VM?
So far I have used the VMware vCenter Converter and have not had any problems. Does it integrate the tools when converting?
No, it does not. VMware tools are to be installed after conversion.
Re: No mouse cursot after migrating.
Posted: Sat Aug 03, 2024 9:12 am
by ipod86
I tested a Win10 and Win11 computer. With the VMware vCenter Converter, only the Win10 computer where the mouse worked.
Re: No mouse cursot after migrating.
Posted: Sat Aug 03, 2024 9:39 am
by yaroslav (staff)
Guess there's something on the VMware tools side.
As a workaround, try converting individual disks.