EV Reach Console - Configuration - Getting Started

Last modified on 2023/07/12 14:02

EV Reach can be used from day one without further configuration. However additional options and extended services are available. This article describes everything you need to know for a successful integration within your environment.

Centralized Configuration of EV Reach

EV Reach includes a broad set of configuration and customizations that can be applied to the operator side and client side. For instance, you can control the user acceptance prompt of a remote control session, or configure the database settings of the operator console.

For large environments, these settings can be centrally configured and globally distributed across your organization.

See Find out more

Team Collaboration

If multiple operators are using EV Reach, team collaboration should be enabled to allow:

  • Sharing of inventory information
  • Sharing or Enforcing of EV Reach Configuration Objects (e.g., Software packages, scripts, etc.)

See Find out more

Managing Systems Over the Internet

The default implementation of EV Reach only allows the support and management of users and machines that are within your organization or connected to your organization via a VPN.

However, it is possible to manage systems over the internet, on-demand or unattended. To do so, you must implement a EV Reach Server and enable the EV Reach Gateway Service.

Once EV Reach Gateway Services have been configured, you will be able to remotely access machines over the internet. 

The EV Reach Client Agents

The management of remote systems requires them to be equipped with the EV Reach Client Agents. The EV Reach Client Agent is automatically installed and maintained by EV Reach on machines within your organization. Other deployment options are available.

See Find out more

Detecting User's Machines using fastConnect

EV Reach can identify the logged-in workstations of your users in real-time. A great feature to get to your user’s machines quickly, without prompting the remote user for any information. However, the detection of logged-in workstations may not work upon initial installation of EV Reach as it has a couple of prerequisites.

See Find out more

Active Directory Integration and Multiple Forest Support

EV Reach automatically detects the Active Directory hierarchy available on the operator's machine and allows the browsing, search, and management of its objects. If EV Reach is installed on a stand-alone machine, or if multiple Active Directory Forests exist, you can configure EV Reach to bind to an individual AD hierarchy using the EV Reach AD Forest Selector.

See Find out more

EV Reach can be used from day one without further configuration. However additional options and extended services are available. This article describes everything you need to know for a successful integration within your environment.

Remote Control Authorization & Authentication

  • By default, only users holding local administrative privileges on a remote machine are authorized to initiate a remote control session (to grant access to non-local admins, see Configuring Authorization).
  • EV Reach automatically uses your credentials when authenticating to the remote machine. If you are executing a task that requires privileges higher than those you hold, EV Reach will automatically prompt you for alternate credentials EV Reach Credential Manager.

Auditing

All actions performed by a EV Reach operator are audited. The default implementation records audit traces in the Windows Event Application Log, however, audits can be centralized using the EV Reach Server.

See Find out more

Branding and Configuring EV Reach Client Agent Behavior

  • Client Side behaviors are fully configurable. By default, an authenticated remote control request is automatically authorized and a visual notification banner is displayed. You can configure other behaviors to meet company guidelines and requirements. (See Customizing EV Reach Client Agent Behavior)
  • Most EV Reach user interface elements displayed on your client machines can be branded with your own text and images. (See Custom Branding)

Smart Card Redirection and FIPS 201 compliance

EV Reach RC will allow users to supply smart card credentials to a remote system that is FIPS 201 compliant. EV Reach supports both T0 and T1 (PIV, Common Access Card, etc...) protocols and will work with any PKI compliant infrastructure using smart cards.

EV Reach RC accomplishes this by using the EV Reach Smart Card Reader Driver on the remote machine. This driver and the EV Reach Client Agent must be installed on the remote system before any smart card authentication can be used.

See Find out more

Tags:
Powered by XWiki © EasyVista 2024