0
Not a bug

Select Monitor feature does not work on MacOS

Justin M 3 years ago updated by SpudGunzZz 2 years ago 3

This has been going on for some time as I figured it would be addressed by an update but it hasn't.  When connecting to systems with multiple monitors from my Macbook I have to view "All" monitors. If I select only one monitor or the other, the screen does not update.  When I change back to "All" monitors the screen updates and becomes responsive again.

ConnectWise Control Version:
19.1
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

Answer
Not a bug

This behavior did not replicate in a number of test environments. Marking thread as not a bug. If the behavior persists after upgrading server and clients to the latest 6.5 release, please update this post with that information.

Waiting for information

Good afternoon,


I've so far been unable to replicate this in our development environment by connecting to two and three-monitor Windows 7/10 guest machines via an OS X 10.11.6 host using the 6.3.13446 client.


Please update this thread with the following information:


1) What version of OS X is installed on the host machine?

2) Are you using the Mac bundle or the jnlp to join sessions from your Mac host machine?

3) Is Java installed on your Mac host? If so, what version?

4) Is there any pattern to the OS installed on the multi-monitor guest machines?


Also, if possible, please post the client logs from your OS X host machine. These should be located at  


~/Library/Logs/screenconnect-<xxxxxxxxxxxxxxxx> (client log) and

/Library/Logs/screenconnect-<xxxxxxxxxxxxxxxx> (client service log), 


where the x's denote your server's public thumbprint.


Cheers,

Ben

Answer
Not a bug

This behavior did not replicate in a number of test environments. Marking thread as not a bug. If the behavior persists after upgrading server and clients to the latest 6.5 release, please update this post with that information.

FWIW - I ran into this exact same problem that Justin described. Removing the Mac Bundle version 6.4 and re-installing the latest version 6.6 fixed the problem for me.