accessibility access on mojave

I just use vnc://ip.address.of.machine with remote management enabled in sharing, everything works great.
If you want to go the hamachi route you can use the PPPC utility and apply a configuration profile to automatically accept the permissions that hamachi needs. This would prevent the dialog box from appearing, and it doesn't require the user to be an admin. Taccy is another good utility to help you determine what permissions the app needs.

@mlizbeth how many machines are being managed and how often are there remote support requests?

i havent used VNC here, but is it similar to ard/screenshare or is there a separate needed?

lastly, how did you deploy remote management to your users? config file or via a combo of scripts?

thank you!

@jcheLC We have 200 currently, most of the Faculty/Staff machines don't see many problems, so I usually only remote in to our lab environments in this manner. However, all of our machines have this configuration enabled.

VNC is the protocol that the Screen Sharing app uses, so it'll work the same.

I used a script to enable remote management and restrict login to 1 specific user.

I think Screen Sharing needs a physical user click to enable it, while remote management you can still script out. This changed in Mojave. When enabling Remote Management in this way, Screen Sharing will become enabled, but in System Preferences it explicitly states "Screen Sharing is being controlled by Remote Management"

#!/bin/bash
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -activate -configure -clientopts -setmenuextra -menuextra no 
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -configure -users its -access -on -privs -all
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -configure -allowAccessFor -specifiedUsers -privs -all
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -restart -agent -menu
/usr/sbin/systemsetup -setremotelogin on
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -config -clientopts -setmenuextra -menuextra no
exit 0

@mlizbeth Thanks for the script example. Do you just put in 1 specific user account in this line after - specifcUsers?

/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -configure -allowAccessFor -specifiedUsers -nameofspecificaccount -privs -all

I only put one user since nobody else needs remote access

/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -targetdisk / -configure **-users its** -access -on -privs -all

@mlizbeth Thanks for the info. I'll test it out on one of my Mojave systems. Most of our computers are still on High Sierra, and the few that are on Mojave have access issues with ARD due to the privacy changes.