Cloud Connector Installation Guide
This document outlines the requirements and steps for installing the Cloud Connector on a Windows machine.
Prerequisites
Windows Server
The Cloud Connector server MUST be accessible from the internet.
Can run in your DMZ or on your internal network (externally accessible via NAT) depending on your network layout and preferences.
The Cloud Connector MUST be installed with administrator privileges
Client ID (UUID) and RTVision Cloud Site Admin Credentials
If these haven’t yet been provided via email, please contact your Implementations contact or RTVision Support.
Network Access
Inbound access
The Cloud Connector MUST have a public IP and port accessible from the internet.
If you’d like to limit inbound access, please contact your Account Manager or RTVision Support to provide the source IPs. We will need to ensure your agency is on the contact list should the IPs change. (In rare scenarios, the IPs could be forced to change).
Outbound access
The Cloud Connector MUST make outbound HTTPS requests to 2 destinations.
If you must restrict outbound access, please contact your Implementations contact or RTVision Support for the current list of destination IPs.
Internal network access to all required internal integrations.
Example: If your Cloud Connector server is internal @ 192.168.1.50, and you have a MSSQL based integration @ 192.168.1.100, you would need a firewall rule of:
Source: 192.168.1.50
Destination: 192.168.1.100
Protocol: TCP
Port: 1433
So that the Cloud Connector service can access your MSSQL database.
Installation Steps
Obtain the Installer
Download the Cloud Connector installer (.exe.zip) from here.
Unzip the file to get the installer.exe
You may encounter an “untrusted publisher” warning when running the executable. Bypass this prompt if it appears*
Run the Installer
The installer will prompt to run as administrator if not already
Configure the Connector
Name: Provide a name (e.g.
cc1).Client ID: Paste the UUID from your email.
IP and Port:
Specify the server IP and port for the Cloud Connector service to listen on.
If the server is assigned a private IP, also provide the public IP and port that it can be accessed from externally via NAT.
TCP/443 is recommended unless your server is already running a web server on that port.
Once all required fields are valid, the Next button appears (bottom-right corner).
Authorize Each Site
On the subsequent screen, click Authorize for each site.
A set of options appears, letting you to navigate to the site by either:
Copying the site URL
Opening in browser
Scanning a QR code
Log in to each site with the admin credentials emailed alongside the Client ID, and authorize access.
Install the service
Once at least one site is authorized, the Next button reappears.
Optionally enter in the account name and password for the service to use
if no account name or password is entered then the default SYSTEM account will be used
If using a group managed service account Group Managed Service Accounts overview
enter in the account name only
should look something like
"CONTOSO\\MyServiceAccount$"where CONTOSO is the domain that has the service account and then the slashes with the name of the account. Finally the entered account name has to end with a$
Press install
If the follow screen appears and status is running then service installed successfully
Note: The “untrusted publisher” prompt is temporary until the installer is signed with an EV certificate that is working on to be obtained.
Setup Windows Firewall (If enabled)
PowerShell (as an administrator)
New-NetFirewallRule -DisplayName "RTVisionCloudConnector" -Action Allow -Direction Inbound -Protocol TCP -LocalPort <listen port>
Install ODBC Drivers (If Needed)
If a database connection is required, install a compatible ODBC driver (e.g., for SQL Server):
Inform us when completed
RTVision staff will configure your integrations to use the Cloud Connector to complete the setup.