The Goverlan Reach Client Agent must be installed on every client machine that needs to be managed by Goverlan Reach. The agent is very small (about 15 MB), stable and secure. It will not affect system performance.
Pushing the Goverlan Reach Client on remote systems can be done in many ways depending if the remote system is within your organization or over the internet.
This article describes information about the deployment and maintenance of the Goverlan Reach Client.
The Goverlan client agent currently only support the Windows operating system. It can run on Windows XP and later versions of Windows. It supports both 32 bit and 64 bit architectures.
Client agents for other platforms are currently under development, please check with our support department for updates.
The Goverlan client agents exposes the network port 22000 by default. This port is used for client communication. All communications to the client agent are encrypted, authenticated and audited.
If a firewall exists between your machine and the remote machine, the firewall must be configured to allow the Goverlan Client Agent port communication. Upon starting, the Goverlan client agent automatically configures the local firewall to authorize communication on that port (this behavior is configurable by policies).
It is possible to change the agent ports to a value of your choice using a Group Policy Object or a Goverlan Reach Server policy. See Network Ports used by Goverlan Reach for further information.
Deploying the Agent within my Organization
Automatic Installation and Maintenance
Within your organization, the Goverlan Client Agent is automatically installed and maintained on a per-needed basis by the Goverlan Operator Console. Upon accessing a remote system, Goverlan prompts you to install the agent if the remote machine is not equipped with them, or provides you with update options if apply.
Automatic agent installation & maintenance has the following prerequisites:
- The operator must hold local administrative privileges on the remote machine. If local administrative privileges are not held, alternate credentials can be specified (See Using Alternate Credentials )
- Port 445 and the C$ \ ADMIN$ shares must be accessible (Windows Print & File Sharing.)
- The Remote Registry service or WMI Management must be enabled on the remote machine.
Pre-Installing Client Agents
In the event you wish to pre-install the Goverlan Client Agent on your machines, you can use one of the following method to push agent installation on one or more systems.
Using the Goverlan Operator Console
Within the Goverlan operator console, right-click on any computer object and select the desired Reach Client Agent action to perform.
Using the Goverlan Agent Manager
The Goverlan Agent Manager can be accessed from the Application menu of the Goverlan Reach Operator Console or the Goverlan Reach Server.
The Goverlan Agent Manager can be use to deploy, update or remove the Goverlan Client Agent on one or more remote machines. It can also be used to push some configuration to these systems.
Using an Installation Package
You can pre-install the Goverlan Client Agent via an installation package that is distributed to your machines and ran manually.
A Goverlan Client Agent installation package can be generated as an MSI or Setup program using the Goverlan Agent Manager.
Using a Goverlan Process Automation
Goverlan Client Agent can also be managed using a Goverlan Process Automation.
- Create a Goverlan Process Automation and define a computer scope
- When configuring the Process Automation Actions, select the desired task under the Goverlan Agents category of the Execute section.
See: Process Automation
In order to manage machines over the internet, the Goverlan Reach Gateway services must be enabled. Once configured, The Goverlan Reach operator console will display a new side panel named On-Demand Assist.
This panel is used to initiate On-Demand assistance sessions, or to install the Goverlan Client agent as a service, enabling unattended remote management of that node.
- Open the Goverlan Reach operator console or Goverlan Reach RC
- Open the On-Demand Assist side panel and click Send a request, then select Generate a client email.
To enable unattended installation, confirm that Enable Permanent Install Mode is activated before generating your client email
- Send the email or the web-link to the remote user
Once the remote user receives the email and runs the downloaded executable, the user will be prompted to choose an execution mode.
The remote user must then click on the provided link to download the small Goverlan Reach Client and run it. The user is then presented with the following options:
On Demand Access
On-demand access provides you with full remote management services of a computer over the internet while the session is active. Remote management services are not restricted to a remote control session, the full set of Goverlan management services can be used during an on-demand session.
In order to gain local administrative access to the machine during the assistance session, ask the remote user to enable the provide administrative access option. This option is required if you wish to handle UAC acceptance prompts.
Instruct the user to click on the Start Support Session button to initiate the remote assistance session. This will generate a session ID that you must enter in the Goverlan operator console to connect to the session.
Once the session is connected, you will be able to perform any management tasks on this node, including remote desktop access, software deployment, task management, etc.
To close a remote assistance session, the remote user must close it by clicking on the Cancel button of the session window.
To perform an unattended installation of the Goverlan Client Agents, instruct the remote user to enable the Authorize Permanent Access option then click on the Provide Unattended Access button.
Once installed, the machine automatically registers itself to the Goverlan Reach Gateway services and is available for unattented management under the External Devices section of the Goverlan Reach operator console.
External unattented nodes are configured with an Organization ID. This organization id is used to group external nodes in containers for easy browsing in the Goverlan operator console. The default organization ID is set to the Organization Name configured in the Gateway services, however it can be modified in the Goverlan Client Control Panel applet.
Goverlan Reach Client Configuration – Control Panel Applet
Once a machine is equipped with the Goverlan Reach Client Agents, a configuration control panel applet is accessible. This control panel applet can be used to review and change the configuration of the agent on the local machine.
The Goverlan Client Configuration applet can be found in the Windows Control Panel > System and Security area (or simply enter ‘Goverlan’ in the Search Control Panel field to find the applet)
Agent Network Settings
Defines the communication port used to communicate with this endpoint as well as the gateway services configuration (if enabled).
Local Desktop Access
Defines the user acceptance configuration and behavior of the agent during a remote desktop access session. For instant, the agent can be configured to prompt the local user to approve a session before it is started, or accept the session automatically and display a notification message, or disable remote desktop access entirely.
How to Globally Configure Client Settings
Client configuration, behavior and branding can be centrally configured using the Goverlan Global Policies feature of the Goverlan Reach Server. Once Global Policies are enforced, the control panel applet will not allow the modification of the client configuration.
Uninstalling the Goverlan Reach Agents
Depending on the method used to install the agent, you can remove the client agent using one of the following method:
|On-site and external unattended nodes||Use the Goverlan operator console or the Goverlan Agent Manager|
|Via installation package||Use the Windows Programs & Features|
|If you no longer have Goverlan installed||Contact our support department and we will send you an uninstaller package|