@donmontalvo
After doing some peeking at past cases with that error, it does look like it’s a permissions based error, so we’re on the right troubleshooting track.
My first question, just for verification, is does the error pop up when they initially try to control or screen share or when they try to do something after getting the remote control going?
If it’s after, what is it that they’re trying to do?
In the linked thread, it looks like they were attempting to push packages via Remote, which requires the Create privilege for Policies since deploying packages or using Casper Remote is technically a policy but instead of it being saved in the JSS it is instead never saved; it’s sort of like a “temporary” or “one off” policy in the JSS’ view.
I did notice that, without the permission of “Screen Share with Remote Computers Without Asking” it wouldn’t start until, on the remote computer, I clicked ‘Allow’ on the dialogue box that popped up. If I clicked Deny, or just let it sit for a few minutes and time out on its own, it failed.
Is it possible that’s what’s happening on your case?
We can easily check by granting that permission or, if you’d rather look at log files, it will show up in the jamf.log on the remote client; if permission was denied the jamf.log will show a message that specifically says “Permission denied by user for Auditor” (Auditor was the account I set up to mimic your Auditors’ permissions).
Amanda Wulff
JAMF Software Support
