Skip to main content
Question

Trying to improve 0 touch deployment

  • August 1, 2024
  • 5 replies
  • 14 views
M
Forum|alt.badge.img+1

Hi there,

 I have recently started a new roll and am trying to fix up the JAMF instance on site. One thing that is really bothering me is that through deployment I need to have the user(s) enable Remote Management. I keep getting the error 

On Macs with macOS 13 and onwards, Jamf is no longer able to automatically enable Remote Management. If you haven't already, please do so manually before proceeding forward with deployment.

Im sure this is great from a security standpoint for users however, when sending computers to users and asking them to do that is a bit of a headache.

I guess what Im asking is, is there a way around this error/warning and a way to enable this with out relaying on the user?

Thank you.  

    5 replies

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • August 1, 2024

    If you are new to Apple management, one word of advice. You do it Apples way, or you don't do it at all. Apple no longer allows Remote Management to be enabled programmatically, there is no way around this or to force it. You can enable Screen Sharing with an MDM command on Supervised Devices which allows you to use ARD or Screen Sharing to access a device for support situations which really has nothing to do with deployment.

     

    What is your current deployment process? 

    M
    Forum|alt.badge.img+11
    • mschlosser
    • Contributor
    • August 1, 2024

    Remote connection to the gui is sort of a 'nice to have feature', but not strictly necessary in my opinion; as you did deeper into jamf function, you'll find there is almost always a way to do what you need, whether they be PPPC Payloads, or package installs, with scripts, or standalone scripts or the commands apple builds into the command line.

    If you GUI connections as and absolute last resort, and typically not necessary, you'll start to like jamf and apple's method's a lot more.

    i've come other believe that if I have to touch a user's mac, something went wrong, art sounds goofy, but i find it helps to view every issue, no matter what it is, how would I do this, if i couldn't touch the computer?

    M

    mvu
    Forum|alt.badge.img+20
    • mvu
    • Jamf Heroes
    • August 1, 2024

    Your mileage may vary, but here's a Jamf Script:

    https://github.com/jamf/Jamf-Nation-Scripts/blob/master/enableARD.sh

    You just need to enter your "targetUsername" in the script.

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • August 1, 2024

    Remote connection to the gui is sort of a 'nice to have feature', but not strictly necessary in my opinion; as you did deeper into jamf function, you'll find there is almost always a way to do what you need, whether they be PPPC Payloads, or package installs, with scripts, or standalone scripts or the commands apple builds into the command line.

    If you GUI connections as and absolute last resort, and typically not necessary, you'll start to like jamf and apple's method's a lot more.

    i've come other believe that if I have to touch a user's mac, something went wrong, art sounds goofy, but i find it helps to view every issue, no matter what it is, how would I do this, if i couldn't touch the computer?

    M


    Apple protects screen recording permissions pretty hard. You can toggle Screen Recording off and on for supervised devices as a mass action or in the inventory record, it must be an MDM command so this cannot be scripted beyond scripting Jamf API commands to do this. Once Screen Recording has been enabled, you can use shell scripts to change who has access to what.

     

    PrivacyPreferencesPolicyControl.Services | Apple Developer Documentation

    bern
    M
    Forum|alt.badge.img+11
    • mschlosser
    • Contributor
    • August 1, 2024

    Apple protects screen recording permissions pretty hard. You can toggle Screen Recording off and on for supervised devices as a mass action or in the inventory record, it must be an MDM command so this cannot be scripted beyond scripting Jamf API commands to do this. Once Screen Recording has been enabled, you can use shell scripts to change who has access to what.

     

    PrivacyPreferencesPolicyControl.Services | Apple Developer Documentation


    ah, thats a good point, good to know that some of those things are being added back as mass actions.

    Terms & ConditionsCookie settingsAccessibility statement