

#Jamf vs apple remote desktop church software
It was used to make the speedy implementation of software and script policies that were uploaded into JAMF where now I must tell clients it will be installed when it can be installed when each client checks in.

It was used to push and finish policies “instantaneously” instead of waiting to push something and constantly checking back on the web interface to see if it was completed. But JAMF Remote was not used to remote into devices as it’s the primary function, of most people. I don’t know what the thinking logic was to remove one of the best tools that you had in your arsenal to work on macs.
#Jamf vs apple remote desktop church pro
I had hoped (and still hope) Jamf was going to integrate Jamf Remote's capabilities into their Jamf Pro UI, but we've yet to see that happen, and something tells me they won't have that in the product by the time Jamf Remote.app is axed. In conclusion, ¯\_(ツ)_/¯ I don't have a great answer to this one. But most products out there are geared toward "remote control" and not so much "remote commands", so that might be easier said than done. Outside of ARD or VNC, you may have to consider looking at some other commercial product that can do remote support.

Microsoft for example, gives RDP away for free, and Microsoft is arguably more reliant on revenue from software than Apple is. (digression: Why Apple still charges for that product is really beyond my comprehension and seems like an insult given that it hasn't been significantly updated in many years. If using a local admin account is possible, there is always things like Apple Remote Desktop, but this is of course an additional cost. I understand it's technically possible to do this, but it doesn't strike me as a great idea and could put you into some difficult situations. Regarding where you say you aren't using local admin accounts, can you clarify this for me? Do you not have ANY local admin accounts on the Macs at all? That doesn't seem like a realistic scenario to me. I completely understand that at best, this might eliminate a small handful of cases where Jamf Remote is relied upon, leaving a lot still that needs to be addressed. I would be willing to bet that some of the items your techs are doing can be handled with regular policies instead of one off commands. One thing I would start with is rethinking a bit about what you really need to be pushing to your Macs over something like Jamf Remote.
