Apostels

Join Date 11/2024

Connection to Windows 10 VM doens't work

Hey,

I've set up a virtual Win10 PC on a VM-Ware Host to be able to use some sort of Thin-Client and RDP to controll the second PC which just broke down some days ago.

Multiplicity 3 says its connected to the virtual WIn10 PC, but i can't seem to controll it in an RDP session.

If I'm in the VMWare Console of the Win10 PC it works flawless and I see the cursor and can controll it - when I connect via RDP it doesn't do anything at all.

Am I missing something or is it not possible at all?

Thanks in advance!

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,
Sorry to hear you are having issues. Need to know more on your system.

Windows 10 full version and OS Build number on both systems.
Multiplicity v3 version number on both systems

Thank you.
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

I've got a Win11 Tower PC that is used to controll the Virtual Win10 one:

Win11 Controll PC:

Version 23H2 (Build: 22631.4169)

Multiplicity 3.6 Build 00105.km

Virtual Win 10:

Version 1703 (Build 15063.483)

Multiplicity 3.6 Build 00105

Maybe thats a to big gap already - I can set up a Windows 11 VM tomorrow as well

Successfully updated karma reason!

It might be due to your older Windows 10 version. Maybe you should update your Windows 10 to current v22H2. Anyway, to be sure, I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

You seem to have a lot of moving parts here and some connection scenes and mediums that make this difficult to follow let alone test.

Perhaps you could diagram this out a bit more and eliminate other connection mediums (RDP).

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

So I just installed a fresh Win11 VM

24H2 Build 26100.2161

Multiplicity 3.6 Build 00105

Its the same issue again - in the VMCenter Konsole I can't see the mouse itself but I can see it hovering over like Edge and stuff and click it and the application opens.

If I'm in the desired RDP session it doesn't seem to connect at all - the primary computer says its connected to the secondary + it says im now controlling the secondary...

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+674

Quoting Apostels,

reply 5

Its the same issue again - in the VMCenter Konsole I can't see the mouse itself but I can see it hovering over like Edge and stuff and click it and the application opens.

Again, hard to follow your situations. However, for this issue, on the Secondary, try:

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Multiplicity controls the local console. So that is acts like physical mouse / keyboard. A remote desktop session by default creates a new session that the local keyboard and mouse cannot control.

I seem to recall there being an option to use the local console session but it seems things may have changed. For more info see here : https://superuser.com/questions/1047139/connect-via-rdp-as-if-it-was-a-local-session

Successfully updated karma reason!

That doesn't seem to work anymore - can open a RDP with mstsc /console when I use the CMD but then I don't see any difference - still only works in the console where I got now two mouse cursors when I control it....

I guess I will just switch back to a second PC then

Successfully updated karma reason!