Skip to content

Architecture and Components

MSPControl is composed of independently hosted services that communicate through REST web services. The Portal provides the user interface, the Enterprise Server applies business logic, and Server components perform changes on managed infrastructure. Web components run as IIS applications on a supported Windows Server installation.

The Portal is the primary web interface. It sends user operations to the Enterprise Server rather than performing infrastructure changes directly. Its IIS application pool should use a limited-permission identity.

The Enterprise Server is the business-logic layer. It stores platform data in SQL Server, exposes operations through REST services, and forwards infrastructure work to Server components. External access should be restricted unless an integration specifically requires it.

A Server component is installed on each managed Windows server. It performs privileged operations such as configuring IIS, permissions, databases, mail services, and other hosted resources. Its application pool requires the permissions needed for those operations.

The Scheduler is a Windows service that executes background work such as usage calculations, reporting, maintenance, and configured scheduled tasks.

The optional End-User Portal provides self-service capabilities such as profile maintenance, cloud-folder access, and password reset for configured users.

The Windows Agent is installed on managed Windows servers or endpoints. It connects devices to MSPControl for monitoring, patching, firewall configuration, and other supported management operations.

  • Restrict public access to backend Enterprise Server and Server endpoints.
  • Use the least-privileged application-pool identity compatible with each component.
  • Protect and back up the SQL Server databases.
  • Monitor the Scheduler service and task results.