SOTI Connect System Requirements

To install SOTI Connect, your system must meet the following minimum hardware, software, and network requirements.

On-Premise Installation of Complete System

This section outlines the essential system requirements for installing and operating SOTI Connect in an on-premises environment.

Component Requirements
Operating Systems
  • Windows 10
  • Windows 11
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022
Note: Windows 10 should have at least the Anniversary update. SOTI recommends Windows 10 for testing and non-production environments.
Hardware Requirements
  • Minimum dual-core processor
  • Minimum 8 GB RAM
User Privileges Administrator privileges required
Required Software
  • .NET Framework 4.7.2
  • .NET 8 Runtime
  • ASP.NET Core Runtime 8
Installer Dependencies
  • UI Installer: .NET 8 Desktop Runtime (includes .NET 8 Runtime) and ASP.NET Core Runtime 8
  • Silent Installer: .NET 8 Runtime and ASP.NET Core Runtime 8
    Troubleshooting: If installing SOTI Connect using SilentInstaller.exe and .NET 8 is not detected on your system, the installation process ends without displaying an error message. To resolve this issue, install .NET 8 on your system.
SQL Server
  • SQL Server 2022
    Note: Tests indicate minimal performance benefits for often used queries when using SQL Server 2022, and significant drawbacks for some queries. Although SQL Server 2022 is compatible with SOTI Connect, SOTI recommends continuing with SQL Server 2019, which remains current and within its support period.
    Note: SOTI is continuously evaluating SQL Server 2022 for future improvements and optimizations.
  • SQL Server 2019 and SQL Server 2019 Express
    Important: SOTI recommends using SQL Server 2019 with SOTI Connect.
  • SQL Server 2017 and SQL Server 2017 Express
Note: Set data truncation settings to 6GB at most for environments using SQL Express for smooth operation.
SQL Permissions A SQL Server user with permissions to create, modify, and drop databases. Specific permissions depend on installation and operating scenarios:
  • Standard working operations: Requires db_owner privilege.
  • During new install or upgrade of SOTI Connect: Requires Sysadmin privilege. The SA account is a super admin account with all the needed permissions for any scenario.
  • Service running as local system and DB installed on the same server: The computer runs the service under the Local System > NT AUTHORITY\System account. This needs Sysadmin permissions during an upgrade.
  • Service running as local system and the DB installed on a remote server: The service runs under the account MachineName$, defined as domainname\computername. Using Microsoft SQL Server, add the user or the group containing the user to the db_owner role.
  • Service running as a service account: Make sure the user account (for example, samplecompany/ConnectMDM) has the required permissions in the DB to run the service.
Note: SOTI recommends installing the databases on a separate machine (server or VM).
SOTI Connect Installer Download the SOTI Connect Installer.
Firewall and Port Requirements The IT domain policies should enable a local administrator to open ports.

If using an MQTT protocol, use a commercial-grade MQTT broker such as HiveMQ. SOTI recommends installing HiveMQ on a separate machine for optimal performance.
Required Network Ports A full installation of SOTI Connect uses many communication ports. The installer adds rules to the Windows Firewall as necessary. For more network security, you may need to open the following ports for SOTI Connect to communicate:
  • 443: Web Access
  • 1234: Logging Service
  • 1433: SQL Server Engine
  • 1883: MQTT Server
  • 4610: Simulator—Homecomfort
  • 4611: Simulator—Hue
  • 4646: File Store
  • 4649: Management Server
  • 4650: File Store Service
  • 4651: Management Server Cluster
  • 5551: WebHook Receiver
  • 8883: MQTT Broker
For more information on SOTI Connect network port requirements, see Network Ports.
Note: SOTI Connect and SOTI MobiControl both require the use of port 443. Due to this, you cannot install both products on the same machine.
SOTI Services
SOTI Services includes the Activation Service, the Notification Service, and the Location Service. These services provide your SOTI Connect deployment with:
  • Updates for licenses
  • Updates for device type definitions
  • Device location features within SOTI Connect

Access all SOTI Services using HTTPS on port 443. Whitelist the following fully qualified domain names and IP addresses with your firewall to enable unrestricted communication between your SOTI Connect installation and the SOTI data center.

Note: To download or update device type definitions, the SOTI Connect management service requires access to the following URL endpoints: notificationservice.soti.net and downloads.soti.net.
IP Addresses to Whitelist SOTI Services are load-balanced across the following IP addresses:
13.248.157.19
54.208.149.103
54.208.194.169
54.209.62.205
54.209.186.178
54.209.186.251
54.209.207.237
75.2.25.8
76.223.23.230
99.83.149.241
Browser Support Below are the supported browsers for using the SOTI Connect user console. SOTI recommends that you use the latest version of the browser.
  • Google Chrome
  • Microsoft Edge
Note: SOTI Connect supports resolutions up to 960 x 720. Although the supported browsers support the use of tablets and smart phones, The SOTI Connect UI is not optimized for these devices.
Certified Device List

To view the supported devices, please refer to the Certified Device List for SOTI Connect.

If you do not find the device you are looking for, please contact your SOTI Account Manager or SOTI.

Optimizing your SOTI Connect Environment

SOTI recommends the following practices to make sure your SOTI Connect environment is optimally configured:

  • Schedule antivirus and malware scans on the virtual machine (VM) during periods of low system load to minimize performance impact.
  • For deployments managing over 10,000 devices, SOTI recommends upgrading to an environment equivalent to an Azure B4MS instance.

    All-in-One Configuration

    Use the table below as a reference to configure your All-in-One SOTI Connect 2025.0 deployment:

    Devices Azure Instance Type SQL Edition Data Truncation HiveMQ Heap Size Queue Size
    Up to 10K B2MS SQL Server 2019 Express Default 4 GB 80K max
    10K—50K B4MS SQL Server 2019 Enterprise or Developer 2x default 8 GB 200K max
    Note: When device check-in and file download occur simultaneously, the system must handle no more than 10,000 devices and perform no more than 2,500 downloads concurrently. The file size is not relevant.
    HiveMQ Specific Configuration for SOTI Connect 2025.0
    • HiveMQ Version: 2023.8
    • Java Version: JDK 21.0.1
    • Heap Size Allocation: Set to 50% of available RAM
    • Set "JAVA_OPTS=-Xmx4g %JAVA_OPTS%" for the run.bat file under C:\hivemq .
    • Set the <max-queue-size> to 4 times the number of devices supported on HiveMQ.
    SQL Server Configuration for SOTI Connect 2025.0
    • Data, log, and TempDB files should reside on separate drives.
      • All drives must use Premium SSD storage.
      • TempDb: Located on ephemeral storage.
      • Data Disk: Enable Read Caching.
      • Log Files: Disable Caching.
      • No compression enabled on any of the SQL drives.
    • Use a dedicated drive for the Operation System.
    • Max memory set to 50% of the VM RAM size.
    • Min memory set to 25% of VM RAM size.
    • Recovery Model: Simple
    • Cost Threshold for Parallelism: 50
    • Max Degree of Parallelism: 2

Data Truncation and Archival Settings Recommendation

  • For B2MS instance (default) SQL disk size recommended: 16 GB

    B2MS archival settings

  • For B4MS (2x default) SQL disk size recommended: 32 GB

    B4MS archival settings

  • For distributed instance (4x default) SQL disk size recommended: 126 GB

    Distributed instance archival setting

MS App Configuration Recommendation

  • For B2MS and B4MS set capacityThresholdValue: 100, detachMinAmountValue: 50 and DbSyncRetriesCount: 0
  • For distributed instance set capacityThresholdValue: 800, detachMinAmountValue: 400 and DbSyncRetriesCount: 0

Database Size and Disk Space Requirements for Storing One Day of Data for Rules History and Device State History

Topology Rule History DB Size Rule History MDF File Size Device History DB Size Device History MDF File Size Total Disk Space Used
B2MS 2 GB 2.5 GB 8GB 8.5 GB 18.1 GB
B4MS 4 GB 7 GB 9GB 9.3 GB 42 GB
Distributed 10 GB 14.6 GB 24GB 25 GB 50 GB for data and 6 GB for logs