1. Home
  2. Goverlan Reach & MDM User Guides
  3. Centralizing the Configuration of Goverlan

Centralizing the Configuration of Goverlan

The configuration of the Goverlan Reach solution, both on the operator side and on the client side, can be centrally configured and deployed across your network.

Using a central configuration, you will be able to:

  • Define the settings of the Goverlan Reach operator console and client agent (e.g., Database settings, communication port, etc.)
  • Restrict the features accessible to Goverlan Reach operators.
  • Define the behavior of Goverlan Client Agent (e.g., Acceptance prompt for a remote desktop access session.)
  • Customize the text and images of the user interface on the client side.

Central Configuration & Auditing via the Goverlan Reach Server

The recommended method to centrally configure the Goverlan solution is to implement a Goverlan Reach Server. The Goverlan Reach Server is included in your Goverlan licenses and doesn’t require a separate fee.

Simply install the Goverlan Reach Server on a Windows Server 2008 R2 or later OS and advertise its existence via a DNS Service Location record or a GPO. Once implemented, use the Goverlan Global Policies features to control the configuration and behavior of Goverlan, and the Goverlan Auditing feature to audit all operator actions across your organization.

See: Goverlan Reach Server

Central Configuration via a Group Policy Object

Goverlan settings can also be centrally configured and distributed via a Group Policy Object. This method is less secure than the Goverlan Reach Server since parameters can be modified post distribution and it doesn’t allow for centralized auditing. However, it is still an easy way to configure Goverlan globally.

A Goverlan GPO can also be used as a back up to the Goverlan Reach Server in the event this one becomes unavailable.

See: Global Goverlan Configuration via a GPO


Updated on June 17, 2020

Related Articles