Multiplicity 3 Pro KVM License Glitch?

190411 - Multiplicity 3 Pro KVM has worked great for us. What a blessing for productivity, thank you.

Running Multiplicity 3 Pro KVM : Version 3.44 Build 00090,
on multiple Windows 10 systems, with all Windows updates current.

One day sitting at a secondary system, I changed advance settings to control the primary from a secondary computer.
Checking the switch: "Control / Allow Secondary to control KVM computers (Activation Needed)".

I received the enter a license key dialog, and then entered in my Pro KVM license, and all worked fine.
After this, upon rebooting the primary system, Multiplicity stopped working on both the secondary and primary computers (icons in the system tray greyed out) with the Error Messege : Your Multiplicity license has expired.

My Object Desktop license has not expired (good until 06/2022).

Both computers; the secondary (I used to work backward to the primary from) and the primary computer throw the Multiplicity license expired error with the "Control / Allow Secondary to control KVM computers" switch turned on in the secondary.

I reentered my license key for Pro KVM on the primary to get working again, and all seemed fine -- but on the next reboot of either the primary or secondary system, I received the same license Multiplicity expiration notice.

I then deselected the switch in the secondary "Allow Secondary to control KVM computers" and reentered the license key for Pro KVM on the primary to get working a second time.

Upon doing so, the Multiplicity icon on the secondary also turned blue.

We'll see if this solves it?

Rebooting the primary computer.
The icon on the primary has now turned blue.

Pro KVM across all systems now appears to be working as before.
I thought you should know about this seemingly weird behavior.

Thanks for the great software.

Jeric

7,825 views 3 replies
Reply #1 Top

Hello,

I have forwarded your problem 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.

Reply #2 Top

Quoting xajo, reply 2

Hi buddy, can you throw some update on the issue? Like solved or anything else?
End of xajo's quote

That setting, 'Allow Secondary to controls KVM computers' is meant to control other KVM (not Seamless) computers, not another Primary.  While I have not (yet) tested the OPs exact scenario, it was never meant to work as he detailed.

Furthermore, a second license is required to have a Secondary control another Secondary - to use that feature.

Sean Drohan
Stardock Support Manager