You can use the Automox Remote Control Module (RCM) to remotely connect to and take control of Windows and macOS devices in your Automox console. The application for macOS requires the remote user to grant permissions to the application, which is described here.
Prerequisites:
To remotely connect to devices, you must have zone administrator, zone operator, or helpdesk operator permissions for the zone where the device is located.
Your zone is under a “Complete” plan that includes RCM. Contact your customer support representative for more information.
To configure consent notifications, you must have global administrator permissions.
See also how to enable Automox remote control permission using MDM: Deploying Automox Remote Control Permissions Configuration Profile via Jamf Pro.
About a Remote Session With macOS
When a remote session is initiated with a macOS device, the remote user must grant permissions for Screen Recordings and Accessibility. The module prompts the user to open the System Settings dialog window with pre-populated settings for the Automox Remote Control application. The user then needs to authenticate (enter a password or use TouchID) and click the toggle to enable these permissions.
Starting a macOS Remote Session and Granting Permissions
The local administrator initiates a remote session.
Refer to Starting a Remote Session.
If consent is enabled on the device details page, the remote user is prompted to grant consent.
The remote user sees a macOS Screen Recording prompt, which automatically shows up when the session connects.
The remote user clicks Open System Settings and the System Settings → Privacy & Security → Screen Recording window opens, where it is pre-populated with the application Automox Remote Control.
The user clicks the toggle to enable Screen Recording, and is prompted for a password (or TouchID, if enabled).
After entering the password to enable Screen Recording, a macOS prompt informs the user that they might need to quit and reopen the application. However, that step is not necessary. The user can click Later.
Next, when the session connects, the administrator sees the remote desktop. As soon as the administrator mouses over or clicks on the blank desktop, the remote user sees a macOS Accessibility Access prompt.
The remote user clicks Open System Settings, and the System Settings → Privacy & Security → Accessibility window opens, where it is pre-populated with the application Automox Remote Control.
The remote user clicks the toggle to enable Accessibility. The password might need to be entered again. However, if the System Settings window is kept open, the user should not need to re-enter their password here, having already done so for Screen Recording.
This concludes the permission-granting experience. The remote user is not directly notified.
When Screen Recording is granted, the administrator can see the remote user screen contents.
When Accessibility is granted, the administrator has full control.
The remote user will not need to go through this experience on subsequent Remote Control sessions, unless the permissions are disabled.
Refer to Remote Control Module for details about configuring consent, using controls, status messages, and error notifications.
Manually Granting Permissions
A remote user can grant permissions outside of the context of a Remote Control session at any time. Note: This is not the standard workflow. This manual process might be useful if a user not at their device at the time that a session is initiated.
Screen Recording
Open System Settings (Preferences) → Privacy & Security → Screen Recording
Select +
You will be prompted for your password (or TouchID, if enabled).
Select Automox Remote Control in the Applications folder of your device (Full Path:
/Applications/Automox Remote Control)
Accessibility
Open System Settings (Preferences) → Privacy & Security → Accessibility
Select +
See previous example under Screen Recording
Select Automox Remote Control in the Applications folder of your device (Full Path:
/Applications/Automox Remote Control)See previous example under Screen Recording
Comments
0 comments
Please sign in to leave a comment.