Goverlan Reach RC makes remote IT support easy. Start helping users by quickly accessing their machines remotely.
Connecting to a Remote System Within My Organization
Connecting to a machine within your organization is very simple:
- Click on the Connect button (or choose Other Options to select an access protocol)
- Specify a user name or a machine name
- Click on Ok
A successful connection has the following prerequisites:
- The remote system must be equipped with the Goverlan Client Agents, however these agents are automatically installed if needed. The remote installation of the Goverlan Agents requires local administrative privileges on the remote machine.
- By default, the technician must hold local administrative privileges on the remote machine to initiate a remote control session (this is configurable). If the technical doesn’t hold local admin privileges, Goverlan automatically prompts for alternate credentials.
Choosing the Access Protocol
Goverlan Reach RC supports multiple access protocols to connect to a wide array of devices:
|Goverlan Reach Protocol (GRC)||Goverlan proprietary access protocol. Allows you to remotely access the screen, keyboard and mouse of a remote machine as if you were physically there.
Supports: Multiple monitors / RDS & Citrix session shadowing / Audio Redirection / UAC Prompt and more…
|Microsoft RDP||Open an RDP session on a remote Windows machine.|
|VNC||Remote desktop access a Windows, Linux, MacOS X, or any other operating system that supports the VNC Server.|
|Intel® vPro™ KVM||Remote Control powered-off machines and start them, or boot to BIOS (only available for Intel vPro Ready machines)|
|Windows Remote Command Prompt||Access the command prompt of the remote system without interrupting the remote user, and execute commands.|
|Telnet / SSH||Open a telnet or SSH session on any devices.|
Clicking on the main Connect button defaults to the Goverlan Reach Protocol. To select another access protocol, click on the Other Options bellow and click on the desired protocol.
Connecting via a System Name
To connect to a system via its name, make sure the Connect To object type is configured to Computer, then specify the computer’s FQDN, shortname or IP address in the Connect To field. It is recommended to use a fully qualified domain name when connecting to a system.
Searching for System Names
If you do not know the exact name of a computer and this one is part of your active directory, you can have Goverlan search for it using one of the following method
- Use one or more wild card in the name – For instance, entering NY-SRV-* and clicking on Connect returns all computer records that starts with NY-SRV-. Entering *-SRV-* and clicking on Connect returns all computer records that includes -SRV- in its name.
- Enter a partial computer name in the Connect To field and click on the search button next to it.
Upon a search, Goverlan presents you with the list of found computer records:
Select the desired computer and click on Set focus.
Connecting via a User Name
To connect to a system via its logged-in user name, make sure the Connect To object type is configured to User, then specify the user name in the Connect To field.
The provided user name information must be in one of the following form:
- User ID – For instance: awoods or DEMO\awoods or firstname.lastname@example.org
- The start string of a full name – For instance: Arron W
- A string with wild cards – For instance: *Woo*
Once you click on Connect, Goverlan searches active directory for user account records that matches the information provided. Once the desired user selected, Goverlan searches for the logged-in workstations of that users and presents you with a machine selection window in the events more than one login session was detected.
Sending Control + Alt + Delete
You can customize the Ctrl Alt Del hotkey combination under Application –> General Settings –> User Interface.
Using the Lock Screen button
Use the Lock Screen button on the session tab or in the main application ribbon bar.
Connecting to a Remote System Over the Internet
Using Goverlan, you can manage systems over the internet, on-demand or unattended.
A Goverlan Reach Server with Goverlan Reach Gateway Services must be configured for this feature to function. Refer to External Device Management for more in-depth information.
Connecting to Multiple Systems
Goverlan Reach RC allows you to connect to as many machine as needed. Each connection is hosted within its own tab for easy switching. You can also select the All Views tab to monitor the screen activity of all your connections simultaneously.
Adding a Connection Tab
To add a connection tab, click on the (+) button located on the right of your existing tabs. Then initiate a new connection from this tab.
Using the My Devices Panel
To open a connection on 2 or more machines:
- Open your My Devices panel
- Expand a machine container
- Right click on one or more computer objects (or right-click on the parent container)
- Select Open Session In Group and select the desired access protocol
To open a connection on a machine in a new tab:
- Open your My Devices panel
- Expand a machine container
- Right click on one machine
- Select Open Session In New Window and select the desired access protocol
Saving and Loading Connection Layouts
The Goverlan Layouts feature allows you to save your connected session information to a file so that it can be reloaded at a later time. Upon reloading, all sessions are automatically reconnected in the order and position you saved them.
Layout controls can be found in the ribbon bar of the Controls tab:
- Saving a layout file – Once you have connected all your sessions, and positioned the Goverlan interface the way you want it to be remembered, click on the Save Layout button, and save the layout file to your disk. You can now close Goverlan.
- Loading a layout file – Open Goverlan, click on the Load Layout button, open the layout file. Goverlan then reestablishes all connections previously saved.
How to Control What Happens on the Client Machine
By default, once a remote control session is authenticated (as a reminder, a technician must hold local admin privileges on a remote machine to initiate a remote control session, but this is configurable), the session is started without further user approval. The remote user sees a notification banner while the session is active:
However, this is fully configurable. You can configure your client machines to prompt the local user to approve a session before it starts, disable remote control access on some other machines, or remove all visual notification on the users’ side (stealth mode). You can configure additional user notification such as email, or post-session user notification.
You can also fully brand the notification messages on the client side by modifying the text or images to your own.
For further information, see: Goverlan Reach RC Client Settings