On-Premise Deployment Overview

• VMware ESXi 6.7
• VMware vSphere
• Hyper-V

• Setting Up the IP, Network and the Machine Role(s)

• Setting Up the Account and Finishing the Deployment

• Installing the Teramind Agent

• Manual/remote/silent agent install options
• Active Directory/Group Policy support
• SIEM & Project Management software integrations

Use your own infrastructure and only pay for resources you consume (i.e. CPU, storage, memory). Full control of your environment means you can provide the SLA you need.

Choose how much storage you want allocated for OCR, user data and application meta data. The nodes will communicate with the master nodes and each other automatically making storage management easier.

Deploy the entire Teramind server with a single OVA/VHD. Support for VMware ESXi and Hyper-V gives you freedom to deploy Teramind on many environments.

Control how often and when backups are taken. Teramind On-Premise supports both on-demand and scheduled backups.

Single file model for security, patch management and feature deployment. One-click deployment from the dashboard makes it easy to keep your server running smoothly.

Export data to SIEM, IDS/IPS and other threat analytics systems via syslog. Active Directory integration and REST-based API opens up possibility for coordinated security orchestration.

You control all aspects of security and compliance including firewall, SSL, VLAN, SSH tunnels, 2FA, IP whitelisting on your firewall etc. Your security measures combined with Teramind’s built-in support for HIPAA, GDPR, PCI DSS and other compliance-specific policy and rules, Teramind On-Premise is ideal for customers in government, healthcare, finance and other regulated industries.

The Teramind virtual appliance comes with a primary volume of 24 GB. This volume contains the Teramind server application and database. The size of this volume can be increased at a later point in time. 

The simplest way to add storage is from your hypervisor, by simply adding a second volume. Teramind will automatically detect, format, and mount the volume once you add it to the virtual appliance. If you use Hyper-V, this volume should be a VHDX file (not VHD).

You can also use a NAS or any filesystem over NFS, or any S3-compatible storage engine. You can contact us for configuration detail.

The size of this second volume can be estimated based on the number of sessions that will be recorded. With the default settings, for sessions with one screen doing normal work activity, you can expect approximately 1 GB per 160 hours.

You can adjust retention policies and recording preferences in monitoring settings at any time. This storage is low-access and can be on magnetic / non-SSD media.

• Microsoft Windows 7 and up (32 & 64-bit)
• Microsoft Windows Server 2012 and up
• Mac OS 10.15 (Catalina) and Mac OS 10.14 (Mojave) *

* At the moment, Teramind on Mac has limited functionalities. You can check out what features are supported here.

• Stand-alone workstation / server
• Terminal server (RDS) *
• Application / Session server
• Citrix
• VMware Horizon

* Ideally, terminal servers should have a maximum of about 30 users or less depending on the number of screens and monitoring settings. Otherwise you may have performance impact.

• Silent MSI
• Deployment via Group Policy or SCCM
• Dashboard-based silent remote installer