Stay up to date on the latest product updates, customer stories, and industry news from Redpoint. Opt-in and select the topics you'd like to learn more about!
Redpoint Interaction v7.x Documentation
Redpoint Interaction v7.x Documentation
Breadcrumbs

Admin: Connecting to RPI in a SaaS environment

RPI client deployment requirements (VDI-agnostic)

Supported deployment models

  1. Local Installation (Client Laptop / Workstation)

  2. Redpoint-Hosted Virtual Desktop Infrastructure (VDI)

  3. Client-Hosted Virtual Desktop Infrastructure (VDI)

Examples: Citrix, Azure Virtual Desktop (AVD), VMware Horizon

Software requirements

General (all deployment models)

  • Windows-based environment (RPI client is Windows-native)

  • Microsoft .NET Framework 4.8 (minimum)

  • Microsoft Edge WebView2 Runtime (required)

  • RPI Client package:

    • MSI installer, or

    • Extracted portable client (Interaction.exe)

Local Installation (Client Laptop / Workstation)

  • Local administrator privileges required:

    • Initial installation

    • Dependency installation

    • Client upgrades

  • Ability to download or receive RPI client package

  • (Optional) Microsoft Excel (for reporting features)

Redpoint-hosted VDI

  • VDI access client or browser required on end-user device

  • No local RPI installation required

  • RPI client and prerequisites managed by Redpoint

Client-hosted VDI

  • Install prerequisites on VDI session hosts:

    • Microsoft Edge WebView2 Runtime

    • .NET Desktop Runtime

    • .NET Framework 4.8 or higher

  • Deploy RPI client

  • Ensure persistence:

    • Installed on base/golden image

    • Available across all session hosts

Networking requirements

All deployment models

  • Outbound HTTPS connectivity over Port 443

  • DNS resolution to Redpoint-hosted endpoints

  • Stable internet connectivity

Local & client-hosted VDI

  • Provide:

    • Public outbound IP address(es)

    • VPN source IP(s), if applicable

  • Connectivity must originate from:

    • Client machine (Local), or

    • VDI session host subnet(s)

Redpoint-hosted VDI

  • Networking managed within Redpoint environment

  • No client-side configuration required

Client side

Egress routing

  • Allow outbound traffic to the internet over Port 443 (HTTPS)

  • Applies to:

    • Local machines

    • VDI session hosts

Optional (feature-dependent)

  • Additional endpoints may be required:

    • Email providers (e.g., SendGrid)

    • CRM platforms (e.g., Salesforce)

Authentication / security

  • Confirm authentication approach:

    • Native RPI authentication

    • Entra ID / Okta (OIDC/SAML)

    • VPN-based access (if required)

  • Ensure:

    • SSL inspection does not break HTTPS traffic

    • Proxy allows outbound access to Redpoint endpoints

    • Authentication flows work within VDI sessions

Access & permissions

All deployments

  • Valid RPI account required before login

Local installation

  • Users must:

    • Have installation or execution rights

    • Be able to run Interaction.exe

VDI (any platform)

  • Users must:

    • Have access to the published RPI application

    • Be assigned to the appropriate user group

    • Have permission to launch applications in the VDI environment

VDI-specific considerations

  • Ensure VDI session hosts:

    • Can resolve and reach Redpoint endpoints

    • Have consistent network routing

  • Validate:

    • Configuration files (Interaction.exe.config) are consistent across sessions

    • No profile redirection or layering issues affect configuration

  • Confirm:

    • User sessions maintain required permissions and environment variables

    • Performance meets expectations in the virtualized environment

RPI client update procedures

This section outlines the available methods for updating the RPI Client following an upgrade.

Option 1: Automatic client update

RPI supports automatic client application updates for environments where users have sufficient permissions.

Key notes:

  • Applicable for local RPI deployments

  • Requires local administrator rights on the user machine

  • Client automatically updates when launching RPI (based on server configuration)

  • Recommended for environments where users can perform installations

Option 2: Manual client update

For users without administrative access or in environments where automatic updates are not enabled, the client can be updated manually.

Process:

  1. After each RPI upgrade, the Operations Team / Service Desk will provide a client download link (zipped package).

  2. Download and extract the updated client files.

  3. Replace the existing RPI Client files with the new version: ensure files are replaced, not merged or partially overwritten.

Alternative for non-admin users:

  • If the user does not have admin privileges:

    • Extract the client files to a location such as the Desktop

    • Run the client from this location (no installation required)

Key notes:

  • Manual updates are required after every RPI upgrade

  • Ensure users always use the latest client version to avoid compatibility issues

  • This method is commonly used for VDI environments or restricted systems

Best practice recommendation

  • Use Automatic Updates whenever possible for consistency and reduced operational overhead

  • Use Manual Updates for:

    • VDI environments

    • Restricted user access scenarios

    • Controlled rollout situations

Notes

  • Non-Windows endpoints (e.g., Mac) require access via VDI or remote desktop solution

  • RPI Client is installed per machine or per VDI image