Riva On-Premise Requirements: Server, Firewall, Scalability

Riva is fully compatible with virtual and physical servers that meet the following criteria:

For initial evaluation: If this is an initial technical evaluation to confirm that Riva is compatible with your environment, you can choose to use Windows Server 2025, 2022, 2019, 2018, or 2016. The evaluation version of Riva is limited to a 5-user license.\
For full evaluation and production installations: If this is a full technical evaluation, a user acceptance test (UAT) evaluation, a pilot evaluation, or a production deployment, Windows Server 2025, 2022, 2019, and 2018 are the recommended operating systems.

Windows Server 2012 is no longer supported for recent versions of Riva.
Windows Server 2016 is supported for initial evaluation only; it is not supported for full technical evaluation, user acceptance test (UAT) evaluation, pilot evaluation, or production deployment.

Requirements for Initial 5-User Evaluations and for Production Environments with 1 to 99 Users Being Synced

Server Platform: Dedicated or Virtual Windows Server 2025, 2022, 2019, 2018.
Software Requirements: Microsoft .NET 4.8 or higher.
Processor (CPU): The latest generation of 2 GHz+ processors with a minimum of 2 cores.
Memory (RAM): 2 GB -- Reserved 512 MB for Riva (50 MB per synchronization thread) - Remaining reserved for operating system (OS).
Disk Space: 10 GB (above OS requirements) plus:
- Log files: 50 MB per week (automatically compressed roll-over);
- Per user: 50 MB for index and storage.

Requirements for Environments with 100 to 499 Users Being Synced

Server Platforms: Dedicated or Virtual Windows Server 2025, 2022, 2019, 2018.
Software Requirements: Microsoft .NET 4.8 or higher.
Processor (CPU): The latest generation of 2 GHz+ processors with a minimum of 2 cores.
Memory (RAM): 2 GB -- Reserved 512 MB for Riva (50 MB per synchronization thread) - Remaining reserved for operating system (OS).
Disk Space: 20 GB (above OS requirements) plus:
- Log files: 100 MB per week (automatically compressed roll-over);
- Per user: 50 MB for index and storage.

Requirements for Environments with 500 to 999 Users Being Synced

Virtualized: VMware, Xen, or Microsoft Hyper-V.
Server Platform: Dedicated or Virtual Windows Server 2025, 2022, 2019, 2018.
Software Requirements: Microsoft .NET 4.8 or higher.
Processor (CPU): The latest generation of 2 GHz+ processors with a minimum of 2 cores.
Memory (RAM): 2 GB -- Reserved 1.5 GB for Riva - Remaining reserved for operating system (OS).
Disk Space: 100 GB (above OS requirements) plus:
- Log files: 250 MB per week (automatically compressed roll-over);
- Per user: 50 MB for index and storage.

Requirements for Environments with 1000+ Users Being Synced

Virtualized: VMware, Xen, or Microsoft Hyper-V.
Server Platform: Dedicated or Virtual Windows Server 2025, 2022, 2019, 2018.
Software Requirements: Microsoft .NET 4.8 or higher.
Processor (CPU): The latest generation of 2 GHz+ processors with a minimum of 4 cores.
Memory (RAM): 4 GB -- Reserved 3 GB for Riva - Remaining reserved for operating system (OS).
Disk Space: 200 GB (above OS requirements).
- Log files: 500 MB per week (automatically compressed roll-over);
- Per user: 50 MB for index and storage.
(Optional.) SQL Database: Microsoft SQL Server.

Prepare IESC Settings

If Internet Explorer Enhanced Security Configuration is installed, add the following websites to the trusted sites list:

http://update.omni-ts.com/*
http://kb.rivacrmintegration.com/*
http://kb.omni-ts.com/*

Prepare Firewall Settings

The Riva server needs to communicate/connect with target email and CRM systems, and with Riva hosted support services. Organization security administrators need to confirm or adjust the Windows host system and corporate firewalls to allow for external connectivity between the Riva server and all the target systems and support services.

For a list of firewall requirements and a complete description of the Riva support resources for the "Check for Updates", "Request License", and "Request Support" wizards, see Firewall settings for Riva.

Prepare HTTP/S Proxy Settings

The Riva Manager application and the Riva CRM Agent service use proxy settings configured in the Internet Explorer browser. There are two proxy conditions to be aware of:

Proxy Requires Authentication - If the proxy server requires authentication, Riva may not be able to read the authentication user name and password from Internet Explorer. For instructions to configure the Riva server for HTTP Proxy Authentication after Riva is installed, see Riva server: Web \ HTTP proxy authentication support.
Riva server does not recognize WPAD scripts. On the Windows system hosting Riva, if Internet Explorer is configured to connect to a WPAD server, either disable that setting or configure an App.Setting that provides an alternate proxy connection.

Prepare Anti-Virus Software on the Riva Server

Anti-virus (AV) software, especially on server platforms, can interfere with the Riva CRM Agent service and other Riva executable files from operating as expected. We recommend that AV software installed on the Windows system hosting Riva be configured to:

not monitor or block network traffic between the Riva server and target systems,
not monitor or block Riva program execution, and
optionally not perform system scans on certain files in the \Riva folder structure.

For more information, see Configure anti-virus software for Riva On-Premise.

Can Existing Windows Systems Be Used for the Riva Server?

Best practice: We recommend not installing Riva on the following types of mission-critical systems:

Active Directory Domain Controllers, DNS, or DHCP servers.
Email servers.
Dedicated application servers, for example, SharePoint or SQL database servers.
CRM servers.

When a Riva server starts to sync data between CRM and email user accounts, there will be an impact on the use of system resources including:

CPU usage will increase for each user being synced concurrently.
System memory will be consumed for each user being synced concurrently.
Disk read/writes to Riva log files will increase for each user being synced concurrently and for the amount of data being synced.
Disk storage space will be consumed for Riva system log files.
Network bandwidth consumption will increase for each user being synced concurrently and for the amount of data being synced.

We recommend a dedicated Riva server or a Windows system, such as a local file or print server, that will not be negatively impacted by increased usage of local system resources. For production deployments, monitor CPU, memory, disk I/O, disk storage, and network bandwidth regularly, and adjust server resources or Riva thread counts as needed.

Riva Sync can be CPU-intensive and disk I/O-intensive because it processes and transforms data between email and CRM systems, while also using multiple databases and log files. Customers should monitor the Riva server using standard IT monitoring tools to confirm that the server has enough resources to perform its sync workload.

Recommended areas to monitor include:

CPU usage: Sustained CPU usage above 80% should be investigated. Sustained CPU usage above 90% for 10 minutes or more may indicate that too many sync threads are allocated or that the server has too few vCPUs for the configured workload.
Memory usage: Memory should generally remain around 60% to 75% utilization. If memory reaches capacity, Riva performance can deteriorate because of increased paging and operating system overhead.
Disk I/O: Monitor disk queue length. Disk I/O should normally fluctuate with sync activity. Some disk activity is expected during active sync processing, but disk I/O should not remain at 100% utilization for sustained periods. A disk queue length above 2 indicates that the system is waiting for disk operations to complete, which can reduce sync performance. A disk queue length above 5 to 10 should be considered high.
Disk storage: Monitor available disk space for Riva log files, indexes, and sync storage. Disk usage increases with the number of synced users, sync volume, and logging level.
Network bandwidth: Monitor network usage between the Riva server, email system, CRM system, and Riva hosted support services. Network consumption increases with the number of users being synced concurrently and the amount of data being synchronized.

If disk I/O becomes a bottleneck, consider splitting Riva logging and databases onto separate drives.

If CPU, memory, or disk I/O cannot be increased, reduce the demand on the Riva server by lowering the Riva policy-level or service-level thread counts. Reducing thread counts limits the amount of data that can be processed simultaneously and can reduce the number of users processed during a sync cycle.

Customers can use existing monitoring platforms such as Splunk, Datadog, or Amazon CloudWatch for EC2-hosted deployments. If no centralized monitoring platform is available, Windows Performance Monitor counters can be configured to monitor resource usage and trigger alerts.

Calculating Riva On-Premise Server Requirements for Production Scalability

For enterprise environments exceeding 1000 target CRM accounts, ensure that sufficient resources are allocated to the Windows system hosting the Riva On-Premise server. For detailed information, see Calculate Riva server requirements for scalability.