Can't connect via KVM to 1 PC but 4 others fine.

I have MP Pro and it works perfectly with 4 PC's.However my new build (1st AMD processor) just gives a black screen.All versions of MP are the same and the only difference in the PC's is the previous 4 have Win10 Pro installed but the new one has Win10 Enterprise. Also the new PC's MP does not show a KVM option on the Configure panel.

Is 'Enterprise' missing something or can MP not work with that version of Win10?

Brainiacs to the rescue,please.

10,056 views 14 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues.I have forward 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

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

Is 'Enterprise' missing something or can MP not work with that version of Win10?
End of quote

Irrelevant.

Also the new PC's MP does not show a KVM option on the Configure panel.
End of quote

Make sure you are activating with your Pro key and not an Object Desktop one or just email \ pass as it will default to it (OD) or the first key with the fewest activation if you have more than one MP version (KM).  Use the 'About' tab on the Primary to 'change' the license'.

I have MP Pro and it works perfectly with 4 PC's.However my new build (1st AMD processor) just gives a black screen
End of quote

When connecting to it - because the new box is a Secondary - yes?

Is it headless (no monitor)?  If so, this is a super cheap fix:
https://www.amazon.com/Display-Emulator-Compatible-Windows-fit-Headless/dp/B07C4TWZRM/ref=sr_1_3?dchild=1&keywords=hdmi+dummy+plug&qid=1595439833&s=electronics&sr=1-3

 

Sean Drohan
Stardock Support Manager

Reply #3 Top

When I installed MP it did not ask for my (any) key. I have now unloaded MP/Rebooted/Uninstalled MP via Control Panel/Deleted MP folder. Then re-installed MP and it started without asking for my key (same as before)

If I switch on the monitor attached to new PC it works & I get the following image instead.

Reply #4 Top

Quoting ellisalden, reply 3

When I installed MP it did not ask for my (any) key. I have now unloaded MP/Rebooted/Uninstalled MP via Control Panel/Deleted MP folder. Then re-installed MP and it started without asking for my key (same as before)



End of ellisalden's quote

Secondary PCs do not ask or need a key nor do they have a KVM tab.

Quoting ellisalden, reply 3

If I switch on the monitor attached to new PC it works & I get the following image instead.
End of ellisalden's quote

Then what I sent you will work or you keep the monitor plugged in - can be shut off in Windows power management but powered on and plugged into the PC.

Sean Drohan
Stardock Support Manager

Reply #5 Top

"Secondary PCs do not ask or need a key nor do they have a KVM tab."

Incorrect - my 4 PC's on Win10 Pro all have the following :-

 

 

So,I ask again,does MP work with Win10 Enterprise??

Reply #6 Top

Quoting ellisalden, reply 5

Incorrect - my 4 PC's on Win10 Pro all have the following :-
End of ellisalden's quote

I actually am correct with a default \ new install...

https://cdn.stardock.us/support/uploads/2020-07-23_12-53-00.mp4

Your evidence of the same UI for the Secondary should also be used...

The only way you can get the KVM tab on a Secondary is if it was once a Primary (thus activated) and \ or one enables this feature (requires an additional license):

https://cdn.stardock.us/support/uploads/2020-07-23_13-12-00.mp4

Quoting ellisalden, reply 5

So,I ask again,does MP work with Win10 Enterprise??
End of ellisalden's quote

My answer remains the same - that it is Win10 Enterprise is irrelevant. 

Sean Drohan
Stardock Support Manager

Reply #7 Top

Right-let's go back to the begining.

PC A = always been the only Primary-KVM option on Control Panel-Tray icon Blue

PC's B&C = original Secondarys-KVM option on Control Panel-Tray icon Grey

PC D = Brand new build Secondary-KVM option on Control Panel-Tray icon Grey

PC E = Brand new build (1st AMD PC) Secondary-standard,no KVM option,panel-Tray icon BLUE

So,what makes PC E different from the others? MP d/loaded direct from my Stardock A/C

If I switch on PC E's monitor I can control from PC A but that somewhat defeats point of MP.

It's coming up to the w/end so why don't you redo the MP coding over w/end to solve problem?

Reply #8 Top

This is what is displayed on PC E when it's monitor is on :-

Reply #9 Top

Quoting ellisalden, reply 7

Right-let's go back to the begining.

PC A = always been the only Primary-KVM option on Control Panel-Tray icon Blue

PC's B&C = original Secondarys-KVM option on Control Panel-Tray icon Grey

PC D = Brand new build Secondary-KVM option on Control Panel-Tray icon Grey

PC E = Brand new build (1st AMD PC) Secondary-standard,no KVM option,panel-Tray icon BLUE

So,what makes PC E different from the others? MP d/loaded direct from my Stardock A/C

If I switch on PC E's monitor I can control from PC A but that somewhat defeats point of MP.

It's coming up to the w/end so why don't you redo the MP coding over w/end to solve problem?
End of ellisalden's quote

As Sean correctly says, the KVM tab will only appear on a secondary if the secondary is activated.  Unless the machine is also going to be used to connect TO other KVM machines there is no point in activating it on a secondary.  When switching between primary and secondary mode you will be prompted to deactivate or you should be able to do so from the secondary about page.

There is no change license button on a secondary unless the computer has been activated and there is one on your screenshot so that is why you are also seeing the KVM tab on a secondary.

Now with regards to your issues :

The colour of the taskbar icon on the primary will always switch depending on mode.  Grey for nothing connected, blue for connected and red for when things are locked on the primary.

On a secondary the icon colour should always be blue with one exception.  If they are also set to be able to use the KVM mode to connect to other computers then the icon may be grey when disconnected.  This is why you have grey icons on PC's B, C and D.

The icon on the screen when you control it via KVM mode is showing as you have the setting enabled to "Show indicator on screen when being controlled via KVM mode".  This can be controlled on a secondary by going to MultiplicityConfig, picking the security tab, then clicking the KVM control settings button.

Finally some video cards will not allow capture of their output when they have no attached monitors.  This is probably why PC E is being picky about not allowing anything to be captured.  This can be worked around using the dummy HDMI (or display port depending on need) plugs which Sean linked to earlier.

What video cards do PC B, C, D and E have?

Reply #10 Top

Thank you for trying to solve the puzzle.

PC B = Radeon HD 7700

PC C = Radeon HD 5570

PC D = GeForce RTX 2060 Super

PC E = Radeon RX 570 RS XXX

As all the above are just for Distributed Computing GPU's not too important.

Reply #11 Top

Quoting ellisalden, reply 10

Thank you for trying to solve the puzzle.

PC B = Radeon HD 7700

PC C = Radeon HD 5570

PC D = GeForce RTX 2060 Super

PC E = Radeon RX 570 RS XXX

As all the above are just for Distributed Computing GPU's not too important.
End of ellisalden's quote

While I would look forward to any work-around Neil might be able to engineer for any black screen issues for remote KVM sessions, if you are expecting an immediate remedy, the HDMI dummy plugs would be the best option.

Sean Drohan
Stardock Support Manager

Reply #12 Top

I,too,await Neil's input & I have not forgotten your dummy plug option.Assuming no progress by next Wed (UK time) I intend to do a clean install of Window 10 followed by a clean install of MP. It doesn't take that long and it would make me feel like I had tried all I could.

Thankfully AmazonUK have an equivalent dummy plug.

I will be back next Wed to update you as I'm sure you will have trouble sleeping until you know :D  

Reply #13 Top

Quoting ellisalden, reply 12
Assuming no progress by next Wed (UK time) 
End of ellisalden's quote

Extremely unlikely.

Sean Drohan
Stardock Support Manager

Reply #14 Top

Decided not to wait to reinstall system and bought a dummy plug.This will surpise you but it worked :blush: . Problem resolved but not why the problem arose in the 1st place.Only physical difference from my other m'cs is that this one had an AMD Ryzen CPU?? Anyway thank you for your help and now onward and upward.Start a replacement build this w/end and it's a 2nd AMD - wonder how this one will go?