I’ve come across a strange issue stopping me rolling out M1 MacBook Pros to our users to replace older Intel machines.
I’m unable to use ARD to screen share onto an M1 Mac in these scenarios:
Filevault on and Firewall on
Filevault on and Firewall off
Works if Filevault is off and Firewall on or Filevault is on and Firewall is off.
I’ve tested a MacBook Pro 14inch and 16inch M1 running Monterey 12.0 through to 12.2 with the same result.
If I test an Intel Mac with the same Filevault/Firewall on, ARD works no problem.
Not sure if I’ve missed something daft on these M1 machines or a bug in Monterey on Apple silicon.
I've never come across that message sorry.
At a bare minimum, all you need for all users to observe is the config profile scoped to the device and the enable remote desktop command sent once from Jamf. If that still fails on a freshly enrolled machine then there may be some restriction / policy preventing this from working.
I was recently able to get this working in Jamf Pro, and wanted to add a couple notes for anyone looking to enable Remote Management via script in the future.
First, thank you @Bol for providing your script! It was very helpful as a basis to set this up in our environment. However, some tweaks were required to get it to work. My notes are below.
I hope this helps! Thanks again to everyone in this thread for taking the time to help get this set up for others!
The script is below. Be sure to supply the appropriate information for parameters 4, 5, and 6. Parameter 4 is your API account username, parameter 5 is your API account password, and parameter 6 is your local administrator account username.
@jkline19 No worries at all and thank you for sharing the Jamf recipe, I had not come across that at all.. Kudos!
When enabling ARD via the api, I understand it turns on remote management for all users with only observe and control permissions which didn't meet our requirements.
Pairing with the kickstart command allowed us to specify one user and their access controls.
Oh vnc, you needed to add these switches to the command line. I kept this page in the initial script so I could always reference back to it, very handy. You too, cheers!
-configure -clientopts -setreqperm -reqperm yes|no ## Allow VNC guests to request permission -configure -clientopts -setvnclegacy -vnclegacy yes|no ## Allow VNC Legacy password mode -configure -clientopts -setvncpw -vncpw mynewpw ## Set VNC Legacy PW
One trick I learned from Richard Purves on how to acquire the target computer's Jamf computer record ID using a custom MDM profile...
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
Make the pref domain in the profile something unique like "com.my-org.jamf".
This will generate an XML plist with a single key/value pair at /Library/Managed Preferences/com.my-org.jamf.plist.
Then you can read it back as a variable anytime you need it to reference it from a script/policy on the Target Mac like this example:
COMPUTER_RECORD_ID=$(defaults read "/Library/Managed Preferences/com.my-org.jamf.plist" JamfProID)
If you aren't using MDM then the only option is to enable via System Preferences, locally on the machine.
That is by design, trying to automate this remotely via script will give you the blank screen described.
I setup three Mac Mini's during the week with no MDM, enabling remote management before deploying the machine worked.