You can use the Automox Remote Control Module (RCM) to remotely connect to and take control of devices in your Automox console. This is available for Windows and macOS devices. You can copy and paste text between devices engaged in the remote session, configure remote user consent notifications, and adjust for multiple monitors on the remote Windows device.
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.
The following topics are described here:
- Starting a Remote Session (Windows)
- Starting a Remote Session (macOS)
- Configuring Consent Notification
- Disconnecting a remote session
- Details of the Remote Control Session
- Status Messages
- Error Notifications
- Related Topics
Starting a Remote Session (Windows)
Follow these steps to create a remote connection to a Windows device in your zone.
Note: If a device is disconnected, it is not possible to use remote control.
Start session from the Actions menu
Start session from the Device Details page
From the Automox console, login to the zone where the device that you want to create a remote connection to is located.
There are two ways to start a remote control session:
On the Devices page, find the device that you want to connect to. Click the Actions menu.
You can also open the Device Details page to start a session.
If your zone is under a Complete plan with RCM, the Remote Control button is available at the top of the device details page. When the button is grayed out, you either do not have the required plan or the permissions to use this feature.
Click Remote Control.
Depending on the settings for consent notification for the device, the remote user may or may not get a pop-up for consent. See the Consent Notification section for more details.
A separate browser window opens. The remote control module is automatically installed as part of the connection process.
Your remote control session has started.
Starting a Remote Session (macOS)
The steps to create a remote connection to a macOS device in your zone include additional prompts to enable required settings. These are described in detail in Remote Control Module for macOS.
Additional requirements for starting a remote session to a macOS device:
The remote user must enable the Screen Recording and Accessibility privacy settings.
With macOS, the administrator of the remote session can only zoom and scroll on a single monitor. The remote user must set the appropriate display as the primary monitor. See the macOS User Guide for details.
Configuring Consent Notification
By default, all devices require consent by the remote user before a remote session can be established. This requirement can be configured by global administrators, as described later in this section.
A consent notification allows remote users the option to accept or deny a remote connection with the administrator.
A consent notification empowers the remote user to decide if they want the administrator to proceed with the connection request.
If the remote user clicks Proceed, the remote control module establishes a secure connection between the remote and admin devices.
If the remote user clicks Cancel, the remote control module stops trying to establish a connection between the remote and admin devices.
By default, consent is required to remotely connect to any device.
Global Administrators can decide which devices need consent from the remote user before establishing the remote session. This can be configured for individual devices from the Device Details page, or in a bulk action for multiple devices from the Devices page.
Only Global Administrators can make changes to the consent settings.
Configuring consent for an individual device
To configure the consent required settings, follow these steps:
Identify the device that you need consent required for.
Go to the device details page of this device.
Ensure that the toggle is switched to the off (left) position.
To bypass consent required settings, follow these steps:
Identify the device that you want to exclude from the consent requirement. The remote user is not asked for consent to establish a connection.
Go to the device details page of this device.
Ensure the toggle is switched to the on (right) position.
Configuring consent for multiple devices (bulk update)
To configure the consent settings for multiple devices, follow these steps:
From the Devices page, select the checkboxes for the devices that you want to configure consent for.
You can select up to 500 devices for this setting.
Note: The RCM is only available on Windows and macOS devices. If you select any Linux-based device, you will be prompted to modify your selection.
Select Actions → Configure Remote Control.
From the Remote Control Configuration window, select how you want to configure the selected devices:
Require consent for the selected devices. This is the default setting that requires consent from the selected devices.
Do not require consent for the selected devices. This setting will bypass the consent requirement for the selected devices. Users will not be asked for consent to establish a connection.
Apply your setting.
Disconnecting a remote session
To disconnect from the remote session, click Disconnect or close the browser window. A notification confirms that the session has ended.
Details of the Remote Control Session
The following features are available within a remote session.
Remote Session Symbols
The green indicator shows the connection status.
Click the disconnect symbol to end the session, or close the browser.
Copy and paste text between the remote device and your local device. (See Using the Shared Clipboard)
Click the Special Key Command button to access the shortcut for Ctrl+Alt+Del to open the Windows Task Manager. You can also use modifier keys.
Adjust Size/Zoom option. Refer to the Zooming and Scrolling description for details.
Enter and exit full screen mode
Using the Shared Clipboard
In general, when you have an active remote session, you can copy and paste directly from your device to the remote device, without using the shared clipboard. The shared clipboard is used to copy and paste text to and from the remote device, and is a requirement when using the Firefox browser.
In addition, with the shared clipboard you can enable individual keystrokes to safely send sensitive text to the remote device while keeping it hidden from the remote user.
Copying from the administrator device to the remote device:
On your Administrator (local) device highlight and copy the text that you want to send to the remote device.
Click the clipboard icon.
Paste text in the Shared Clipboard field.
When you perform a paste operation on the remote device desktop, you will paste the copied text.
Copying from the remote device to the administrator device:
On the remote device, highlight and copy the text that you want to send to the administrator device.
Click the clipboard icon.
The text appears in the Shared Clipboard field. When you perform a paste operation on the administrator device, you will paste the copied text.
Sending text using the individual keystrokes option
You can copy and paste sensitive text by enabling individual keystrokes.
When you are connected to the remote device, make sure the field where the text should be entered is selected.
On your Administrator device, click the clipboard icon.
Select the Send text as individual strokes checkbox.
Enter the text in the Shared Clipboard field. Text entered is only visible on the administrator (local) device. The text is pasted in the selected field on the remote device hidden from the remote user.
Using Special Key Commands
The special key command button enables you to access shortcuts and modifier keys.
To open the Windows Task Manager, click Ctrl + Alt + Del
For remote devices running Windows, the available modifier keys include:
Ctrl or Control
Win or Windows logo
Alt or Alternate
For remote devices running macOS, the available modifier keys include:
To use a modifier, select the corresponding button. Then a message appears below to let you know you can then use the keys on your keyboard for further action. Your keystroke is sent to the remote device along with your selected modifier key(s).
For example: If you select the Windows modifier key and then press the X key on your physical keyboard, the remote device will receive the Windows + X key combination (this key combination opens the Quick Link menu in the Windows operating system). For other key combinations, refer to Microsoft support documentation.
Click to view: Example of a remote session
The following is a list of Remote Control connection status messages and meanings.
Automox is authenticating with the Remote Control API.
During this time, dependencies and session packages are installed on the remote device.
Asking Remote User for Permission
When consent is required for the device, this status indicates that a prompt has been shown to the remote user asking for consent to proceed with the remote control session.
This status displays for a brief moment to indicate that consent was provided by the remote device’s user.
Opening Secure Tunnel
Waiting for a VNC server to become available using web socket tunnel.
The VNC connection is being established.
The VNC connection is active
Either the VNC or Remote Control API web socket connections are closed
The RCM signals that it is closing the tunnel. (In this case, the administrative user did not click Disconnect.)
Error Notification Message
“Error - Remote Control setup failed, try again later.”
The CloudFlare tunnel failed to open
“Error - Unable to connect to a Remote Control session, try again later.”
The VNC server connection failed
“Error - Unauthorized to start a Remote Control session.”
“There is either no active user or the user did not grant permission for the remote session.”
The device is configured to required consent from the remote user but that consent was not provided
Article is closed for comments.