macOS - ​Parental control is blocking ScreenConnect

Branislav Kosik 5 years ago updated by anonymous 3 years ago 7

Parental control is blocking access to ScreenConnect GUI under guest account while Screenconect is listed and whitelisted in parental controlapp restrictions. Current workaround is to disable parental contrrols on the mac.

These error messages appear in dmesg when Parental Control is enabled.

Error message while blocking:

mcxalr{7} ** Denying execute for uid=201 path=/opt/screenconnect-69449ba1d361d3da.app/Contents/MacOS/AllitRemoteSupport Client

(screenconnect) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

and this one in Guest screen (so the Guest cannot work, it appears every 5 seconds):

You don´t have permission to use the application "jspawnhelper."

For more information, contact the person who set up your account.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:
Waiting for information

Good afternoon,

Thank you for reporting this behavior.

If I understand you correctly, you have installed an access client onto an OS X endpoint where one of the users is restricted by parental controls.

You have explicitly permitted the user access to the application (i.e., by granting access to AllitRemoteSupport Client - opt), but when you connect to the endpoint while the restricted user is logged in, the host is presented with a black screen, and the guest user sees a message stating that they do not have permission to use the required application. Is this correct?

Also, please submit the following information about your environment:

1) Version of ScreenConnect

2) Version of OS X installed on the guest machine where parental controls are enabled



Yes, the app "screenconnect client" is shown in the parental control GUI and checked to allow it.

Upon connection, i have the "waiting for consent" screen but the consent window never actually shows, instead the permission error shows up.

Operating System:

Mac OS X (10.11.6)

Client Version:


Good afternoon,

Thank you for following up with that information. I was able to replicate the behavior you describe in our test environment when attempting to connect to an OS X guest with the 6.1.12292 access client installed while a user restricted by parental controls is logged in (the parental controls explicitly allow the ScreenConnect Client for this restricted user).

I have registered an issue with development, and it is currently under investigation.



Hello Ben,

I would like to ask if this issue will be fixed in next stable release. I checked 6.2 release log, but I didn't find any mention about it.



Hello, do you have any news about this bug? Do you plan to fix it in next release?




Good morning Branislav,

This issue has been transitioned to the development team for review and resolution. While I'm unable to guarantee that a fix will be included in the next release, I can assure you that we are actively investigating the best way to mitigate the anomalous behavior.



Hi Branislav,

Are you still experiencing this issue on the latest version? The latest stable is 6.6, 6.7 is to be next in a couple of weeks.