System requirements for System Center Orchestrator
Important
Service Provider Foundation (SPF) is discontinued from System Center 2025. However, SPF 2022 will continue to work with System Center 2025 components.
This article details the system requirements for System Center 2025 - Orchestrator.
System requirements for System Center 2025 - Orchestrator
The following sections provide general performance and scalability guidance for System Center 2025 - Orchestrator and state the recommended hardware configurations for various workloads. As System Center 2025 is built to be flexible and scalable, the hardware requirements for specific scenarios may differ from the guidelines that are presented here.
Hardware
| Orchestrator Server Role | x64 Processor (min) | Memory (min) | Disk space (min) |
|---|---|---|---|
| All server roles | 2.1 GHz, dual-core CPU | 2 GB | 200 MB |
Server operating system
The following versions of Windows Server operating system are supported.
| Component | Windows Server 2022 Standard, Datacenter with Desktop Experience | Windows Server 2025 Standard, Datacenter with Desktop Experience |
|---|---|---|
| All server roles | Supported | Supported |
Client operating system
The following versions of Windows client operating system are supported for the Orchestrator.
| Component | Windows Server 2022 Standard, Datacenter with Desktop Experience | Windows Server 2025 Standard, Datacenter with Desktop Experience |
|---|---|---|
| Runbook Designer | Supported | Supported |
Running the Setup
Install the Microsoft Visual C++ Redistributable (>= 14.34) before running the Setup executable (SetupOrchestrator.exe).
Software
The following software is required for a full installation of Orchestrator on a single computer:
Microsoft SQL Server – Orchestrator requires only the basic SQL Server features found in the Database Engine Service. No additional features are required. Orchestrator supports SQL_Latin1_General_CP1_CI_AS for collation. The installation wizard uses SQL_Latin1_General_CP1_CI_AS as the default collation to create the orchestration database. For more information, see the section on SQL Server.
Note
Management servers and runbook servers installed on the same computer must use the same database.
Microsoft Internet Information Services (IIS) – Orchestrator Setup enables IIS if it isn't enabled.
Microsoft .NET Framework 4.5 or later.
Ensure that Microsoft OLE DB Driver for SQL Server v19 is installed on machines that host the Management Server, Runbook Service, Runbook Designer, or the Web API Service.
Join the computer to an Active Directory domain.
SQL Server
Note
- For the supported versions of SQL, use the service packs/cumulative updates that are currently supported by Microsoft.
- SQL Always ON is supported, except in cases where configuration is done on multi subnets.
| SQL version | Supported |
|---|---|
| SQL Server 2022 | Y |
| SQL Server 2019 | Y |
| SQL Server 2017 | Y |
Note
When you deploy Orchestrator in an Always ON scenario, the Database Availability wizard prompts for the database encryption key password. For information on how to retrieve the password, see database migration.
.NET requirements
Orchestrator requires .NET Framework 4.5 or later to run; we recommend installing .NET Framework 4.7.2.
Orchestrator Web API requires the following versions of .NET Core and Hosting Bundles:
| SCO version | .NET Core |
|---|---|
| 2025 RTM | .NET Core 8 Hosting Bundle |
Virtualization
Deploying and running Orchestrator on a virtualized operating system is fully supported. The software requirements are the same as those listed above. Any of the Orchestrator roles can also be run on a virtualized server running in Microsoft Azure.
This article details the system requirements for System Center 2022 - Orchestrator.
System requirements for System Center 2022 - Orchestrator
The following sections provide general performance and scalability guidance for System Center 2022 - Orchestrator and state the recommended hardware configurations for various workloads. As System Center 2022 is built to be flexible and scalable, the hardware requirements for specific scenarios may differ from the guidelines that are presented here.
Hardware
| Orchestrator Server Role | x64 Processor (min) | Memory (min) | Disk space (min) |
|---|---|---|---|
| All server roles | 2.1 GHz, dual-core CPU | 2 GB | 200 MB |
Server operating system
The following versions of Windows Server operating system are supported.
| Component | Windows Server 2019 Standard, Datacenter with Desktop Experience | Windows Server 2022 Standard, Datacenter with Desktop Experience |
|---|---|---|
| All server roles | Supported | Supported |
Client operating system
The following versions of Windows client operating system are supported for the Orchestrator.
| Component | Windows Server 2019 Standard, Datacenter with Desktop Experience | Windows Server 2022 Standard, Datacenter with Desktop Experience |
|---|---|---|
| Runbook Designer | supported | Supported |
Running the Setup
Install the Microsoft Visual C++ Redistributable before running the Setup executable (SetupOrchestrator.exe).
Software
The following software is required for a full installation of Orchestrator on a single computer:
Microsoft SQL Server 2019 – Orchestrator requires only the basic SQL Server features found in the Database Engine Service. No additional features are required. Orchestrator supports SQL_Latin1_General_CP1_CI_AS for collation. The installation wizard uses SQL_Latin1_General_CP1_CI_AS as the default collation to create the orchestration database. For more information, see the section on SQL Server.
Note
Management servers and runbook servers installed on the same computer must use the same database.
Microsoft Internet Information Services (IIS) – Orchestrator Setup enables IIS if it isn't enabled.
Microsoft .NET Framework 4.5 or later.
Ensure that Microsoft OLE DB Driver for SQL Server v18 is installed on machines that host the Management Server, Runbook Service, Runbook Designer, or the Web API Service.
Join the computer to an Active Directory domain.
SQL Server
Note
- For the supported versions of SQL, use the service packs/cumulative updates that are currently in support by Microsoft.
- SQL Always ON is supported, except in cases where configuration is done on multi subnets.
| SQL version | Supported |
|---|---|
| SQL Server 2022 | Y |
| SQL Server 2019 | Y |
| SQL Server 2017 | Y |
Note
When you deploy Orchestrator in an Always ON scenario, the Database Availability wizard prompts for the database encryption key password. For information on how to retrieve the password, see database migration.
.NET requirements
Orchestrator requires .NET Framework 4.5 or later to run; we recommend installing .NET Framework 4.7.2.
Orchestrator Web API requires the following versions of .NET Core and Hosting Bundles:
| SCO version | .NET Core |
|---|---|
| 2022 RTM | .NET Core 5 Hosting Bundle |
| 2022 UR1, UR2 | .NET Core 6 Hosting Bundle |
Virtualization
Deploying and running Orchestrator on a virtualized operating system is fully supported. The software requirements are the same as those listed above. Any of the Orchestrator roles can also be run on a virtualized server running in Microsoft Azure.
This article details the system requirements for System Center 2019 - Orchestrator.
System requirements for System Center 2019 - Orchestrator
The following sections provide general performance and scalability guidance for System Center 2019 - Orchestrator and state the recommended hardware configurations for various workloads. As System Center 2019 is built to be flexible and scalable, the hardware requirements for specific scenarios may differ from the guidelines that are presented here.
Hardware
| Orchestrator Server Role | x64 Processor (min) | Memory (min) | Disk space (min) |
|---|---|---|---|
| All server roles | 2.1 GHz, dual-core CPU | 2 GB | 200 MB |
Server operating system
The following versions of Windows Server operating system are supported.
| Component | Windows Server 2016 Standard, Datacenter with Desktop Experience | Windows Server 2019 Standard, Datacenter with Desktop Experience |
|---|---|---|
| All server roles | Supported | Supported |
Client operating system
The following versions of Windows client operating system are supported for the Orchestrator.
| Component | Windows Server 2016 Standard, Datacenter with Desktop Experience | Windows Server 2019 Standard, Datacenter with Desktop Experience | Windows 10 |
|---|---|---|---|
| Runbook Designer | Supported | Supported | Supported |
Software
The following software is required for a full installation of Orchestrator on a single computer:
Microsoft SQL Server 2016 or 2017– Orchestrator requires only the basic SQL Server features found in the Database Engine Service. No additional features are required. Orchestrator supports SQL_Latin1_General_CP1_CI_AS for collation. The installation wizard uses SQL_Latin1_General_CP1_CI_AS as the default collation to create the orchestration database. For more information, see the section on SQL Server.
Note
Management servers and runbook servers installed on the same computer must use the same database. The management server must run as a 32-bit application.
Microsoft Internet Information Services (IIS) – Orchestrator Setup enables IIS if it isn't enabled.
Microsoft .NET Framework 3.5 Service Pack 1 - Orchestrator Setup installs and enables .NET Framework 3.5 SP1 if it isn't installed and enabled.
Microsoft .NET Framework 4
Microsoft SQL Server 2012 Native Client - QFE (applies to SQL 2012/2014/2016).
We recommend the following software for a full installation of Orchestrator on a single computer:
Join the computer to an Active Directory domain.
Note
On the first use of the Orchestration console, you're prompted to install Microsoft Silverlight on the computer if it isn't already installed. Install Silverlight 5.0.
Tip
New version of the Web API and Orchestration Console have been released that doesn't depend on Silverlight. Follow instructions in the announcement blog post to download and install them.
SQL Server
Note
- For the supported versions of SQL, use the service packs/cumulative updates that are currently in support by Microsoft.
- SQL Always ON is supported, except in the cases where configuration is done on multi subnets.
| SQL version | Supported |
|---|---|
| SQL Server 2019 | Y |
| SQL Server 2017 | Y |
| SQL Server 2016 and SPs as detailed here | Y |
Note
When you deploy Orchestrator in an Always ON scenario, the Database Availability wizard prompts for the database encryption key password. For information on how to retrieve the password, see database migration.
.NET requirements
All Orchestrator server roles require .NET 3.5 SP1 in order to run the setup program. The Orchestrator Web Service requires .NET 4.5 with WCF Activation.
You can download .NET 3.5 SP1 from the download center.
To turn on WCF activation
- On the Windows Start screen, select the Server Manager tile.
- On the Manage menu in the Server Manager console, select Add Roles and Features.
- Go through the wizard until you reach the Features page.
- Expand .NET Framework 4.5 Features.
- Select .NET Framework 4.5 if it isn’t already selected.
- Expand WCF Services.
- Select HTTP Activation, if it isn’t already selected.
- Select Next and follow the prompts to finish the installation. If you have problems, check the issues covered in Troubleshoot Your Orchestrator Installation.
Virtualization
Deploying and running Orchestrator on a virtualized operating system is fully supported. The software requirements are the same as those listed above. Any of the Orchestrator roles can also be run on a virtualized server running in Microsoft Azure.
This article details the system requirements for System Center 2016 - Orchestrator.
System requirements for System Center 2016 - Orchestrator
The following sections describe general performance and scalability guidance for System Center 2016 - Orchestrator and state the recommended hardware configurations for various workloads. As System Center 2016 is built to be flexible and scalable, the actual hardware requirements for specific scenarios may differ from the guidelines that are presented here.
Hardware
| Orchestrator Server Role | x64 Processor (min) | Memory (min) | Disk space (min) |
|---|---|---|---|
| All server roles | 2.1 GHz, dual-core CPU | 2 GB | 200 MB |
Server operating system
The following versions of Windows Server operating system are supported.
| Component | Windows Server 2012 R2 Standard, Datacenter | Windows Server 2016 Standard, Datacenter with Desktop Experience | Windows Server Core 2016 |
|---|---|---|---|
| All server roles | Supported | Supported | Not Supported |
Client operating system
The following versions of Windows client operating system are supported for the Orchestrator.
| Component | Windows 7 | Windows 8 | Windows 8.1 | Windows 10 Enterprise |
|---|---|---|---|---|
| Runbook Designer | Not supported | Not Supported | Not Supported | Supported |
Software
The following software is required for a full installation of Orchestrator on a single computer:
Microsoft SQL Server 2012, 2014, or 2016 – Orchestrator requires only the basic SQL Server features found in the Database Engine Service. No additional features are required. Orchestrator supports SQL_Latin1_General_CP1_CI_AS for collation. The installation wizard uses SQL_Latin1_General_CP1_CI_AS as the default collation to create the orchestration database. For more information, see the section on SQL Server.
Note
Management servers and runbook servers installed on the same computer must use the same database. The management server must run as a 32-bit application.
Microsoft Internet Information Services (IIS) – Orchestrator Setup enables IIS if it isn't enabled.
Microsoft .NET Framework 3.5 Service Pack 1 - Orchestrator Setup installs and enables .NET Framework 3.5 SP1 if it isn't installed and enabled.
Microsoft .NET Framework 4
Microsoft SQL Server 2012 Native Client - QFE (applies to SQL 2012/2014/2016).
We recommend the following software for a full installation of Orchestrator on a single computer:
- Join the computer to an Active Directory domain.
Note
On the first use of the Orchestration console, you are prompted to install Microsoft Silverlight on the computer if it isn't already installed. Install Silverlight 5.0.
SQL Server
Note
- For the supported versions of SQL, use the service packs that are currently in support by Microsoft.
- SQL Always ON is supported, except in the cases where configuration is done on multi subnets.
| SQL version | Supported |
|---|---|
| SQL Server 2008 | N |
| SQL Server 2012 and SPs as detailed here | Y |
| SQL Server 2014 and SPs as detailed here | Y |
| SQL Server 2016 and SPs as detailed here | Y |
Note
When you deploy Orchestrator in an Always ON scenario, the Database Availability wizard prompts for the database encryption key password. For information on how to retrieve the password, see database migration.
.NET requirements
All Orchestrator server roles require .NET 3.5 SP1 in order to run the setup program. The Orchestrator Web Service requires .NET 4.5 with WCF Activation.
You can download .NET 3.5 SP1 at:
To turn on WCF activation
- On the Windows Start screen, select the Server Manager tile.
- On the Manage menu in the Server Manager console, select Add Roles and Features.
- Go through the wizard until you reach the Features page.
- Expand .NET Framework 4.5 Features.
- Select .NET Framework 4.5, if it isn’t already selected.
- Expand WCF Services.
- Select HTTP Activation, if it isn’t already selected.
- Select Next and follow the prompts to finish the installation. If you have problems, check the issues covered in Troubleshoot Your Orchestrator Installation.
Virtualization
Deploying and running Orchestrator on a virtualized operating system is fully supported. The software requirements are the same as those listed above. Any of the Orchestrator roles can also be run on a virtualized server running in Microsoft Azure.