System Requirements

On-Premise Installation of Complete System

• Supported Windows versions:
  • 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.
• Minimum dual-core processor with 8GB of RAM
• Administrator privileges
• .NET Framework 4.7.2
• .NET8 Runtime and ASP.NET Core Runtime 8

  Required Dependencies

  Installer	Dependency
  UI Installer	.NET 8 Desktop Runtime (includes .NET8 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 2017, SQL Server 2017 Express, SQL Server 2019, SQL Server 2019 Express and SQL Server 2022
  Important: SOTI recommends using SQL Server 2019 with SOTI Connect.
  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.
• 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, which 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.
• SOTI Connect installation package.

• 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.

SOTI recommends installing the databases on a separate machine (server or VM).

Network Security for the Complete Installation

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:

For more information on SOTI Connect network port requirements, see Network Ports.

Supported Browsers

• Google Chrome
• Microsoft Edge

SOTI Services

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.

SOTI Services are load-balanced across the following IP addresses:

Optimizing your SOTI Connect Environment

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

• Schedule the antivirus/malware scan on the VM to run only during periods of low system load.
• For instances expected to manage over 10,000 devices, SOTI recommends upgrading to a B4MS instance. Use the table below as a reference to configure your All-in-One SOTI Connect environment:

  Devices	Instance Type	SQL Edition	Data Truncation	HiveMQ Heap Size	Queue Size
  10K	B2MS	SQL Express 2019	Default	4GB	80K max
  10-50K	B4MS	SQL Server 2019 Developer	2x default	8GB	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
  • Heap size configuration: 50% of 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 by the hive.
  SQL Server Specific Configuration for SOTI Connect 2025.0

  • Data, log and Tempdb files are placed on separate drives
    • All the disks are of premium SSD type
    • TempDb - ephemeral
    • Data disk - with Read caching enabled
    • Log files - without caching
    • No compression enabled on any of the SQL drives
  • Separate drive for the Operation System
  • Max memory set to 50% of the VM RAM size
  • Recovery model set to Simple
  • Min memory set to 25% of VM RAM size
  • Cost threshold for parallelism to 50
  • Max degree of parallelism to 2

Data Truncation and Archival Settings Recommendation

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

  

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

  

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

  

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