Prerequisites
Overview
Section titled “Overview”Prepare the Windows Server before running the MSPControl installer. MSPControl 3.1 requires IIS, ASP.NET Core Hosting Bundle 10.0.0 or later, .NET Framework, URL Rewrite, a Visual C++ runtime, and a compatible SQL Server configuration.
Prepare the server automatically
Section titled “Prepare the server automatically”The guided setup asks before making changes and shows the exact planned actions. It can install the required IIS role services, .NET Framework 4.8, ASP.NET Core Hosting Bundle 10, Visual C++ 2015–2022 x64, URL Rewrite, and an optional local SQL Server 2025 Express instance. It can also validate an existing SQL Server.
- Download and extract
MSPControl-Prerequisite-Setup.zip. Keep all four files together in the extracted folder. - Run
Start-MSPControl-Prerequisites.cmd. Approve elevation when Windows asks. - Review the server analysis and SQL choice. The setup detects already satisfied requirements and skips them.
- Confirm the planned actions. Existing IIS sites can be interrupted if IIS must restart, so use a maintenance window on a shared server.
- Restart and rerun when requested. The setup resumes safely by rechecking the server and installing only missing items.
- Keep the generated log and JSON result. They are stored in the extracted folder under
work\logsandwork\results.
Release 1.0.0 was validated on a clean Windows Server 2019 Standard lab server. The signed MSPControl installer then reported every prerequisite as satisfied. Continue to use a snapshot or current backup when testing on other Windows Server versions or an existing shared server.
Before you begin
Section titled “Before you begin”- Use an x64 edition of Windows Server 2016, 2019, 2022, or 2025. All Windows Server editions are supported.
- Sign in with an account that can add Windows roles and install software.
- Confirm which MSPControl release you will install.
- You can install MSPControl on a new server or on an existing server that meets the requirements below.
- Back up any existing IIS and SQL Server configuration before changing a shared server.
Supported prerequisite matrix
Section titled “Supported prerequisite matrix”| Component | Requirement | Notes |
|---|---|---|
| Operating system | Windows Server 2016, 2019, 2022, or 2025; any edition; x64 | A dedicated server is not required. |
| Web server | Web Server (IIS) with .NET Extensibility, ASP.NET, ISAPI Extensions, and ISAPI Filters | Install IIS before the ASP.NET Core Hosting Bundle. |
| ASP.NET Core Hosting Bundle | 10.0.0 or later | Enforced by the MSPControl 3.1 installer. |
| .NET Framework | 4.8 or later | Required by the approved prerequisite guidance. |
| URL Rewrite | URL Rewrite Module 2.0 for IIS | Restart IIS after installation. |
| Visual C++ Redistributable | Microsoft Visual C++ 2015–2022 x64, major version 14 or later | The x86 package is not required for the supported x64 server deployment. |
| SQL Server | SQL Server 2016 SP2 or later; any edition, including Express | Apply current service packs and security/cumulative updates. For SQL Server 2022, install Cumulative Update 17 or later. |
| SQL configuration | Database Engine Services; case-insensitive server collation; Mixed Mode authentication; TCP/IP enabled | SQL_Latin1_General_CP1_CI_AS or an equivalent case-insensitive collation is accepted. Full-Text and Semantic Extractions for Search is optional but recommended. |
| Administrator access | Local administrator permissions during installation | The installer checks for administrator membership. |
| CPU, RAM, and disk | No fixed minimum is published | Size the server for Windows Server, SQL Server, the selected MSPControl components, data volume, and expected workload. |
Official downloads
Section titled “Official downloads”Use only the official Microsoft download pages below. IIS itself is a Windows Server role, so enable it through Server Manager > Add Roles and Features rather than downloading a separate IIS installer.
Prepare the server
Section titled “Prepare the server”- Install IIS and its application-development features. Enable .NET Extensibility, ASP.NET, ISAPI Extensions, and ISAPI Filters. Do not install Application Initialization.
- Install ASP.NET Core Hosting Bundle 10.0.0 or later. Install IIS first. Under ASP.NET Core Runtime, choose the Windows Hosting Bundle. If the Hosting Bundle was installed before IIS, repair the Hosting Bundle after enabling IIS.
- Install .NET Framework 4.8 or later and the Visual C++ 2015–2022 x64 runtime. Complete any restart requested by the prerequisite installers.
- Install URL Rewrite. MSPControl requires URL Rewrite Module 2.0; choose Microsoft’s current English x64 installer, which is currently version 2.1. Restart IIS after installation.
- Prepare SQL Server 2016 SP2 or later. Any edition, including SQL Server 2025 Express, is permitted. Apply current service packs and security/cumulative updates. Enable Mixed Mode authentication and TCP/IP, use a case-insensitive server collation, and ensure the installation account has sufficient rights. Apply CU17 or later when using SQL Server 2022.
- Run the MSPControl prerequisite check. Resolve every failed item before continuing with installation.
Verify the result
Section titled “Verify the result”Open the MSPControl installer and confirm that every prerequisite check required for your selected installation type passes.
Network bindings
Section titled “Network bindings”MSPControl component ports are configurable for each installation. The default ports are:
| Component | Default port |
|---|---|
| Portal | 9010 |
| Enterprise Server | 9003 |
| Server | 9002 |
Configure IIS bindings and firewall rules for the ports actually selected in your environment; the defaults are not mandatory universal firewall values. MSPControl supports proxy use.
The web components can use HTTP or HTTPS IIS bindings. A certificate is optional to MSPControl when HTTP is used and is required when you select an HTTPS binding. Use HTTPS whenever traffic crosses an untrusted network.
SQL Server uses the configured SQL Server host, instance, and port. Do not assume TCP 1433 when a named instance or dynamic port is used. Optional integrations can require additional vendor or customer endpoints and are not core MSPControl network requirements.