Control Permissions In For Terminal S Install Of MacOS

To set up Connectwise Control on a brand new install of macOS 10.14, these steps are required: Install.pkg as normal (this allow remote viewing but no control) Reboot macOS computer After reboot, attempt remote control, this will prompt a popup asking if the macOS computer wants to allow Click Open System Preferences Click lock (bottom left), enter computer password Check box next to screnconnect-xxxxxxxxx Reboot Remote control again works In cases where remote control was working on a macOS 10.14 computer where Connectwise upgraded from 6.6 to 6.7, connectwise software must first be removed using these steps: From Access website, select session End Uninstall and end On macOS computer, open system preferences accessibility Click lock (bottom left), enter computer password select screenconnect-xxxxxxxxx, click - to remove Reboot Install using steps above I believe this complexity is due in part to some sort of increased system security in the new macOS.

I have a few headless Mac servers I am wanting to upgrade to Mojave, but cannot do that until this is resolved.

In that case, Id encourage you to contact support so we can take a closer look at your case.

Based on what Im seeing, the only way to get keyboard and mouse going again is go to follow the original steps above while physically on the computer.

The only other way weve seen around this is to use Apple Remote Desktop (ARD) andor VPN to get into the Mac, since it doesnt require a 3rd-party authentication.

Is it possible that one of the permission request prompts was declined during the first installation.

Host is also 10.14 Mojave.

Ive uninstalled the remote agent, rebooted, and reinstalled and granted all of the recommended permissions, with no success.

On the remote computer: open system preferences click Security Privacy icon click Privacy tab along top click Accessibility on left unlock using password select screenconnect-123abc entry click minus button to remove reboot attempt remote control, this should cause access warning to pop up approve access warning At this point remote control should work again.

It seems that this process must be repeated each time the ConnectWise Control agent updates.

Since posting this topic a few weeks ago I have had to repeat this on each 10.14 Mac to regain remote mouse and keyboard control.

You need to have an incoming screenconnect session to add the privacy setting properly.

In other words, much of this might be the same with any remote control tools aside from Apples remote desktop or VPN.

Here is Teamviewers guide on this topic: Still I think ConnectWise Control could be a bit more straightforward on this.

It would be great to see it check for this new security allowance, be more consistent with asking the system for control (as much as Apple allows this), and most importantly, keep remote control allowance through ConnectWise agent upgrades.

You can check by using the following command in terminal codesign -dr - optscreenconnect-.app It gives the following response optscreenconnect-.app: code object is not signed at all In a future release if ConnectWise release a signed application you can give accessibility access using Jamf by creating a configuration profile.

Then users wont need to go into system preferences and approve it, which they need admin access to do and youll be able to connect to labs to troubleshoot issues instead of just observing.

I havent tested the newer versions but didnt see any info about it on the release notes.

A great resource for info about this is the Macadmin TCC slack channel A requirement is that the application has to be signed.

Ive only been able to test ConnectWise 6.6, I get the prompt that the application in optscreenconnect is not signed.

I cant confirm if it works correctly on version 6.7 or 6.8 but I havent seen any information in the release notes.

I finally today looked again and stumbled on this above, while it did not work I kept at it and finally figured it out (and will share what I found - BTW, this worked on 10.14.1 as well, I have both now working yay) So here is what you need to know extra.

I kept getting the allow or deny choices in the pop up message so I could not follow it (find it).

Finally I found it, its a tab under Security Privacy (I know the vast majority of folks are saying Duh, assume I know less than many savvy Mac users, lol).

Control Permissions In Mac For Terminal Installs